Quickstart

Get from clone to a working skill in under 5 minutes.

Prerequisites

1. Choose an Install Path

Source checkout

Use the source checkout when you are developing this repository or installing base skills from a local clone:

git clone <this-repo-url> ~/agentic-skills
cd ~/my-project
npx skillpacks init

npx skillpacks init installs repo-managed base skill directories project-local into the current repository's .claude/skills/ and .codex/skills/ roots and records base_skills: true in .agents/project.json. Track-latest installs are managed copies with drift metadata; pinned archived skills are the symlink case. Domain packs are not installed as base skills — that is intentional context hygiene.

npm CLI

With the published npm package, use npx skillpacks from the project that should receive local skills:

cd ~/my-project
npx skillpacks --version
npx skillpacks init
npx skillpacks list

The npm CLI installs base skills project-local only — there is no user-home (global) install path. npx skillpacks init installs base skills into the current repository's local .claude/skills/ and .codex/skills/ roots and records base_skills: true in .agents/project.json. Later npx skillpacks refresh updates those base skills from the package snapshot being run. To clean up deprecated user-home skillpacks state from the retired init path, run npx skillpacks cleanup --global; use npx skillpacks cleanup --global --dry-run to preview the cleanup first. Plain npx skillpacks cleanup removes stale BIP config from projects below the current directory. Domain packs are never installed as base skills.

The scoped alias package is published from the same release artifact and version. Users who prefer that package identity can run npx @glexcorp/gskp init, npx @glexcorp/gskp install devtool, and the same subcommands.

2. Install a Pack in Your Project

Navigate to any project repository and install the pack that matches your domain:

cd ~/my-project
npx skillpacks init
npx skillpacks install devtool    # for developer tools
npx skillpacks install game        # for games
npx skillpacks install business-research   # for SaaS/business apps

From a source checkout, the equivalent compatibility route is:

~/agentic-skills/scripts/pack.sh install devtool

This creates .agents/project.json and project-local skill roots in .claude/skills/ and .codex/skills/. init is the base-skill step; install is the domain-pack or individual-pack-skill step.

The npm CLI can also install a canonical deck from manifest metadata:

npx skillpacks install-deck business-afps
npx skillpacks install-deck devtool-afps
npx skillpacks install-deck game-afps

3. Reload Skills in Your CLI

Skills are not hot-reloaded. After installing:

4. Verify the Installation

Source checkout:

~/agentic-skills/scripts/pack.sh status

npm:

npx skillpacks status

Or from within Claude Code: run /init-agentic-skills (guided pack setup). From Codex: run $init-agentic-skills.

5. Run Your First Skill

The AFPS (Alignment First, Prototype Second) workflow is the default product workflow. A typical first cycle:

Claude Code:

/codebase-status          # see what you're working with
/idea-scope-brief         # shape a rough idea into a scoped brief

Codex:

$codebase-status
$idea-scope-brief

For projects with an existing tasks/todo.md:

/exec                     # execute the next planned step

6. Confirm It Worked

After running a skill, look for these artifacts:

Alignment page maintenance from npm is available through consumer-safe commands:

npx skillpacks alignment pages audit
npx skillpacks alignment pages serve --port 8907
npx skillpacks alignment pages open alignment/example.html --browser auto
npx skillpacks alignment pages inject-tts --force alignment/example.html

Source/package maintenance commands such as npx skillpacks alignment bundles --check and npx skillpacks alignment verify require a checkout with this repository's docs/, packs/, and focused test files. From a source checkout, the direct script paths remain available fallbacks: node scripts/upgrade-alignment-page.mjs, node scripts/audit-alignment-pages.mjs, node scripts/serve-alignment.mjs, node scripts/open-html-page.mjs, and node scripts/inject-tts.mjs.

One-off npx skillpacks ... works when the network is available or the npm cache is warm. For repeat or offline alignment workflows, add skillpacks as a devDependency in the target repo or use a pinned npm spec such as npx skillpacks@<version> alignment pages audit.

Migration Notes

Moving from a source checkout to npm does not change the project-local files. From the target project directory, run the npm command that matches your existing pack designation:

npx skillpacks refresh
npx skillpacks doctor

skillpacks@<semver> selects the package snapshot. Skill pins remain skill-level pins, for example npx skillpacks pin quality-sweep v0.0. If a pinned archive version is not present in the installed npm package, upgrade the npm package or use a source checkout that contains that archive.

What's Next