CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

endgame-status

Report VS Code endgame status, focusing on test-plan progress, tester activity, release-branch PRs, and release-build availability.

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

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

An exceptionally tight, high-signal instruction skill: concrete commands and queries, explicit classification criteria and thresholds, and failure-state handling throughout, all within a compact, well-organized body. The only minor gap is that the overall workflow sequence is conveyed through section ordering and temporal conditions rather than explicit numbered steps.

DimensionReasoningScore

Conciseness

The body is dense, imperative guidance with no padding and no explanation of concepts Claude already knows — every bullet encodes a non-obvious rule (e.g., slot-counting rules, attribution for bot cherry-picks, publication vs. merge-status distinctions). This matches the anchor for lean, efficient content where every token earns its place, rather than anchor 4's minor over-explanation.

5 / 5

Actionability

It provides a copy-paste-ready command ("gh search issues 'repo:microsoft/vscode is:issue is:open \"Endgame\"' --json number,title,url"), exact queries, labels, and repositories, explicit slot classification criteria (Completed/In Progress/Not Started), a numeric threshold ("5 or more TPIs"), and defined table columns. For an instruction-only skill this matches the anchor for fully executable, case-covering guidance.

5 / 5

Workflow Clarity

Sections are sequenced by explicit temporal conditions ("While testing is underway", "Once the testing day in the current plan has passed") with verification requirements threaded throughout ("Verify inclusion against the published build's source revision", "Confirm the release from the plan's title"). It falls short of anchor 5 because there is no explicit numbered sequence, checklist, or error-recovery loop structure — matching anchor 4's clear sequence with minor gaps. The skill is read-only reporting, so the destructive/batch validation cap does not apply.

4 / 5

Progressive Disclosure

This is a ~50-line, single-purpose skill with no bundle files and no need for external references, organized under clear section headers (Find the Current Plan, Test-Plan Progress, After Testing Day, Release Changes, Builds and Handoff). Per the simple-skill guideline, well-organized sections alone warrant a 5; the one optional cross-skill reference is clearly signaled with a complete fallback path.

5 / 5

Total

19

/

20

Passed

Description

70%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 specific, distinctive description that clearly scopes the skill to VS Code endgame reporting with four concrete focus areas. Its main weakness is the absence of any explicit 'Use when...' trigger guidance, which both caps completeness and leaves some natural trigger phrases unsurfaced.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks for VS Code endgame status, test-plan progress, or release readiness during an endgame or recovery endgame."

Include natural trigger synonyms users might say, such as "testing day", "endgame report", or "release candidates", to broaden keyword coverage.

Consider mentioning the read-only nature ("reports without making changes") so it is distinguishable from skills that modify issues or releases.

DimensionReasoningScore

Specificity

The description names one action ("Report VS Code endgame status") with four concrete focus areas ("test-plan progress, tester activity, release-branch PRs, and release-build availability"), matching the anchor for several specific items with minor gaps in coverage. It falls short of anchor 5 because it uses a single reporting verb rather than multiple distinct concrete actions, and above anchor 3 because it enumerates more than 1-2 specific capabilities.

4 / 5

Completeness

The "what" is clear (report endgame status with four stated focus areas), but there is no "Use when..." clause or equivalent explicit trigger guidance; the "when" is only weakly implied by the topic itself. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural domain keywords are present — "endgame", "test-plan progress", "tester activity", "release-branch PRs", "release-build" — which a VS Code endgame champion would actually say. A few natural variations are missing (e.g., "testing day", "endgame report", "release readiness"), so it fits anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"VS Code endgame" is a highly specific, well-defined niche term with distinct triggers (endgame, test plan, release branch), making confusion with generic GitHub status or reporting skills unlikely. It clearly matches the anchor for a clear niche with minimal conflict risk, rather than anchor 4's minor overlap with closely related skills.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

microsoft/vscode

Path

.github/skills/endgame-status/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.