CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-paper

Triage an academic paper into a structured reference summary for the research repo. Use when given an arxiv ID, arxiv URL, DOI, or paper PDF. Creates references/{slug}.md; adds REVIEWED.md entry and REFERENCE_INDEX.md row. Triggers: triage paper, add paper, analyse paper, review paper, literature review, survey paper, benchmark paper, deep dive paper, arxiv, DOI.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 strong, well-structured body: concrete repo-specific rules, a clearly gated workflow, and real one-level-deep bundle references. Weaknesses are minor — one broken copy command, validation steps not embedded in the workflow sequence, and some redundancy between the Philosophy, Anti-Patterns, and reference-listing sections.

Suggestions

Fix the Quick Commands copy line to the real template path ("cp assets/templates/REFERENCE-paper.yaml ...") or drop it, since step 4 already directs reading the template from assets/templates/REFERENCE-paper.yaml.

Wire validation into the workflow: add an explicit step after step 4 ("Run ./scripts/validate-reference-paper.sh references/<slug>.md; fix and re-run until it passes") and after step 8, instead of leaving validators only in Quick Commands.

Merge the "References" and "Reference Material" sections into one, and fold the two overlapping benchmark-number anti-patterns ("NEVER invent benchmark numbers" and "NEVER state an evaluation number without marking it as reported") into one to trim tokens.

DimensionReasoningScore

Conciseness

Mostly lean ("Keep language precise. Do not pad."), but trimmable: the Philosophy section restates anti-patterns, two benchmark-number anti-patterns overlap, "References" and "Reference Material" sections list the same artifacts, and a stray table-row comment sits inside the Quick Commands code block. Fits anchor 4 (efficient with minor trimmable instances), not 5 (every token earning its place).

4 / 5

Actionability

Concrete grep/curl/validator commands, a slug format with examples, and a template-driven step 4 — but "cp templates/REFERENCE-paper.md references/<slug>.md" references a nonexistent path (the real file is assets/templates/REFERENCE-paper.yaml), so that command fails as written. Anchor 4 (mostly executable, minor gaps), not 3 (guidance goes well beyond pseudocode) or 5 (one command is broken).

4 / 5

Workflow Clarity

Eight clearly sequenced steps with a duplicate-check gate (step 2) and a user-confirmation gate (step 7). However, the validators appear only in Quick Commands, not wired into the step sequence — no explicit 'validate after creating the file' checkpoint — so the 5 anchor's fully explicit validation chain is not met.

4 / 5

Progressive Disclosure

All referenced bundle files exist (references/mcp-servers.md, references/reviewed-and-index-formats.md, both templates, schemas, validators), are one level deep, and are well signaled with a when-to-use table. The duplicated "References"/"Reference Material" listings are a minor organization gap — anchor 4, not 5.

4 / 5

Total

16

/

20

Passed

Description

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

An exemplary description: concrete capabilities, an explicit 'Use when' clause with real input formats, and a comprehensive trigger list including synonyms. Third-person voice throughout, concise, and clearly distinct from neighboring skills.

DimensionReasoningScore

Specificity

Multiple concrete actions with specific artifacts: "Triage an academic paper into a structured reference summary", "Creates references/{slug}.md", "adds REVIEWED.md entry and REFERENCE_INDEX.md row" — comprehensive coverage matching the top anchor.

5 / 5

Completeness

Explicitly answers both: what ("Creates references/{slug}.md; adds REVIEWED.md entry and REFERENCE_INDEX.md row") and when ("Use when given an arxiv ID, arxiv URL, DOI, or paper PDF") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasings with synonyms and identifiers: "triage paper, add paper, analyse paper, review paper, literature review, survey paper, benchmark paper, deep dive paper, arxiv, DOI", plus "arxiv ID, arxiv URL, DOI, or paper PDF". No common variation missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — academic paper intake for a research repo — with domain-specific triggers (arxiv, DOI, literature review); unlikely to fire for unrelated skills.

5 / 5

Total

20

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 4 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 6 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

pantheon-org/tekhne

Path

skills/documentation/research/triage-paper/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.