CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

methodology-extractor

Extract experimental methods from one or more papers into a structured protocol-oriented summary; use when comparing methods across studies or drafting reproducible procedures.

Quality

67%

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/Evidence Insight/methodology-extractor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 skill has a clear purpose, real validation commands, and a genuine one-level-deep reference, but the body is bloated with roughly ten overlapping governance sections and boilerplate checklists that crowd out concrete guidance. The core extraction procedure itself is described only abstractly, with no runnable invocation of scripts/main.py or sample output.

Suggestions

Consolidate the redundant governance sections (Error Handling, Failure Handling, When Not to Use, Input Validation, User Checkpoints, Output Requirements, Output Contract, Response Template) into a single compact section; delete or move the Risk Assessment, Security Checklist, Lifecycle Status, and Evaluation Criteria boilerplate to a reference file.

Add an executable invocation of the core functionality, e.g. a real command like `python scripts/main.py --paper-ids ... --method-type "Western Blot"` plus a short sample of the structured output format.

Move the audit commands and fallback boundary detail (already duplicated in references/audit-reference.md) out of the main body to eliminate duplication and shrink the overview.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: Error Handling, Failure Handling, When Not to Use, Input Validation, User Checkpoints, Output Requirements, Output Contract, and Response Template repeat the same missing-input/stop/partial-output guidance, and Risk Assessment, Security Checklist, Lifecycle Status, and Evaluation Criteria are boilerplate padding unrelated to the extraction task. It stays above anchor 1 only because it never explains concepts Claude already knows.

2 / 5

Actionability

Concrete audit commands exist ("python -m py_compile scripts/main.py", "python scripts/main.py --help") along with Parameters, Returns, and a brief Example, but the core extraction task itself is never given an executable invocation (no real scripts/main.py call with paper_ids and method_type) and no sample of the structured output format. This is 'some concrete guidance but incomplete' rather than mostly-executable anchor 4.

3 / 5

Workflow Clarity

The five-step Workflow is sequenced with explicit checkpoints ("Validate that the request matches the documented scope and stop early", fallback on failure, Quick Validation section, User Checkpoints before batch operations), so the batch-operation validation cap at 3 does not apply. It falls short of anchor 5 because key steps like "Use the packaged script path or the documented reasoning path" remain abstract rather than command-backed, and there is no validate-fix-retry loop for the extraction output itself.

4 / 5

Progressive Disclosure

The single reference (references/audit-reference.md) is real, clearly signaled in a References section, and one level deep with no nesting, but the SKILL.md body inlines large generic compliance content (risk table, security checklist, lifecycle status, evaluation criteria) that belongs in a separate reference file. This is anchor 3 (some structure, content that should be separate is inline) rather than 4, where organization gaps are only minor.

3 / 5

Total

12

/

20

Passed

Description

71%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 solid description that clearly states both capability and explicit use triggers in third person. Its main weakness is thin keyword coverage: it lacks the synonyms and concrete artifact types (methods section, protocol extraction, systematic review, PDF/PMID) that would make triggering reliable across phrasings.

Suggestions

Add natural trigger synonyms such as 'methods section', 'protocol extraction', 'systematic review', or 'reproducibility check' to broaden keyword coverage.

Enumerate one or two more concrete actions (e.g., 'compare parameter variations across studies and flag deviations') to raise capability specificity.

DimensionReasoningScore

Specificity

"Extract experimental methods from one or more papers into a structured protocol-oriented summary" names the domain and 1-2 concrete actions (extract, produce structured summary) but offers no broader action inventory, matching anchor 3. It is above anchor 2 because the actions are specific rather than generic, and below anchor 4 because only the extraction action is truly enumerated.

3 / 5

Completeness

It explicitly answers both "what" ("Extract experimental methods... into a structured protocol-oriented summary") and "when" with two concrete trigger clauses ("use when comparing methods across studies or drafting reproducible procedures"), matching the anchor-5 example pattern of what + explicit when with concrete triggers.

5 / 5

Trigger Term Quality

Natural terms like "papers", "comparing methods", "reproducible procedures", and "protocol" are present, but common variations users would say are missing (e.g., "methods section", "protocol extraction", "systematic review", PMIDs, PDFs). This is anchor 3 (some relevant keywords, missing common variations) rather than 4, whose keyword coverage is noticeably fuller.

3 / 5

Distinctiveness Conflict Risk

The paper-methodology-extraction niche has distinct triggers that would not fire for unrelated skills, but it could overlap with general literature-review or paper-analysis skills. This is anchor 4 (mostly distinct, minor overlap risk with closely related skills) rather than 5 (clear niche with minimal conflict risk).

4 / 5

Total

15

/

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/Evidence Insight/methodology-extractor/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.