plugin-management
Discover and suggest relevant plugins, inspect app permissions and dependencies, and manage plugin connections or removal. Use when the user asks about plugins or when a task would materially benefit from an external app, account, service, or data source that available tools cannot access.
- License 许可
- MIT
- 最近更新
- 2026-09-22
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- plugin-management
- description
- Discover and suggest relevant plugins, inspect app permissions and dependencies, and manage plugin connections or removal. Use when the user asks about plugins or when a task would materially benefit from an external app, account, service, or data source that available tools cannot access.
03 SKILL.md 正文
Plugin Management
Use the Plugin Management app to discover useful integrations and manage existing plugins. Choose the most direct capability for the user's task before searching for anything new.
Choose the right capability
- Use an available built-in tool when it already provides the needed capability. General web search, image generation, memory, and sites do not require a plugin unless the user requests a specific external provider or a capability unavailable natively.
- Use an already connected plugin when it can complete the task.
- Search for a plugin when an external app, account, service, or data source would materially improve the result and no available tool can access it.
Infer plugin intent from the user's actual task. Requests involving email, calendars, messaging, documents, project management, customer systems, finance, or analytics may need an external integration even when the user never says "plugin," "install," or "connect."
Before saying an external service is unavailable, requesting pasted data, or proposing a manual workaround, determine whether a relevant plugin exists.
Find and suggest plugins
Call search_plugins with concise provider names, product names, or capability
keywords. For example, use Gmail, calendar, or project management, not
the entire user request. The currently available tools and any recommended
plugin list are not a complete directory.
When a relevant unconnected plugin would help, call suggest_plugins with its
exact returned plugin ID. Suggest the smallest useful set, preferably three or
fewer. Do not suggest plugins that are already installed or already pending.
Suggestions do not block the task. Continue any work that does not require the connection and briefly explain what still needs the user's action. Never claim a plugin is installed or connected without verification. Use its tools only after its individual connection is confirmed.
Manage existing plugins
- Use
get_app_permissionsto inspect a plugin's permissions. - Use
update_app_permissionsonly for a permission change the user requested. Ask before ambiguous, broad, or risky changes. - Use
get_plugin_dependenciesto inspect required apps or dependencies. - Use
uninstall_apponly when the user explicitly requests removal. Correct an obvious spelling mistake when the intended plugin is unambiguous, and pass its actual name without inventing an identifier.
Keep user-facing explanations focused on the task, connection state, and requested change. Do not expose internal tool names or claim actions happened without checking their results.
04 同仓库更多 Skills
skill-installer
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
skill-creator
Create or update a Codex skill with appropriately scoped instructions and any needed supporting resources.
review-agent
Perform a read-only, defect-first review of a specified code change and return every actionable finding. Use when another agent delegates review of uncommitted changes, a base-branch diff, a commit, or custom review instructions.
plugin-creator
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
openai-docs
Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when they refer to Codex—and for OpenAI APIs/products and ChatGPT Work. Also use for model choice/migration, prompting, SDKs, Responses, Realtime, agents, evals, and Chat/Work/Codex comparisons. Do not use for generic app/software tasks that merely mention Codex.
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.