skills.rest
ririnto
ririntoCOMMUNITY
Explore all skills by this author →
GitHub

plugin-authoring

Align Claude Code plugin roots with paired manifests, README, and used runtime components.

Updated Apr 9, 2026
Search Tags:#codex#offline#plugin#manifests#authoring#claude-code#workspace-structure
One-click install
npx skills add https://github.com/ririnto/sinon --skill plugin-authoring-ririnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-authoring
Source: https://github.com/ririnto/sinon/tree/main/plugins/agent-capability-kit/skills/plugin-authoring
Command: npx skills add https://github.com/ririnto/sinon --skill plugin-authoring-ririnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or refactor one plugin root so paired manifests and the README match the filesystem layout, and optional runtime surfaces appear only when the plugin truly needs them.

Core Features & Use Cases

  • One-root plugin structuring: Aligns Claude Code and Codex plugin roots with coherent manifest pairs and README, removing unused runtime files.
  • Minimal, deterministic surfaces: Keeps only the components the plugin actually uses, simplifying maintenance and deployment.
  • Offline authoring workflow: Enables end-to-end plugin authoring from local files without network access.

Quick Start

Author a plugin root by arranging .claude-plugin/, .codex-plugin/, README.md, and only the required runtime components to match the actual plugin layout.

Frequently Asked Questions about plugin-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Claude Code plugin root with paired manifests?▼

Structure a Claude Code plugin root by aligning `.claude-plugin/` and `.codex-plugin/` manifests with a README and only the required runtime components to match the actual filesystem layout.

What is the best way to organize offline plugin authoring for multiple surfaces?▼

Offline plugin authoring is best organized by arranging local files into a single coherent root with paired manifests and minimal runtime surfaces, ensuring deterministic structure without network access.

Can I remove unused runtime components when refactoring a Codex plugin root?▼

Yes, refactoring a Codex plugin root removes unused runtime files to keep only the components the plugin actually uses, simplifying maintenance and deployment across project surfaces.

Do I need network access to create a Claude Code plugin with paired manifests?▼

No, the offline authoring workflow enables end-to-end plugin creation and reorganization from local files without requiring network access.

Why does my plugin manifest path correctness fail the agent marketplace contract?▼

Manifest path correctness fails when the paired manifests do not match the filesystem layout, requiring you to scope components and declare resources precisely to satisfy the agent marketplace contract.

Related Skills

Explore More Software Engineering Skills→
mattbobambrosemattbobambrose
1

rename-plugin

Rename plugins across marketplace files and update catalog entries.

Community
Intermediate
EmasoftEmasoft
4

plugin-validation-skill

Validate Claude Code plugin manifests, hooks, skills, MCP servers, and marketplace entries.

Community
Advanced
m2ai-portfoliom2ai-portfolio
4

self-healing-claudex

Orchestrate autonomous build-and-review loops pairing Claude planning with Codex adversarial review.

Official
Advanced
SSiertsemaSSiertsema

readme-generator

Generates README.md files from analyzed repository structure and contents.

Community
Intermediate