Claude Cursor Skill

create-skills-repo

**WORKFLOW SKILL** - Create or safely maintain a portable skills marketplace repository for multiple AI coding agents. INVOKES: bundled Node.js generator, standalone create-skill, standalone create-gh-pages-site, Vally, git, and gh. USE FOR: create a skills repo, scaffold an agen

LLM Mart · 0 points · 5 views 0 listing impressions 0 install-command copies
Download jongio-skills-skills_create-skills-repo-5345f8c.zip · 979 KB

Install

skills CLI npx skills add https://github.com/jongio/skills/tree/main/skills/create-skills-repo
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install jongio-skills@llmmart
Git git clone https://github.com/jongio/skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole jongio/skills collection as a plugin from our marketplace. Git is the plain clone.

README

create-skills-repo

Create or safely maintain a portable skills marketplace repository with all current cross-agent manifests, Vally validation, secure CI, Dependabot, a functional example skill, and an optional catalog.

Install

npx skills add jongio/skills --skill create-skills-repo

Reload skills, then ask:

/create-skills-repo create a skills marketplace for my organization

Local CLI

node scripts/cli.mjs create ./my-skills --owner-login octocat
node scripts/cli.mjs upgrade ./my-skills
node scripts/cli.mjs sync ./my-skills
node scripts/cli.mjs check ./my-skills
node scripts/cli.mjs dry-run upgrade ./my-skills

Catalog generation defaults on and composes the standalone create-gh-pages-site skill. If that skill is unavailable, creation stops before target writes and prints the exact install command. Use --no-catalog to opt out intentionally. The reusable skills-catalog template comes from the shared jongio/gh-pages-templates registry at an immutable commit.

The generated repository seeds the bundled canonical create-skill snapshot and uses its noninteractive fixture mode to create example-skill. This skill keeps individual authoring in the standalone tool.

Development tooling, the bundled authoring snapshot, and newly generated skills pin @microsoft/vally-cli to 0.18.0. The bundled shared tooling lockfile matches the authoring skill's pin so noninteractive repository creation works without installing dependencies. Intentional eval fixtures and unrelated template dependency snapshots remain unchanged.

Vally requires grader names to be unique across each eval file and at most 60 characters long. Strict-lint existing eval specs before running them.

Versioning

Creation accepts --package-version <semver> (default 1.0.0). Generated repositories include scripts/version-skills.mjs with check, sync, and bump <package|skill-name> <major|minor|patch> commands; add --dry-run to preview. package.version in the managed configuration is the aggregate source of truth, and each skill uses metadata.version in SKILL.md. Skill bumps also patch the aggregate plugin and update managed hashes transactionally. CI checks distribution version parity. Release commands hold shared locks during both planning and application. In the source marketplace, a create-skill release also refreshes its bundled metadata and patches the containing create-skills-repo release.

Generator sync preserves each discovered skill version. Upgrade reads the incoming bundled authoring skill's version, not a hard-coded 1.0.0. It rejects an authoring-skill downgrade and patches the aggregate when upgrading to a newer authoring-skill release. For legacy authored skills, sync preserves the existing marketplace version; run the generated version helper's sync to populate missing metadata. Private npm tooling versions and schema/template versions remain independent.

Safety guarantees

  • New repositories are completed in sibling staging directories.
  • Managed upgrades preflight all hashes and roll back a failed transaction.
  • User-modified managed files block the entire operation.
  • Unmanaged files are preserved.
  • check and dry-run write nothing.
  • GitHub plans contain argument arrays and are never executed by the CLI.
  • Git and GitHub writes require explicit approval outside the CLI.

Development

npm test
npm run eval:lint

Tests use injected composition fixtures because the canonical templates/repository/skills/create-skill/ snapshot is populated from the standalone skill by the repository coordinator.

License

MIT. See LICENSE.

Skill manifest

Create Skills Repository

Create and maintain a repository whose canonical skills/ directory is discoverable by GitHub Copilot, Codex, ChatGPT desktop, Claude Code, Cursor, Gemini CLI, and Agent Plugins compatible hosts.

Commands

Command Behavior
create Build a new repository in a sibling staging directory, validate it, then publish it locally in one rename.
upgrade Update the managed repository baseline and bundled create-skill snapshot.
sync Rebuild skill-derived manifests, documentation, and Dependabot entries.
check Report managed drift and registration drift without writing files.
dry-run Preflight create, upgrade, or sync and report the exact local changes without writing files.

