diff --git a/README.md b/README.md
index ceee905..1092d3a 100644
--- a/README.md
+++ b/README.md
@@ -96,6 +96,10 @@ npx @manningworks/projex remove project old-project --force
 
 The CLI automatically installs the `@manningworks/projex` package as a dependency, and copied components import types directly from it.
 
+### Agent skill
+
+The repo ships an agent skill at [`skills/projex/`](https://github.com/ManningWorks/Projex/tree/main/skills/projex) that teaches any coding agent to drive the Projex CLI end-to-end — `init`, components, content, and config. Install by copying `skills/projex/` into your agent's skills directory (e.g. `.claude/skills/`). Added in [PR #40](https://github.com/ManningWorks/Projex/pull/40).
+
 ## Documentation
 
 - [Full Documentation](https://projex.manningworks.dev)
diff --git a/packages/docs/src/cli.md b/packages/docs/src/cli.md
index 372bece..1d0c537 100644
--- a/packages/docs/src/cli.md
+++ b/packages/docs/src/cli.md
@@ -733,3 +733,9 @@ import { ProjectCard } from '@manningworks/projex'
 ```
 
 Both approaches work. The CLI gives you ownership of the code, while package imports are easier to update.
+
+---
+
+## Agent Skill
+
+Prefer to let a coding agent drive the CLI? The repo ships an agent skill at [`skills/projex/`](https://github.com/ManningWorks/Projex/tree/main/skills/projex) that teaches any coding agent to drive the Projex CLI end-to-end — `init`, components, content, and config. Install by copying `skills/projex/` into your agent's skills directory (e.g. `.claude/skills/`). Added in [PR #40](https://github.com/ManningWorks/Projex/pull/40).