CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

citation-chasing-mapping

Use when identifying seminal papers in a research field, mapping research lineage and intellectual heritage, discovering related work through reference tracking, or finding potential collaborators through co-citation analysis. Maps citation networks to trace research evolution...

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/citation-chasing-mapping/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 reads like an auto-generated template with the description pasted in twice, duplicated sections, and boilerplate governance text, wrapped around a genuinely useful but unverifiable API walkthrough. Its most serious defects are that every referenced bundle file (scripts/, references/) is missing from the package and the code examples use inconsistent method names against that nonexistent API.

Suggestions

Remove the duplicated description pastes (the 'Use this skill when the task needs...' and 'Key Features' bullets), merge the two 'When to Use' sections and the two 'References' headings, and drop the generic template boilerplate (Output Requirements / Response Template / Input Validation) that adds nothing specific to citation mapping — this alone would cut the file roughly in half.

Ship the referenced bundle files (`scripts/main.py`, `references/guide.md`, `references/examples/`, `references/api-docs/`, `references/audit-reference.md`) or delete the references; broken paths are worse than none. Move the four Core Capabilities API walkthroughs into `references/api-docs/` and keep only a Quick Start in SKILL.md.

Reconcile the API surface in the code examples — `identify_research_clusters` vs `detect_clusters` and `visualize_network` vs `visualize` are inconsistent — and fix the 'See `## Workflow` above' pointer in Implementation Details, which points to a section that appears below it. Add a concrete validation step (e.g., check node/edge counts or that the output JSON parses) after network construction.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the frontmatter description is pasted verbatim twice ("Use this skill when the task needs Use when identifying seminal papers..." and again under Key Features), there are two competing trigger sections ("## When to Use" and "## When to Use This Skill"), two "## References" headings, and generic template boilerplate ("Output Requirements", "Response Template", "Input Validation", "Quality Checklist") that adds no citation-mapping-specific value. This matches the anchor for several unnecessary padded sections; it is above a 1 only because it does not explain basic concepts Claude already knows.

2 / 5

Actionability

There is concrete-looking guidance (bash commands like `python -m py_compile scripts/main.py` and `python scripts/main.py --seed-pmid 12345678 --depth 2 ... --visualize`, plus worked Python examples), but the Python examples target an API that does not exist in the bundle and are internally inconsistent — `mapper.identify_research_clusters(...)` in Quick Start vs `mapper.detect_clusters(...)` in Core Capabilities, and `visualize_network(...)` vs `visualize(...)` — making them effectively pseudocode. This is the anchor for 'some concrete guidance but incomplete / pseudocode instead of executable code', not a 2, since specific commands and parameter values are given throughout.

3 / 5

Workflow Clarity

Steps exist (a 4-step Example run plan, a 5-step ## Workflow, and an Error Handling fallback), but validation checkpoints are generic ('validate the request matches the documented scope') rather than verifying actual outputs, and the structure is muddled: three competing step lists, a 'See `## Workflow` above' pointer in Implementation Details that actually points to a section below, and no checkpoint that validates the produced network. This fits 'steps listed but validation gaps; checkpoints missing or implicit', not a 4.

3 / 5

Progressive Disclosure

The body references `scripts/main.py`, `references/guide.md`, `references/examples/`, `references/api-docs/`, and `references/audit-reference.md`, yet none of these files exist in the bundle, so every reference is broken. Additionally, four subsections of API-style usage examples (Core Capabilities) are inlined directly in SKILL.md — content that the skill itself says belongs in `references/api-docs/`. Broken references plus inlined reference material matches the 'minimal structure / references buried or nonexistent' anchor; it is not a 3 because the navigation that exists does not resolve to real files.

2 / 5

Total

10

/

20

Passed

Description

75%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 with an explicit 'Use when' trigger, third-person voice, and multiple concrete domain actions. Its main defect is that the capability sentence is truncated mid-sentence by a literal '...', so the 'what' half of the description is incomplete, and a few natural synonyms (bibliometrics, citation graph, literature review) are absent.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "identifying seminal papers", "mapping research lineage and intellectual heritage", "discovering related work through reference tracking", "finding potential collaborators through co-citation analysis" — rather than vague language. It falls short of a 5 because the capability statement "Maps citation networks to trace research evolution..." is cut off mid-sentence by a literal ellipsis, leaving coverage of what the skill actually does incomplete.

4 / 5

Completeness

Both parts are present: an explicit trigger ("Use when identifying seminal papers... or finding potential collaborators...") and a what-statement ("Maps citation networks to trace research evolution"). It is not a 5 because the 'what' clause terminates in an ellipsis, so the answer to 'what does this do' is literally incomplete rather than clearly and fully explicit.

4 / 5

Trigger Term Quality

Natural phrases a researcher would say are present: "seminal papers", "research lineage", "related work", "collaborators", "co-citation analysis", "citation networks". Not a 5 because common synonyms and variations are missing — no "bibliometrics", "citation analysis", "citation graph", "literature review", or "h-index" — so keyword coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

Citation-network mapping and co-citation analysis form a fairly distinct bibliometric niche with clear triggers, giving minimal conflict risk with unrelated skills. Only a minor overlap risk remains with adjacent literature-search or systematic-review skills, which keeps it below a 5.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 15 missing

Warning

Total

13

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/citation-chasing-mapping/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.