Use the standalone create-skill skill for individual authoring.

Generated repositories include scripts/version-skills.mjs: use check, sync, or bump <package|skill-name> <major|minor|patch> (--dry-run previews). The managed config owns the aggregate version; skill metadata.version owns individual releases. Never reset discovered versions or hand-edit managed version mirrors. Private npm tooling versions are independent.

Read references/command-contract.md before running a command. Read references/generated-repository.md when reviewing the generated shape.

Workflow

  1. Resolve the target and requested command.

  2. For create, gather the owner login, owner name, repository name, visibility, display name, and description. Catalog generation is enabled unless the user explicitly opts out.

  3. Run the matching local command by absolute path while keeping the target workspace as the process context:

    node "<skill-dir>/scripts/cli.mjs" create "<target>" --owner-login "<login>"
    node "<skill-dir>/scripts/cli.mjs" upgrade "<target>"
    node "<skill-dir>/scripts/cli.mjs" sync "<target>"
    node "<skill-dir>/scripts/cli.mjs" check "<target>"
    node "<skill-dir>/scripts/cli.mjs" dry-run upgrade "<target>"
    
  4. If catalog generation is enabled, the generator must resolve create-gh-pages-site before creating a staging directory. If it cannot, stop and show the exact install command printed by the generator. Never substitute another site generator. Resolve the shared jongio/gh-pages-templates registry to a full commit SHA and pass it with --catalog-registry-ref, unless the user explicitly provides a reviewed local templates directory.

  5. If the canonical create-skill snapshot or its fixture capability is unavailable, stop before target writes. Never hand-build example-skill.

  6. Treat conflict status or exit code 2 as blocked. List every conflicting managed path. Do not force, delete, or overwrite user changes.

  7. Run the generated repository's validation:

    npm ci --prefix .github/tools/vally --ignore-scripts
    npm test --prefix .github/tools/vally
    
  8. Preview the catalog locally before proposing publication:

    npm ci --prefix site --ignore-scripts
    npm run dev --prefix site
    
  9. Read the returned githubPlan. It contains exact program and argument arrays and a binding hash. Show every command and the target repository to the user.

  10. Get explicit approval before each git or GitHub write. Execute only the approved arrays. Never infer approval from a flag, automation mode, or an earlier approval. Repository creation, push, Pages publication, and every later GitHub write retain their own approval gates.

Safety invariants

  • The CLI never imports a GitHub client or executes git or gh.
  • Catalog and example composition run only in a sibling staging directory.
  • check and dry-run never write files.
  • Managed files carry SHA-256 state. A user edit, deletion, symlink, or untracked collision blocks the full operation before target writes.
  • Upgrade and sync use a lock, immediate recheck, temporary files, and rollback so a reported failure leaves no partial managed update.
  • Unmanaged files and authored skills are preserved.
  • Input paths, identities, URLs, visibility, templates, and configuration keys are validated before use.
  • External tools receive argument arrays with shell: false.
  • Generated workflows use pinned action SHAs, least privilege, persist-credentials: false, ignored dependency lifecycle scripts, job timeouts, and trusted triggers.

Exit criteria

  • The requested command reports created, unchanged, updated, clean, or planned.
  • Conflict and drift results are not reported as success.
  • Generated validation passes.
  • Catalog preview is local until the owner explicitly approves publication.
  • No git or GitHub write occurs without its required approval.
