Skip to content

chore(claude-directory): submit plugins/skillx in the developer portal and track listing metrics #151

Open

Description

@mrgoonie

Follow-up to #141. The plugin itself is built and verified in plugins/skillx/. The remaining step can only be done by a person.

Blocker

Submitting to the Claude directory goes through the developer portal (https://claude.ai/directory/manage). It must be done by an owner of the claude.ai organization that will own the listing long term; the first organization to submit a repository folder holds it. An agent session cannot do this.

Steps

The full procedure is in docs/claude-plugin.md#directory-submission.

  1. Submit new → Plugin bundle, with:
    • repository nextlevelbuilder/skillx
    • path plugins/skillx
    • branch main
  2. Click Validate and resolve anything marked Blocking.
  3. Submit. The expected reviewer hold is "Runs a pinned npx or uvx package" (skillx-sh@0.7.1).
  4. Optional: submit https://skillx.sh/api/mcp as an MCP connector and pair it with the listing.
  5. Record on this issue:
    • the submission link
    • the review status
    • after launch, the Usage tab figures: installs, skill runs, error rates

Done when

The listing is live (or its review outcome is recorded), and the links and metrics are written down here.

Activity

  1. self-assigned this
    on Oct 28, 2026
  2. clark-cant commented on Oct 31, 2026

    @clark-cant

    Verified the submission prerequisites on main at c95ab77 (2026-10-31T22:05Z). The bundle side is ready:

    • plugins/skillx/.claude-plugin/plugin.json is version: 2.0.0 and the root .claude-plugin/marketplace.json entry skillx is also 2.0.0, so the two agree as docs/claude-plugin.md requires.
    • .mcp.json declares one HTTP server, https://skillx.sh/api/mcp.
    • privacyPolicyUrl resolves to plugins/skillx/README.md#privacy and that ## Privacy heading exists.
    • docs/claude-plugin.md#directory-submission exists and matches the steps here: repository nextlevelbuilder/skillx, path plugins/skillx, branch main. The optional MCP-connector pairing in step 4 is the same endpoint.
    • help-visible commands used by the skill (search, check, prepare_install, install) all exist in the pinned CLI version.

    Two things to settle before pressing Submit:

    1. The pinned launcher is stale. plugins/skillx/skills/skillx/SKILL.md:27, plugins/skillx/README.md:39,51 and docs/claude-plugin.md:43,109 all pin npx --yes skillx-sh@0.7.1. npm latest is 0.8.0, and chore(main): release skillx-sh 0.9.0 #164 is queued to publish 0.9.0, which is the release that adds skillx add (feat(cli): lock, update and sync skills from skillx add; project scope, several runtimes, commit refs #168/feat(cli): add skillx add to install skills from GitHub, git URLs or local paths #120). Submitting at 0.7.1 is not broken, because the skill only calls search/check/prepare_install/install, but it ships a CLI two minors behind and forces an immediate follow-up plugin release. The documented rule is to raise the pin in a plugin release after that CLI version is on npm, so the clean order is: merge chore(main): release skillx-sh 0.9.0 #164, publish 0.9.0, then raise the pin to 0.9.0 together with plugin.json 2.0.0 -> 2.1.0 and the matching marketplace.json entry, then submit.
    2. No plugin tag exists yet. git tag holds only skillx-sh-v0.8.0 and older releases, so the claude plugin tag plugins/skillx agreement check in the docs has not been run for 2.0.0.

    The blocker stands as written: submission needs an owner of the claude.ai organization that should hold the listing, and the first organization to submit the folder owns it, so an agent session cannot do this step. When it is submitted, please record the submission link, the review status, and after launch the Usage tab figures (installs, skill runs, error rates) here; that is the only remaining part of the Done-when.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions