CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keyword-velocity-tracker

Calculate literature growth velocity and acceleration to assess research.

Quality

63%

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/keyword-velocity-tracker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 body delivers genuinely actionable material — executable commands, parameter tables, formulas, a stage-classification rubric, and a checkpointed workflow with fallbacks — but buries it in roughly a hundred lines of generic boilerplate sections and inlines what should live in reference files. The result is a bloated SKILL.md that dilutes its own good content.

Suggestions

Cut the boilerplate sections that add no task-specific knowledge (Key Features, Implementation Details, Output Requirements, Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) and fix the dangling "See `## Workflow` above" pointer.

Move the I/O schemas, algorithm description, stage judgment criteria, and configuration tables into a references/ file (e.g. references/algorithm.md), keeping SKILL.md as a concise overview with one-level-deep links.

Verify and correct the Python API import path and replace the opaque `cd "20260318/scientific-skills/..."` example path with the actual relative path from the skill root.

DimensionReasoningScore

Conciseness

The ~295-line body carries pervasive padding: "Key Features" restates the description, "Implementation Details", "Output Requirements", "Security Checklist", "Evaluation Criteria", and "Lifecycle Status" are generic boilerplate that adds nothing Claude does not already know, and "See `## Workflow` above for related details" is a dangling self-reference placed before that section exists. It is not 3 because the padding is extensive rather than occasional, and not 1 because genuinely useful task-specific content (parameter tables, formulas, runnable commands) is interleaved with the filler.

2 / 5

Actionability

Concrete, mostly executable guidance is present: `python scripts/main.py --keyword "artificial intelligence" --data-file data.json`, a runnable Python API example with real data, parameter tables with defaults, explicit velocity/acceleration formulas, and a py_compile quick check. It is not 5 because the import path `from skills.keyword_velocity_tracker.scripts.main import ...` is unverified against the actual bundle layout and the usage example cds into an opaque dated path, and not 3 because the commands and code shown are executable rather than pseudocode.

4 / 5

Workflow Clarity

The Workflow section gives a five-step sequence with explicit checkpoints (confirm objective and inputs, validate scope and stop early on unsupported assumptions, run with available inputs, return a structured result, switch to fallback on failure), reinforced by the Quick Check and Audit-Ready Commands sections and an Error Handling section naming failure points. It is not 5 because steps remain high-level (e.g. "choose the packaged workflow") without per-step commands or a fix-and-retry loop, and not 3 because validation checkpoints are explicitly present rather than missing.

4 / 5

Progressive Disclosure

The body is well-sectioned and its one reference (references/audit-reference.md) is real and properly signaled in a References section, but ~150 lines of I/O schema, algorithm description, stage criteria, and configuration detail are inlined in SKILL.md when they belong in references/ — only a thin audit-reference file exists alongside them. It is not 4 because the split between overview and detail is not "mostly appropriate" (the bulk of reference material sits inline), and not 2 because section structure is clear and the existing reference is clearly signaled.

3 / 5

Total

13

/

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 states a clear, concrete capability (literature growth velocity and acceleration) in third person, but it is a single short sentence with no use-when trigger guidance, thin synonym coverage, and a vague closing clause. It lands at the midpoint of the scale: serviceable what, missing when.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about publication trends, keyword growth rates, or the lifecycle/maturity of a research field."

Enumerate the concrete actions so the capability list is comprehensive: compute growth velocity, detect acceleration/deceleration, classify the field stage (embryonic/growth/mature/decline), and project future counts.

Add natural synonyms users would say — "publication trends", "bibliometric analysis", "keyword growth", "field lifecycle" — to strengthen trigger matching and distinctiveness.

DimensionReasoningScore

Specificity

"Calculate literature growth velocity and acceleration" names the domain and two concrete actions, but the trailing "to assess research" is generic and no further capabilities are listed, matching the anchor for 1-2 concrete actions without comprehensiveness. It is not 4 because the description does not list several specific actions, and not 2 because the actions named are concrete rather than minimal or generic.

3 / 5

Completeness

The description gives a clear "what" (calculate literature growth velocity and acceleration) but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the "when" is entirely absent rather than merely imprecise, and not 2 because the "what" is clear and concrete.

3 / 5

Trigger Term Quality

"literature growth", "velocity", and "acceleration" are relevant domain keywords a user might say, but common natural variations like "publication trends", "keyword analysis", or "bibliometrics" are missing. It is not 2 because the terms present are domain-relevant rather than generic filler, and not 4 because synonym coverage is thin.

3 / 5

Distinctiveness Conflict Risk

The bibliometric velocity/acceleration niche is fairly distinct with low conflict risk, though the broad trailing phrase "to assess research" could overlap with general research-assessment skills. It is not 5 because of that residual overlap and not 3 because the core trigger terms are specific to this skill's niche rather than broadly overlapping.

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/Evidence Insight/keyword-velocity-tracker/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.