CtrlK
BlogDocsLog inGet started
Tessl Logo

item-management

Patterns for managing MSBuild item groups: Include/Remove/Update semantics, item metadata, batching with %(Metadata), transforms, per-item filtering, and cross-product batching pitfalls. USE FOR: diagnosing and fixing item group anti-patterns in .csproj files, reviewing item management for correctness, fixing CS2002 duplicate file warnings from SDK globbing, fixing targets that run more times than expected due to cross-product batching, fixing Include vs Update misuse on SDK-globbed items, fixing FileWrites registration for generated file clean support, moving generated files to IntermediateOutputPath. DO NOT USE FOR: target chain architecture (use target-authoring), property patterns (use property-patterns), incrementality (use incremental-build), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.

74

Quality

91%

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

83%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 concise, highly actionable pattern catalog with excellent BAD/GOOD examples and no token waste. Its one gap is the absence of an explicit diagnose→fix→verify workflow with validation checkpoints, which the description implies and the batch/destructive nature warrants.

Suggestions

Add a short diagnostic workflow with a validation checkpoint, e.g. after fixing a cross-product batching issue: rebuild and confirm the target runs the expected number of times / CS2002 warnings are gone.

Add a 'Verify your fix' checklist (rebuild, check target run count, run `dotnet clean` to confirm FileWrites registration) for the destructive/batch operations the skill covers.

Consider moving the full batching edge-cases and transform-syntax detail into a references/ file, leaving SKILL.md as a tighter overview with one-level-deep pointers.

DimensionReasoningScore

Conciseness

Lean throughout — tables, short code blocks, and one-line rules ('Exclude only works on Include', 'Update does not add items') that clarify non-obvious MSBuild semantics rather than padding concepts Claude already knows; every section earns its place.

5 / 5

Actionability

Fully executable copy-paste XML for every operation (Include/Remove/Update, batching via Outputs and task params, transforms, Exclude, conditional inclusion, PrivateAssets), plus BAD/GOOD contrast in Common Pitfalls that directly shows the fix.

5 / 5

Workflow Clarity

Well-organized by topic but it is a pattern catalog, not a sequenced diagnostic workflow; the description promises 'diagnosing and fixing' yet the body provides no validate/rebuild/verify checkpoint for the batch and .csproj-editing operations, triggering the destructive/batch cap of 3.

3 / 5

Progressive Disclosure

Clean section headers and self-contained organization with no nested references, but it is a ~150-line single-file monolith with no bundle files; deeper detail (full transform syntax, batching edge cases) could be offloaded to reference files.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplar description: concrete capabilities, natural trigger terms including a real error code and file extension, explicit use/don't-use guidance, and clear disambiguation from neighboring skills. Voice is appropriately third-person/imperative.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('diagnosing and fixing item group anti-patterns', 'fixing CS2002 duplicate file warnings', 'fixing FileWrites registration', 'moving generated files to IntermediateOutputPath') with comprehensive coverage of the item-management domain.

5 / 5

Completeness

Explicitly answers both 'what' ('Patterns for managing MSBuild item groups: Include/Remove/Update semantics, item metadata, batching...') and 'when' via concrete 'USE FOR:' / 'DO NOT USE FOR:' trigger clauses, satisfying the explicit-trigger requirement.

5 / 5

Trigger Term Quality

Includes natural user phrases and concrete signals — the real error code 'CS2002 duplicate file warnings', '.csproj files', 'targets that run more times than expected', and 'FileWrites' — covering synonyms, file extensions, and symptom language users actually say.

5 / 5

Distinctiveness Conflict Risk

The 'DO NOT USE FOR' clause explicitly disambiguates sibling skills (target-authoring, property-patterns, incremental-build, msbuild-antipatterns), giving it a clear niche with minimal conflict risk.

5 / 5

Total

20

/

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
dotnet/skills
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.