CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-tool

Triage a tool or library into a structured reference summary for the research repo. Use when given a GitHub URL, npm package, PyPI package, or CLI tool name. Creates references/{slug}.md with architecture overview and scope assessment; adds REVIEWED.md entry and REFERENCE_INDEX.md row. Triggers: triage tool, add tool, analyse tool, GitHub project, npm package, PyPI package, library, framework, CLI tool, MCP server, open source project.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, actionable skill body: a numbered triage workflow with confirmation gates, executable commands, and genuine one-level-deep bundle references that all exist on disk. The main weaknesses are one incorrect Quick Command path and validation scripts that are listed but never explicitly placed in the step sequence, plus mild redundancy across the Mindset, Workflow, and Anti-Patterns sections.

Suggestions

Fix the Quick Command `cp templates/REFERENCE-tool.md references/<slug>.md` — the actual template is `assets/templates/REFERENCE-tool.yaml`, so either correct the path or replace the cp with an instruction to create the file from the template's required_fields.

Wire validation into the workflow sequence, e.g. add to step 5: 'After writing references/<slug>.md, run ./scripts/validate-reference-tool.sh references/<slug>.md and fix any errors before updating REVIEWED.md' (and the analogous validate-analysis-tool.sh call in step 10).

Trim redundancy between the Mindset section, the numbered Workflow, and the Anti-Patterns — the duplicate-check and confirmation rules are each stated three times; consolidating them would sharpen the token budget.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no concept explanations, no filler — but there is some redundancy: the duplicate-check and confirmation rules each appear in Workflow, Quick Commands, and Anti-Patterns, and the Mindset section partially restates workflow rules. Minor trimmable content, matching the 'efficient with minor over-explanation' anchor rather than the every-token-earns-its-place 5.

4 / 5

Actionability

Mostly executable guidance: concrete grep/curl/git-submodule commands, real template and validator paths, and a concrete REVIEWED.md row format. Minor gaps keep it below 5: the Quick Command `cp templates/REFERENCE-tool.md references/<slug>.md` references a path that does not exist (templates live at assets/templates/ and are .yaml), and the curl snippet hardcodes the /main/ branch only.

4 / 5

Workflow Clarity

A clear 10-step sequence with real checkpoints (duplicate grep with "If already present, report it and stop", confirmation gates for vendoring and promotion). However, the validator scripts are listed only in Quick Commands and the References section — no step explicitly says to run them after creating a file, so validation is available but not wired into the sequence, matching 'most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

SKILL.md is a well-signaled overview and every referenced path exists one level deep in the bundle: references/classification-guide.md for the taxonomy, assets/templates/*.yaml for required fields, assets/schemas/*.json, and scripts/validate-*.sh. Content is appropriately split rather than inlined, and the References section maps each artifact to its purpose.

5 / 5

Total

17

/

20

Passed

Description

96%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 in third-person voice that explicitly states what is created (references/{slug}.md, REVIEWED.md row, REFERENCE_INDEX.md row) and when to use it, with an explicit trigger list. The only risk is that a few very broad triggers (library, framework, open source project) could fire for related-but-different intents.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named artifacts: "Creates references/{slug}.md with architecture overview and scope assessment; adds REVIEWED.md entry and REFERENCE_INDEX.md row" — comprehensive coverage of what the skill produces, not just vague triage language.

5 / 5

Completeness

Both halves are explicit: what ("Triage a tool or library into a structured reference summary... Creates references/{slug}.md... adds REVIEWED.md entry") and when ("Use when given a GitHub URL, npm package, PyPI package, or CLI tool name" plus a concrete Triggers list). This matches the 5-anchor example structure.

5 / 5

Trigger Term Quality

The explicit Triggers list covers natural user phrasings broadly: "triage tool, add tool, analyse tool, GitHub project, npm package, PyPI package, library, framework, CLI tool, MCP server, open source project", plus input forms ("GitHub URL, npm package, PyPI package, or CLI tool name") — synonyms and common variations are all present.

5 / 5

Distinctiveness Conflict Risk

The niche (triage into a structured reference summary for a research repo) and its file artifacts are distinct, but broad trigger terms like "library", "framework", and "open source project" could overlap with other research-repo or evaluation skills. Mostly distinct with minor overlap risk, not the clear-minimal-conflict of a 5.

4 / 5

Total

19

/

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: 6 deeper-than-1-level

Warning

referenced_paths_exist

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

Warning

Total

13

/

16

Passed

Repository

pantheon-org/tekhne

Path

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