apm-usage
- Repo stars 2,746
- Author updated Live
- Author repo apm
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @microsoft · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: apm-usage
description: > APM (Agent Package Manager) is the open-source package manager for AI coding agents. It lets t…
category: other
runtime: no special runtime
---
# apm-usage output preview
## PART A: Task fit
- Use case: > APM (Agent Package Manager) is the open-source package manager for AI coding agents. It lets teams install, share, and govern reusable instructions, prompts, agents, skills, and MCP server configurations across projects. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to activate / Key rules / Reference” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “> APM (Agent Package Manager) is the open-source package manager for AI coding agents. It lets teams install, share, and govern reusable instructions, prompts, agents, skills, and MCP server configurations across projects. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to activate / Key rules / Reference” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “When to activate / Key rules / Reference”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: apm-usage
description: > APM (Agent Package Manager) is the open-source package manager for AI coding agents. It lets t…
category: other
source: microsoft/apm
---
# apm-usage
## When to use
- > APM (Agent Package Manager) is the open-source package manager for AI coding agents. It lets teams install, share, a…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to activate / Key rules / Reference” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "apm-usage" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to activate / Key rules / Reference
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} APM Usage
APM (Agent Package Manager) is the open-source package manager for AI coding agents. It lets teams install, share, and govern reusable instructions, prompts, agents, skills, and MCP server configurations across projects.
When to activate
- User mentions
apmor "Agent Package Manager" - Questions about installing or managing AI-agent packages
- Setting up instructions, prompts, agents, skills, or chatmodes
- Configuring MCP servers through apm.yml
- Authentication for private repos (GitHub, ADO, GHES, Artifactory)
- Policy enforcement or
apm audit - Package authoring or publishing
- Compiling agent context (
apm compile) - Troubleshooting apm errors
Key rules
- Commit these files: apm.yml, apm.lock.yaml, .apm/, .github/, .claude/, .cursor/
- Never commit: apm_modules/ (add to .gitignore)
- Team sync: after
git clone, runapm installto restore dependencies - Update deps:
apm install --updaterefreshes to latest refs - Pin versions: use tags (
#v1.0.0) in production, branches for development - ASCII only: all CLI output and source must stay within printable ASCII
Reference
For detailed guidance, see the following resources:
- Installation -- install and update APM
- Workflow -- core workflow, apm.yml format, what to commit
- Commands -- full CLI command reference
- Dependencies -- all dependency formats and version pinning
- Authentication -- token setup for private repos
- Governance -- policy engine and audit checks
- Package Authoring -- creating APM packages
- Troubleshooting -- common errors and fixes
Decide Fit First
Design Intent
How To Use It
Boundaries And Review