Index of every page on this site: llms.txt
Make a skill

Skillgen

Keep your package skill current. After each release tag, Skillgen opens a pull request that updates the Skill in your repository. You review it and decide what merges.

Set up Skillgen

  1. Check your repository

    • A public GitHub repository with a published npm package. Its package.json sits at the root, or in a monorepo under packages/<name>/. Skillgen supports npm packages only.
    • A Skill in skills/<name>/SKILL.md beside that package.json. A root package may keep one SKILL.md at the root instead.
    • Up to 9 files and 64 KiB in total: SKILL.md and Markdown files under references/.
    • Release tags that match the package version, such as 1.4.0, v1.4.0 or name@1.4.0. If one tag releases several packages with Skills, each gets its own pull request. A tag older than the version on your default branch, such as a maintenance release, starts no run.
    • npm links each version to its tag commit, through provenance or gitHead.
    No Skill yet? Make a skill

  2. Turn it on for each repository

    Sign in to skilld with GitHub. Your account lists the public repositories you maintain that have a Skill. Turn Skillgen on for each one it should update. Skillgen never runs on a repository you did not turn on.

    Choose repositories

  3. Install the App

    On GitHub, choose Only select repositories, then pick the repositories you turned on.

    Install Skillgen
    • Contents: write. Skillgen pushes one branch for each release.
    • Pull requests: write. Skillgen opens the pull request.
    • It asks for no Actions, administration, or issues access.

  4. Review the pull request

    Skillgen starts with your latest tag when you install the App. If you turned the repository on after the install, it starts at your next tag. Each new tag starts another run. If npm has not published the version yet, the run waits. Each run must finish within an hour of starting.

    A model drafts the update from the tagged source with the skilld Harness. A separate review must accept it before anything reaches your repository. If the Skill needs no change, Skillgen opens nothing.

    Look for a pull request titled docs(skills): update for v1.4.0. It changes only your Skill's folder. Skillgen never overwrites a branch that already exists. You decide what merges.