CtrlK
BlogDocsLog inGet started
Tessl Logo

project-management

GitHub issue and project-board management for the dotnet/msbuild repo. Use when asked to file/triage/update issues, post comments, amend issue bodies, move sprints, bulk-update project board fields, or audit items by sprint/status/assignee.

69

Quality

85%

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

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 highly actionable, executable skill body with strong domain-specific gotchas and real command examples. Its weaknesses are modest redundancy and a monolithic structure that would benefit from splitting large reference blocks into separate files.

Suggestions

Split the bulk GraphQL pagination script and the 9-item gotchas catalog into separate files (e.g., references/bulk-queries.md, references/gotchas.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Collapse the duplicated single-item update methods — keep `gh project item-edit` as the primary path and reference the equivalent GraphQL mutation only where it adds value, noting the equivalence once.

Rewrite the "Common workflows" sketches as numbered steps with explicit validate→fix→retry checkpoints for the batch/destructive cases (bulk sprint moves, body overwrites) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Dense and almost entirely concrete commands/code with little padding and a sound assumption that Claude knows gh/GraphQL basics; minor redundancy (e.g., the GraphQL mutation that "works the same" as `gh project item-edit`) and a few superfluous inline comments keep it just below lean.

4 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout — real `gh` commands with concrete project/field IDs, a complete GraphQL pagination script, and specific single-item update commands covering the common cases.

5 / 5

Workflow Clarity

Multi-step sequences are sketched (e.g., create → addProjectV2ItemById → updateProjectV2ItemFieldValue) with validation present for risky ops (pre-post review, null guards, overwrite warnings), but checkpoints are scattered across a gotchas catalog rather than woven as explicit validate→fix→retry loops inside each workflow.

4 / 5

Progressive Disclosure

Good internal section structure, but the ~308-line doc is monolithic with no bundle files and large inline reference blocks (the bulk GraphQL script, the 9-item gotchas catalog) that would be better split into separate referenced files.

3 / 5

Total

16

/

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 specific, well-scoped description that clearly states both capability and trigger conditions in third-person voice. Trigger term coverage is strong though not maximally synonym-rich, which is the only minor gap.

DimensionReasoningScore

Specificity

Enumerates many concrete actions — "file/triage/update issues, post comments, amend issue bodies, move sprints, bulk-update project board fields, or audit items by sprint/status/assignee" — with comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both "what" ("GitHub issue and project-board management for the dotnet/msbuild repo") and "when" ("Use when asked to file/triage/update issues...") with concrete enumerated trigger phrases.

5 / 5

Trigger Term Quality

Strong natural triggers ("file issues", "post comments", "move sprints", "bulk-update", "audit items") that users would actually say, but fewer synonyms per concept than the anchor-5 example expects.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single repo ("for the dotnet/msbuild repo") with distinct, narrow triggers, giving a clear niche and minimal conflict risk with other skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
dotnet/msbuild
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.