q-and-a-prep-partner

Predict challenging questions for presentations and prepare structured responses.

Quality

33%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./scientific-skills/Academic Writing/q-and-a-prep-partner/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description conveys a reasonable concept—preparing for tough presentation questions—but is too brief and lacks explicit trigger guidance ('Use when...') to help Claude reliably select it. It would benefit from more specific actions, natural trigger terms, and a clear 'when to use' clause.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for help preparing for Q&A sessions, anticipating audience objections, or rehearsing presentation defenses.'

Include more natural trigger terms users would say, such as 'Q&A prep', 'tough questions', 'audience objections', 'presentation defense', 'devil's advocate'.

Expand the capability list with concrete actions, e.g., 'Identifies likely objections, generates devil's advocate questions, and drafts concise talking-point responses with supporting evidence.'

Dimension	Reasoning	Score
Specificity	It names a domain (presentations) and describes two actions (predict challenging questions, prepare structured responses), but lacks detail on what 'structured responses' entails or additional concrete capabilities.	2 / 3
Completeness	It describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'what' itself is also fairly thin, bringing it to 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'presentations', 'questions', and 'responses', but misses common natural variations users might say such as 'Q&A prep', 'audience questions', 'tough questions', 'presentation defense', or 'anticipate objections'.	2 / 3
Distinctiveness Conflict Risk	The focus on predicting challenging questions for presentations is somewhat specific, but 'presentations' could overlap with general presentation creation/editing skills, and 'structured responses' is generic enough to cause confusion.	2 / 3
	Total	7 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is heavily padded with generic boilerplate (risk assessment, security checklist, lifecycle status, evaluation criteria) that consumes significant tokens without adding value for the core task. The actual domain-specific content—how to predict challenging presentation questions and craft structured responses—is minimal and superficial. The skill reads more like a project management template than actionable guidance for Q&A preparation.

Suggestions

Remove all generic boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Response Template) that don't provide Q&A-specific guidance, and eliminate circular cross-references between sections.

Add concrete examples of generated questions and response frameworks for at least one scenario (e.g., given an abstract about CRISPR therapy, show 2-3 predicted questions with structured responses).

Provide specific guidance on what makes a challenging question for each question type (methodology, statistical, etc.) rather than just listing the categories.

Consolidate the duplicated workflow/usage/example sections into a single clear workflow with specific validation steps for question quality.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and repetitive. Contains extensive boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria) that add no value for Claude. Multiple sections reference each other circularly ('See ## Prerequisites above', 'See ## Usage above'). The core task—predicting Q&A questions—is buried under layers of generic project management scaffolding that Claude already knows how to do.	1 / 3
Actionability	Provides concrete CLI commands and parameters (--abstract, --topic, --field, --audience), which is useful. However, the actual skill content—how to predict challenging questions and structure responses—is barely addressed. The question types are listed but with no guidance on how to generate them or what makes a good response framework. The actionable parts are mostly about running a script rather than performing the intellectual task.	2 / 3
Workflow Clarity	There is a numbered workflow and an example run plan with steps, plus error handling and fallback paths mentioned. However, the workflow steps are generic ('Confirm the user objective', 'Validate that the request matches') rather than specific to Q&A preparation. There are no validation checkpoints specific to the quality of generated questions or response frameworks.	2 / 3
Progressive Disclosure	References a separate file (references/audit-reference.md) and organizes content into sections. However, the main file is bloated with content that should either be removed or split out (Risk Assessment, Security Checklist, Lifecycle Status are all inline). The circular 'See ## X above' references are confusing and suggest poor organization.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: aipoch/medical-research-skills
Commit: 0b96148

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.