Files (skills)
  • evals
    • create-skills-repo
      • eval.yaml 1.7 KB
        Loading…
  • references
    • command-contract.md 2.8 KB
      Loading…
    • example-skill.fixture.json 707 B
      Loading…
    • generated-repository.md 3.7 KB
      Loading…
  • scripts
    • arguments.mjs 2 KB · in bundle
    • catalog.mjs 8.2 KB · in bundle
    • cli.mjs 16.1 KB · in bundle
    • config.mjs 7.6 KB · in bundle
    • github-plan.mjs 1.5 KB · in bundle
    • managed-files.mjs 13.1 KB · in bundle
    • process-tools.mjs 10.5 KB · in bundle
    • render.mjs 11.8 KB · in bundle
    • repository-files.mjs 1.3 KB · in bundle
  • templates
    • catalog
      • skills-catalog
        • .github
          • workflows
            • deploy.yml 917 B
              Loading…
        • public
          • favicon.svg 246 B · in bundle
        • src
          • pages
            • index.astro 394 B · in bundle
        • .nojekyll 0 B · in bundle
        • .npmrc 38 B · in bundle
        • astro.config.mjs 132 B · in bundle
        • index.html 365 B · in bundle
        • package.json 293 B
          Loading…
        • README.md 126 B
          Loading…
        • template.json 192 B
          Loading…
    • repository
      • .agents
        • plugins
          • marketplace.json.template 382 B · in bundle
      • .claude-plugin
        • marketplace.json.template 332 B · in bundle
        • plugin.json.template 282 B · in bundle
      • .codex-plugin
        • plugin.json.template 282 B · in bundle
      • .cursor-plugin
        • marketplace.json.template 323 B · in bundle
      • .github
        • tools
          • vally
            • .npmrc 18 B · in bundle
            • package-lock.json 108.1 KB
              Loading…
            • package.json 431 B
              Loading…
        • workflows
          • skill-eval.yml 3.8 KB
            Loading…
          • skill-lint.yml 2.9 KB
            Loading…
        • dependabot.yml.template 321 B · in bundle
      • scripts
        • version-skills.mjs 417 B · in bundle
      • skills
        • create-skill
          • evals
            • create-skill
              • eval.yaml 5.1 KB
                Loading…
            • README.md 289 B
              Loading…
          • references
            • art-and-provenance.md 2.2 KB
              Loading…
            • fixture-mode.md 2.1 KB
              Loading…
            • repository-discovery.md 2.5 KB
              Loading…
          • scripts
            • art.mjs 6.7 KB · in bundle
            • create-skill.mjs 12.3 KB · in bundle
            • png.mjs 9 KB · in bundle
            • providers.mjs 5.1 KB · in bundle
            • registration.mjs 21 KB · in bundle
            • render.mjs 10.8 KB · in bundle
            • repository.mjs 9.4 KB · in bundle
            • versioning.mjs 6.7 KB · in bundle
            • versions.mjs 4 KB · in bundle
          • test
            • art.test.mjs 5.6 KB · in bundle
            • cli.test.mjs 10.8 KB · in bundle
            • helpers.mjs 4.1 KB · in bundle
            • png.test.mjs 7 KB · in bundle
            • providers.test.mjs 6.9 KB · in bundle
            • registration.test.mjs 14.4 KB · in bundle
            • render.test.mjs 6.1 KB · in bundle
            • repository.test.mjs 5.6 KB · in bundle
            • versions.test.mjs 11.7 KB · in bundle
          • .gitignore 29 B · in bundle
          • .npmrc 18 B · in bundle
          • .vally.yaml 65 B
            Loading…
          • LICENSE 1 KB · in bundle
          • package-lock.json 125.3 KB
            Loading…
          • package.json 1012 B
            Loading…
          • README.md 2.4 KB
            Loading…
          • SKILL.md 9.8 KB
            Loading…
          • thumbnail.png 354.7 KB · in bundle
      • test
        • distribution-manifests.test.mjs 5.9 KB · in bundle
      • .gitattributes 73 B · in bundle
      • .gitignore 87 B · in bundle
      • .vally.yaml 71 B
        Loading…
      • gemini-extension.json.template 114 B · in bundle
      • LICENSE 1.1 KB · in bundle
      • marketplace.json.template 221 B · in bundle
      • plugin.json.template 371 B · in bundle
      • README.md.template 2.4 KB · in bundle
  • test
    • catalog.test.mjs 6.4 KB · in bundle
    • cli.test.mjs 27.3 KB · in bundle
    • create-skill-parity.test.mjs 1.6 KB · in bundle
    • process-tools.test.mjs 15.8 KB · in bundle
    • validation.test.mjs 7.6 KB · in bundle
    • versioning.test.mjs 4.7 KB · in bundle
    • workflow.test.mjs 4.7 KB · in bundle
  • .npmrc 18 B · in bundle
  • .vally.yaml 65 B
    Loading…
  • LICENSE 1 KB · in bundle
  • package-lock.json 108.2 KB
    Loading…
  • package.json 1 KB
    Loading…
  • README.md 3.6 KB
    # create-skills-repo
    
    Create or safely maintain a portable skills marketplace repository with all
    current cross-agent manifests, Vally validation, secure CI, Dependabot, a
    functional example skill, and an optional catalog.
    
    ## Install
    
    ```sh
    npx skills add jongio/skills --skill create-skills-repo
    ```
    
    Reload skills, then ask:
    
    ```text
    /create-skills-repo create a skills marketplace for my organization
    ```
    
    ## Local CLI
    
    ```sh
    node scripts/cli.mjs create ./my-skills --owner-login octocat
    node scripts/cli.mjs upgrade ./my-skills
    node scripts/cli.mjs sync ./my-skills
    node scripts/cli.mjs check ./my-skills
    node scripts/cli.mjs dry-run upgrade ./my-skills
    ```
    
    Catalog generation defaults on and composes the standalone
    `create-gh-pages-site` skill. If that skill is unavailable, creation stops
    before target writes and prints the exact install command. Use `--no-catalog`
    to opt out intentionally. The reusable `skills-catalog` template comes from
    the shared `jongio/gh-pages-templates` registry at an immutable commit.
    
    The generated repository seeds the bundled canonical `create-skill` snapshot
    and uses its noninteractive fixture mode to create `example-skill`. This skill
    keeps individual authoring in the standalone tool.
    
    Development tooling, the bundled authoring snapshot, and newly generated skills
    pin `@microsoft/vally-cli` to `0.18.0`. The bundled shared tooling lockfile matches
    the authoring skill's pin so noninteractive repository creation works without
    installing dependencies. Intentional eval fixtures and unrelated template
    dependency snapshots remain unchanged.
    
    Vally requires grader names to be unique across each eval file and at most
    60 characters long. Strict-lint existing eval specs before running them.
    
    ## Versioning
    
    Creation accepts `--package-version <semver>` (default `1.0.0`).
    Generated repositories include `scripts/version-skills.mjs` with `check`,
    `sync`, and `bump <package|skill-name> <major|minor|patch>` commands; add
    `--dry-run` to preview. `package.version` in the managed configuration is
    the aggregate source of truth, and each skill uses `metadata.version` in
    `SKILL.md`. Skill bumps also patch the aggregate plugin and update managed
    hashes transactionally. CI checks distribution version parity.
    Release commands hold shared locks during both planning and application.
    In the source marketplace, a `create-skill` release also refreshes its bundled
    metadata and patches the containing `create-skills-repo` release.
    
    Generator sync preserves each discovered skill version. Upgrade reads the
    incoming bundled authoring skill's version, not a hard-coded `1.0.0`.
    It rejects an authoring-skill downgrade and patches the aggregate when upgrading
    to a newer authoring-skill release.
    For legacy authored skills, sync preserves the existing marketplace version;
    run the generated version helper's `sync` to populate missing metadata.
    Private npm tooling versions and schema/template versions remain independent.
    
    ## Safety guarantees
    
    - New repositories are completed in sibling staging directories.
    - Managed upgrades preflight all hashes and roll back a failed transaction.
    - User-modified managed files block the entire operation.
    - Unmanaged files are preserved.
    - `check` and `dry-run` write nothing.
    - GitHub plans contain argument arrays and are never executed by the CLI.
    - Git and GitHub writes require explicit approval outside the CLI.
    
    ## Development
    
    ```sh
    npm test
    npm run eval:lint
    ```
    
    Tests use injected composition fixtures because the canonical
    `templates/repository/skills/create-skill/` snapshot is populated from the
    standalone skill by the repository coordinator.
    
    ## License
    
    MIT. See [LICENSE](LICENSE).
    
  • SKILL.md 5.4 KB
    ---
    name: create-skills-repo
    description: >-
      **WORKFLOW SKILL** - Create or safely maintain a portable skills marketplace
      repository for multiple AI coding agents. INVOKES: bundled Node.js generator,
      standalone create-skill, standalone create-gh-pages-site, Vally, git, and gh.
      USE FOR: create a skills repo, scaffold an agent skills marketplace, upgrade a
      skills repository, sync skill manifests, check managed skills repo files, dry
      run a skills repository update. DO NOT USE FOR: authoring one skill (use
      create-skill), creating an unrelated GitHub Pages site (use
      create-gh-pages-site), or general repository health files (use repo-ready).
    metadata:
      version: "1.1.2"
    ---
    
    # Create Skills Repository
    
    Create and maintain a repository whose canonical `skills/` directory is
    discoverable by GitHub Copilot, Codex, ChatGPT desktop, Claude Code, Cursor,
    Gemini CLI, and Agent Plugins compatible hosts.
    
    ## Commands
    
    | Command | Behavior |
    |---|---|
    | `create` | Build a new repository in a sibling staging directory, validate it, then publish it locally in one rename. |
    | `upgrade` | Update the managed repository baseline and bundled `create-skill` snapshot. |
    | `sync` | Rebuild skill-derived manifests, documentation, and Dependabot entries. |
    | `check` | Report managed drift and registration drift without writing files. |
    | `dry-run` | Preflight `create`, `upgrade`, or `sync` and report the exact local changes without writing files. |
    
    Use the standalone `create-skill` skill for individual authoring.
    
    Generated repositories include `scripts/version-skills.mjs`: use `check`,
    `sync`, or `bump <package|skill-name> <major|minor|patch>` (`--dry-run` previews).
    The managed config owns the aggregate version; skill `metadata.version` owns
    individual releases. Never reset discovered versions or hand-edit managed
    version mirrors. Private npm tooling versions are independent.
    
    Read [references/command-contract.md](references/command-contract.md) before
    running a command. Read
    [references/generated-repository.md](references/generated-repository.md) when
    reviewing the generated shape.
    
    ## Workflow
    
    1. Resolve the target and requested command.
    2. For `create`, gather the owner login, owner name, repository name,
       visibility, display name, and description. Catalog generation is enabled
       unless the user explicitly opts out.
    3. Run the matching local command by absolute path while keeping the target
       workspace as the process context:
    
       ```sh
       node "<skill-dir>/scripts/cli.mjs" create "<target>" --owner-login "<login>"
       node "<skill-dir>/scripts/cli.mjs" upgrade "<target>"
       node "<skill-dir>/scripts/cli.mjs" sync "<target>"
       node "<skill-dir>/scripts/cli.mjs" check "<target>"
       node "<skill-dir>/scripts/cli.mjs" dry-run upgrade "<target>"
       ```
    
    4. If catalog generation is enabled, the generator must resolve
       `create-gh-pages-site` before creating a staging directory. If it cannot,
       stop and show the exact install command printed by the generator. Never
       substitute another site generator.
       Resolve the shared `jongio/gh-pages-templates` registry to a full commit SHA
       and pass it with `--catalog-registry-ref`, unless the user explicitly provides
       a reviewed local templates directory.
    5. If the canonical `create-skill` snapshot or its fixture capability is
       unavailable, stop before target writes. Never hand-build `example-skill`.
    6. Treat conflict status or exit code 2 as blocked. List every conflicting
       managed path. Do not force, delete, or overwrite user changes.
    7. Run the generated repository's validation:
    
       ```sh
       npm ci --prefix .github/tools/vally --ignore-scripts
       npm test --prefix .github/tools/vally
       ```
    
    8. Preview the catalog locally before proposing publication:
    
       ```sh
       npm ci --prefix site --ignore-scripts
       npm run dev --prefix site
       ```
    
    9. Read the returned `githubPlan`. It contains exact program and argument
       arrays and a binding hash. Show every command and the target repository to
       the user.
    10. Get explicit approval before each git or GitHub write. Execute only the
        approved arrays. Never infer approval from a flag, automation mode, or an
        earlier approval. Repository creation, push, Pages publication, and every
        later GitHub write retain their own approval gates.
    
    ## Safety invariants
    
    - The CLI never imports a GitHub client or executes `git` or `gh`.
    - Catalog and example composition run only in a sibling staging directory.
    - `check` and `dry-run` never write files.
    - Managed files carry SHA-256 state. A user edit, deletion, symlink, or
      untracked collision blocks the full operation before target writes.
    - Upgrade and sync use a lock, immediate recheck, temporary files, and rollback
      so a reported failure leaves no partial managed update.
    - Unmanaged files and authored skills are preserved.
    - Input paths, identities, URLs, visibility, templates, and configuration keys
      are validated before use.
    - External tools receive argument arrays with `shell: false`.
    - Generated workflows use pinned action SHAs, least privilege,
      `persist-credentials: false`, ignored dependency lifecycle scripts, job
      timeouts, and trusted triggers.
    
    ## Exit criteria
    
    - The requested command reports `created`, `unchanged`, `updated`, `clean`, or
      `planned`.
    - Conflict and drift results are not reported as success.
    - Generated validation passes.
    - Catalog preview is local until the owner explicitly approves publication.
    - No git or GitHub write occurs without its required approval.
    
  • thumbnail.png 441.9 KB · in bundle

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.