CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage

Find worthwhile FastMCP issues to work on in a backlog or release window, verify promising candidates, and present concrete picks with existing PR links.

Quality

75%

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 ./.agents/skills/triage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a dense, high-signal instruction skill: exact gh commands with a cloud-session fallback, explicit decision criteria, built-in verification steps, and clear routing to sibling skills. The only notable gaps are the headerless wall-of-prose organization and a final paragraph that drifts into abstract maintainer-session jargon (EGM, Cloud node) without concrete steps.

DimensionReasoningScore

Conciseness

The body is lean throughout: no explanation of what gh, FastMCP, or triage concepts are; every sentence carries a directive ("Do not rank solely by recency, comment count, or how small a proposed patch looks", "check for a revert first"). It assumes Claude's competence and every token earns its place, matching anchor 5.

5 / 5

Actionability

Concrete, copy-paste-ready commands dominate: exact gh invocations with --json field lists, a REST fallback URL ("gh api \"repos/PrefectHQ/fastmcp/pulls?state=all&per_page=100&page=N\""), and specific decision rules (want/marginal/don't want, cleanup-pass criteria). The final paragraph's batch/maintainer guidance ("Use upstream EGM in the maintainer session") is comparatively abstract and unexecutable, keeping it below anchor 5.

4 / 5

Workflow Clarity

A clear sequence runs from reading AGENTS.md and the contribution policy, through a bounded inventory and PR linking, to verification checkpoints (trace code and git history, distinguish fixed/released/proposed, check for reverts) and a defined output. It is not 5 because there are no explicit feedback loops or error-recovery steps for the verification phase (e.g., what to do when evidence contradicts a pick), though the skill is read-only so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

At ~30 lines it stays within SKILL.md appropriately, with clearly signaled one-level references to sibling skills ([fix-issue](../fix-issue/SKILL.md), [review-issue](../review-issue/SKILL.md)) and the contributing guide; no nested reference chains. It falls short of anchor 5 because there are no section headers at all — the guidance is dense flowing prose a reader must parse linearly — and some reference paths cannot be resolved from the skill's own directory.

4 / 5

Total

17

/

20

Passed

Description

58%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 is specific and domain-anchored, clearly stating three concrete actions in third person without fluff. Its main weaknesses are the absence of an explicit 'Use when' trigger clause and thin coverage of natural trigger phrasing users would actually say.

Suggestions

Add an explicit trigger clause, e.g. "Use when asked to triage the FastMCP backlog, find issues worth working on, or pick work after a release."

Include natural synonyms users would say — "triage", "good issues to contribute to", "issue backlog" — to improve trigger matching.

Briefly signal the boundary with sibling skills (e.g. "...but not for implementing fixes") to reduce overlap with fix-issue/review-issue.

DimensionReasoningScore

Specificity

Phrases like "Find worthwhile FastMCP issues to work on in a backlog or release window", "verify promising candidates", and "present concrete picks with existing PR links" name the domain and several concrete actions. It falls short of anchor 5 because coverage is not comprehensive — the verification and cleanup/batch-proposal capabilities in the body are only thinly represented here.

4 / 5

Completeness

The 'what' is clear (find, verify, present picks with PR links), but there is no 'Use when...' clause or equivalent explicit trigger guidance; "in a backlog or release window" only weakly implies the 'when'. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3 — not 4, which requires both what and when with at least an implicit-but-present when.

3 / 5

Trigger Term Quality

Relevant keywords exist ("FastMCP issues", "backlog", "release window", "PR links") but common natural phrases are missing — notably "triage" itself, "good first issues", "what should I work on", or "contribution candidates". Users would plausibly say several of these missing variations, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The FastMCP-specific scope ("FastMCP issues", repo-named PRs) gives it a clear niche with minimal conflict against generic skills. It stops short of anchor 5 because the description doesn't distinguish when this skill applies versus the sibling fix-issue/review-issue skills it routes to, leaving some overlap risk within its own bundle.

4 / 5

Total

14

/

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

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

PrefectHQ/fastmcp

Path

.agents/skills/triage/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.