skills/skills-cli/SKILL.md
Manage skills with the skills CLI for Codex, Claude Code, and Pi. Use for discovering, installing, listing, updating, removing, or initializing skills; skills.sh; lock-file restore; node_modules sync; and project vs global agent installation troubleshooting.
npx skillsauth add sjunepark/custom-skills skills-cliInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use bunx skills commands to manage skills.
bunx skills list for project scope and bunx skills list -g for global scope.bunx skills find <query> or bunx skills add <source> --list to discover options.https://github.com/sjunepark/custom-skills/tree/main/skills rather than the repo root or current working tree so installs can update across machines without exposing repo-local .agents/ and .claude/ skills.--copy -g -a claude-code -a pi so the skills live directly in ~/.claude/skills and ~/.pi/agent/skills and skills list -g reports Agents: Claude Code, Pi.~/.agents/skills installs are for intentional universal multi-harness sharing; they can make skills list -g report many agents for one skill.-g.bunx skills check then bunx skills update. For this repo's published skills, prefer reinstall-from-remote when converting from shared ~/.agents/skills installs to Claude Code + Pi only.bunx skills remove ... with matching scope/agent flags.bunx skills add <package-or-url>bunx skills add <source> --skill <name> -a <agent> [-g] -ybunx skills add <source> --allbunx skills add <source> --skill '*' --copy -g -a claude-code -a pi -ybunx skills list [-g] [-a <agent>]bunx skills find [query]bunx skills remove [skill...] [-g] [-a <agent>]bunx skills checkbunx skills updatebunx skills init [name]bunx skills experimental_installbunx skills experimental_sync--agent and --skill flags for reproducibility.--yes only for non-interactive runs.--copy or the goal is this repo's normal machine-global Claude Code + Pi setup.bunx skills list without -g reports project-visible skills for the current directory; do not use it to answer what is globally installed.. or ./skills, and do not use the repo root URL; use https://github.com/sjunepark/custom-skills/tree/main/skills.skills list -g to show only Agents: Claude Code, Pi for this repo's published skills, do not leave those installs in ~/.agents/skills; install them with --skill '*' --copy -g -a claude-code -a pi -y.--all for that setup. In the current skills CLI, --all expands to --skill '*' --agent '*' -y, which overrides the Claude Code + Pi restriction and recreates shared ~/.agents/skills installs.chezmoi add on live skills directories.Read references/cli.md for source formats, scopes, and practical command recipes.
development
Long-running systematic codebase review with a persistent ledger in reviews/. Use to plan review areas, continue the next review pass, check campaign status, triage findings with the user, or apply auto-tier fixes. Modes: plan, continue, status, triage, fix (default continue).
development
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, empty states, UX review, visual hierarchy, information architecture, accessibility, performance, responsive behavior, theming, typography, spacing, layout, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, design systems, tokens, live browser iteration, and ambitious visual effects. Not for backend-only or non-UI tasks.
development
Manually integrate Git branch work without blind mechanical merges. Use when merging, transplanting, or refactoring branch work; resolving conflicts; preserving source-branch intent in a clean current-branch structure; or auditing that source additions, removals, tests, and docs landed intentionally.
testing
Prepare, audit, set up, and guide Release Please releases. Use when releasing, preparing or reviewing a release PR, adding Release Please, classifying SemVer impact or breaking changes, writing Release Please-compatible Conventional Commit guidance, or documenting release criteria. Release work requires existing Release Please config; setup requires an explicit setup request.