# Commands and Skills You work with Context through a handful of conversational entries. Everything else — the lifecycle CLI commands, the Indexers and the workflow's own step Skills — runs behind them, chosen by the current Route rather than typed by you. ```mermaid flowchart LR you["You, in plain language"] --> entry["Entry Skill
/c4a:context and others"] entry --> cli["context CLI
current Route"] cli --> step["Workflow step Skills"] cli --> idx["Indexer Skills"] step --> cli idx --> cli ``` ## Entries you invoke | Entry | Use it to | Example | | --- | --- | --- | | `/c4a:context` | Create a Context knowledge workspace, continue one, and run production, review, update and build | *"Build reviewed knowledge for ../billing-service for on-call engineers."* | | `/c4a:context-plan` | Plan a large project or a broad update in stages before production | *"Plan knowledge for these three repositories and the design folder."* | | `/c4a:context-inspect-search` | Ask questions against knowledge packages or approved knowledge, with sources | *"How are refunds retried? Cite the code."* | | `/c4a:context-repo-content` | Register or edit documentation and authored Skills in the same repository, without starting production | *"Register docs/ and .agents/skills as repository content."* | `/c4a:context` is the production entry for new and existing knowledge workspaces. The other three entries do not drive production themselves: a plan, an answer that points to a gap, or registered repository content is handed back to `/c4a:context` when knowledge should be produced. A conversation where Context is already active continues without invoking it again; ordinary coding or design conversations never start it on their own. To create a new Indexer, ask in plain language — *"Create an Indexer Skill for our RPC framework in ./skills"*. The `context-indexer-create` Skill picks this up; it is not a menu command. ## How each host spells them | Host | How entries appear | | --- | --- | | Claude Code | Plugin commands `/c4a:context`, `/c4a:context-plan`, `/c4a:context-inspect-search`, `/c4a:context-repo-content` | | Cursor | Commands `/c4a-context`, `/c4a-context-plan`, `/c4a-context-inspect-search`, `/c4a-context-repo-content` | | Codex | Skills invoked by name: `context`, `context-plan`, `context-inspect-search`, `context-repo-content` | | Local install into one repository (`context plugin install --local`) | The same entries without the `c4a` plugin namespace | Restart or refresh the host after installing or updating the plugin so it loads the current entries. See [Installation](). ## Skills that run on their own | Skill | When it runs | | --- | --- | | `context-code-indexer`, `context-markdown-indexer`, `context-note-indexer`, `context-sessions-indexer` | The Agent selects them for the current sources and requirements during planning and writing. Installing one makes it available; it is not enabled for every knowledge workspace. See [Community Indexers](). | | `context-inspect-search` | Also when a host or Bot configuration routes knowledge questions to it. | | Workflow step Skills: `work-production-stage`, `translate-site-locales`, `record-workspace-version`, the Indexer lifecycle steps, and `recover-workspace` | Each runs when the current Route selects its step — writing a production stage, translating the site, recording a version, or recovering a stuck task. | Indexer Skills are installed without a plugin namespace, so they keep the same names in every host. Every Skill in the Agent plugin, with its trigger and hand-off, is listed in the [Skills reference](). ## What you never need to type The lifecycle commands — `context source add`, `context review …`, `context build` and the rest — are run by the Agent with the exact revision the Route returns. You will see them in progress messages, but you describe goals instead. There is no `context continue` command: when the Agent starts, `context entry` and `context status` observe the knowledge workspace and return the next step. The full command list is in the [CLI Commands reference](). ## Requests you will use often | You want to | Say something like | Read more | | --- | --- | --- | | Start | *"Create a Context knowledge workspace in ./kb for …; readers are …"* | [Quick Start]() | | Add material | *"Add ../docs/refunds to the sources and re-plan the affected part."* | [Working with Agents]() | | Fix a page | *"Revise the retry page: the limit is five, not three."* | [Revising a Page]() | | Follow a change | *"The billing repository moved to a new release; update the affected pages."* | [Updating Knowledge]() | | Hand off review | Add a `CONTEXT_RUN_POLICY` block to the task | [Managed Mode and Review Policy]() | --- ## Sources - [context/plugins/context/README.md L19–L26 · 3b0ce0a]() - [context/packages/context-cli/README.md L78–L111 · 3b0ce0a]() - [context/packages/context-cli/README.md L61–L73 · 3b0ce0a]() - [context/ARCHITECTURE.md L358–L366 · 3b0ce0a]() - [context/plugins/context/skills/context-indexer-create/SKILL.md L1–L16 · 3b0ce0a]() - [context/packages/context-cli/README.md L43–L59 · 3b0ce0a]() - [context/plugins/context/README.md L72–L74 · 3b0ce0a]() - [context/plugins/context/README.md L10–L17 · 3b0ce0a]() - [context/plugins/context/README.md L14–L26 · 3b0ce0a]() - [context/plugins/context/README.md L74–L81 · 3b0ce0a]() - [context/packages/context-cli/context-workflow/graphs/workspace.yaml L331–L350 · 3b0ce0a]() - [context/packages/context-cli/README.md L94–L107 · 3b0ce0a]() - [context/packages/context/docs/getting-started.md L155–L157 · 3b0ce0a]() - [context/packages/context/docs/guides/agent-guide.md L17–L42 · 3b0ce0a]()