CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

biotech-pitch-deck-narrative

Use biotech-pitch-deck-narrative for academic writing workflows that need structured investor-facing storytelling, explicit assumptions, and clear output boundaries.

Quality

64%

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/biotech-pitch-deck-narrative/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 body delivers verified, executable commands and a well-sequenced workflow with explicit stop and fallback conditions, supported by a genuine one-level-deep reference structure. Its main weakness is bloat: triplicated command blocks, boilerplate governance sections, and broken or placeholder cross-references (Dependencies/Prerequisites, the dated cd path) inflate token cost without adding guidance.

Suggestions

Collapse the duplicated command blocks — 'Example Usage', 'Quick Check', and 'Audit-Ready Commands' all repeat the same py_compile/--help commands; keep one.

Move governance boilerplate (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria) into references/audit-reference.md and fix the broken 'See ## Prerequisites above' cross-reference and the nonexistent requirements.txt claim.

Replace the environment-specific 'cd "20260318/scientific-skills/..."' path with a relative path from the skill root so the example is truly self-contained as claimed.

DimensionReasoningScore

Conciseness

The ~190-line body is noticeably padded: 'Key Features' restates the description verbatim, the same py_compile/--help commands appear three times across 'Example Usage', 'Quick Check', and 'Audit-Ready Commands', and governance boilerplate (Risk Assessment, Security Checklist, Lifecycle Status with a time-sensitive 'Next Review Date: 2026-03-20') adds little actionable value. The 'Dependencies' section even declares stdlib modules against a nonexistent requirements.txt. It is not 1 because it never explains basic concepts Claude already knows.

2 / 5

Actionability

Commands are concrete and verified executable (py_compile, --help, and '--stage series-a --audience biotech-specialist' match the actual argparse in scripts/main.py), and the Parameters table matches the script. It is not 5 because the Example Usage block's 'cd "20260318/scientific-skills/Academic Writing/biotech-pitch-deck-narrative"' is an environment-specific path that breaks copy-paste readiness and contradicts the claim that commands 'avoid placeholder paths'.

4 / 5

Workflow Clarity

The 5-step Workflow is clearly sequenced with a stop condition ('If scientific support or market context is missing, stop and request the minimum additional inputs') and the Error Handling section defines failure points and a manual fallback. It is not 5 because there is no explicit validate-output-then-proceed feedback loop on the deliverable itself.

4 / 5

Progressive Disclosure

The bundle structure is sound: references/audit-reference.md exists, is one level deep, and is clearly signaled with a linked description, and scripts/main.py is the primary implementation surface. It is not 5 because ~190 lines of governance content (risk, security, lifecycle, evaluation criteria) are inlined in SKILL.md that belong in the reference file, and the 'See "## Prerequisites" above' cross-reference points to a section that appears later in the document.

4 / 5

Total

14

/

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 follows a 'Use when...' template and states both what and when, but its capability language is abstract and its 'academic writing workflows' framing mischaracterizes a fundraising-narrative skill and creates conflict risk with actual academic-writing skills. Natural trigger terms a user would say (fundraising, investor pitch, deck rewrite) are largely absent.

Suggestions

Replace abstract attribute nouns with concrete actions, e.g. 'Builds and rewrites biotech pitch deck narratives for fundraising, separating assumptions, evidence status, and diligence gaps.'

Add natural trigger phrases users would actually say: 'fundraising', 'investor pitch', 'deck rewrite', 'pitch deck section', not just 'investor-facing storytelling'.

Drop the 'academic writing workflows' framing — it mischaracterizes the skill's purpose and causes overlap with genuine academic-writing skills.

DimensionReasoningScore

Specificity

The description names the domain ("structured investor-facing storytelling") but the listed capabilities are abstract attributes ("explicit assumptions, and clear output boundaries") with no concrete action verbs like builds, rewrites, or generates, matching the anchor 'Names the domain but actions are minimal or generic'. It does not reach 3 because no 1-2 concrete actions are stated.

2 / 5

Completeness

Both elements are explicit: the 'what' is 'structured investor-facing storytelling, explicit assumptions, and clear output boundaries' and the 'when' is the trigger clause 'for academic writing workflows that need...'. It is not 5 because the when-clause is generic and mischaracterizes the skill as academic writing rather than giving concrete trigger phrases.

4 / 5

Trigger Term Quality

Relevant keywords are present ("biotech", "pitch deck", "investor-facing", "storytelling") but common natural phrases users would say — "fundraising", "investor pitch", "deck rewrite", "narrative" — are missing, fitting 'Some relevant keywords but missing common variations or synonyms'. It is above 2 because more than one or two generic keywords exist.

3 / 5

Distinctiveness Conflict Risk

The biotech investor-narrative niche is fairly distinct, but the 'academic writing workflows' framing invites overlap with genuine academic-writing skills, fitting 'Somewhat specific but could still overlap with similar skills'. Not 4 because the framing actively raises conflict risk rather than presenting a minor overlap.

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/Academic Writing/biotech-pitch-deck-narrative/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.