Official Provider SkillView repo
Add a new command (verb) to the DARC CLI. Use when asked to "add a darc command", "create a new darc verb", "add a darc operation", or extend the darc tool with a new subcommand.
Files1 files
SKILL.md51 lines
Loading editor…
Install
RecommendedOne command — your agent picks it up automatically.
Select an AI agent above to see the install command.
or
Manual Install
More stepsDownload the file and paste it into your agent's system prompt.
Skill details
Versionv1.0.0
Author.NET
Categorycoding
Skill IDdotnet/arcade-services/.github/skills/add-darc-command
Related skills
Arcade Services Failed Work ItemsList failed Product Construction Service (PCS/Maestro) work items in a time window and summarize retry-exhausted operations. Use for "list failed work items", "summarize PCS failures", or "what failed in Maestro". Teams-free and read-only; use arcade-services-work-item-analysis for root-cause investigation.Arcade Services Work Item AnalysisAnalyze one failed PCS/Maestro work item by operation ID, correlate exceptions and traces with repository source, and offer a local fix, PR, further analysis, or issue creation. Use for "why did this work item fail" or "analyze this PCS operation". Teams-free; read-only until an explicit follow-up decision.Arcade Services Work Item Analysis TeamsInvestigate a PCS/Maestro failure alert or selected failed work item and post findings to its Teams alert thread. Use for "investigate the Maestro alert and post findings", "reply to the pcs-workitem-failure-alert", or "analyze this work item and post to Teams". Reuses the Teams-free listing and analysis skills.Setup Dev EnvironmentSet up an arcade-services local development environment from zero by following docs/DevGuide.md. Use when asked to "set up my dev environment", "bootstrap local development", "get me running locally", or "configure the repo for local dev". Runs the automatable steps, verifies prerequisites, and flags the human-gated ones.Api ReviewAuthor and file a separate ASP.NET Core API review issue from an originating issue and an implementation pull request or commits. USE FOR writing API review issues, preparing api-ready-for-review proposals, filling API proposal templates, creating API review descriptions from issues and code changes, "fill out the API review", "prepare API review", or opening a pull request that changes public API. DO NOT USE FOR reviewing API design decisions, approving APIs, implementing APIs, or general code Review Public ApiReview a proposed public API for the dotnet/aspnetcore repo the way the @dotnet/aspnet-api-review team would, and recommend concrete changes to the API shape. USE FOR reviewing an API proposal or api-ready-for-review issue, critiquing a ref-assembly diff, deciding whether a new or changed type/method/overload/property should be added at all, evaluating whether an API change or addition is a good idea, changing/extending an existing API or a shipped default/convention, or checking naming/namespac