Repo-owned skills

Skills quickstart for coding-agent teams.

CortexPilot already ships a public, repo-owned skills quickstart here. The truthful adoption path today is: reuse repo-owned playbooks for Codex / Claude Code workflows, and adapt the same playbooks for adjacent tools such as OpenClaw without pretending CortexPilot is already a listed or shipped item inside those official plugin ecosystems.

Open the adoption path Open compatibility matrix See integration guide See builder quickstart See maintainer fast path

Need the fastest proof-first walkthrough before you adopt repo-owned skills? Open use-case guide.

What a CortexPilot skill is

Playbook

Repeatable behavior

A skill is a repo-owned playbook that tells an agent when to trigger, what to read first, what to avoid, and what “done” means.

Boundary

Truthful scope

Skills are not magic capability unlocks. They organize how agents work with the repo's real MCP, docs, contracts, and runbook boundaries.

Portability

Cross-agent reuse

The same playbook can guide Codex or Claude Code style workflows directly, and can also be adapted to adjacent coding-agent tools without inventing fake official support.

How to use skills today

  1. Start from this public guide, then choose the closest adoption lane: protocol, skills, builder packages, or proof-first cases.
  2. Read the tracked repo entrypoints before you start broad exploration or code changes.
  3. Use the skill together with the repo's truthful entrypoints: read-only MCP, API/client packages, docs, and Task Board.
  4. Keep the skill boundary honest: if a playbook says hosted or write-MCP is frozen, treat that as a real stop sign.

Best-fit usage by coding agent

Codex

Use repo-local skills as execution contracts around Command Tower, Workflow Cases, Proof & Replay, and repo-owned MCP/API surfaces.

Claude Code

Use the same skill pack when you want the repo's own safety rails, docs-first read order, and operator-facing truth layers.

OpenClaw

Use skills as an adaptation layer for repo truth. OpenClaw has real plugin and skills surfaces, but CortexPilot currently lands on the integration-and-skills side first rather than claiming an official shipped plugin.

What this page is not claiming

The truthful product story is smaller but stronger: the repository already gives teams reusable, inspectable skill playbooks that align with the real Command Tower / MCP / Proof & Replay contract.

Fast path for maintainers

sed -n '1,220p' README.md
sed -n '1,220p' docs/README.md
sed -n '1,220p' AGENTS.md

Those three tracked files are enough to understand the public product spine, the docs inventory, and the repo-owned AI working contract without depending on local-only overlays.

FAQ

Are skills the same as a plugin marketplace?

No. CortexPilot skills are repo-owned playbooks that guide agent behavior around the repo's real docs, MCP, contracts, and workflow boundaries.

Can Codex and Claude Code teams use these today?

Yes. The public skills quickstart is designed for Codex and Claude Code style workflows that need repeatable operating playbooks on top of the current Command Tower and proof surfaces.

How should OpenClaw teams interpret this page?

OpenClaw belongs in the adjacent coding-agent layer. Use this page as an adaptation guide for repo truth, not as a claim that CortexPilot already ships an official OpenClaw plugin package.

Does this page imply a hosted skill registry or write-capable MCP?

No. The current public story is repo-owned skills plus read-only MCP and current builder entrypoints, not a hosted skill registry or public write-capable MCP.