Apollo Toolkit Skills

A curated skill catalog for Codex, OpenClaw, Trae, Agents, and Claude Code with a managed installer that keeps the toolkit in ~/.apollo-toolkit and copies each skill into the targets you choose.

Included skills

docs-project
archive
commit
exam-pdf-workflow
spec
implement
plan
improve-observability
init-project-html
learning-error-book
maintain-project-constraints
novel-to-short-video
openai-text-to-image-storyboard
optimise-skill
read-github-issue
qa
review
fix
systematic-debug
test-case-strategy
text-to-short-video
update-project-html
version-release
video-production

Install with npm or npx

shows a branded Apollo Toolkit terminal welcome screen with a short staged reveal
installs a managed copy into ~/.apollo-toolkit
lets you multi-select codex, openclaw, trae, agents, claude-code, or all
asks whether to install skills as symlinks (recommended) or file copies
lets you choose whether to include codex-exclusive skills in non-codex targets
copies or symlinks ~/.apollo-toolkit/<skill> into each selected target
removes stale previously installed skill directories that existed in the previous installed version but no longer exist in the current package skill list
replaces legacy symlink-based installs created by older Apollo Toolkit installers with real copied directories
writes a manifest (.apollo-toolkit-manifest.json) per target for future uninstall and skill tracking

Symlink vs Copy

Mode	Pro	Con
Symlink (recommended)	Auto-updates when you `git pull` in `~/.apollo-toolkit`; no need to re-run installer after patch updates	Changes pushed to the repo automatically reflect in your skills — you may receive updates you did not intend to accept
Copy	Stable snapshot; won't change until you re-run the installer	Must manually re-run `apltk` after each toolkit update to get the latest skills

Uninstall

apltk uninstall                    # Choose which agent targets to uninstall
apltk uninstall codex              # Remove only from codex
apltk uninstall codex agents --yes # Non-interactive cleanup for selected targets

The uninstall flow removes the manifest-tracked current and historical skill
directories for the selected targets, then removes each target manifest.

Global install

npm i -g @laitszkin/apollo-toolkit
apltk
apollo-toolkit

After global install, both apltk and apollo-toolkit launch the same Apollo Toolkit CLI. Running apltk directly opens the interactive installer page, which first checks the npm registry for newer versions; if one is available, the CLI prompts and auto-updates globally.

Beyond installation mode, apltk also exposes common skill scripts as simple CLI tools, for example:

apltk tools
apltk codegraph status --json
apltk create-specs "Membership upgrade flow" --change-name membership-upgrade-flow
apltk open-github-issue --help

# Browse architecture HTML atlas and active-spec diffs
apltk architecture          # opens resources/project-architecture/index.html
apltk architecture diff     # paginates docs/plans/**/architecture_diff/ vs atlas

# CodeGraph code intelligence (powered by @colbymchenry/codegraph)
apltk codegraph --help      # Discover current CodeGraph exploration commands
apltk codegraph <subcommand> --help

Before scripting or delegating any apltk command, inspect the current guidance with apltk --help, apltk tools, and the relevant apltk <tool> --help.

Non-interactive install

npx @laitszkin/apollo-toolkit codex
npx @laitszkin/apollo-toolkit agents
npx @laitszkin/apollo-toolkit claude-code
npx @laitszkin/apollo-toolkit codex openclaw
npx @laitszkin/apollo-toolkit all

Add --symlink (recommended) or --copy to skip the interactive prompt:

npx @laitszkin/apollo-toolkit codex --symlink
npx @laitszkin/apollo-toolkit all --copy

Optional overrides

APOLLO_TOOLKIT_HOME=~/custom-toolkit npx @laitszkin/apollo-toolkit codex
CODEX_SKILLS_DIR=~/custom-codex-skills npx @laitszkin/apollo-toolkit codex
OPENCLAW_HOME=~/.openclaw npx @laitszkin/apollo-toolkit openclaw
TRAE_SKILLS_DIR=~/.trae/skills npx @laitszkin/apollo-toolkit trae
AGENTS_SKILLS_DIR=~/.agents/skills npx @laitszkin/apollo-toolkit agents
CLAUDE_CODE_SKILLS_DIR=~/.claude/skills npx @laitszkin/apollo-toolkit claude-code

Local installer scripts

Installers still live in scripts/ for local repository usage and curl / iwr installation:

