market-access-value

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

Quality

52%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/market-access-value/SKILL.md

Quality

Content

70%

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 clear, well-validated workflow with a real one-level reference, but it is padded with verbatim repetition, generic boilerplate, and broken internal cross-references, and its domain-specific guidance is vaguer than its validation commands. Tightening the repetition and replacing example-outputs with actionable payer-value instructions would raise the weaker dimensions.

Suggestions

Remove the three verbatim repeats of the description sentence and fix the broken cross-references ("## Prerequisites" and "## Workflow" appear below, not above) to tighten conciseness.

Replace the illustrative "ICER = $45,000/QALY" line with concrete steps or a runnable reference for how the skill produces ICER, budget-impact, and value-dossier outputs.

Trim generic boilerplate (Security Checklist, Evaluation Criteria, Lifecycle Status) or move it into a reference file so the body stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body repeats the description sentence verbatim three times ("When to Use", "Key Features", and the frontmatter) and includes generic boilerplate (Security Checklist, Evaluation Criteria, Lifecycle Status) plus broken cross-references ("See `## Prerequisites` above" and "See `## Workflow` above" point to sections that are below), so it is mostly functional but padded with unnecessary repetition and could be tightened.	2 / 3
Actionability	It provides executable validation commands ("python -m py_compile scripts/main.py", "python scripts/main.py --help") and lists parameters/returns, but the core domain guidance for actually developing a payer value proposition is vague — "ICER = $45,000/QALY with uncertainty analysis" is an example output rather than instructions — so concrete guidance is present but incomplete.	2 / 3
Workflow Clarity	The five-step Workflow is clearly sequenced with validation checkpoints ("Validate that the request matches the documented scope and stop early if...") and an explicit fallback path on failure (step 5), reinforced by dedicated Error Handling and Input Validation sections, matching the clear-sequence-with-feedback-loops anchor.	3 / 3
Progressive Disclosure	SKILL.md serves as an overview with a single, real, one-level-deep reference (references/audit-reference.md) that is clearly signaled and linked, and a packaged scripts/main.py entry point, so navigation is easy and the reference structure is appropriately shallow.	3 / 3
	Total	10 / 12 Passed

Description

35%

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 a domain but lacks concrete actions and natural trigger terms, and it omits any explicit "Use when..." guidance. Its generic "academic writing" framing also blurs its true payer/market-access niche and raises conflict risk with academic-writing skills.

Suggestions

Add concrete action verbs reflecting what the skill does, e.g. "Develop payer value propositions, draft HTA submission narratives, and calculate ICER/budget-impact model text."

Append an explicit trigger clause naming natural user terms, e.g. "Use when drafting payer value dossiers, HTA submissions, reimbursement applications, or pricing/reimbursement negotiations."

Drop the generic "academic writing workflows" label in favor of market-access-specific language to reduce overlap with academic-writing skills.

Dimension	Reasoning	Score
Specificity	The phrase "Use market access value for academic writing workflows that need structured execution, explicit assumptions, and clear output boundaries" names a domain and hints at qualities (structured execution, explicit assumptions, output boundaries) but names no concrete actions or verbs describing what the skill actually does, landing at the domain-named-but-incomprehensive level rather than the vague level 1.	2 / 3
Completeness	It states a partial "what" but includes no "Use when..." clause or equivalent explicit trigger guidance for when to invoke it, so per the judging guidelines completeness is capped at 2 rather than reaching the explicit-both-what-and-when level 3.	2 / 3
Trigger Term Quality	"market access value" and "academic writing workflows" are technical/overly-generic phrases rather than natural terms a user would say; the genuine trigger terms a payer-focused user would speak (payer, ICER, HTA submission, value dossier, reimbursement) are absent, and "academic writing workflows" is a misleading generic label for what is a market access skill.	1 / 3
Distinctiveness Conflict Risk	The "academic writing workflows" framing is generic and would overlap with general academic-writing skills, while the true payer/market-access niche is obscured, so it is somewhat specific but could still conflict with similar skills.	2 / 3
	Total	7 / 12 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
Commit: 7cc5680

Reviewed: 3 days 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.