CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

protocol-standardization

Standardize fragmented experimental steps into reproducible protocol documents when you need method organization, lab SOP drafting, or cross-operator reproducibility; missing parameters must be explicitly marked as "To be supplemented/Not provided".

Quality

72%

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/Protocol Design/protocol-standardization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

A well-structured, genuinely actionable instruction skill: clear workflow, strong anti-fabrication rules, a real template and reference guide, and a concrete worked example. The main cost is token weight — five generic boilerplate sections at the end and a repetitive example inflate the body without adding protocol-specific guidance.

Suggestions

Cut or merge the generic 'Output Contract', 'Failure Handling', 'User Checkpoints', 'Input Validation', and 'Quick Validation' sections into a short, protocol-specific validation checklist, saving roughly 30 lines of boilerplate.

Trim the worked example to 2–3 parameter fields marked 'To be supplemented/Not provided' — the convention is established after a few uses — or move the full example into references/guide.md.

Make 'Validate logical sequence and operability' concrete by listing the specific checks (step ordering, unit consistency, missing-parameter flags) that Output Check should perform.

DimensionReasoningScore

Conciseness

The protocol-specific content (When to Use, Implementation Details, the worked example) is efficient and earns its tokens, but the tail sections — 'Output Contract', 'Failure Handling', 'User Checkpoints', 'Input Validation', 'Quick Validation' — are generic scaffold boilerplate (e.g., 'Primary output: Structured result or target file aligned with this skill's objective') that adds little skill-specific value, and the example repeats 'To be supplemented/Not provided' fifteen-plus times where a few instances would establish the convention. This lands on anchor 3 (mostly efficient, some tightening needed) rather than 2 because the padding is concentrated in a few sections rather than permeating the document.

3 / 5

Actionability

Concrete guidance throughout: a four-step workflow, explicit parameter rules ('Never fabricate values', unit conventions), real bundle paths (assets/protocol_template.md, references/guide.md), an output naming convention ('{Experiment_Info_Abbreviation}.txt' in outputs/), and a full worked input→output example. It is not a 5 because some directives stay abstract — 'Validate logical sequence and operability' gives no check procedure — leaving minor gaps per anchor 4.

4 / 5

Workflow Clarity

The sequence is explicit and ordered (Step Review → Parameter Completion → Standardization → Output Check), with validation present via 'Output Check: Validate logical sequence and operability', the 'Critical Parameters to Supplement' list, and a Quick Validation section, plus user checkpoints before batch operations. It misses anchor 5 because the error path is stated generically ('report the failing step... recovery suggestions') rather than as an explicit validate→fix→retry feedback loop.

4 / 5

Progressive Disclosure

The bundle structure is sound: SKILL.md is the overview, assets/protocol_template.md (a fill-in template) and references/guide.md (checklists) both exist and are clearly signaled by path, one level deep. It is not a 5 because the ~50-line worked example output inlined in SKILL.md is content that could be split into references, and guide.md partially duplicates body content rather than adding a distinct layer.

4 / 5

Total

15

/

20

Passed

Description

66%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, niche-specific description that clearly states what the skill does and when to use it, with an unusual and memorable anti-fabrication convention. Its weaknesses are the narrow trigger-term coverage and slightly abstract 'when' phrasing, plus a second-person slip in the trigger clause.

Suggestions

Broaden trigger terms with natural user phrasings such as 'standardize a protocol', 'write an SOP', or 'clean up messy lab notes' to improve natural-language matching.

Replace the abstract 'cross-operator reproducibility' trigger with something a user would actually say, e.g. 'when multiple operators must follow the same method'.

Rewrite the trigger clause in third person ('Use when the user needs method organization...') to comply with the third-person voice convention.

DimensionReasoningScore

Specificity

The description names the domain ("fragmented experimental steps", "reproducible protocol documents") and two concrete actions — standardize steps into protocols and "missing parameters must be explicitly marked as 'To be supplemented/Not provided'" — but stops short of the comprehensive action list of level 4. It also opens with an imperative verb but slips into second person in the trigger clause ("when you need method organization"), which the third-person-voice guideline penalizes, keeping it at anchor 3 rather than 4.

3 / 5

Completeness

Both halves are present: the "what" is concrete ("Standardize fragmented experimental steps into reproducible protocol documents") and the "when" is explicit ("when you need method organization, lab SOP drafting, or cross-operator reproducibility"). It falls short of anchor 5 because the trigger phrases are more abstract than concrete user utterances (compare "when the user mentions PDFs, forms, or document extraction"), matching anchor 4 where the 'when' could be more explicit or specific.

4 / 5

Trigger Term Quality

It offers some relevant natural phrases — "method organization", "lab SOP drafting" — but misses common variations users would actually say ("standardize a protocol", "write an SOP", "protocol template", "experimental protocol") and leans on the jargon-y "cross-operator reproducibility" rather than natural language. This matches anchor 3 (relevant keywords, missing synonyms) rather than 4, whose keyword coverage would be broader.

3 / 5

Distinctiveness Conflict Risk

This occupies a clear niche — lab protocol standardization and SOP drafting — with distinctive triggers ("lab SOP drafting", "cross-operator reproducibility", the 'To be supplemented/Not provided' marking convention) that no general documentation or writing skill would claim, so conflict risk is minimal per anchor 5.

5 / 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/Protocol Design/protocol-standardization/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.