Add a plugin manifest and a marketplace file for Claude Code and Codex
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- json
- Área
- tooling
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 1
- Forks
- 0
- Merge medio
- 10 min
- PR fusionados (30 d)
- 11
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de jeromeetienne/coding_agent_plugin
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
jeromeetienne/coding_agent_plugin#29 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
jeromeetienne/coding_agent_plugin#7 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 Medio día Aptitud para principiantes 68/100
jeromeetienne/coding_agent_plugin#26 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
jeromeetienne/coding_agent_plugin#25 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
jeromeetienne/coding_agent_plugin#19 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de jeromeetienne/coding_agent_plugin
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
bug documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
cqframework/vscode-cql#198 ·
-
bug documentation good first issue help wanted testing
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
Show evidence time and supersede warnings in the memory inspectorPosiblemente ocupada @Sinchanak-212 la tomó hoy. Abiertoarea: ux good first issue priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
rohit746/pdf-view.nvim#109 ·
Los mantenedores suelen responder en 1 día