macOS/Linux: scripts/install_skills.sh
Windows (PowerShell): scripts/install_skills.ps1

Local usage

./scripts/install_skills.sh
./scripts/install_skills.sh codex
./scripts/install_skills.sh codex --symlink
./scripts/install_skills.sh all --copy
./scripts/install_skills.sh uninstall
./scripts/install_skills.sh uninstall codex trae

./scripts/install_skills.ps1
./scripts/install_skills.ps1 codex
./scripts/install_skills.ps1 agents --symlink
./scripts/install_skills.ps1 all --copy
./scripts/install_skills.ps1 uninstall
./scripts/install_skills.ps1 uninstall codex trae

Curl / iwr one-liners

curl -fsSL https://raw.githubusercontent.com/LaiTszKin/apollo-toolkit/main/scripts/install_skills.sh | bash
curl -fsSL https://raw.githubusercontent.com/LaiTszKin/apollo-toolkit/main/scripts/install_skills.sh | bash -s -- codex --symlink
curl -fsSL https://raw.githubusercontent.com/LaiTszKin/apollo-toolkit/main/scripts/install_skills.sh | bash -s -- uninstall

irm https://raw.githubusercontent.com/LaiTszKin/apollo-toolkit/main/scripts/install_skills.ps1 | iex

In curl / iwr mode, the scripts clone or update the managed toolkit copy under ~/.apollo-toolkit by default. Override with APOLLO_TOOLKIT_HOME if you need a different location.

External dependency skills

The install commands below were checked with the Skills CLI unless otherwise noted.

Skill name	Used by	Author / producer	Install command / note
`pdf`	`exam-pdf-workflow`, `financial-research`, `learning-error-book`, `weekly-financial-event-report`	OpenAI (`openai/skills`)	`npx skills add openai/skills@pdf -g -y`
`spreadsheet`	`record-spending`	OpenAI (`openai/skills`)	`npx skills add openai/skills@spreadsheet -g -y`
`remotion-best-practices`	`novel-to-short-video`, `video-production`	Remotion (`remotion-dev/skills`)	`npx skills add remotion-dev/skills@remotion-best-practices -g -y`
`code-simplifier`	`open-source-pr-workflow`	Sentry (`getsentry/skills`)	`npx skills add getsentry/skills@code-simplifier -g -y`

Compatibility note:

spec produces standardized specification documents. It can produce either a single spec set under docs/plans/{YYYY-MM-DD}/{change_name}/ or a coordinated parallel batch under docs/plans/{YYYY-MM-DD}/{batch_name}/{change_name}/ with shared coordination.md.
plan converts completed spec documents into a detailed execution plan (PROMPT.md) with dependency analysis, batch scheduling, and subagent routing. implement then reads PROMPT.md and executes mechanically without making its own coordination decisions.
read-github-issue uses GitHub CLI (gh) directly for remote issue discovery and inspection, so it does not add any extra skill dependency.
review is a local skill that reviews spec compliance of changes against governing planning documents, assessing business goals before secondary code-practice concerns. It outputs REPORT.md (issue list only, no solutions).
qa reads REPORT.md and spec documents to generate FIX.md — a complete fix plan with dependency analysis and subagent routing. fix then reads FIX.md and executes mechanically.
update-project-html is a local skill that depends on init-project-html for semantic rules and on the apltk architecture CLI to refresh the base atlas after code changes; for spec overlay diagrams use spec-to-project-html instead.

Code Intelligence: CodeGraph

The apltk codegraph subcommand system is built on @colbymchenry/codegraph, a tree-sitter-backed local code knowledge graph engine by Colt McHenry. Use it as a codebase exploration tool: start with apltk codegraph --help, then inspect subcommand help for the current command surface.

Special thanks to Colt McHenry for this excellent work, enabling LLM agents to discover code structure deterministically instead of relying on grep/Read.

Release publishing

GitHub Releases can publish the npm package automatically through npm Trusted Publishing.

Before the workflow can succeed, configure the npm package to trust this GitHub repository and the publish workflow. After that, creating a GitHub Release will trigger .github/workflows/publish-npm.yml and run npm publish --provenance --access public.

Notes

This repository is intended for personal toolkit curation and experimentation.
Skill folders are stored as regular files, not git submodules.

apollo-toolkit