Summary
Several canonical skills under .agents/skills/ are inconsistent with the quality standards recently introduced in dynamo-skill-writer (see SetupUpdate branch). This issue tracks the proposed improvements.
Proposed changes
High priority
dynamo-dotnet-janitor
- Description is too vague to trigger reliably. Suggested replacement:
"Perform janitorial cleanup and modernization of C#/.NET code in Dynamo. Use when removing dead code, updating to modern C# syntax, resolving analyser warnings, fixing naming violations, or reducing technical debt — without changing behavior."
- Missing all standard sections:
When to use, When not to use, Inputs expected, Output format, Boundaries.
- References
microsoft.docs.mcp tool with no availability caveat — should be noted as optional.
dynamo-ecosystem-reviewer
- Body is ~12 lines with no standard sections:
When to use, When not to use, Inputs expected, Output format, Boundaries.
- Add these from the existing prose.
Medium priority
Add Boundaries sections (✅ Always / ⚠️ Ask first / 🚫 Never) to:
dynamo-dotnet-expert — relevant for PublicAPI.Unshipped.txt edits and public API changes
dynamo-jira-ticket — relevant for filing tickets in an external system
dynamo-onboarding — should be documented as read-only to prevent unintended edits
dynamo-ecosystem-reviewer — read-only review; easy to make explicit
Low priority
dynamo-content-designer and dynamo-ux-designer
- Both have a stray
metadata:\n version: "1.0" frontmatter field not present in any other skill.
- No functional impact but inconsistent; remove to keep frontmatter stable.
dynamo-codebase-patterns
- Launches directly into prose without
When to use / When not to use headers.
- Add these for consistency with the rest of the skill catalog.
Acceptance criteria
Summary
Several canonical skills under
.agents/skills/are inconsistent with the quality standards recently introduced indynamo-skill-writer(seeSetupUpdatebranch). This issue tracks the proposed improvements.Proposed changes
High priority
dynamo-dotnet-janitorWhen to use,When not to use,Inputs expected,Output format,Boundaries.microsoft.docs.mcptool with no availability caveat — should be noted as optional.dynamo-ecosystem-reviewerWhen to use,When not to use,Inputs expected,Output format,Boundaries.Medium priority
Add⚠️ Ask first / 🚫 Never) to:
Boundariessections (✅ Always /dynamo-dotnet-expert— relevant forPublicAPI.Unshipped.txtedits and public API changesdynamo-jira-ticket— relevant for filing tickets in an external systemdynamo-onboarding— should be documented as read-only to prevent unintended editsdynamo-ecosystem-reviewer— read-only review; easy to make explicitLow priority
dynamo-content-designeranddynamo-ux-designermetadata:\n version: "1.0"frontmatter field not present in any other skill.dynamo-codebase-patternsWhen to use/When not to useheaders.Acceptance criteria
dynamo-dotnet-janitordescription updated; standard sections added; optional tool noteddynamo-ecosystem-reviewerstandard sections addedBoundariessections added todynamo-dotnet-expert,dynamo-jira-ticket,dynamo-onboarding,dynamo-ecosystem-reviewermetadata:frontmatter removed fromdynamo-content-designeranddynamo-ux-designerWhen to use/When not to useheaders added todynamo-codebase-patterns.agents/README.mdQuick Reference descriptions updated where skill scope changed./.github/scripts/sync_agent_wrappers.ps1 -Check