Index of every page on this site: llms.txt
All skills
github avatar

/add-community-extension

@61d3abb
by githubgithub/spec-kit151k stars
13,535
Run it yourself

Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension work.

Use this Skill: https://skilld.dev/gh/github/spec-kit/add-community-extension

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈87 tokens for metadata: the name and description. ≈1.7k when used: this file.

Description uses 4.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈349 characters, or 4.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Add Community Extension

Process an extension submission issue and add or update it in the community catalog.

When to Use

  • A new [Extension] submission issue is filed
  • An existing extension submits an update issue (new version, changed metadata)
  • You need to add or update a community extension in extensions/catalog.community.json and docs/community/extensions.md

Procedure

1. Fetch the submission issue

Read the GitHub issue to extract all metadata:

  • Extension ID, name, version, description, author
  • Repository URL, download URL, homepage, documentation, changelog
  • License, required spec-kit version, optional tool dependencies
  • Number of commands and hooks
  • Tags

2. Validate against publishing rules

Check all of the following (per docs/extensions/publishing.md):

Check How
Repository exists and is public Fetch the repository URL
extension.yml manifest present Confirm in repo file listing
README.md present Confirm in repo file listing
LICENSE file present Confirm in repo file listing
GitHub release exists matching version Check releases on the repo page
Download URL is accessible Validate the submitted URL first: scheme must be https, host must be exactly github.com, it must not include username/password, query string, or fragment, and its path must match archive/refs/tags/<tag>.zip or releases/download/<tag>/<asset>.zip; also verify the release exists. Only then fetch the archive with redirects enabled. Validate each redirect and the final URL against an explicit safe-host policy (github.com, codeload.github.com, or release-assets.githubusercontent.com) and require HTTPS; allow the signed query string used by release-assets.githubusercontent.com. Require the final response to be HTTP 200.
Extension ID is lowercase-with-hyphens only Regex: ^[a-z][a-z0-9-]*$
Version follows semver Format: X.Y.Z
Submission checklists are all checked Confirm in issue body

3. Determine if this is an add or update

Search extensions/catalog.community.json for the extension ID.

  • Not found → this is a new addition. Proceed to step 4.
  • Found → this is an update. Proceed to step 4 but replace the existing entry in-place instead of inserting.

4. Add or update extensions/catalog.community.json

New extension: Insert the entry in alphabetical order by extension ID.

Update: Replace the existing entry in-place. Update only the fields that changed (typically version, download_url, description, provides, requires, tags, updated_at). Preserve created_at and downloads/stars from the existing entry.

Use the existing entries as the format template. Entry format:

{
  "<id>": {
    "name": "<name>",
    "id": "<id>",
    "description": "<description>",
    "author": "<author>",
    "version": "<version>",
    "download_url": "<download_url>",
    "repository": "<repository>",
    "homepage": "<homepage>",
    "documentation": "<documentation>",
    "changelog": "<changelog>",
    "license": "<license>",
    "category": "<category>",
    "effect": "<effect>",
    "requires": {
      "speckit_version": "<speckit_version>"
    },
    "provides": {
      "commands": <N>,
      "hooks": <N>
    },
    "tags": ["<tag1>", "<tag2>"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "<today>T00:00:00Z",
    "updated_at": "<today>T00:00:00Z"
  }
}

Category — free-form string; common values: docs, code, process, integration, visibility Effect — one of: read-only, read-write

If the extension has optional tool dependencies, add a "tools" array inside "requires":

"tools": [{ "name": "<tool>", "required": false }]

Also update the top-level "updated_at" timestamp in the catalog.

After editing, validate the JSON by running:

python3 -c "import json; json.load(open('extensions/catalog.community.json')); print('Valid JSON')"

5. Add or update docs/community/extensions.md community extensions table

New extension: Insert a new row into the # Community Extensions table in alphabetical order by extension name.

Update: Find the existing row and update the description or other changed fields in-place.

Determine the category and effect from the extension's behavior:

| <Name> | <Description> | `<category>` | <Effect> | [<repo-name>](<repository-url>) |

Category — free-form; common values: docs, code, process, integration, visibility Effect — write canonical values read-only or read-write in extension.yml and catalog.community.json; use Read-only/Read+Write only for the docs table display

6. Commit, push, and open PR

Use add- for new extensions, update- for updates:

# New extension
git checkout -b add-<extension-id>-extension

# Update
git checkout -b update-<extension-id>-extension
git add extensions/catalog.community.json docs/community/extensions.md

# New extension
git commit -m "Add <Name> extension to community catalog

Add <id> extension submitted by @<issue-author> to:
- extensions/catalog.community.json (alphabetical order)
- docs/community/extensions.md community extensions table

Closes #<issue-number>"

# Update
git commit -m "Update <Name> extension to v<version>

Update <id> extension submitted by @<issue-author>:
- extensions/catalog.community.json (version, download_url, etc.)
- docs/community/extensions.md community extensions table

Closes #<issue-number>"

git push origin <branch-name>

Then create a PR to upstream (github/spec-kit) with:

  • Title: Add <Name> extension to community catalog (or Update <Name> extension to v<version>)
  • Body: Include validation summary, Closes #<issue-number>, and cc @<issue-author>
  • Head: <fork-owner>:<branch-name>
  • Base: main

Common Pitfalls

  • Alphabetical order matters — entries must be sorted by ID in the JSON and by name in the docs table.
  • Don't forget the catalog updated_at — the top-level timestamp in catalog.community.json must be refreshed.
  • Validate JSON after editing — a trailing comma or missing brace will break the catalog.
  • Use Closes not Fixes — Closes #N is the correct keyword for submission issues.
  • Match the proposed entry but verify — the issue may include a proposed JSON block, but always validate field values against the actual repository state.
  • Preserve created_at on updates — keep the original created_at value; only change updated_at.
  • Preserve downloads and stars on updates — these reflect usage metrics and must not be reset.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill processes community-submitted extensions from GitHub issues. While it includes robust validation for URLs and metadata, it is susceptible to indirect prompt injection because it ingests untrusted data from GitHub issue bodies to update local configuration files.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: MEDIUM · 1 issue

Signed by skilld at 61d3abb. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 days ago
argument-hint
GitHub issue URL or number for the extension submission

README badge

README badge for github/spec-kit/add-community-extension