开发与测试
ai-coding-agents-plugins
Designs plugin systems for coding-agent runtimes and CLIs. Use when adding plugin manifests, extension points, built-in plugins, or reloadable agent integrations.
vasilyu1983 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add vasilyu1983/AI-Agents-public --skill ai-coding-agents-plugins技能说明
name: ai-coding-agents-plugins description: "Designs plugin systems for coding-agent runtimes and CLIs. Use when adding plugin manifests, extension points, built-in plugins, or reloadable agent integrations." compatibility: Portable core. Works on Claude Code and Codex. version: "1.1" last_validated: 2026-07-11
AI Coding Agents Plugins
Use this skill to design or review plugin systems for coding-agent runtimes, especially terminal-first CLIs that load skills, hooks, MCP servers, commands, agents, or output styles from installable extensions.
This skill owns plugin architecture for coding agents. For the broader coding-agent creation workflow, start with ../ai-coding-agents/SKILL.md.
ASCII Flow
plugin package
|
v
manifest validation
identity + version + capability declarations + trust class
|
v
install or load
built-in | user | project | marketplace | repo-local
|
v
registration
skills + commands + tools + hooks + agents + MCP servers
|
v
policy filter + namespace
only safe capabilities enter the runtime
|
v
reload/disable/uninstall invalidates caches and visible registries
Quick Reference
| Question | Read | Outcome |
|---|---|---|
| How should a coding-agent plugin be structured? | references/plugin-manifest-and-capability-model.md | Package layout, manifest fields, capability families |
| How should plugins load, reload, and register? | references/plugin-loading-and-runtime-lifecycle.md | Discovery order, activation flow, cache and reload rules |
| Where should trust boundaries live? | references/plugin-trust-boundaries-and-safety.md | Install-time safety, runtime restrictions, policy controls |
| How does OpenAI Codex structure plugin manifests and marketplace lifecycle? | references/openai-codex-plugin-manifest-and-marketplace.md | Skills/MCP/apps/hooks paths, interface metadata, path rules, marketplace add/remove/upgrade |
| How does GitHub Copilot CLI structure plugin manifests and marketplaces? | references/github-copilot-cli-plugin-manifest-and-marketplace.md | Manifest search order, component paths, marketplace.json shape, install sources, cross-runtime manifest convergence with Claude Code |
When To Use
- Design a plugin system for a coding-agent CLI or terminal runtime
- Add installable extensions that provide commands, skills, hooks, agents, or MCP servers
- Separate built-in capabilities from marketplace or repo-local plugins
- Define plugin manifests, capability registration, namespacing, or reload behavior
- Review whether a plugin architecture has safe trust boundaries and host-owned precedence
Use Other Skills
| Need | Use Instead |
|---|---|
| End-to-end coding agent or coding team design | ../ai-coding-agents/SKILL.md |
| MCP server design and connectivity | ../agents-mcp/SKILL.md |
| Hook authoring and lifecycle automation | ../agents-hooks/SKILL.md |
| Subagent definitions and delegation contracts | agents-subagents |
| Generic CLI and SDK design outside agent runtimes | ../software-devtools/SKILL.md |
| Skill packaging and shared-skills validation | ../agents-skills/SKILL.md |
Default Workflow
- Classify the extension surface. Decide whether the user actually needs a plugin, or just a local skill, hook, MCP server, or built-in command.
- Define capability families first. Model commands, skills, hooks, agents, output styles, and MCP servers as typed host-owned extension points.
- Choose the trust boundary. Decide what is allowed at install time, what is allowed at runtime, and which fields third-party plugin content is forbidden to control.
- Write the manifest contract. Keep identity, metadata, dependencies, and capability declarations in the manifest instead of relying on implicit folder discovery alone.
- Namespace plugin-provided components. Avoid collisions by having the host prefix commands, agents, and output styles with the plugin name or source.
- Define deterministic load order. Core runtime first, then built-ins, then installed plugins, then session-local overlays or inline plugins.
- Split plugin state into layers. Keep install intent, materialized on-disk plugin contents, and active in-memory components as separate layers.
- Design reload semantics explicitly. Separate cache clearing, component re-registration, and transport reconnection. Do not assume hot reload is safe for every capability type.
- Preserve partial success. A failing plugin should not take down the whole runtime if unaffected capability families can still be swapped safely.
- Validate with hostile cases. Test duplicate names, invalid manifests, blocked plugins, stale caches, plugin disable, and partial reload failures.
Host Rules
Use these defaults unless the runtime has a better documented model:
- Treat the host as the only authority on precedence, activation, and capability registration.
- Keep plugin manifests declarative. Avoid executing plugin code just to discover metadata.
- Make built-ins look like plugins to the UI and registry, but keep their trust and enablement rules host-controlled.
- Keep plugin-provided component names namespaced by plugin ID or plugin name.
- Allow third-party plugins to contribute capabilities, but do not let nested files silently escalate permissions beyond what the user approved at install time.
- Prefer reloadable registries for commands, agents, hooks, output styles, and MCP connections, but allow resta