CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blind-review-sanitizer

Use blind-review-sanitizer for academic writing workflows that need structured anonymization, explicit assumptions, and clear output boundaries for double-blind submission.

Quality

64%

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/blind-review-sanitizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 body delivers genuinely actionable commands, a concrete parameter table, and a well-signaled one-level reference to the bundled audit file, with a clearly sequenced workflow including stop conditions and validation checks. However, it is significantly padded with overlapping, generic policy boilerplate (triplicated output/error/input sections) that inflates token cost without adding skill-specific value.

Suggestions

Merge the overlapping "Error Handling"/"Failure Handling"/"Input Validation" sections and the three output-shape sections ("Output Requirements", "Output Contract", "Response Template") into single concise sections, cutting the body roughly in half.

Drop generic template sections ("Required Inputs" table, "User Checkpoints", "Quick Validation") that restate universal agent behavior and add no anonymization-specific guidance.

Add a small before/after example of a sanitized manuscript excerpt to show what the script's changes look like, closing the actionability gap.

DimensionReasoningScore

Conciseness

The ~190-line body is padded with several generic policy sections that add little skill-specific knowledge: overlapping "Error Handling"/"Failure Handling"/"Input Validation" sections, three separate output-shape sections ("Output Requirements", "Output Contract", "Response Template"), a "Required Inputs" table with generic fields like "User task description", plus boilerplate "User Checkpoints" and "Quick Validation" lists. This matches anchor 2 ("several unnecessary explanations or padded sections") rather than anchor 3's mostly-efficient profile, since well over a third of the body is duplicative boilerplate.

2 / 5

Actionability

Concrete, executable commands are provided ("python -m py_compile scripts/main.py", "python scripts/main.py --help", a real example invocation with --input/--authors), and the Parameters table documents concrete flags. Minor gaps keep it below anchor 5: no sample input/output showing what sanitization produces, and the workflow's actual transformation behavior is delegated to the bundled script without illustration.

4 / 5

Workflow Clarity

The 5-step Workflow is clearly sequenced with explicit stop/fallback conditions ("If the request lacks a file path or enough identifiers, stop and request the minimum missing input"), and validation checkpoints exist (Quick Check compile verification, error-handling fallbacks, overwrite review before output). It falls short of anchor 5 because there is no validate→fix→retry feedback loop for the sanitization output itself (e.g., re-running or verifying removal after fixes), only bounded fallback reporting.

4 / 5

Progressive Disclosure

The body is well-sectioned, and the one reference ([references/audit-reference.md](references/audit-reference.md), verified to exist) is clearly signaled, described, and exactly one level deep; the bundled scripts/main.py also exists as referenced. This matches anchor 4 (good structure, references mostly clear, minor organization gaps) rather than anchor 5 because substantial generic policy content is inlined in SKILL.md that could be split into a separate reference file.

4 / 5

Total

14

/

20

Passed

Description

53%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 correctly identifies a distinct niche (double-blind submission anonymization) but describes it in abstract workflow language rather than concrete capabilities. It lacks an explicit 'Use when...' trigger clause and natural user phrasing such as "peer review", "manuscript", or "de-identify", which limits both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause naming natural user phrases, e.g. "Use when preparing a manuscript for double-blind peer review, anonymizing author-identifying content, or blinding a paper for submission".

Replace abstract qualities ("explicit assumptions, and clear output boundaries") with concrete actions such as "Removes author names, affiliations, acknowledgments, and self-citations from .docx, .md, and .txt manuscripts".

Include common synonyms users would say ("de-identify", "blind the manuscript", "peer review") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("academic writing workflows", "double-blind submission") and one concrete action ("structured anonymization"), but "explicit assumptions, and clear output boundaries" are abstract qualities rather than actions, and coverage of what the skill actually does is not comprehensive. It sits between the anchor 2 example ("Processes PDF files" — single generic action) and anchor 4 (several specific actions); the single domain-tied action with surrounding fluff lands it at 3.

3 / 5

Completeness

The "what" is present but high-level ("structured anonymization ... for double-blind submission"), and the "when" is only weakly implied via "for academic writing workflows that need structured anonymization" — there is no explicit 'Use when...' clause with concrete trigger phrases, which caps completeness at 3 per the judging guidelines. It is above anchor 2 because both what and when are at least gestured at, but below anchor 4 whose 'when' is an explicit, direct trigger statement.

3 / 5

Trigger Term Quality

Relevant keywords like "anonymization", "academic writing", and "double-blind submission" are present, but common natural variations users would say are missing: "peer review", "manuscript", "de-identify", "blind the manuscript", and supported file types (.docx, .md, .txt). This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms") rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

Double-blind manuscript anonymization is a clear niche with distinct triggers; conflict risk is limited to minor overlap with closely related academic-writing/editing skills. Not anchor 5 because the description lacks concrete trigger phrases that fully disambiguate it from general writing-assistance skills.

4 / 5

Total

13

/

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/blind-review-sanitizer/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.