Skip to main content
hc
Submit
skillsFirst-partyReview first Safety ✓ Privacy ✓

Codex Plugin Creator Capability Pack Skill

Expert Codex plugin capability pack for safe plugin scaffolding, manifest quality, MCP integration, and maintainable distribution.

by JSONbored·added 2026-04-11·
Claude CodeCodexWindsurfGeminiCursorCLI
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first — review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Canonical URL
https://heyclau.de/entry/skills/codex-plugin-creator-capability-pack
Source URLs
https://github.com/openai/codex, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/codex-plugin-creator-capability-pack.mdx
Package URL
/downloads/skills/codex-plugin-creator-capability-pack.zip
Package SHA256
7ea59a73540f97320dc9819720d4dc25f6d117f44096d7aa6011a4857cced8f0
Safety notes
Scaffolds and validates plugin manifests and may run plugin or build commands; review generated manifests and scripts before installing or executing them.
Privacy notes
Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model., Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-11

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

—

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done

  • Source provenance statusRequired

    Marked as first-party.

    Done

  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done

  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done

  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done

  • Package verification flag

    Package marked verified.

    Done

  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending

  • Baseline comparison available

    No baseline peer selected yet.

    Pending

  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Difficulty

87/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done

  • Confirm metadata review state

    Listing has review metadata.

    Done

  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done

  • Review privacy notesRequired

    Privacy notes are present.

    Done

  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending

  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending

  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
Install & runtime1Permissions & scopes1General1

Safety & privacy surface

Safety & privacy surface

1 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens, third-party handling.

3 areas
  • SafetyExecution & processesScaffolds and validates plugin manifests and may run plugin or build commands; review generated manifests and scripts before installing or executing them.
  • PrivacyThird-party handlingInputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model.
  • PrivacyCredentials & tokensRedact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.

Safety notes

  • Scaffolds and validates plugin manifests and may run plugin or build commands; review generated manifests and scripts before installing or executing them.

Privacy notes

  • Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model.
  • Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.

Prerequisites

  • Plugin use case and scope
  • Manifest and MCP requirements
  • Deployment target constraints

Schema details

Install type
package
Reading time
9 min
Difficulty score
87
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
7ea59a73540f97320dc9819720d4dc25f6d117f44096d7aa6011a4857cced8f0
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-04-11
Retrieval sources
https://github.com/openai/codexhttps://github.com/modelcontextprotocolhttps://modelcontextprotocol.io/specification/
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the Codex plugin creator capability pack."

# Required output
1) Plugin architecture and capability boundaries
2) Manifest and permissions review
3) Security and observability checklist
4) Release and maintenance plan

About this resource

Knowledge Freshness

This capability pack is pinned to documentation verified on 2026-04-11.

Retrieval Sources

Core Workflow

  1. Define plugin scope, trust boundaries, and runtime dependencies.
  2. Build manifest with minimum required capabilities only.
  3. Validate tool behavior and failure paths with regression tests.
  4. Add observability and troubleshooting hooks.
  5. Publish with maintenance and compatibility policy.

Overview

This skill helps agents build practical plugins that stay secure and maintainable instead of becoming one-off brittle integrations.

Capability Scope

  • Plugin architecture and capability boundaries
  • Manifest quality and permission minimization
  • MCP tool interoperability guidance
  • Error handling and observability setup
  • Release governance and compatibility notes

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Production Rules

  • Minimize plugin permissions and document each permission reason.
  • Validate tool contracts against strict schema expectations.
  • Keep plugin error handling explicit and observable.
  • Ship updates with backward-compatibility notes when behavior changes.

Troubleshooting

Issue: Plugin has excessive privilege scope
Fix: reduce manifest permissions to explicit operational minimum.

Issue: Tool calls are inconsistent across clients
Fix: enforce contract tests against expected schema/shape.

Issue: Plugin errors are hard to diagnose
Fix: add request IDs, structured logs, and clear failure categories.

Output Contract

  1. Plugin plan with trust boundaries.
  2. Manifest with justification per permission.
  3. Validation and regression-test protocol.
  4. Maintenance and deprecation plan.
#codex#plugins#mcp#developer-tooling#capability-pack

