CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-triage

Generate an issue triage report for the C# MCP SDK. Fetches all open issues, evaluates SLA compliance against SDK tier requirements, reviews issue discussions for status and next steps, cross-references related issues in other MCP SDK repos, and produces a BLUF markdown report. Use when asked to triage issues, audit SLA compliance, review open issues, or generate an issue report.

70

Quality

85%

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 instruction-only skill with a clear sequenced workflow and properly externalized references. The main weaknesses are mild redundancy between the Anti-Patterns and Step 5.0 safety guidance and the absence of a final report-verification checkpoint.

Suggestions

Collapse the repeated safety anti-patterns (suspicious links, downloads, code execution) into a single 'see Step 5.0' pointer to remove redundancy with the Safety Scan table.

Add a copy-paste command for paginating open issues (e.g. a `gh issue list` or API pagination snippet) so the fetch step is executable rather than descriptive.

Add a final verification checkpoint in Step 7/8 confirming the report file was written and that backlog counts match the aggregate metrics before presenting the summary.

DimensionReasoningScore

Conciseness

The body is task-focused and avoids explaining concepts Claude already knows, but the Anti-Patterns section restates the safety guidance already covered in Step 5.0 (suspicious links, downloads, code execution), which could be trimmed.

4 / 5

Actionability

Concrete guidance throughout — the live fetch URL, the classification table, per-issue fields to capture, and the exact `gh gist create` command — but issue fetching is described abstractly ('Paginate through all open issues via the GitHub API') without a copy-paste curl/gh command, leaving a minor gap.

4 / 5

Workflow Clarity

An explicit 8-step sequence with real checkpoints (Step 1 fetch-fail stop, Step 5.0 safety scan, rate-limit partial-completion handling) and checklist tables; docked one point because there is no final output-verification step confirming the rendered report and aggregate counts reconcile.

4 / 5

Progressive Disclosure

The SKILL.md is an overview/process document that points via clearly signaled markdown links to two real one-level-deep references — report-format.md (large template) and cross-sdk-repos.md (repo/theme list) — both appropriately externalized and easy to navigate.

5 / 5

Total

17

/

20

Passed

Description

92%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, third-person description that concretely enumerates the skill's actions and pairs them with explicit 'Use when...' triggers tied to a specific repository. Only minor weakness is a lack of synonyms or extension variants in the trigger terms.

DimensionReasoningScore

Specificity

Lists five concrete actions — 'Fetches all open issues', 'evaluates SLA compliance against SDK tier requirements', 'reviews issue discussions for status and next steps', 'cross-references related issues in other MCP SDK repos', 'produces a BLUF markdown report' — giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (the five-action pipeline producing a BLUF report) and 'when' ('Use when asked to triage issues, audit SLA compliance, review open issues, or generate an issue report') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — 'triage issues', 'audit SLA compliance', 'review open issues', 'generate an issue report' — but lacks synonyms or file-extension variants, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to the C# MCP SDK with a clear niche (issue triage / SLA auditing) and distinct triggers, making conflict with other skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
modelcontextprotocol/csharp-sdk
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.