Skip to content

Skills in the Dynamo Repo can be improved #17027

@QilongTang

Description

@QilongTang

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

  • dynamo-dotnet-janitor description updated; standard sections added; optional tool noted
  • dynamo-ecosystem-reviewer standard sections added
  • Boundaries sections added to dynamo-dotnet-expert, dynamo-jira-ticket, dynamo-onboarding, dynamo-ecosystem-reviewer
  • Stray metadata: frontmatter removed from dynamo-content-designer and dynamo-ux-designer
  • When to use / When not to use headers added to dynamo-codebase-patterns
  • .agents/README.md Quick Reference descriptions updated where skill scope changed
  • Wrapper sync check passes: ./.github/scripts/sync_agent_wrappers.ps1 -Check

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions