SamuelAsherRivello/ai-skills-library

ai-skills-library-pull

Copy one named AI Skills Library skill or all valid library skills into global Codex skills.

ai-skills-library-push

Copy one named global Codex skill or all valid global skills into the local AI Skills Library checkout.

ai-skills-library-welcome

Confirm that the shared ai-skills-library Codex skills are installed and available in the current project.

ai-skills-create-game

Create and publish Babylon Lite games using the repository template, shared skills library, OpenSpec, and GitHub Pages. Default to single player; support requested multiplayer by extending and releasing the shared Colyseus server.

ai-skills-create-github-repo

Create a GitHub repository from the shared repository template and prepare its local checkout.

ai-skills-library-move-global

Move one or all valid project-local skills into global Codex skills.

ai-skills-library-move-project

Move one or all valid global Codex skills into the current project.

ai-skills-library-status

Compare library, Codex user, and current-project skills in one lean status report.

docker-sandbox-codex

Set up and use Docker Sandboxes to run Codex in isolated microVMs, including installation, authentication, skills, workspaces, and lifecycle management.

docker-sandboxes-status

Inspect a Docker Sandbox's actual workspace exposure, policies, ports, and network activity. Use from host PowerShell; do not use to start or nest sandboxes.

openspec-apply-change

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says "openspec apply", "opsx apply", or "openspec implement".

openspec-archive-change

Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".

openspec-commit-inclusive

Commit complete files related to one archived OpenSpec proposal while excluding wholly unrelated files.

openspec-dashboard

Open, set up, or inspect the local OpenSpecUI dashboard for an OpenSpec project. Check required CLI dependencies first, install or initialize missing pieces when authorized, and keep the dashboard read-only unless the user explicitly requests an action.

openspec-explore

Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when…

openspec-grill-me

Interview the user about an OpenSpec exploration, proposal, or standalone plan using consistent numbered choices and a recommended answer. Investigate codebase facts directly and reconcile confirmed decisions into authorized planning artifacts. Planning only;…

openspec-macro-finalize-sync-archive-commit-push

Run an ordered macro of OpenSpec finalization skills after apply: verify readiness, sync specs, archive, commit scoped files, then push normally when the remote branch is unchanged. Stop with clear blockers instead of creating release infrastructure, merging…

openspec-propose

Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says…

openspec-release-version

Release a repository through its checked-in GitHub Actions version workflow. Inspect the repository setup first; if required workflow/version infrastructure is missing, do not create it, and instead report why the repo is not release-ready.

openspec-sync-specs

Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says "openspec sync" or "opsx sync".

openspec-update-change

Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Also use when the user…