Name: project-management
Rating: 79.2 (1 reviews)
Author: dotnet

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.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, expert-level reference: executable commands, real identifiers, sequenced workflows with error-recovery checkpoints, and no token waste on concepts Claude already knows. It tops every dimension.

Dimension	Reasoning	Score
Conciseness	The body is lean and command/code-first with no general-concept padding (no 'what is an issue' exposition); length is driven by genuinely needed GraphQL and command detail, every section earning its tokens.	3 / 3
Actionability	Provides fully executable `gh` commands with real node IDs and a complete, runnable Python GraphQL pagination loop — copy-paste ready, no pseudocode.	3 / 3
Workflow Clarity	Multi-step flows (create → addProjectV2ItemById → set sprint) are explicitly sequenced, with a 'Common errors and gotchas' recovery section, a sanitization checklist, and a 'show user before posting' checkpoint for batch/destructive ops.	3 / 3
Progressive Disclosure	No bundle files exist; this single SKILL.md is well-sectioned (Where things live, Tooling, Actions, Errors, Workflows), which satisfies the simple-skill allowance for progressive disclosure without external references.	3 / 3
	Total	12 / 12 Passed

Description

100%

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: concrete capabilities, explicit 'Use when' trigger, repo-scoped niche, and natural trigger terms. It caps no dimension and reads at the top of the rubric.

Dimension	Reasoning	Score
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' — matching the multiple-specific-actions anchor.	3 / 3
Completeness	States what it does ('GitHub issue and project-board management for the dotnet/msbuild repo') and an explicit 'Use when asked to...' trigger clause, satisfying both what and when.	3 / 3
Trigger Term Quality	Natural user-facing phrases like 'file/triage/update issues', 'post comments', 'move sprints', and 'audit items by sprint/status/assignee' give good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to the dotnet/msbuild repo and a specific project board, a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: dotnet/msbuild
Path: .github/skills/project-management/SKILL.md
Commit: c88db8e

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.