Official agent skill

Autopilot Issue Delivery Worker

by microsoft in microsoft/apm

A skill your agent uses to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler.

OfficialMITAuto-check passedDevOps & Cloud

Install Autopilot Issue Delivery Worker

skills CLI
$ npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install microsoft/apm autopilot-issue-delivery-worker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/microsoft/apm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/autopilot-issue-delivery-worker .claude/skills/autopilot-issue-delivery-worker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
autopilot-issue-delivery-worker
GitHub stars
4k
Token cost
~1.7k tokens
SKILL.md length
751 words
Files
24 (incl. references, assets)
Skills in repo
27
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler.

  • Works in 4 steps: Caller ORIGIN / INVOCATION_MODE → GH_AW_* or GITHUB_ACTIONS -> unattended → gh api user --jq .login succeeds ->… → …
  • Implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler
  • SKILL.md covers Activation card, Inputs, ORIGIN and assignment and Gate (both selectors), plus 2 more sections
  • Calls gh and node

What it does

Autopilot Issue Delivery Worker is an agent skill from microsoft/apm, published by the product's own GitHub organization. Use this skill to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler. Queue signal is status/accepted or a named bounded accept; that is not permission. Requires fresh human-scope evidence from scripts/governance before any mutate. May reproduce a bug, implement the accepted change, and open a fix PR. Not a queue manager and not a triage scheduler. Works in the scheduler's session, a child session, Cloud Agent, Remote Agent, or Agentic Workflow.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 24 other files, including reference files and assets (for example `assets/acceptance-observer.md`, `assets/autopilot-triage-schema.json` and `assets/confidence-gate-rubric.md`).

It sits in DevOps & Cloud, covering Monitoring and alerting. It works with GitHub. The repository describes itself as: Agent Package Manager. The licence is MIT.

When your agent uses it

  • Implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler
  • Tasks that involve Monitoring and alerting

Example prompts

  • “/autopilot-issue-delivery-worker”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Caller ORIGIN / INVOCATION_MODE
  2. GH_AW_* or GITHUB_ACTIONS -> unattended
  3. gh api user --jq .login succeeds -> actor-session
  4. Else unattended (fail closed)

What it can do on your machine

Read from SKILL.md and the folder at commit 280b8a7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Autopilot Issue Delivery Worker loads about 1.7k tokens when it runs, and up to ~3.7k if it reads all its reference files. Until then it costs about 130 tokens; SKILL.md has 751 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~130
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/apm at commit 280b8a7, republished under its MIT licence (© microsoft). 751 words, ~1,746 tokens.