Source citations

Add this badge to your README

Show that Codex Plugin Creator Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/codex-plugin-creator-capability-pack.svg)](https://heyclau.de/entry/skills/codex-plugin-creator-capability-pack)

How it compares

Codex Plugin Creator Capability Pack Skill side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field
Codex Plugin Creator Capability Pack Skill

Expert Codex plugin capability pack for safe plugin scaffolding, manifest quality, MCP integration, and maintainable distribution.

Open dossier
Codex Automations Orchestrator Capability Pack Skill

Expert automation-orchestration capability pack for designing safe, low-noise recurring Codex workflows with clear runbooks.

Open dossier
MCP Remote Server Trust Review Capability Pack Skill

Expert MCP remote server trust review capability pack for auditing OAuth flows, transport security, tool permissions, data exfiltration risk, and vendor scope before connecting Claude Code to third-party MCP servers.

Open dossier
Next stepsDiffers
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Open dossierAPI JSONOpen LLMOpen sourceNewsletterClaim listing
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2026-04-11Package verified2026-04-11Package not verified
Source provenanceDiffersSource-backedNo submission linkSubmission linkedSource submission
SubmitterDiffers——kiannidev
Install riskReview firstLow riskReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand———
Categoryskillsskillsskills
Sourcefirst-partyfirst-partysource-backed
AuthorJSONboredJSONboredkiannidev
Added2026-04-112026-04-112026-06-14
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo———
Safety notes✓Scaffolds and validates plugin manifests and may run plugin or build commands; review generated manifests and scripts before installing or executing them.✓Designs and runs automation workflows that can execute commands and trigger external actions; review each automation's permissions and triggers before enabling it.✓Remote MCP servers run outside Anthropic control; Claude Code MCP integration does not guarantee vendor security or data isolation. OAuth tokens issued to an MCP server may grant persistent access to third-party accounts until revoked in the vendor admin console. Tools that read, write, delete, or execute on external systems can cause irreversible production changes when invoked by the model. SSE and streamable HTTP transports must use TLS; do not approve cleartext remote endpoints on untrusted networks. This skill recommends scoping and approval steps; it must not add MCP servers or approve OAuth consent without explicit user authorization.
Privacy notes✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.✓MCP tool results can contain customer names, ticket contents, database rows, repository secrets, and internal URLs that should not be pasted into public issues. OAuth consent screens and server logs may expose account emails, organization identifiers, and access tokens if shared without redaction. Remote server vendors may retain prompts, tool arguments, and responses under their own privacy policies outside Anthropic data handling. Public trust-review summaries should describe risk categories and mitigations, not full tool schemas or live OAuth tokens.
Prerequisites
  • Plugin use case and scope
  • Manifest and MCP requirements
  • Deployment target constraints
  • Automation goals and success metrics
  • Notification channel
  • Operational owner
  • The remote MCP server URL, vendor documentation, and intended Claude Code or Desktop use case.
  • Access to the MCP server manifest, tool list, OAuth client registration details, and transport configuration.
  • Security or platform stakeholders available to review third-party data access before production rollout.
  • A concrete integration goal such as issue tracking, CRM lookup, database queries, or deployment automation.
Install
curl -L https://heyclau.de/downloads/skills/codex-plugin-creator-capability-pack.zip -o codex-plugin-creator-capability-pack.zip && unzip -o codex-plugin-creator-capability-pack.zip -d ./codex-plugin-creator-capability-pack
curl -L https://heyclau.de/downloads/skills/codex-automations-orchestrator-capability-pack.zip -o codex-automations-orchestrator-capability-pack.zip && unzip -o codex-automations-orchestrator-capability-pack.zip -d ./codex-automations-orchestrator-capability-pack
—
Config———
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Related guides

Source-backed guides for putting this to work.

guides

Adding Plugin Install Hints to Developer CLIs

Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by JPette1783
guides

Auditing MCP Client Configuration Before Team Rollout

Audit MCP client configuration before sharing it with a team.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by YB0y
guides

Building a Claude Code Plugin Marketplace

Publish a marketplace.json catalog on a git repo so users can /plugin marketplace add and /plugin install — including private-repo hosting.

Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by JPette1783

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.