CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

market-access-value

Use market access value for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries.

Quality

51%

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/market-access-value/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 body has a genuinely clear workflow with validation gates, error handling, and a well-signaled one-level-deep reference bundle, but it is wrapped in substantial template boilerplate and duplicated description text that wastes context. Actionability for the actual market-access task is thin — real commands exist only for compile/help checks, while the domain parameters and example are stubs. Trimming the boilerplate and replacing the stub sections with a worked example would raise both conciseness and actionability.

Suggestions

Cut the boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria, Output Requirements, Response Template) and the duplicated description text in 'When to Use' and 'Key Features' — they add tokens without task guidance.

Replace the bare 'Parameters' labels and the one-line 'Example' with a concrete worked example: a sample invocation of scripts/main.py with representative inputs and the expected output sections.

Remove the circular cross-references ('See `## Prerequisites` above', 'See `## Workflow` above') and the non-portable example cd path, merging the 'Example run plan' and 'Workflow' sections into a single step list.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the frontmatter description is restated verbatim in 'When to Use' and again in 'Key Features', and generic boilerplate sections (Risk Assessment table, Security Checklist, Lifecycle Status, Evaluation Criteria, Output Requirements, Response Template) plus circular cross-references ('See `## Prerequisites` above', 'See `## Workflow` above') add tokens without task value. This matches 'several unnecessary explanations or padded sections' at level 2; it is not level 1 because it never explains concepts Claude already knows, and not level 3 because the padding is pervasive rather than occasional.

2 / 5

Actionability

There is concrete executable guidance for verification ('python -m py_compile scripts/main.py', 'python scripts/main.py --help'), but core task guidance is incomplete: 'Parameters' entries are bare labels ('`drug_profile`: Efficacy/safety data'), the 'Example' is a single line ('ICER = $45,000/QALY with uncertainty analysis'), the run plan hedges ('if the script uses fixed settings'), and the example cd path is a non-portable local directory. This fits 'some concrete guidance but incomplete; missing key details' at level 3 rather than level 4, since the commands cover only compile/help checks and never show how to execute the actual task.

3 / 5

Workflow Clarity

The Workflow section gives a clear five-step sequence with validation checkpoints ('stop early if the task would require unsupported assumptions', fallback on execution failure), reinforced by explicit Error Handling and Input Validation gates and a compile-check step before deeper execution. It does not reach level 5 because two competing step lists (Example run plan vs Workflow) partially conflict and the checkpoints are generic rather than tied to concrete re-validation commands, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The bundle structure is sound: references/audit-reference.md exists, is one level deep, and is clearly linked under '## References'; scripts/main.py exists and is referenced consistently; sections are well-headered and navigable. Minor gaps keep it at level 4 rather than 5: roughly 190 lines with inline boilerplate (risk/security/lifecycle/evaluation criteria) that belongs in a reference file or should be removed, and only one reference file for a body of this size.

4 / 5

Total

13

/

20

Passed

Description

28%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 is a meta-process sentence about workflows needing structure and assumptions rather than a statement of what the skill does or when to use it. It names the domain but omits every concrete capability (ICER calculation, budget impact model, value dossier, payer objection handling) and every natural domain trigger term. A user asking for HTA or payer work would be unlikely to phrase their request in these terms.

Suggestions

State the concrete capabilities the body already documents, e.g. 'Develop payer value propositions: produce ICER calculation narratives, budget impact model text, value dossier sections, and payer objection handlers.'

Add an explicit 'Use when...' clause with natural trigger scenarios, e.g. 'Use when preparing HTA submissions, payer negotiations, pricing strategy, or reimbursement applications.'

Drop the generic process language ('structured execution, explicit assumptions, and clear output boundaries'), which applies to virtually any workflow skill and creates conflict risk with unrelated academic-writing skills.

DimensionReasoningScore

Specificity

The description names the domain ("market access value", "academic writing workflows") but its only 'actions' are generic process qualities — "structured execution, explicit assumptions, and clear output boundaries" — with no concrete capabilities. The actual deliverables the body lists (ICER narrative, budget impact model, value dossier) are absent, so it matches 'names the domain but actions are minimal or generic' rather than the 1-2 concrete actions of level 3.

2 / 5

Completeness

There is no 'Use when...' clause or equivalent trigger guidance (capped at 3 by guideline, and this is below that), and the 'what' is vague — the description never states what the skill produces. It reads as a vague when-like clause ('Use ... for workflows that need ...') without a 'what', matching anchor 2 rather than anchor 3's clear 'what'.

2 / 5

Trigger Term Quality

The available terms ("market access value", "academic writing", "structured execution") are one or two generic keywords plus process meta-language users would not naturally say. Natural trigger phrases for this domain (HTA, payer negotiation, reimbursement, ICER, value dossier, pricing) are entirely missing, matching 'missing the natural phrases users say' at level 2 rather than level 3's 'some relevant keywords' with partial coverage.

2 / 5

Distinctiveness Conflict Risk

"Market access value" is a distinctive niche term, but the framing "academic writing workflows that need structured execution, explicit assumptions" would plausibly trigger for any generic academic-writing or process-structuring skill. It is somewhat specific yet has real overlap risk with similar skills, fitting anchor 3; it does not reach level 4's 'mostly distinct' because the academic-writing framing invites wrong-skill triggers.

3 / 5

Total

9

/

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/market-access-value/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.