CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

q-and-a-prep-partner

Predict challenging questions for presentations and prepare structured responses.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/q-and-a-prep-partner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%Weight 40%Scale 1-5

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

The executable core is solid — real commands, accurate parameter documentation matching the script, a working validation check, and a clearly signaled one-level-deep reference — but it is buried in roughly 100 lines of generic audit-template boilerplate and self-referential filler that add no operational value. The net effect is a skill that works but pays a heavy token cost for what it delivers.

Suggestions

Delete the template-filler sections (Risk Assessment, Security Checklist, Evaluation Criteria/Test Cases, Lifecycle Status) and the self-referential pointer sections (Dependencies, Example Usage intro, Implementation Details) — they carry no Q&A-prep-specific information and account for most of the verbosity.

Consolidate the three overlapping process descriptions (Example Usage run plan, ## Workflow, Implementation Details) into one sequenced workflow that embeds the py_compile validation checkpoint and the fallback path inline.

Document what `scripts/main.py` actually outputs (format and output location) so the 'Output' section's three vague bullets become concrete, reviewable deliverables.

DimensionReasoningScore

Conciseness

The ~200-line body is noticeably verbose with many padded, zero-information boilerplate sections: "Scope-focused workflow aligned to: ...", "Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable", self-referential placeholders ("See `## Prerequisites` above for related details", "See `## Usage` above", "See `## Workflow` above"), and generic audit-template filler (Risk Assessment table, Security Checklist, Evaluation Criteria, Test Cases, Lifecycle Status with a review date of 2026-03-06). This matches 'Noticeably verbose; several unnecessary explanations or padded sections'; not score 1 because it never explains concepts Claude already knows (no 'what is a PDF' style padding) — the padding is boilerplate, not concept tuition.

2 / 5

Actionability

The Usage section gives copy-paste-ready commands ("python scripts/main.py --abstract abstract.txt --field oncology", "python scripts/main.py --topic \"CRISPR therapy\" --audience experts") that were verified against the script's actual argparse interface (--abstract, --topic, --field, --audience, --n-questions all match), plus executable validation commands ("python -m py_compile scripts/main.py"). This fits 'Mostly executable guidance; concrete code or commands with minor gaps' — not score 5 because key details such as what the script outputs and where it writes are unspecified, and much of the surrounding guidance is abstract.

4 / 5

Workflow Clarity

A sequence exists (Example Usage run plan, the 5-step "## Workflow", Quick Check, Audit-Ready Commands) with an explicit validation checkpoint ("python -m py_compile scripts/main.py" as 'Quick Check') and a fallback path on failure, which goes beyond the score-3 anchor's implicit checkpoints. However, the same process is described redundantly across three overlapping sections with generic, non-operational steps ("Confirm the user objective", "Validate that the request matches the documented scope"), fitting 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit' — the duplication and vagueness obscure the actual operational sequence, keeping it below score 4's 'clear sequence'.

3 / 5

Progressive Disclosure

Scored against the actual bundle (SKILL.md + references/audit-reference.md + scripts/main.py): the single reference is clearly signaled in a dedicated "## References" section with a one-line description, exists at exactly one level deep, and the script path is documented throughout. Content split is appropriate for a two-file bundle, matching 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps' — the gaps (duplicated self-referential sections) slightly exceed 'minor', keeping it below score 5.

4 / 5

Total

13

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 states a clear, moderately specific 'what' in third person with two concrete actions, but it entirely lacks a 'Use when...' trigger clause and omits the natural terms (especially 'Q&A') users would most likely say. It is serviceable but sits squarely at the midpoint of the rubric.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user is preparing for a talk, defense, or presentation and wants to anticipate Q&A / tough audience questions.'

Add natural synonyms users would actually say — 'Q&A', 'tough questions', 'audience questions', 'defense', 'rehearsal' — to improve trigger-term coverage.

Optionally name one more concrete capability (e.g. categorizing questions by methodology, statistics, or limitations) to lift specificity from two actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Predict challenging questions for presentations and prepare structured responses" names the domain (presentations) and exactly two concrete actions — predicting questions and preparing responses — matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is not score 4 because only two actions are listed, not 'several specific actions' with minor gaps (no mention of question categorization, response framing, or audience tailoring in the description itself).

3 / 5

Completeness

The 'what' is clear (predict challenging questions, prepare structured responses) but there is no 'Use when...' clause or any equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not score 2 because the 'what' half is concrete rather than vague; not score 4 because no 'when' is present even weakly.

3 / 5

Trigger Term Quality

Relevant keywords like "challenging questions", "presentations", and "structured responses" are present, but the most natural phrases users would say — "Q&A", "tough questions", "audience questions", "talk", "defense" — are missing, fitting the anchor 'Some relevant keywords but missing common variations or synonyms'. Not score 4 because the missing natural-term set is substantial, not just 'a few'.

3 / 5

Distinctiveness Conflict Risk

The Q&A-anticipation niche ("Predict challenging questions for presentations") is mostly distinct with only minor overlap risk against closely related presentation-preparation or academic-writing skills. Not score 5 because "prepare structured responses" is generic and could pull in general writing-assistance requests; not score 3 because the question-prediction focus is more specific than the 'could still overlap with similar skills' anchor.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/q-and-a-prep-partner/SKILL.md

Reviewed

Table of Contents

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.