market-access-value

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

Quality

44%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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 is well-structured with real bundle files and a serviceable validated workflow, but it is padded with repetitive templated sections and its documented parameters diverge from the actual script. Tightening the boilerplate and reconciling the parameter docs would materially raise quality.

Suggestions

Reconcile the "Parameters" section with scripts/main.py's real flags (--name, --indication, --output, --demo) and add a concrete copy-paste run example using those flags.

Remove the duplicated description string from "When to Use"/"Key Features" and consolidate the redundant compile/help commands (Quick Check, Audit-Ready Commands, Example Usage) into one block.

Cut generic boilerplate (Risk Assessment table, Security Checklist, Evaluation Criteria, Lifecycle Status with a stale 2026-03-06 date) that does not advance the skill's actual task.

Dimension	Reasoning	Score
Conciseness	The body is noticeably verbose with many padded/templated sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) and repetition — the description string is restated verbatim in both "When to Use" and "Key Features", and `python -m py_compile scripts/main.py` appears in three sections; a stale "Next Review Date: 2026-03-06" also adds time-sensitive noise, fitting "noticeably verbose; several unnecessary padded sections."	2 / 5
Actionability	Concrete executable commands exist (`python -m py_compile scripts/main.py`, `python scripts/main.py --help`) and a real script is referenced, but the documented "Parameters" (drug_profile, comparator, market) do not match the script's actual flags (--name, --indication, --output, --demo) and no copy-paste run invocation is given, fitting "some concrete guidance but incomplete; missing key details."	3 / 5
Workflow Clarity	The Workflow section gives a clear 5-step sequence with an explicit stop-early validation (step 2) and a documented fallback path (step 5), plus a dedicated Error Handling section, fitting "clear sequence with most checkpoints present"; it does not reach 5 because there is no output-validation feedback loop (validate generated artifact -> fix -> retry).	4 / 5
Progressive Disclosure	Bundle files are real and referenced one level deep with clear signaling ([references/audit-reference.md], scripts/main.py), and the body is organized into titled sections, fitting "good structure; references mostly clear"; it stays at 4 rather than 5 because the SKILL.md overview itself is bloated with generic sections that could be trimmed or split out.	4 / 5
	Total	13 / 20 Passed

Description

36%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 names its domain but relies on a single generic verb ("Use") and templated boilerplate, giving a weak "what" and a non-concrete "when." It is recognizable but not actionable or well-triggered.

Suggestions

Replace the generic "Use ... for ... workflows" framing with concrete outputs, e.g., "Generates payer value propositions, ICER narratives, budget-impact model text, and value dossier sections for HTA submissions and reimbursement applications."

Add a real "Use when..." clause with natural trigger terms a user would actually say (payer negotiations, HTA submission, reimbursement, ICER, pricing strategy).

Drop the templated "structured execution, explicit assumptions, and clear output boundaries" phrase, which reads as boilerplate and dilutes distinctiveness.

Dimension	Reasoning	Score
Specificity	The only action verb is "Use" ("Use market access value for academic writing workflows"); the domain is named but no concrete capability (e.g., producing payer value propositions, ICER, dossiers) is stated, matching the "names domain but actions minimal/generic" anchor and sitting below the 1-2-concrete-actions bar for a 3.	2 / 5
Completeness	The description is essentially a "Use X for Y" trigger clause with only a vague "what" ("use market access value") and no statement of what the skill actually produces, matching "only 'when' is present without 'what"; it does not reach 3 because the "what" is not clear and the "when" is templated rather than a concrete trigger.	2 / 5
Trigger Term Quality	"market access value" is a relevant domain keyword, but the natural terms a user would say (HTA, payer, ICER, reimbursement, value dossier) are absent and the surrounding "structured execution, explicit assumptions, clear output boundaries" is templated boilerplate rather than natural phrasing, fitting "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	"market access value" is a specific niche, but the generic templated trigger "academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries" would overlap with many structured-workflow skills, fitting "somewhat specific but could still overlap with similar skills."	3 / 5
	Total	10 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 63c61d3

Reviewed: 12 hours ago

Table of Contents

Discovery Implementation Validation

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.