Add a plugin manifest and a marketplace file for Claude Code and Codex
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- json
- Ambito
- tooling
Direzione di ricerca
Read the Claude Code plugin marketplace documentation and the Codex plugin build documentation linked in the issue, then inspect README.md, CONTEXT.md, and the nine skills under skills/. Add the four specified manifest and marketplace files, validate with claude plugin validate ., and install from the local folder in both tools. Done means all nine skills load in each tool and README.md and CONTEXT.md describe the new installation process.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
The repository holds nine skills in the folder skills/, but it has no plugin manifest and no marketplace file. A skill is not a plugin: a plugin is a package that has a manifest file, and it can hold many skills. Without a manifest, Claude Code and Codex cannot install the nine skills with one command from a marketplace. The rule "The repository has no plugin manifest; installation currently installs individual skills" in CONTEXT.md describes this state today.
Proposed change
Make the repository root one plugin that contains the nine skills, and add one marketplace file that lists this plugin. Claude Code and Codex use different file names, so add both sets of files:
| Tool | Plugin manifest | Marketplace file |
|---|---|---|
| Claude Code | .claude-plugin/plugin.json |
.claude-plugin/marketplace.json |
| Codex | .codex-plugin/plugin.json |
.agents/plugins/marketplace.json |
The SKILL.md files in skills/ stay as they are. Both tools read them.
What is verified
- Claude Code requires a
name, anowner, and apluginsarray inmarketplace.json. Each entry inpluginsrequires anameand asource. The entrynamemust equal thenameinplugin.json. Source: https://code.claude.com/docs/en/plugin-marketplaces.md - Test run: a copy of
skills/with aplugin.json(fieldsname,description,version) and amarketplace.json(entry with"source": "./") passedclaude plugin validate. The only messages were warnings about a missing README, LICENSE, and icon in the test folder. This repository already has README.md and LICENSE. - Codex requires in each
plugins[]entry of.agents/plugins/marketplace.json:name,source,policy(withinstallationandauthentication), andcategory. Thesource.pathstarts with./and is relative to the repository root. The.codex-plugin/plugin.jsonfile has askillsfield, for example"./skills/". Source: https://developers.openai.com/codex/plugins/build/
What is not verified
- The Codex documentation does not say that a local entry can use
./to point at the repository root itself. If it cannot, use a Git entry with"source": "url", which the documentation names for a plugin at the repository root. - The Codex documentation gives no full example for
.codex-plugin/plugin.json. The required fields are not listed. - Nothing has been installed yet with
claude plugin marketplace addor withcodex plugin marketplace add. Onlyclaude plugin validateran. - When installed from a plugin, the skills get the plugin name as a prefix. The command
/issue_creationbecomes/<plugin name>:issue_creation. Check that this is acceptable.
Tasks
- Choose the plugin name. Proposal:
coding-agent-plugin. - Add the four files in the table above.
- Run
claude plugin validate .and fix every error. - Install the plugin in Claude Code from the local folder, then run
claude plugin details <plugin name>and check that all nine skills are listed. - Install the plugin in Codex from the local folder and check that all nine skills load. This test proves or removes the Codex assumption about the repository root.
- Replace the rule about "no plugin manifest" in CONTEXT.md, and add the plugin installation commands to README.md.
Acceptance
claude plugin marketplace add jeromeetienne/coding_agent_pluginfollowed by the plugin install command installs all nine skills in Claude Code.- The matching Codex commands install all nine skills in Codex.
- README.md and CONTEXT.md match the new state.
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 1
- Fork
- 0
- Merge medio
- 10m
- PR unite (30g)
- 11
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di jeromeetienne/coding_agent_plugin
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
jeromeetienne/coding_agent_plugin#29 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
jeromeetienne/coding_agent_plugin#7 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 Mezza giornata Idoneità per principianti 68/100
jeromeetienne/coding_agent_plugin#26 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
jeromeetienne/coding_agent_plugin#25 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
jeromeetienne/coding_agent_plugin#19 · 3 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di jeromeetienne/coding_agent_plugin
Issue simili
-
bug documentation
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
cqframework/vscode-cql#198 ·
-
bug documentation good first issue help wanted testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno
-
Show evidence time and supersede warnings in the memory inspectorForse già presa @Sinchanak-212 l’ha presa oggi. Apertaarea: ux good first issue priority: medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
rohit746/pdf-view.nvim#109 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
daeh/zotero-markdb-connect#187 ·