CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

expert-interview-topics

Generates professional interview titles and questions based on expert background and topic. Provides a structured workflow for interview preparation.

Quality

57%

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/Other/expert-interview-topics/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 skill body delivers a genuinely executable core — a documented CLI matching the real script and a clearly chained three-prompt workflow — but wraps it in ~80 lines of generic templated boilerplate, duplicated sections, and fabricated validation/output expectations that contradict the script's actual behavior. The useful content is accurate; the packaging around it is not.

Suggestions

Delete the templated filler sections ("Key Features", "Dependencies", "Output Contract", "Recommended Workflow", "Deterministic Output Rules", "Completion Checklist", and similar generic process rules) and merge the duplicated Usage/Validation sections into one of each.

Fix the fabricated "Quick Validation" expected output and the "expert_interview_topics_result.md" claim to match the script's actual stdout-only, three-prompt output.

Correct the broken "See `## Usage` above" reference (the Usage section appears after it) by restructuring into a single ordered document: What it does → Command → Output → Example → When not to use.

DimensionReasoningScore

Conciseness

Roughly half of the ~160-line body is templated boilerplate that adds nothing skill-specific — "Use this skill when the request matches its documented task boundary", "Key Features", "Dependencies", "Output Contract", "Recommended Workflow", "Failure Handling", "Deterministic Output Rules", "Completion Checklist" — all of which restate process discipline Claude already applies. There is also a broken self-reference: "See `## Usage` above for related details" (line 28) points to a section defined later in the document (line 64). This matches anchor 2 (noticeably verbose, several padded sections); it is worse than 3 because the filler is pervasive rather than occasional.

2 / 5

Actionability

The core guidance is concrete and executable — `python scripts/main.py --topic "<topic>" --background "<expert_background>" [--file "<path>"]` with documented arguments, a runnable example, and an accurate description of the three output prompts and their placeholders. However, "Quick Validation" fabricates an expected `--help` output ("Result file: expert_interview_topics_result.md / Validation summary: PASS/FAIL / Assumptions") that argparse never produces, and the "Output Contract" recommends a deterministic result file the prompt-only script never writes — internal contradictions a reader cannot execute against. Fits anchor 3 (concrete guidance but incomplete/with key inaccuracies); not 4 because the fabricated validation output materially misleads.

3 / 5

Workflow Clarity

The real workflow is explicitly sequenced: the script emits Step 1 (title generation prompt, ready to use), Step 2 (selection prompt with a `{generated_titles}` placeholder to fill from Step 1), and Step 3 (question prompt with `{selected_title}` from Step 2), and the doc explains the chaining and the optional transcript file. Pre-run checks (`python -m py_compile`, `--help`, `validate_skill.py`) are present. Fits anchor 4 (clear sequence, most checkpoints present, minor validation gaps); not 5 because there are no error-recovery feedback loops and the validation steps are superficial.

4 / 5

Progressive Disclosure

Bundle references are real and accurate (`scripts/main.py`, `scripts/validate_skill.py` both exist and match the documented interface), and the bulky prompt templates correctly live in the script rather than inlined in SKILL.md. But the document itself is poorly organized: duplicated sections ("## Usage" vs "## Example Usage", "## Validation Shortcut" vs "## Quick Validation"), two competing top-level narratives, and the broken "See `## Usage` above" cross-reference. Fits anchor 3 (some structure but could be better organized); not 4 because the duplication and broken navigation are more than minor gaps.

3 / 5

Total

12

/

20

Passed

Description

50%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 "what" with two concrete actions in a distinct niche, but has no "when to use" trigger guidance and only partial natural keyword coverage, and it risks conflicting with generic job-interview-prep requests. It sits squarely at the midpoint of the scale.

Suggestions

Append an explicit trigger clause, e.g. "Use when preparing an expert, podcast, or media interview and the user needs interview titles or interview questions."

Add natural synonyms users would say ("expert interview", "podcast interview", "media interview", "interview prep") to broaden trigger coverage.

Disambiguate from job-interview preparation by anchoring on the expert-interview context (e.g., "interviewing a subject-matter expert for an article, podcast, or event").

DimensionReasoningScore

Specificity

"Generates professional interview titles and questions based on expert background and topic" names the domain plus two concrete actions (title generation, question generation), but the second sentence "Provides a structured workflow for interview preparation" is generic filler. This matches anchor 3 (names domain and 1-2 concrete actions, not comprehensive); it falls short of 4 because no further specific actions or capabilities are enumerated.

3 / 5

Completeness

The "what" is clearly stated ("Generates professional interview titles and questions") but there is no "when" — no "Use when..." clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines a missing "Use when..." clause caps completeness at 3, which also matches anchor 3 (clear what, when missing).

3 / 5

Trigger Term Quality

Natural terms like "interview titles", "interview questions", "expert background", and "interview preparation" are present, but common variations users would actually say ("expert interview", "podcast interview", "media interview", "interview prep") are missing. Fits anchor 3 (some relevant keywords but missing common variations or synonyms) rather than 4 because keyword coverage is partial.

3 / 5

Distinctiveness Conflict Risk

"expert background and topic" signals an expert/media-interview niche, but the bare word "interview" is ambiguous — a user preparing for a job interview would plausibly trigger this skill incorrectly. Fits anchor 3 (somewhat specific but could still overlap with similar skills); not 4 because the conflict with job-interview-preparation requests is a realistic overlap, not a minor one.

3 / 5

Total

12

/

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/Other/expert-interview-topics/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.