chore: prepare the Codex manifest for submission - #37
Merged
Conversation
Bumps the Codex manifest to 0.1.3-beta. It was still on 0.1.0-beta, two releases and thirteen skills behind what the repo actually ships. Fixes the plugin source path in the agents marketplace file: the spec requires every path to start with `./`, and this one was a bare `.`. Deliberately NOT changed: policy.authentication is still ON_INSTALL. This plugin needs no authentication, so that value looks wrong, but the field is required and ON_INSTALL is the only value the published spec names. Asking before guessing at an enum in a submission manifest.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Two changes to the Codex-side manifests, ahead of submitting to the Codex directory.
.codex-plugin/plugin.jsonversion0.1.0-beta→0.1.3-beta.agents/plugins/marketplace.jsonsource.path"."→"./"Why
The version was two releases behind. The Codex manifest still declared
0.1.0-beta, which is the 18-skill wave-1 release. The repo ships 31 skills now. Submitting as-is would list a version that does not describe what a user gets.The source path violated the spec. The plugin docs state that every path must start with
./, and this one was a bare..Deliberately not changed
policy.authenticationis stillON_INSTALL. This plugin ships skills only — no MCP server, no API, nothing to authenticate against — so that value looks wrong, and the Claude manifest has no auth field at all. Butpolicy.authenticationis a required field andON_INSTALLis the only value the published spec names; it documents the field as "decide whether auth happens on install or first use" without enumerating the values or covering the no-auth case. Guessing at an enum in a submission manifest is worse than leaving the one documented value, so this needs an answer from the Codex side first.The same applies to
interface.capabilities, currently["Interactive", "Read", "Write"]. The spec shows["Read", "Write"]as an example and never enumerates the allowed values, so whetherInteractiveis valid — and whether we should be declaring something for the skills that run shell commands — is also worth confirming rather than guessing.Checked and fine
screenshots: []— the field is optional, so an empty array is not a submission blocker.assets/unity.svg(2,456 bytes) andassets/unity-small.svg(2,227 bytes).skills: "./skills/"matches the documented form.Note on version drift
.claude-plugin/plugin.jsonstays at0.1.2-betaon purpose; its next bump goes with #31. So the two manifests describe the same skill set under different version numbers until then.