apm-package-author

Name: apm-package-author
Author: thomast1906

1installs53forks

How to install apm-package-author?

thomast1906/github-copilot-agent-skills/apm-package-author

$npx -y skills add thomast1906/github-copilot-agent-skills --skill apm-package-author

Installs into the current project.

Summary

Create, maintain, and troubleshoot APM (Agent Package Manager) manifests for distributing GitHub Copilot skills, agents, and MCP servers. USE FOR: creating apm.yml root manifests; creating packages/* sub-manifests; bundling MCP server config into a package; installing packages fr

Files · 1

View on GitHub

SKILL.md

1	# APM Package Author
2
3	APM ([docs](https://microsoft.github.io/apm/) · [GitHub](https://github.com/microsoft/apm)) distributes GitHub Copilot skills, agents, and MCP servers as versioned packages installable with one command. Use this skill to create manifests, wire MCP dependencies, or troubleshoot installs.
4
5	## When to Use
6
7	Use this skill when you need to:
8
9	- Create or update an `apm.yml` root manifest or `packages/*` sub-manifest for a GitHub Copilot skills/agents repository
10	- Bundle MCP server configuration into an APM package so consumers get MCP wired automatically on install
11	- Install a package from a GitHub repo using the APM CLI
12	- Troubleshoot APM install failures (missing `.vscode/mcp.json`, Codex CLI warnings, 404 errors, cached installs)
13
14	Do not use this skill for:
15	- General GitHub Copilot customization questions (use default agent)
16	- Creating `SKILL.md` files (use the `skill-creator` skill)
17	- Writing MCP server implementation code
18
19	Identify which task applies and jump to that section:
20
21	- Creating packages for a repo → [Package Creation Workflow](#package-creation-workflow)
22	- Installing a package into a project → [Install Commands](#install-commands)
23	- Something went wrong → [Troubleshooting](#troubleshooting)
24	- Detailed YAML reference → [references/manifest-patterns.md](references/manifest-patterns.md)
25	- MCP transport details → [references/mcp-config.md](references/mcp-config.md)
26
27	---
28
29	## Package Creation Workflow
30
31	### 1. Install APM CLI (if not already installed)
32
33	```bash
34	curl -sSL https://aka.ms/apm-unix \| sh # macOS / Linux
35	irm https://aka.ms/apm-windows \| iex # Windows (PowerShell)
36	```
37
38	Verify: `apm --version`
39
40	### 2. Decide the package structure
41
42	Choose based on how consumers will install:
43
44	\| Pattern \| When to use \|
45	\|---\|---\|
46	\| Single-concern package `packages/<topic>/apm.yml` \| One cohesive domain (e.g. terraform, diagramming, architect). Preferred. \|
47	\| Meta-package \| One package references other packages — lets users `apm install` everything at once. Good for a repo root `apm.yml`. \|
48
49	For a typical skills repo, use one `packages/<name>/` per domain plus a root `apm.yml` that pulls them all in. Read [references/manifest-patterns.md](references/manifest-patterns.md) for complete YAML examples of both patterns.
50
51	### 3. Scaffold each package directory
52
53	```bash
54	mkdir -p packages/<name>/.apm
55	touch packages/<name>/.apm/.gitkeep # APM writes its install cache here — directory must exist
56	```
57
58	The `.apm/.gitkeep` placeholder is mandatory — without the directory APM may fail to write the install cache.
59
60	### 4. Write the `apm.yml` manifest
61
62	Minimum required fields:
63
64	```yaml
65	name: my-package-name # kebab-case, must be unique
66	version: 1.0.0
67	description: >
68	One sentence describing what this bundle installs.
69	author: github-username
70	license: MIT
71	target: vscode # always set for VS Code projects
72
73	dependencies:
74	apm:
75	- owner/repo/.github/agents/my-agent.agent.md
76	- owner/repo/.github/skills/my-skill
77	```
78
79	Key rules:
80	- All `apm:` paths must be full `owner/repo/...` virtual paths — relative paths do not work.
81	- Exclude any skills marked 🚧 WIP. Comment them out with a reason so they're easy to re-add later: `# cost-optimization excluded — WIP`
82	- Agents can still be included even when their companion skills are WIP.
83	- `target: vscode` controls `apm compile` output format only — it does NOT suppress Codex CLI warnings about HTTP MCP servers (those are cosmetic; the install still succeeds).
84
85	If skills require MCP servers, add an `mcp:` block. Read [references/mcp-config.md](references/mcp-config.md) for transport types, Docker examples, and the Azure MCP exception.
86
87	### 5. Update the root `apm.yml`
88
89	Add the new package to the root manifest so `apm install owner/repo` installs everything:
90
91	```yaml
92	dependencies:
93	apm:
94	- owner/repo/packages/my-new-package
95	- owner/repo/packages/existing-package
96	```
97
98	### 6. Test the install
99
100	```bash
101	mkdir -p /tmp/apm-test/.vscode
102	cd /tmp/apm-test
103	apm install owner/repo/packages/<name>#your-branch --runtime vscode
104	```
105
106	Verify that `.vscode/mcp.json` was created (if the package has MCP deps) and that skills/agents landed in `.git

People who liked this also viewed

6 picks

Type

apm-package-author

1installs53forks

View on GitHub

How to install apm-package-author?

thomast1906/github-copilot-agent-skills/apm-package-author

$npx -y skills add thomast1906/github-copilot-agent-skills --skill apm-package-author

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# APM Package Author
2
3	APM ([docs](https://microsoft.github.io/apm/) · [GitHub](https://github.com/microsoft/apm)) distributes GitHub Copilot skills, agents, and MCP servers as versioned packages installable with one command. Use this skill to create manifests, wire MCP dependencies, or troubleshoot installs.
4
5	## When to Use
6
7	Use this skill when you need to:
8
9	- Create or update an `apm.yml` root manifest or `packages/*` sub-manifest for a GitHub Copilot skills/agents repository
10	- Bundle MCP server configuration into an APM package so consumers get MCP wired automatically on install
11	- Install a package from a GitHub repo using the APM CLI
12	- Troubleshoot APM install failures (missing `.vscode/mcp.json`, Codex CLI warnings, 404 errors, cached installs)
13
14	Do not use this skill for:
15	- General GitHub Copilot customization questions (use default agent)
16	- Creating `SKILL.md` files (use the `skill-creator` skill)
17	- Writing MCP server implementation code
18
19	Identify which task applies and jump to that section:
20
21	- Creating packages for a repo → [Package Creation Workflow](#package-creation-workflow)
22	- Installing a package into a project → [Install Commands](#install-commands)
23	- Something went wrong → [Troubleshooting](#troubleshooting)
24	- Detailed YAML reference → [references/manifest-patterns.md](references/manifest-patterns.md)
25	- MCP transport details → [references/mcp-config.md](references/mcp-config.md)
26
27	---
28
29	## Package Creation Workflow
30
31	### 1. Install APM CLI (if not already installed)
32
33	```bash
34	curl -sSL https://aka.ms/apm-unix \| sh # macOS / Linux
35	irm https://aka.ms/apm-windows \| iex # Windows (PowerShell)
36	```
37
38	Verify: `apm --version`
39
40	### 2. Decide the package structure
41
42	Choose based on how consumers will install:
43
44	\| Pattern \| When to use \|
45	\|---\|---\|
46	\| Single-concern package `packages/<topic>/apm.yml` \| One cohesive domain (e.g. terraform, diagramming, architect). Preferred. \|
47	\| Meta-package \| One package references other packages — lets users `apm install` everything at once. Good for a repo root `apm.yml`. \|
48
49	For a typical skills repo, use one `packages/<name>/` per domain plus a root `apm.yml` that pulls them all in. Read [references/manifest-patterns.md](references/manifest-patterns.md) for complete YAML examples of both patterns.
50
51	### 3. Scaffold each package directory
52
53	```bash
54	mkdir -p packages/<name>/.apm
55	touch packages/<name>/.apm/.gitkeep # APM writes its install cache here — directory must exist
56	```
57
58	The `.apm/.gitkeep` placeholder is mandatory — without the directory APM may fail to write the install cache.
59
60	### 4. Write the `apm.yml` manifest
61
62	Minimum required fields:
63
64	```yaml
65	name: my-package-name # kebab-case, must be unique
66	version: 1.0.0
67	description: >
68	One sentence describing what this bundle installs.
69	author: github-username
70	license: MIT
71	target: vscode # always set for VS Code projects
72
73	dependencies:
74	apm:
75	- owner/repo/.github/agents/my-agent.agent.md
76	- owner/repo/.github/skills/my-skill
77	```
78
79	Key rules:
80	- All `apm:` paths must be full `owner/repo/...` virtual paths — relative paths do not work.
81	- Exclude any skills marked 🚧 WIP. Comment them out with a reason so they're easy to re-add later: `# cost-optimization excluded — WIP`
82	- Agents can still be included even when their companion skills are WIP.
83	- `target: vscode` controls `apm compile` output format only — it does NOT suppress Codex CLI warnings about HTTP MCP servers (those are cosmetic; the install still succeeds).
84
85	If skills require MCP servers, add an `mcp:` block. Read [references/mcp-config.md](references/mcp-config.md) for transport types, Docker examples, and the Azure MCP exception.
86
87	### 5. Update the root `apm.yml`
88
89	Add the new package to the root manifest so `apm install owner/repo` installs everything:
90
91	```yaml
92	dependencies:
93	apm:
94	- owner/repo/packages/my-new-package
95	- owner/repo/packages/existing-package
96	```
97
98	### 6. Test the install
99
100	```bash
101	mkdir -p /tmp/apm-test/.vscode
102	cd /tmp/apm-test
103	apm install owner/repo/packages/<name>#your-branch --runtime vscode
104	```
105
106	Verify that `.vscode/mcp.json` was created (if the package has MCP deps) and that skills/agents landed in `.git

People who liked this also viewed

6 picks

Type