📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
@@ -1,39 +1,47 @@
|
||||
# Codex CLI Skills
|
||||
# AAS Core with Codex CLI
|
||||
|
||||
If you want **Codex CLI skills** that are easy to install and practical in a local coding loop, this repository is designed for that exact use case.
|
||||
For Codex, the recommended AAS path is **AAS Core**: a local, agent-first control plane that lets Codex search and read every catalog skill, choose the exact IDs itself, and preserve that selection before anything is installed.
|
||||
|
||||
Agentic Awesome Skills supports Codex CLI through the `.codex/skills/` path and gives you a wide set of reusable task playbooks for planning, implementation, debugging, testing, security review, and delivery.
|
||||
The AAS MCP server is local and read-only. Codex can call `search_skills`, `get_skill`, `compose_stack`, `inspect_stack`, and `diff_stack`; changes remain in the CLI lifecycle, where `validate` and `plan` are preview operations and `apply` requires explicit approval.
|
||||
|
||||
Release `9.0.0` also adds a first-class Codex plugin distribution plus bundle plugins. If you want the full explanation of root plugin vs bundle plugin vs full install, read [plugins.md](plugins.md).
|
||||
Start with the [AAS Core guide](aas-core.md). Direct skill installation and Codex plugins remain supported when you already know exactly which payload you want.
|
||||
|
||||
> **Preview status:** Complete catalog search, agent-owned selection, manifest validation, and planning are the documented path. Stop after plan review; apply and recovery remain experimental.
|
||||
|
||||
## How to use Agentic Awesome Skills with Codex CLI
|
||||
|
||||
Install the library into your Codex path, then invoke focused skills directly in your prompt. The most common pattern is:
|
||||
Configure AAS Core for Codex, then describe the real task instead of manually searching a large directory. The normal flow is:
|
||||
|
||||
1. install with `npx agentic-awesome-skills --codex`
|
||||
2. choose one workflow-oriented skill such as `@brainstorming`, `@concise-planning`, or `@test-driven-development`
|
||||
3. ask Codex to apply that skill to a concrete file, feature, test, or bugfix
|
||||
1. Codex discovers the local AAS MCP tools.
|
||||
2. Codex searches and reads the complete catalog, then chooses the exact skills using its project understanding.
|
||||
3. Codex calls `compose_stack` and proposes `aas-stack.json` for you to review.
|
||||
4. The AAS CLI validates the manifest and previews the exact plan.
|
||||
5. Stop after reviewing the plan unless you are deliberately participating in controlled preview development.
|
||||
|
||||
## Why use this repo for Codex CLI
|
||||
|
||||
- It supports Codex CLI with a dedicated install flag and a standard skills layout.
|
||||
- It gives Codex native, complete local catalog discovery through MCP.
|
||||
- It keeps the agent's exact selection, project profile, validation, and planning inspectable.
|
||||
- It separates read-only agent tools from approval-gated CLI mutations.
|
||||
- It is strong for local repo work where you want to move from planning to implementation to verification without changing libraries.
|
||||
- It includes both general-purpose engineering skills and deeper specialist tracks.
|
||||
- It gives you docs and bundles, not just raw skill files.
|
||||
- It still supports direct installs and plugin distributions as delivery surfaces.
|
||||
|
||||
## Install Codex CLI Skills
|
||||
## Direct install and plugins
|
||||
|
||||
Use a direct install only when you intentionally want the library copied into Codex's skills path:
|
||||
|
||||
```bash
|
||||
npx agentic-awesome-skills --codex
|
||||
```
|
||||
|
||||
If you prefer a plugin-style Codex integration, this repository also ships repo-local plugin metadata in `.agents/plugins/marketplace.json` and `plugins/agentic-awesome-skills/.codex-plugin/plugin.json`.
|
||||
For plugin-style packaging, this repository also ships repo-local metadata in `.agents/plugins/marketplace.json` and `plugins/agentic-awesome-skills/.codex-plugin/plugin.json`.
|
||||
|
||||
It also generates bundle-specific Codex plugins so you can install a curated pack such as `Essentials` or `Web Wizard` as a marketplace plugin instead of loading the full library.
|
||||
|
||||
Those Codex plugins are plugin-safe filtered distributions. Skills that still depend on host-specific paths or undeclared setup stay in the repository, but are not published into the Codex plugin until they are hardened.
|
||||
|
||||
For the canonical explanation of how Codex plugins relate to the full library and bundle installs, read [plugins.md](plugins.md).
|
||||
For the canonical explanation of how Core, Codex plugins, and direct installs relate, read [plugins.md](plugins.md).
|
||||
|
||||
### Verify the install
|
||||
|
||||
@@ -51,6 +59,14 @@ test -d .codex/skills || test -d ~/.codex/skills
|
||||
|
||||
## Example Codex CLI prompts
|
||||
|
||||
With AAS Core configured:
|
||||
|
||||
```text
|
||||
Inspect this parser project, search and read the complete AAS catalog, and choose the exact skill IDs you judge most useful for designing and testing the change. Use compose_stack with a project profile, show me the schema 2 aas-stack.json, inspect it, and preview the plan; do not apply it.
|
||||
```
|
||||
|
||||
After installing or activating a chosen skill, direct invocation still works:
|
||||
|
||||
```text
|
||||
Use @concise-planning to break this feature request into an implementation checklist.
|
||||
```
|
||||
@@ -65,6 +81,7 @@ Use @create-pr once everything is passing and summarize the user-facing changes.
|
||||
|
||||
## What to do next
|
||||
|
||||
- Start with [`aas-core.md`](aas-core.md) for setup, trust boundaries, and the stack lifecycle.
|
||||
- Read [`ai-agent-skills.md`](ai-agent-skills.md) if you want a framework for choosing between broad and curated skill libraries.
|
||||
- Read [`plugins.md`](plugins.md) if you want the plugin-specific install story for Codex and Claude Code.
|
||||
- Use [`workflows.md`](workflows.md) when you want step-by-step execution patterns for common engineering goals.
|
||||
|
||||
Reference in New Issue
Block a user