CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

expert-interview-generator

Generates a full expert interview article including introduction, Q&A body, and summary based on interview questions and expert background. Use when you have interview questions and an expert profile and need a polished article.

Quality

73%

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-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 core five-step workflow is genuinely well designed — named prompts with exact inputs, a draft/no-draft branch, length constraints, and a clear assembly order — and the bundle structure uses references appropriately. However, about half the document is generic template filler, and the executable/verification claims (the --help output, the validation summary format) do not match the actual script, which undermines both conciseness and actionability.

Suggestions

Delete or collapse the template sections (When to Use, Key Features, Dependencies, Implementation Details, Required Inputs, Output Contract, Validation and Safety Rules, Failure Handling) down to the few lines that carry skill-specific information.

Fix the verification path to match reality: either give scripts/flow.py a real CLI (--help, argument parsing) or replace the fabricated 'expected output format' with what the script actually produces, and use a path relative to the skill root instead of '20260316/scientific-skills/...'.

Add a genuine post-generation checkpoint, e.g. verify the Q&A body is ~2000 words and follows the 'Question: ...? / Expert Name: ...' format before final assembly.

DimensionReasoningScore

Conciseness

Roughly half the body is templated boilerplate that adds no skill-specific information: 'Use this skill when the request matches its documented task boundary', the Key Features section repeating the frontmatter description verbatim, 'See ## Workflow above for related details', and generic Required Inputs / Output Contract / Validation and Safety Rules / Failure Handling sections that could apply to any skill. This matches 'noticeably verbose; several unnecessary explanations or padded sections'; the one specific thing (the five-step workflow) is efficient, so it is not a 1.

2 / 5

Actionability

The workflow steps are concrete — each names a specific prompt in references/prompts.md (verified to exist) with exact inputs and constraints ('approximately 2000 words', '150-word introduction') — but executable claims are broken: the Example Usage hard-codes an environment-specific path ('cd "20260316/scientific-skills/..."'), and scripts/flow.py has no CLI, so 'python scripts/flow.py --help' will not produce the claimed 'Result file / Validation summary / Assumptions' output. This is 'some concrete guidance but incomplete / missing key details'; not a 2 because the core generative steps are fully specified.

3 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with per-step inputs, an explicit branch ('Path A (With Draft)' vs 'Path B (No Draft)' based on text1), word-count constraints, and a numbered final assembly structure. Not a 5: validation checkpoints are weak — the Quick Validation section's expected output does not match what flow.py actually does, and there is no check that the 2000-word/Q&A-format constraints were met; not a 3 because the sequence itself is coherent and a pre-run verification step is at least attempted.

4 / 5

Progressive Disclosure

The detailed prompts are correctly split into references/prompts.md (one level deep, real file) and each workflow step signals exactly which named prompt to use ('the Expert Introduction Prompt in references/prompts.md'), with scripts/flow.py for text assembly. Not a 5: the SKILL.md overview is cluttered by the boilerplate sections and contains the awkward self-reference 'See ## Workflow above for related details'; not a 3 because references are clearly signaled and appropriately placed.

4 / 5

Total

13

/

20

Passed

Description

83%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.

A strong description that clearly states the deliverable (expert interview article with intro, Q&A body, summary), its inputs, and an explicit 'Use when' trigger clause in third person. Keyword coverage and section coverage have minor gaps (no 'Q&A'/'transcript' synonyms; preface/profile sections unstated).

Suggestions

Add natural synonym triggers such as 'Q&A', 'interview transcript', or 'write up an interview' to broaden natural-language matching.

Mention the preface and expert-profile sections so the stated output coverage matches the full article structure the skill produces.

DimensionReasoningScore

Specificity

The description lists several concrete actions and outputs — 'Generates a full expert interview article including introduction, Q&A body, and summary based on interview questions and expert background' — naming the deliverable, its sections, and both input types. Not a 5: coverage has minor gaps (e.g., the expert profile/preface sections produced by the workflow are not all mentioned); not a 3: it goes well beyond naming a domain with 1-2 actions.

4 / 5

Completeness

It explicitly answers both: what — 'Generates a full expert interview article including introduction, Q&A body, and summary' — and when — 'Use when you have interview questions and an expert profile and need a polished article'. Both are concrete and explicit, matching the top anchor; a 4 would require the 'when' to be less specific than this.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present: 'interview questions', 'expert profile', 'expert background', 'polished article'. Not a 5: common variations like 'Q&A', 'interview transcript', or 'write up an interview' are missing; not a 3: the keywords go beyond a single generic term and cover both input and output vocabulary.

4 / 5

Distinctiveness Conflict Risk

'Expert interview article' with interview-question/expert-profile inputs is a fairly clear niche with distinct triggers. Not a 5: it could mildly overlap with general article-writing or interview-formatting skills since no file types or strongly unique markers distinguish it; not a 3: it is much more specific than 'works with document files' style overlap.

4 / 5

Total

17

/

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-generator/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.