CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

literature-statistics

Generate statistics for publication-year and journal distributions from local references or PDFs; use when you need standardized Year/Journal tables and a summary without any network access.

Quality

74%

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/Other/literature-statistics/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 technical core is strong — precise parsing/normalization/sorting rules, a real and complete PDF script, and a concrete output contract. It is dragged down by ~50 lines of generic, internally duplicated governance boilerplate and by an example command that invokes a script (process_references.py) absent from the bundle.

Suggestions

Cut or condense the generic sections (When Not to Use, Required Inputs, Recommended Workflow, Output Contract, Validation and Safety Rules, Failure Handling, Quick Validation) into a few skill-specific lines — the no-network/no-guessing rules are already stated in Key Features and Failure Handling and Safety Constraints, and the duplicated second failure-handling section adds nothing.

Fix the reference-file example: scripts/process_references.py does not exist in the bundle, so either ship that script or replace the example with the actual documented procedure for .bib/.ris/pasted-text inputs.

Make the Quick Validation section accurate: `python scripts/process_pdfs.py --help` prints argparse usage, not "Result file: literature_statistics_result.md / Validation summary: PASS/FAIL", so show the real expected output or replace the check with a concrete one (e.g., running the script on a two-file test directory).

DimensionReasoningScore

Conciseness

Roughly a third of the body is generic governance boilerplate with no skill-specific information — "Do not use this skill when the required source data, identifiers, files, or credentials are missing", "A clearly specified task goal aligned with the documented scope", "Run a final validation pass for completeness, consistency, and safety" — and rules repeat across sections ("no network access" appears three times; there are two separate failure-handling sections). This matches the anchor for noticeably verbose with several padded sections. It is not 3 because the padding exceeds 'some unnecessary explanation', and not 1 because the technical core (parsing rules, normalization, sorting, commands, output format) is lean and never explains concepts Claude already knows.

2 / 5

Actionability

The PDF path is fully executable ("python scripts/process_pdfs.py --input-dir \"./pdfs\" --output \"./literature_stats.md\"" — verified to exist in the bundle), and the parsing rules are precise and implementable ("Year: first 4-digit year in the range 1900-2099", "Journal: first non-empty value among JO / JF / T2"), matching the mostly-executable anchor. It is not 5 because Example 2 invokes "python scripts/process_references.py" which does not exist in the bundle, the pasted-text/.bib/.ris paths (primary use cases) have no executable entry, and the Quick Validation expected output does not match what `--help` actually prints; not 3 because the concrete command, real script, exact parsing rules, and concrete expected-output format leave only minor gaps.

4 / 5

Workflow Clarity

The 8-step Processing Pipeline ("1. Detect input type... 6. Aggregate counts and compute percentages... 8. For PDF directories, use...") gives a clear sequence, sorting requirements are explicit (count descending, then name ascending), validation is addressed ("Run this minimal verification path before full execution") and failure handling includes recovery steps. This matches the clear-sequence-most-checkpoints anchor. It is not 5 because the validation checkpoints are vague prose rather than concrete executable checks, the Quick Validation's expected output is inaccurate, and the workflow is scattered across five overlapping sections; not 3 because validation is explicitly present (not absent) and the batch operation is read-only.

4 / 5

Progressive Disclosure

Structure matches the actual bundle: core instructions live in SKILL.md, examples are externalized one level deep and clearly signaled ("For additional examples, see: `references/examples.md`" — verified to exist), and executable code lives in scripts/process_pdfs.py with pinned requirements.txt. This fits the good-structure anchor. It is not 5 because SKILL.md is a ~180-line manual rather than a lean overview — the expected-output block and validation boilerplate could be externalized or trimmed, and examples.md is referenced only once mid-document; not 3 because the references that exist are real, one level deep, and well signaled.

4 / 5

Total

14

/

20

Passed

Description

78%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 strong description that explicitly covers both what the skill does and when to use it, with concrete deliverables (year table, journal table, summary) and a distinctive niche. The main improvement space is richer trigger vocabulary (citations, literature, .bib/.ris).

DimensionReasoningScore

Specificity

The description lists several concrete deliverables — "Generate statistics for publication-year and journal distributions", "standardized Year/Journal tables and a summary", "from local references or PDFs" — which matches the anchor for several specific actions with minor gaps. It is not 5 because a single umbrella verb ("Generate statistics") covers the actions and the parsing/normalization capabilities are absent; not 3 because more than 1-2 concrete actions are named across both input types and both output tables.

4 / 5

Completeness

Both parts are explicit: the 'what' is "Generate statistics for publication-year and journal distributions from local references or PDFs" and the 'when' is "use when you need standardized Year/Journal tables and a summary without any network access", matching the anchor where both are present but 'when' could be more specific. It is not 5 because the trigger clause restates deliverables rather than naming concrete user scenarios; not 3 because the 'use when' clause is explicit, not weakly implied.

4 / 5

Trigger Term Quality

Natural user terms are present: "publication-year", "journal distributions", "references", "PDFs", "Year/Journal tables", "statistics" — good keyword coverage matching the anchor. It is not 5 because common synonyms and extensions users would say ("citations", "literature", "bibliography", ".bib", ".ris") are missing; not 3 because coverage goes beyond 'some relevant keywords' with both domain terms and generic input synonyms.

4 / 5

Distinctiveness Conflict Risk

"publication-year and journal distributions", "standardized Year/Journal tables", and "without any network access" define a clear niche (literature-reference statistics) with distinct triggers, so it would not fire for general PDF-extraction or generic data-analysis requests — matching the minimal-conflict-risk anchor. It is not 4 because the overlap with neighboring skills is genuinely minor: the when-clause requires Year/Journal tables, which excludes generic 'process my PDFs' or 'analyze this data' requests.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/literature-statistics/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.