Download SKILL.mdSave it as .claude/skills/autopilot-issue-delivery-worker/SKILL.md (or your agent's skills folder). This skill also uses 23 other files; get the full folder from GitHub.
name
autopilot-issue-delivery-worker
description
Use this skill to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler. Queue signal is `status/accepted` or a named bounded accept; that is not permission. Requires fresh human-scope evidence from scripts/governance before any mutate. May reproduce a bug, implement the accepted change, and open a fix PR. Not a queue manager and not a triage scheduler. Works in the scheduler's session, a child session, Cloud Agent, Remote Agent, or Agentic Workflow.
activation_card
on

autopilot-issue-delivery-worker

Per-issue implementation worker. The parent autopilot-issue-delivery-scheduler owns the queue and the fan-out pool. You own exactly one ISSUE_NUMBER.

Do not pick more issues. Do not fill other slots.

Activation card

activation_card: on. Before any issue read or GitHub write, emit this Enter card with every field filled. Missing field -> stop.

text
skill: autopilot-issue-delivery-worker
skill_path: <resolved directory of this SKILL.md>
mode: run
subject: microsoft/apm#<issue-number>
path: delivery
intent: implement one already-selected issue
origin: unattended | actor-session
write: on | off
repo: microsoft/apm
issue: <positive integer>
invocation: agentic-workflow | actor-session

Rules:

  • write defaults to on when the caller omitted it.
  • write: off returns the filled template only. Do not assign, comment, label, edit, or open a PR.
  • write: on may assign @me (actor-session only) and implement inside the accepted scope. Unattended never assigns and never implements.
  • origin fail-closed unknown -> unattended.
  • One issue. Do not nest a scheduler path.

After the run, emit this Exit receipt:

text
skill: autopilot-issue-delivery-worker
subject: microsoft/apm#<issue-number>
path: delivery
write: on | off
assigned: yes | no | skipped
pushed: yes | no
approved: n/a

Inputs

  • ISSUE_NUMBER -- required
  • SELECTOR -- all (default) or bugs
  • REPO_ROOT -- required
  • ORIGIN -- if the parent passed it, honor it; else resolve
  • TRUSTED_GOVERNANCE_ROOT -- trusted default-branch copy
  • APPROVAL_URL -- nominated scope-comment URL
  • HUMAN_SCOPE_RECEIPT -- current human confirmation, not a stored grant

ORIGIN and assignment

Resolve ORIGIN before any GitHub write:

  1. Caller ORIGIN / INVOCATION_MODE
  2. GH_AW_* or GITHUB_ACTIONS -> unattended
  3. gh api user --jq .login succeeds -> actor-session
  4. Else unattended (fail closed)

INTENT is implement.

When ORIGIN is actor-session, assignment is a hard gate. It is the public signal of which user is working this issue. GitHub allows multiple assignees, so a read-then-add is not a claim. Before reproduce, edits, or a PR:

  1. Read current assignees. Ignore bot logins (github-actions, dependabot, copilot, web-flow).
  2. If another human is assigned, escalate. Do not steal.
  3. If unassigned, gh issue edit --add-assignee @me.
  4. Re-read assignees immediately. Continue only if @me is the sole human assignee. Being listed among several humans is not a claim.
  5. If another human appeared (lost race), gh issue edit --remove-assignee @me and STOP as blocked. Do not implement.
  6. If already assigned to @me alone, continue.
  7. Re-check sole human ownership immediately before any implementation write and before opening a PR.

Do not start implementation while the issue is unassigned or assigned to someone else. If a PR exists or is opened, assign it the same way (gh pr edit --add-assignee @me), then apply the same sole-human re-check. Do not request that actor as a reviewer. Never alter CODEOWNERS reviewRequests. If ORIGIN is unattended or unknown, skip assignee writes. A failed required assignee write is blocked.

Never write human decision labels. Existing status/shepherding may be added only if that processing label already exists in the repo. Do not apply status/accepted. Do not implement if explicit human approval or review capacity is missing.

Show full SKILL.md (333 more words)Show less

Gate (both selectors)

Refuse unless the issue already has status/accepted or the parent recorded a bounded accept. That is the queue signal, not permission. triage/recommended and status/triaged are not authorization. Escalate; do not implement.

Selector bugs also requires type/bug. Selector all accepts any type.

Then re-check human-scope evidence. Do not create another parser or roster; authority.cjs alone interprets the record. From TRUSTED_GOVERNANCE_ROOT (trusted default-branch copy, never the issue worktree):

node scripts/governance/eligibility.cjs --help
node scripts/governance/eligibility.cjs --repo microsoft/apm --issue N --approval-url URL

Require state: record-present with authorizes_implementation: false. That result is evidence, never permission; current snapshots cannot detect deleted withdrawals. Then require fresh explicit responsible-human confirmation for this issue's bounded scope. ORIGIN unattended never claims to have obtained it -- STOP and return blocked. ORIGIN actor-session may proceed only after the caller confirms in this session. Assignment, labels, eligibility reports, and prior receipts are not that confirmation. Any other state (withdrawn, error, missing tool) -- STOP.

Procedure

  1. Do not run the triage scheduler. Triage belongs to autopilot-issue-triage-scheduler. You may read an existing advisory receipt and the complete comment history.
  2. If ORIGIN is actor-session, pass the assignment hard gate first.
  3. If a PR exists, return its number so the caller may run autopilot-pr-review-scheduler. Do not request yourself as reviewer. Do not start PR review from this worker.
  4. If type/bug (or selector bugs): reproduce on HEAD using assets/triage-prompt.md (LEGIT / UNCLEAR / FIXED-AT-HEAD). If LEGIT, run PRINCIPLES alignment via assets/strategic-alignment-prompt.md. If greenfield and aligned: assets/fix-prompt.md (TDD + mutation-break), then open one PR.
  5. Otherwise follow assets/solution-pipeline-prompt.md and type-specific assets/implement-*.md. Open at most one PR. Author the body with pr-description-skill.

Return

JSON with issue, status (done / escalate / blocked / pr-opened / pr-in-flight), optional pr, and a one-line note. inspect status before reading pr or branch. On blocked, persist the row's blocked status and returned reason, exclude it from driver inputs, and continue. Malformed or wrong-issue returns also block. Only pr-opened returns are handed to autopilot-pr-review-scheduler. Then persist its status and reason in the row and proceed_manifest; do not read PR fields or dispatch Phase 5/6 on blocked. Do not auto-merge.

ASCII only.

© microsoft, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 23 other files (references, assets) in .agents/skills/autopilot-issue-delivery-worker of microsoft/apm.

  • SKILL.md
  • assets/acceptance-observer.md
  • assets/autopilot-triage-schema.json
  • assets/confidence-gate-rubric.md
  • assets/final-report-template.md
  • assets/fix-prompt.md
  • assets/ground-truth-table.md
  • assets/ideate-prompt.md
  • assets/implement-bug.md
  • assets/implement-docs.md
  • assets/implement-feature.md
  • assets/implement-refactor.md
  • assets/model-routing.md
  • assets/plan-panel-prompt.md
  • assets/plan-schema.json
  • assets/solution-pipeline-prompt.md
  • assets/strategic-alignment-prompt.md
  • assets/task-implement-prompt.md
  • assets/triage-digest-template.md
  • assets/triage-prompt.md
  • … and 4 more

Open the folder on GitHubat commit 280b8a7

Compare with similar skills

Autopilot Issue Delivery Worker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Autopilot Issue Delivery Worker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Autopilot Issue Delivery Worker this skillmicrosoft/apm4k—~1.7kAutomated safety check: PassMIT
Tool ConnectorZhixiangLuo/10xProductivity478—~925Automated safety check: PassMIT
Golang Samber Hotsamber/cc-skills-golang3.4k—~2kAutomated safety check: PassMIT
Admingrafana/skills279—~1.5kAutomated safety check: PassApache-2.0
Skill Findermizchi/skills356—~3.2kAutomated safety check: PassNone
Datasources Provisioninggrafana/skills279—~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • Tool Connector

    ZhixiangLuo/10xProductivity

    Connect any tool you use at work to your agent — including internal company tools, custom-built systems, deployment portals, incident trackers, internal knowledge bases, HR systems, and commercial…

    478 GitHub stars~925 tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Golang Samber Hot

    samber/cc-skills-golang

    In-memory caching in Golang using samber/hot — eviction algorithms (LRU, LFU, TinyLFU, W-TinyLFU, S3FIFO, ARC, TwoQueue, SIEVE, FIFO), TTL, cache loaders, sharding, stale-while-revalidate, missing…

    3.4k GitHub stars~2k tokensUpdated 7 days ago
    DevOps & CloudAuto-check passed
  • Admin

    grafana/skills

    Official

    Manage Grafana Cloud accounts — organizations, stacks, RBAC roles and assignments, SSO/SAML/OAuth/GitHub auth, service accounts for CI/CD, user invites, team membership, and API-driven provisioning.

    279 GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Skill Finder

    mizchi/skills

    Use ONLY when the user explicitly asks to discover or evaluate a skill from OUTSIDE the curated catalog — e.g., "find a Stripe skill", "is there a skill for X?", "evaluate this candidate before…

    356 GitHub stars~3.2k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed
  • Official

    Generate a copy-paste Grafana data source provisioning file (YAML or Terraform) for any plugin from its standardized settings schema on the plugins CDN.

    279 GitHub stars~2.8k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Oss Alternatives

    tinyfish-io/tinyfish-cookbook

    Find actively maintained open source alternatives to any paid SaaS tool or commercial API.

    2.2k GitHub stars~2.2k tokensUpdated 6 days ago
    DevOps & CloudAuto-check passed

More from microsoft/apm

All 27 skills in this repo
  • Cut Release

    microsoft/apm

    Official

    A skill your agent uses to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the…

    4k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Docs Corpus Audit

    microsoft/apm

    Official

    A skill your agent uses to run a holistic regrounding pass on the entire microsoft/apm documentation corpus against current source code, page-by-page, and emit surgical fixes for stale claims.

    4k GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed
  • Official

    A skill your agent uses to verify CLAIM-LEVEL grounding of a documentation page (or set of pages) against the source code.

    4k GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Official

    A skill your agent uses to write the PR description (PR body) for any pull request opened against microsoft/apm.

    4k GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed
  • Official

    Drive ONE already selected open pull request in microsoft/apm to mergeable.

    4k GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Apm Spec Guardian

    microsoft/apm

    Official

    A skill your agent uses to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline /…

    4k GitHub stars~4.9k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Autopilot Issue Delivery Worker

What does Autopilot Issue Delivery Worker do?

A skill your agent uses to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler. Autopilot Issue Delivery Worker is an agent skill from microsoft/apm, published by the product's own GitHub organization. Use this skill to implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler.

When should I use Autopilot Issue Delivery Worker?

Autopilot Issue Delivery Worker fits situations like: implement ONE microsoft/apm issue already selected by autopilot-issue-delivery-scheduler; tasks that involve Monitoring and alerting.

How do I install Autopilot Issue Delivery Worker in Claude Code?

Run `npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -a claude-code`. Or copy the skill folder (.agents/skills/autopilot-issue-delivery-worker in microsoft/apm) into .claude/skills/autopilot-issue-delivery-worker in your project. Claude Code loads it when a task matches its description.

How do I install Autopilot Issue Delivery Worker in Codex?

Run `npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -a codex`. Or copy the skill folder (.agents/skills/autopilot-issue-delivery-worker in microsoft/apm) into .agents/skills/autopilot-issue-delivery-worker in your project. Codex loads it when a task matches its description.

Can I use Autopilot Issue Delivery Worker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/apm --skill autopilot-issue-delivery-worker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/autopilot-issue-delivery-worker, .gemini/skills/autopilot-issue-delivery-worker, .github/skills/autopilot-issue-delivery-worker and .opencode/skills/autopilot-issue-delivery-worker in your project.

What does Autopilot Issue Delivery Worker need to run?

Going by SKILL.md and its folder, Autopilot Issue Delivery Worker needs the command-line tools its instructions call (gh and node).

Does Autopilot Issue Delivery Worker access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Autopilot Issue Delivery Worker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Autopilot Issue Delivery Worker use?

Autopilot Issue Delivery Worker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Autopilot Issue Delivery Worker use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2k tokens, read only when the agent opens those files.

What are the alternatives to Autopilot Issue Delivery Worker?

Skills that share tags, products or a category with Autopilot Issue Delivery Worker: Tool Connector (ZhixiangLuo/10xProductivity, 478 stars), Golang Samber Hot (samber/cc-skills-golang, 3.4k stars), Admin (grafana/skills, 279 stars) and Skill Finder (mizchi/skills, 356 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Autopilot Issue Delivery Worker?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/apm, which has 3,978 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 7, 2026.

Source: microsoft/apm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.