docs: add Command Code as a native skills provider

Command Code has a native skills CLI (cmd skills add <owner/repo>) that
clones the repo, discovers every SKILL.md, and installs into
.commandcode/skills/ — no plugin manifest or copied files needed.

- README: add Command Code install block
- docs/commandcode-setup.md: setup guide (install/manage/usage, paths)
- docs/comparison.md: add Command Code to tooling reach

Verified end-to-end against addyosmani/agent-skills: add (all / -s / @branch /
path / --global / --force), list (+ -d), and remove (project / --global) via
the CLI, plus skill discovery in the TUI slash menu.

Signed-off-by: Vipul Gupta (@vipulgupta2048) <vipulgupta2048@gmail.com>
Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
Signed-off-by: Vipul Gupta (@vipulgupta2048) <vipulgupta2048@gmail.com>
This commit is contained in:
Vipul Gupta (@vipulgupta2048)andCommandCodeBot committed 2026-08-02 23:54:39 +05:30
1 parent 7829ffd90d
commit e8089ebe61
3 files changed
+85 -1

No files matched your search

+15
View File
@@ -176,6 +176,21 @@ Codex reads the root `skills/` directory directly through `.codex-plugin/plugin.
</details>
<details>
<summary><b>Command Code</b></summary>
Install natively with the built-in `cmd skills` command. Command Code clones the repo, discovers every `SKILL.md`, and installs into `.commandcode/skills/`:
```bash
cmd skills add addyosmani/agent-skills # pick skills to install (project)
cmd skills add addyosmani/agent-skills --global # install for all projects (~/.commandcode/skills/)
cmd skills add addyosmani/agent-skills -s spec-driven-development # install a specific skill
```
Installed skills show up in the TUI slash menu, e.g. `/spec-driven-development`. See [docs/commandcode-setup.md](docs/commandcode-setup.md).
</details>
<details>
<summary><b>Other Agents</b></summary>
+69
View File
@@ -0,0 +1,69 @@
# Using agent-skills with Command Code
[Command Code](https://commandcode.ai) has a native skills system. The built-in `cmd skills` command clones a GitHub repo, recursively discovers every `SKILL.md`, and installs the ones you pick.
The Command Code binary is available as `cmd` (and the aliases `cmdc` on Windows / `command-code`). The examples below use `cmd`.
## Install
**Project scope** (installs into `.commandcode/skills/` at the current git root — the default):
```bash
cmd skills add addyosmani/agent-skills
```
In an interactive terminal this shows a multi-select so you can choose which of the 24 skills to install. Pipe/non-interactive invocations install all discovered skills.
**Install a specific skill:**
```bash
cmd skills add addyosmani/agent-skills -s spec-driven-development
```
**User scope** (installs into `~/.commandcode/skills/`, available in every project):
```bash
cmd skills add addyosmani/agent-skills --global
```
**Other supported forms:**
```bash
cmd skills add addyosmani/agent-skills@main # a specific branch
cmd skills add addyosmani/agent-skills/skills/interview-me # a specific path in the repo
cmd skills add addyosmani/agent-skills --force # overwrite / update if already installed
```
## Manage
```bash
cmd skills list # list installed skills (project + user + bundled)
cmd skills remove spec-driven-development # remove a project-scoped skill
cmd skills remove spec-driven-development --global # remove a user-scoped skill
```
`--force` on `add` re-fetches and overwrites an existing skill, which is how you update to the latest version.
## Usage
Installed skills are discovered automatically and appear in the TUI slash menu, tagged `[skill]`:
```
/spec-driven-development [skill] Write a spec before writing code…
```
Type `/` to browse, or start typing a skill name to filter. Use `/skills` to enable/disable skills.
## Where skills live
Command Code discovers skills from these locations (project entries resolve against the nearest git root):
| Scope | Path |
|-------|------|
| Project | `.commandcode/skills/<name>/SKILL.md` |
| Project (agents-compat) | `.agents/skills/<name>/SKILL.md` |
| User | `~/.commandcode/skills/<name>/SKILL.md` |
| User (agents-compat) | `~/.agents/skills/<name>/SKILL.md` |
`cmd skills add` writes to `.commandcode/skills/` (project) or `~/.commandcode/skills/` (`--global`).
+1 -1
View File
@@ -23,7 +23,7 @@ People often ask how **agent-skills** relates to the two other "skills for codin
| **Entry points** | Slash commands mapped 1:1 to phases (`/spec` `/plan` `/build` `/test` `/review` `/code-simplify` `/ship`, plus `/webperf`), with a `/build auto` full-plan mode | Skill-chained pipeline (`brainstorming`, `writing-plans`, `subagent-driven-development`) | Slash commands (`/grill-me`, `/tdd`, `/to-prd`, `/diagnosing-bugs`, `/grill-with-docs`) |
| **Distinctive mechanisms** | Anti-rationalization tables and Red Flags in every skill; parallel review **personas** in `/ship`; reference checklists; a **three-tier eval framework** in CI | Subagent-driven development with a task reviewer (spec + quality) and a fix loop; git-worktree isolation; skills-that-write-skills, pressure-tested | The **grilling** primitive (one question at a time, design-tree walking); seam-based TDD; explicit user-invoked vs model-invoked split; issue-tracker integration |
| **Quality measurement** | Trigger, routing, and behavioral evals run against the catalog (in-repo, some in CI) | Pressure-testing methodology is core to its philosophy; the eval suite itself now lives in a separate repo | None shipped in-repo |
| **Tooling reach** | Claude Code, Cursor, Gemini CLI, Antigravity, OpenCode, Windsurf, Copilot, Kiro, Codex, plus the `npx skills` CLI | One of the widest and most actively churned surfaces: Claude Code, Codex, Cursor, Copilot CLI, OpenCode, Kimi, Factory Droid, Antigravity, Pi | Claude Code first, distributed via `npx skills add`; other agents work with varying fidelity |
| **Tooling reach** | Claude Code, Cursor, Gemini CLI, Antigravity, OpenCode, Windsurf, Copilot, Kiro, Codex, Command Code, plus the `npx skills` CLI | One of the widest and most actively churned surfaces: Claude Code, Codex, Cursor, Copilot CLI, OpenCode, Kimi, Factory Droid, Antigravity, Pi | Claude Code first, distributed via `npx skills add`; other agents work with varying fidelity |
| **Governance** | Actively reviews and merges community contributions; every skill ships an eval | Largely solo-authored; a substantial backlog of unmerged community PRs | Solo-authored, self-merged, developed openly in public |
| **Best for** | Driving a feature through every phase with a human checkpoint at each | Long, autonomous, reasoning-heavy or exploratory work | A pragmatic, battle-tested daily loop, strongest at requirements and TDD |