← 输入框|github.com|刷新
Skip to content

Adopt the Agent Plugins standard: flat skills/, one portable package - #9

Merged
Carlos Robles (croblesm) merged 2 commits into
mainfrom
standard/agent-plugins-flat-layout
Aug 27, 2026
Merged

Carlos Robles (croblesm) merged 2 commits into
mainfrom
standard/agent-plugins-flat-layout

Conversation

@croblesm

Copy link
Copy Markdown
Contributor

The strategy document adopted Agent Plugins 1.0.0, the vendor-neutral packaging standard where Microsoft is a core maintainer. Its discovery rule made our layout unusable.

The problem

"The fixed discovery location is skills/. Each immediate child directory containing a path named exactly SKILL.md ... is treated as one skill. Clients MUST NOT recursively search deeper descendants for additional skills."

Under skills/<domain>/<skill>/, a conforming client sees skills/drivers-and-connectivity/, finds no SKILL.md, and is forbidden from looking deeper. It loads nothing. No escape through the manifest either: the schema is closed and has no field for enumerating skill paths. Identical in 1.1.0.

What changed

skills/ is flat. Domain is metadata in the sidecar, generated into the README, llms.txt and the Hub. One layout now serves every channel: the portable package, the GitHub Copilot one-level rule, and gh skill's skills/*/SKILL.md convention.

plugin.json at the root, generated and validated against the published schema. Its ten permitted top-level fields are a closed set, so it is generated from package.json and the catalog rather than hand-written.

Four manifests removed. Codex, Cursor and Grok are all Agent Plugins clients, as are VS Code, GitHub Copilot, ChatGPT and Kiro, so the portable package serves them:

Removed .codex-plugin/ .cursor-plugin/ .grok-plugin/ .agents/plugins/
Kept .claude-plugin/, because Claude Code is the one client outside the standard
Generated surfaces 9 to 6

Re-verified after migrating

Not assumed, because the whole point of the change is what a client actually loads:

  • gh skill install . --from-local enumerates all 24
  • installing one lands flat, with its references/ directory intact
  • npx skills add -l finds the same 24
  • plugin.json validates against the published plugin.schema.json: no extra keys, all required present
  • parity, manifest both directions, sidecar schema, prefill contract, house rules all green

An unplanned benefit

Three of the four syndication destinations now need no reshaping at all. awesome-copilot, skills-for-fabric and the container repo are all flat skills/<name>/, which is exactly what we now are. Conforming removed the fan-out transform most likely to go wrong.

Still open

Nothing has been observed loading an Agent Plugins package. A manifest that validates is not a manifest that loads, and that is folded into issue #4. mcp.json joins the package when a hosted endpoint exists, not before, because a pointer to nothing is worse than an absent file.

Doing this at 24 skills cost an afternoon. At 142 it would have been a migration.

The strategy document adopted the Agent Plugins 1.0.0 standard, where Microsoft
is a core maintainer. Its discovery rule is fixed and non-recursive:

  The fixed discovery location is skills/. Each immediate child directory
  containing a path named exactly SKILL.md is treated as one skill. Clients
  MUST NOT recursively search deeper descendants for additional skills.

Under the domain-directory layout a conforming client saw skills/<domain>/, found
no SKILL.md inside it, and was forbidden from looking deeper. It would have
loaded nothing. The manifest offered no way out either: the schema is closed and
has no field for enumerating skill paths, and the rule is identical in 1.1.0.

So skills/ is now flat and the domain is metadata in the sidecar, generated into
the README, llms.txt and the Hub. One layout serves every channel: the portable
package, the GitHub Copilot one-level rule, and gh skill.

plugin.json is generated at the repository root and validated against the
published schema. Its ten permitted top-level fields are a closed set, so it is
generated from package.json and the catalog rather than hand-written, and it
cannot drift.

Four manifests are removed. Codex, Cursor and Grok are all Agent Plugins
clients, as are VS Code, GitHub Copilot, ChatGPT and Kiro, so the portable
package serves them. .claude-plugin/ stays because Claude Code is the one client
outside the standard. Generated surfaces went from nine to six, which is a real
reduction in what can drift.

Re-verified after migrating rather than assumed: gh skill install and npx skills
add both enumerate all 24 skills and install them flat, and a skill with a
references directory carries it across.

Doing this at 24 skills cost an afternoon. At 142 it would have been a migration.
The flat layout was a convention held up by nothing. Now a nested skill fails the
build, with the reason in the message rather than a rule id to look up.

This check lives here rather than in the skill linter because only a
repository-level tool knows where the skills root is. The linter is handed
individual skill directories, so it cannot tell what sits between the root and
the skill; the constitution records that split with enforced_by, and the
linter reports it as enforced elsewhere rather than claiming or ignoring it.

Verified by planting the exact mistake a contributor would make: grouping a
skill under a domain directory. It fails, and the message says the skill would
not load in any conforming client.
@croblesm
Carlos Robles (croblesm) merged commit 218eeac into main Aug 27, 2026
2 checks passed
@croblesm
Carlos Robles (croblesm) deleted the standard/agent-plugins-flat-layout branch August 27, 2026 22:45
Carlos Robles (croblesm) added a commit that referenced this pull request Sep 18, 2026
The author on every manifest is now Microsoft SQL, the description leads with
Microsoft SQL, and microsoft-sql is the first keyword.

Grok Build installs from .grok-plugin/marketplace.json, which this repository
stopped generating in PR #9, so `grok plugin install microsoft` had nothing to
read. It is generated again, in the source format Grok documents. AGENTS.md
listed .grok-plugin/ and .agents/plugins/ as generated when neither was; it now
names what the generator writes.

Cursor honours displayName now. It showed Microsoft SQL for this plugin, so the
comment claiming it ignores the field is replaced with that measurement.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant