From selection to use

Start with AAS Core in Codex or Claude. Configure the local MCP using the Codex or Claude guide. With the MCP available, ask the agent to inspect your project, compare relevant skills, and save the exact selection. Then validate its manifest and review the resulting plan before any installation. The first configuration command previews a change and returns an approval digest:

npm exec --yes --ignore-scripts --package=agentic-awesome-skills@20.6.0 -- aas mcp configure \
  --host codex \
  --scope user \
  --config /absolute/path/to/codex/config.toml \
  --cache-root /absolute/path/to/aas-cache

Use --host claude and its configuration path for Claude. The Core setup guide explains approval, reconnection, validation, and planning. To hand the reviewed IDs to the direct installer, use aas stack install-preview as described in the manifest handoff; that command only prepares a --dry-run preview and does not apply a Core plan.

Install selected skills directly

If you already know the IDs, preview a focused install into your host's skill directory:

npm exec --yes --ignore-scripts --package=agentic-awesome-skills@20.6.0 -- \
  agentic-awesome-skills --release 20.6.0 --path .agents/skills \
  --skills brainstorming,systematic-debugging --dry-run

Review the preview, then repeat without --dry-run when ready. The direct installer does not consume or apply a Core plan. Antigravity's watched skill directory can overload its context, so its default target requires a selected set, a filter, or an explicit --all override. See the installation guide and security guidance for other targets, auditing, and failure modes.