📦 deps(thirdparty): update snapshots
This commit is contained in:
ci[bot]
@@ -0,0 +1,182 @@
|
||||
# AAS Core: Agent-Owned Skill Stacks
|
||||
|
||||
AAS Core lets Codex and Claude search and read the complete local AAS catalog, preserve their exact skill selection as reproducible desired state, and preview a validated plan before any target change.
|
||||
|
||||
> **The agent inspects and chooses. AAS records and validates. You control.**
|
||||
|
||||
The primary durable artifact is [`aas-stack.json`](#the-stack-manifest). It records the exact skill IDs chosen by the coding agent; it is not the output of a Core ranking system. An audit-enabled flow can also persist a separate canonical `aas-selection-evidence.json` sidecar. The local MCP is a read-only catalog, composition, and evidence boundary; a client or the `aas` CLI performs persistence, the CLI validates and plans, and Workbench is a browser-local review surface.
|
||||
|
||||
## How it works
|
||||
|
||||
```text
|
||||
your project
|
||||
-> Codex or Claude inspects the repository
|
||||
-> agent searches and reads the complete local AAS catalog
|
||||
-> agent chooses the exact skill IDs
|
||||
-> compose_stack validates and returns the manifest in memory
|
||||
-> client or CLI persists aas-stack.json and optional evidence sidecar
|
||||
-> you review the artifacts
|
||||
-> aas stack validate
|
||||
-> aas stack plan (preview; no skill changes)
|
||||
```
|
||||
|
||||
AAS MCP does not scan the repository and does not decide which skills are best. Codex or Claude uses its own project understanding and judgment. All 1,968 skills in the current catalog remain individually searchable, readable, selectable, and usable; missing or incomplete metadata never makes a skill ineligible. Core has no semantic policy that favors a small stack, while every stack manifest has an explicit technical maximum of 128 skills.
|
||||
|
||||
## Configure the local MCP
|
||||
|
||||
> **Release boundary:** AAS Core landed after release 14.6.0. Use an exact Core-capable release rather than an unreviewed moving tag.
|
||||
|
||||
```bash
|
||||
npm exec --yes --ignore-scripts --package=agentic-awesome-skills@X.Y.Z -- aas mcp configure \
|
||||
--host codex \
|
||||
--scope user \
|
||||
--config /absolute/path/to/codex/config.toml \
|
||||
--cache-root /absolute/path/to/aas-cache
|
||||
```
|
||||
|
||||
Use `--host claude` with the appropriate absolute Claude MCP configuration path for Claude. The first command is a preview and returns an approval digest without changing the host configuration. Review it, then repeat the exact command with:
|
||||
|
||||
```text
|
||||
--approve <approval-digest>
|
||||
```
|
||||
|
||||
Configuration is explicit and integrity-bound. AAS installs or reuses an exact content-addressed runtime, verifies it, and changes only its managed MCP configuration section. Restart the host if it does not reload MCP configuration automatically.
|
||||
|
||||
## Ask the agent to choose the stack
|
||||
|
||||
Give the agent the desired outcome and constraints, and leave selection judgment with the agent:
|
||||
|
||||
```text
|
||||
Inspect this repository. Search and read the complete local AAS catalog, then
|
||||
enumerate the project's primary capability areas. For each capability, run a
|
||||
focused search, paginate or refine until you find plausible candidates, and use
|
||||
get_skill to compare multiple candidates when available. Select at least one
|
||||
non-redundant valid skill for every covered capability. Explicitly report as a
|
||||
catalog gap any capability for which the catalog has no valid match. At minimum,
|
||||
evaluate architecture/runtime, languages/frameworks, domain behavior,
|
||||
data/storage, external integrations, testing/quality, security/privacy,
|
||||
user experience/accessibility when user-facing, deployment/operations, and
|
||||
maintenance workflow; mark dimensions not applicable instead of silently
|
||||
omitting them. Do not stop at the first few matches or optimize for the smallest
|
||||
stack. Core imposes no semantic small-stack policy; the manifest format has a
|
||||
technical maximum of 128 selected skills.
|
||||
Only then use compose_stack with a project profile to validate the exact IDs and
|
||||
return a schema 2 manifest in memory, and use inspect_stack before presenting
|
||||
it. Do not install or apply anything.
|
||||
```
|
||||
|
||||
This capability-coverage contract is delivered to supported clients in the MCP
|
||||
`initialize` instructions and reinforced by the tool descriptions. It is an
|
||||
agent obligation, not a Core ranking or eligibility policy: Core still accepts
|
||||
and preserves any structurally valid set of catalog IDs and never chooses for the
|
||||
agent.
|
||||
|
||||
The local MCP exposes these read-only tools:
|
||||
|
||||
- `search_skills` — retrieve deterministic, paginated matches from every skill in the verified local catalog without scores or ranking;
|
||||
- `get_skill` — inspect one skill and optionally read its full content;
|
||||
- `compose_stack` — validate the agent-selected IDs and return the stack manifest in memory without writing it;
|
||||
- `inspect_stack` — validate and explain a proposed manifest;
|
||||
- `diff_stack` — compare manifests using verified local catalogs.
|
||||
- `export_selection_evidence` — combine the server-recorded session trace with an agent-declared capability ledger and an already composed and inspected manifest;
|
||||
- `inspect_selection_evidence` — validate the sidecar's structure, digests, catalog identity, manifest binding, and factual cross-references without judging skill suitability.
|
||||
|
||||
Search results use a stable catalog order and contain no relevance score, recommendation, or preferred ordering. Codex or Claude evaluates the returned candidates semantically and chooses exact IDs. Metadata returned by search or inspection is informational context; Core does not use risk, source, setup, compatibility, review, or evidence metadata to rank, exclude, or disable a skill.
|
||||
|
||||
MCP calls do not install or remove skills, update catalogs, edit host configuration, persist a stack, or apply it. Full skill text is returned only when requested and remains marked as untrusted content.
|
||||
|
||||
## The stack manifest
|
||||
|
||||
`aas-stack.json` records agent-chosen desired state:
|
||||
|
||||
```json
|
||||
{
|
||||
"schemaVersion": 2,
|
||||
"name": "project-stack",
|
||||
"catalog": {
|
||||
"package": "agentic-awesome-skills",
|
||||
"version": "<version>",
|
||||
"integrity": "sha256-..."
|
||||
},
|
||||
"targets": [{ "host": "codex", "scope": "project" }],
|
||||
"profile": {
|
||||
"goals": ["build", "test"],
|
||||
"projectType": "web application",
|
||||
"languages": ["typescript"],
|
||||
"frameworks": ["react"],
|
||||
"constraints": ["preview only"]
|
||||
},
|
||||
"skills": [
|
||||
{ "id": "example-skill" }
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The manifest pins catalog identity, targets, the project profile, and exact agent-selected skill IDs. It intentionally has no selection policy: Core validates identity and structure but does not overrule the agent's choice because metadata is missing, incomplete, or cautionary.
|
||||
|
||||
`compose_stack` produces this manifest only in MCP process memory. Persist it through the client or the CLI. Audit-enabled CLI flows publish `aas-stack.json` together with `aas-selection-evidence.json` in the requested `artifact-dir`, keeping the sidecar separate from the desired-state manifest.
|
||||
|
||||
## Selection evidence sidecar
|
||||
|
||||
`aas-selection-evidence.json` makes the selection process auditable without moving semantic judgment into Core. It binds a path-safe project fingerprint, catalog identity, manifest digest, the agent-declared ten-dimension capability ledger, capability-to-skill mappings, and the actual `search_skills`, `get_skill`, `compose_stack`, and `inspect_stack` facts recorded by that MCP server session. `export_selection_evidence` takes the ledger but obtains the trace from server-owned session state; the caller cannot supply a replacement historical trace. `inspect_selection_evidence` performs structural and factual validation only.
|
||||
|
||||
The trace records effective search query/cursor/limit values and returned IDs, opened skill IDs, exact compose IDs, inspect outcomes, safe error codes, deterministic retry attempts, and canonical input/output byte counts. Monotonic call durations are recorded separately outside the evidence digest. Client name and version come from MCP initialization when valid and available; model identity is omitted unless a trusted protocol surface supplies it.
|
||||
|
||||
The sidecar does not prove that a capability is correctly interpreted, that a selected skill is best, or that semantic coverage is sufficient. Repository evidence references are relative and contain no file contents or absolute paths. Search queries are recorded verbatim as factual trace data, so do not put secrets, credentials, private source text, or personal data in `search_skills` queries. Runtime observations that are not deterministic are not part of the canonical evidence digest.
|
||||
|
||||
The digest makes later edits detectable but is not a signature or cross-session identity attestation. The non-falsification guarantee is narrower: callers cannot inject or replace historical tool calls through `export_selection_evidence`; a standalone inspector can verify structure and digests, not who produced the file.
|
||||
|
||||
To publish the manifest and exported sidecar without exposing a one-file intermediate state, use a new artifact directory:
|
||||
|
||||
```bash
|
||||
aas stack create \
|
||||
--selection /absolute/path/to/agent-selection.json \
|
||||
--evidence /absolute/path/to/exported-evidence.json \
|
||||
--artifact-dir /absolute/path/to/new-audit-artifact \
|
||||
--require-evidence
|
||||
```
|
||||
|
||||
The destination must not already exist. The CLI validates both artifacts, writes private staged files named `aas-stack.json` and `aas-selection-evidence.json`, synchronizes them, and publishes the complete directory with one rename. The original `stack create --selection ... --out ...` manifest-only path remains supported.
|
||||
|
||||
## Validate and preview the plan
|
||||
|
||||
Use absolute paths in automation and review the JSON result from each command:
|
||||
|
||||
```bash
|
||||
aas stack validate --manifest /absolute/path/to/aas-stack.json
|
||||
|
||||
aas stack plan \
|
||||
--manifest /absolute/path/to/aas-stack.json \
|
||||
--target codex:project \
|
||||
--target-root /absolute/path/to/project \
|
||||
--cache-root /absolute/path/to/aas-cache \
|
||||
--runtime-integrity '<npm-sri>' \
|
||||
--out /absolute/path/to/plan.json
|
||||
```
|
||||
|
||||
`stack validate` is read-only. `stack plan` writes only the requested plan artifact and does not materialize skills or AAS managed state in the target. The immutable plan binds the manifest, runtime, catalog, target identity, current managed state, and exact logical operations.
|
||||
|
||||
Stop after reviewing the plan unless you are deliberately participating in controlled preview development. `stack apply` and `stack recover` remain experimental and require explicit opt-in.
|
||||
|
||||
## Privacy, trust, and limits
|
||||
|
||||
- MCP is local stdio, process-per-session, read-only, offline-capable, and contains no model credentials or telemetry.
|
||||
- Codex or Claude owns semantic selection. Different agents or project observations may reasonably produce different stacks.
|
||||
- Catalog integrity and manifest validation are deterministic; skill suitability is an agent judgment, not a Core score.
|
||||
- Core does not impose a semantic skill-count target. The technical manifest maximum is 128 skills, and every one of the current catalog's 1,968 skills remains individually searchable, readable, selectable, and usable. Metadata remains visible but informational.
|
||||
- Evidence exports include raw `search_skills` queries; keep secrets and sensitive project content out of those queries.
|
||||
- Catalog updates and runtime changes are explicit. There is no resident daemon or implicit auto-update.
|
||||
- Skill prose is untrusted content and does not gain instruction authority by being returned through MCP.
|
||||
|
||||
## Other ways to use the catalog
|
||||
|
||||
Direct installs, specialized plugins, bundles, workflows, and the legacy installer remain available. These surfaces distribute or curate catalog content; AAS Core adds complete local access, durable agent-owned selection, manifest validation, and a reviewable plan.
|
||||
|
||||
## Next reads
|
||||
|
||||
- [Getting Started](getting-started.md)
|
||||
- [Usage](usage.md)
|
||||
- [Skills vs MCP Tools](skills-vs-mcp-tools.md)
|
||||
- [Plugins for Claude Code and Codex](plugins.md)
|
||||
- [Bundles](bundles.md)
|
||||
- [FAQ](faq.md)
|
||||
+10
-9
@@ -1,27 +1,28 @@
|
||||
# Agentic Awesome Skills vs Awesome Claude Skills
|
||||
|
||||
If you are comparing **Agentic Awesome Skills** with **Awesome Claude Skills**, the decision usually comes down to breadth vs curation.
|
||||
If you are comparing **Agentic Awesome Skills** with **Awesome Claude Skills**, first decide whether you need complete catalog access with agent-owned reproducible selection or an editorial discovery list.
|
||||
|
||||
For clarity: the repository many people still refer to as `awesome-claude-skills` now lives at [VoltAgent/awesome-agent-skills](https://github.com/VoltAgent/awesome-agent-skills).
|
||||
|
||||
## TL;DR
|
||||
|
||||
- Choose **Agentic Awesome Skills** if you want a large installable library, broad tool coverage, and strong onboarding.
|
||||
- Choose **Agentic Awesome Skills** if you want AAS Core to turn an explicit project profile into an explainable, reviewable skill stack, with broad catalog and distribution support around it.
|
||||
- Choose **VoltAgent Awesome Agent Skills** if you want a curated list with a strong official-team angle and a tighter scope.
|
||||
|
||||
## At-a-glance comparison
|
||||
|
||||
| Criteria | Agentic Awesome Skills | VoltAgent Awesome Agent Skills |
|
||||
| --- | --- | --- |
|
||||
| Best for | Breadth, installation, multi-tool daily use | Curated discovery and official/community highlights |
|
||||
| Catalog shape | Large installable library with bundles, workflows, docs, and generated catalog | Curated awesome-list style collection |
|
||||
| Best for | Complete local catalog access, agent-owned selection, durable desired state, and plan preview | Curated discovery and official/community highlights |
|
||||
| Product shape | AAS Core with local MCP, CLI, stack/plan artifacts, Workbench review, and supporting catalog/distribution | Curated awesome-list style collection |
|
||||
| Supported tools | Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, Kiro, OpenCode, Copilot, more | Claude Code, Codex, Antigravity, Gemini CLI, Cursor, Copilot, OpenCode, Windsurf, more |
|
||||
| Onboarding | Installation docs, bundles, workflows, getting-started guides | Curated README and categorized references |
|
||||
| Good fit when | You want one repo to install and work from | You want a smaller list to browse and evaluate |
|
||||
| Good fit when | You want an agent to inspect a project and choose exact IDs from the full catalog | You want a smaller list to browse and evaluate manually |
|
||||
|
||||
## Why choose Agentic Awesome Skills
|
||||
|
||||
- You want a single GitHub repository that acts as both a skill source and an installable working library.
|
||||
- You want Codex or Claude to search and read a complete catalog through a local, read-only MCP and own the selection.
|
||||
- You want the approved selection recorded as `aas-stack.json` and validated before an immutable plan is produced.
|
||||
- You care about onboarding assets like [`bundles.md`](bundles.md), [`workflows.md`](workflows.md), and tool-specific guides.
|
||||
- You need coverage across many domains, not just a curated shortlist.
|
||||
|
||||
@@ -33,11 +34,11 @@ For clarity: the repository many people still refer to as `awesome-claude-skills
|
||||
|
||||
## Honest tradeoffs
|
||||
|
||||
- Antigravity can feel bigger and noisier at first because it optimizes for breadth.
|
||||
- The AAS catalog is larger and its evidence remains uneven; Core reports unknowns rather than treating breadth as certified quality.
|
||||
- VoltAgent can be easier to skim quickly because it optimizes for curation.
|
||||
- If you want both, a sensible workflow is to browse curated lists first and install a broader library once you know your use cases.
|
||||
- If you want both, use curated lists for editorial discovery and AAS Core when you need a reproducible agent-selected project stack.
|
||||
|
||||
## Suggested next step
|
||||
|
||||
- If you want to install and start using skills today, go back to [`README.md`](../../README.md) and follow the installation guide.
|
||||
- If you want project-specific composition, start with the [AAS Core guide](aas-core.md). If you already know exact skill IDs, use the direct distribution options in [`README.md`](../../README.md).
|
||||
- If you are still evaluating tool-specific options, continue with [`best-claude-code-skills-github.md`](best-claude-code-skills-github.md) or [`best-cursor-skills-github.md`](best-cursor-skills-github.md).
|
||||
|
||||
@@ -1,29 +1,32 @@
|
||||
# AI Agent Skills
|
||||
|
||||
If you are researching **AI agent skills** on GitHub, the biggest decision is usually not "which single skill is best?" but "do I want a broad installable library or a smaller curated collection?"
|
||||
If you are researching **AI agent skills** on GitHub, the useful first decision is whether you want agent-owned project selection with reproducible state or manual catalog browsing.
|
||||
|
||||
Agentic Awesome Skills is built for the first path: broad coverage, multiple supported tools, installation help, onboarding docs, bundles, workflows, and a catalog that supports both beginner and advanced users.
|
||||
Agentic Awesome Skills is built around **AAS Core**: Codex or Claude inspects the project, searches and reads the complete local catalog, chooses exact skill IDs, and uses `compose_stack` to pin them in `aas-stack.json`. The CLI validates that agent-owned state and produces an immutable preview plan before any target change.
|
||||
|
||||
## What to look for in an AI agent skills library
|
||||
The catalog, plugins, bundles, workflows, and direct installer remain supporting content and distribution surfaces. AAS does not scan the repository, call a remote model, or write project files through MCP.
|
||||
|
||||
- **Installability**: can you put the skills where your tool expects them without manual copying?
|
||||
- **Supported tools**: does the repo work with Claude Code, Cursor, Codex CLI, Gemini CLI, and related environments?
|
||||
- **Breadth vs curation**: do you want many options or a smaller shortlist of high-signal entries?
|
||||
- **Onboarding quality**: are there docs, bundles, workflows, and examples, or only raw files?
|
||||
- **Trust model**: does the repo identify official sources, security posture, and community review expectations?
|
||||
## What to look for in an AI agent skill system
|
||||
|
||||
- **Explicit input boundary**: is project analysis performed by the coding agent and passed as a reviewable profile?
|
||||
- **Agent-owned selection**: can the coding agent search and read every skill before choosing exact IDs?
|
||||
- **Reproducibility**: can the chosen IDs be pinned to a catalog identity and replayed without a metadata eligibility gate?
|
||||
- **Durable desired state**: can the approved selection be recorded independently of the agent conversation?
|
||||
- **Preview before change**: can the system validate the manifest and produce an exact plan without changing the target?
|
||||
- **Source and compatibility evidence**: are provenance, risk, host support, and distribution boundaries explicit?
|
||||
|
||||
## When Agentic Awesome Skills is a good fit
|
||||
|
||||
- You want one library that spans planning, coding, debugging, testing, security, infra, product, and marketing.
|
||||
- You care about installation paths and practical onboarding, not only catalog size.
|
||||
- You want bundles and workflows to reduce choice overload.
|
||||
- You need compatibility across more than one AI coding assistant.
|
||||
- You use Codex or Claude and want the agent to choose a focused stack for a real project.
|
||||
- You want complete local search and inspection without repository scanning or remote-model calls by AAS.
|
||||
- You need a reviewable `aas-stack.json` and CLI validation and planning before target changes.
|
||||
- You also value a broad catalog and multiple distribution options around the Core workflow.
|
||||
|
||||
## When a smaller curated repo may be better
|
||||
|
||||
- You only want a narrow shortlist of highly curated or vendor-focused skills.
|
||||
- You prefer reviewing fewer files even if coverage is lower.
|
||||
- You are evaluating alternatives for a single tool and want a quick comparison first.
|
||||
- You only want a fixed, vendor-maintained shortlist and do not need project-aware composition.
|
||||
- You prefer selecting and invoking individual skills manually.
|
||||
- Your host does not yet have an AAS Core adapter and direct distribution is sufficient.
|
||||
|
||||
## Start with a tool-specific guide
|
||||
|
||||
@@ -32,7 +35,7 @@ Agentic Awesome Skills is built for the first path: broad coverage, multiple sup
|
||||
- [`codex-cli-skills.md`](codex-cli-skills.md)
|
||||
- [`gemini-cli-skills.md`](gemini-cli-skills.md)
|
||||
|
||||
## Compare broad vs curated libraries
|
||||
## Compare catalogs and distribution models
|
||||
|
||||
- [`agentic-awesome-skills-vs-awesome-claude-skills.md`](agentic-awesome-skills-vs-awesome-claude-skills.md)
|
||||
- [`best-claude-code-skills-github.md`](best-claude-code-skills-github.md)
|
||||
@@ -40,6 +43,6 @@ Agentic Awesome Skills is built for the first path: broad coverage, multiple sup
|
||||
|
||||
## Quick recommendation
|
||||
|
||||
- Choose **Agentic Awesome Skills** if you want a large, installable, multi-tool library with onboarding help.
|
||||
- Choose a smaller curated repo if you want fewer choices and more editorial filtering.
|
||||
- If you are unsure, install this repo first, start with [`bundles.md`](bundles.md), and then compare alternatives once you know your preferred workflow.
|
||||
- Choose **AAS Core** if you want complete local catalog access, agent-owned selection, reproducible stack composition, and a preview plan.
|
||||
- Choose direct distribution if you already know the exact skills you want or your host does not support the Core path.
|
||||
- Choose a smaller curated repository if a fixed editorial shortlist matters more than complete catalog access and durable desired state.
|
||||
|
||||
@@ -1,18 +1,18 @@
|
||||
# Best Claude Code Skills on GitHub
|
||||
|
||||
If you are looking for the **best Claude Code skills on GitHub**, there is no single perfect repository for every user. The right choice depends on whether you want breadth, curation, or official reference material.
|
||||
If you are looking for the **best Claude Code skills on GitHub**, there is no single perfect repository for every user. The right choice depends on whether you want complete catalog access with Claude-owned selection, curated discovery, or official reference material.
|
||||
|
||||
## Best overall installable library
|
||||
## Best for agent-selected project stacks
|
||||
|
||||
### 1. [sickn33/agentic-awesome-skills](https://github.com/sickn33/agentic-awesome-skills)
|
||||
|
||||
Best for teams and individual developers who want one large installable library with onboarding docs, bundles, workflows, and support for more than just Claude Code.
|
||||
Best for teams and individual developers who want Claude to inspect a project, search and read the complete catalog through a local read-only MCP, choose exact IDs, and produce a reviewable `aas-stack.json` before CLI validation and planning.
|
||||
|
||||
Choose this if you want:
|
||||
|
||||
- a broad library you can install and use immediately;
|
||||
- bundles and workflows to reduce choice overload;
|
||||
- compatibility beyond Claude Code alone.
|
||||
- complete local catalog access with Claude-owned selection;
|
||||
- durable desired state plus immutable plan preview;
|
||||
- a broad catalog, plugins, bundles, workflows, and direct distribution around Core.
|
||||
|
||||
## Best curated shortlist
|
||||
|
||||
@@ -52,11 +52,11 @@ Choose this if you want:
|
||||
|
||||
## How to choose quickly
|
||||
|
||||
- Choose **Agentic Awesome Skills** if you want the most practical install-and-use path.
|
||||
- Choose **Agentic Awesome Skills** if you want project-specific composition and a reviewable lifecycle before any target change.
|
||||
- Choose **VoltAgent Awesome Agent Skills** if you want the strongest curated shortlist.
|
||||
- Choose **anthropics/skills** if official vendor reference matters most.
|
||||
- Choose **karanb192/awesome-claude-skills** if you want a smaller community-first Claude library.
|
||||
|
||||
## Recommended next step
|
||||
|
||||
If you want to get productive quickly, install [Agentic Awesome Skills](https://github.com/sickn33/agentic-awesome-skills) and start with [`claude-code-skills.md`](claude-code-skills.md) plus [`bundles.md`](bundles.md).
|
||||
If you want a project-specific stack, start with the [AAS Core guide](aas-core.md) and [`claude-code-skills.md`](claude-code-skills.md). Use direct distribution only when you already know the exact skills or fixed plugin you want.
|
||||
|
||||
@@ -1,12 +1,12 @@
|
||||
# Best Cursor Skills on GitHub
|
||||
|
||||
If you are searching for the **best Cursor skills on GitHub**, the best option depends on whether you want a broad installable library, a curated discovery list, or a smaller community collection.
|
||||
If you are searching for the **best Cursor skills on GitHub**, the best option depends on whether you want an agent-composed project stack, a broad direct distribution, a curated discovery list, or a smaller community collection. Cursor does not yet have a native AAS Core adapter, so its current AAS path is direct distribution rather than the Codex/Claude Core workflow.
|
||||
|
||||
## Best overall installable library
|
||||
## Broadest AAS direct distribution for Cursor
|
||||
|
||||
### 1. [sickn33/agentic-awesome-skills](https://github.com/sickn33/agentic-awesome-skills)
|
||||
|
||||
Best for developers who want one repository they can install into Cursor and keep using across frontend, backend, testing, infra, product, and growth work.
|
||||
Best for developers who want the AAS catalog delivered into Cursor across frontend, backend, testing, infra, product, and growth work while treating AAS Core as the repository's primary product for supported agent clients.
|
||||
|
||||
Choose this if you want:
|
||||
|
||||
@@ -52,11 +52,11 @@ Choose this if you want:
|
||||
|
||||
## How to choose quickly
|
||||
|
||||
- Choose **Agentic Awesome Skills** if you want the strongest install-and-use path for real day-to-day Cursor work.
|
||||
- Choose **Agentic Awesome Skills** if you want its broad supporting catalog and direct Cursor distribution today, with a clear boundary that this is not yet the native AAS Core path.
|
||||
- Choose **VoltAgent Awesome Agent Skills** if you want curation first and installation later.
|
||||
- Choose **Ai-Agent-Skills** if you want a smaller installable library.
|
||||
- Choose **cursor-skills** if you want the most Cursor-specific starting point.
|
||||
|
||||
## Recommended next step
|
||||
|
||||
If your goal is to start working in Cursor today, install [Agentic Awesome Skills](https://github.com/sickn33/agentic-awesome-skills) and continue with [`cursor-skills.md`](cursor-skills.md).
|
||||
If your goal is to start working in Cursor today, use the direct distribution guidance in [`cursor-skills.md`](cursor-skills.md). For the primary product model and current Codex/Claude path, read the [AAS Core guide](aas-core.md).
|
||||
|
||||
@@ -825,7 +825,9 @@ _For shipping clean changes in public repositories._
|
||||
**Plugin status:** Codex plugin-safe · Claude plugin-safe
|
||||
|
||||
- [`commit`](../../skills/commit/): High-quality conventional commits.
|
||||
- [`create-branch`](../../skills/create-branch/): Create a safe topic branch before committing.
|
||||
- [`create-pr`](../../skills/create-pr/): PR creation with review-ready context.
|
||||
- [`pr-writer`](../../skills/pr-writer/): Write and open structured pull requests.
|
||||
- [`requesting-code-review`](../../skills/requesting-code-review/): Ask for targeted, high-signal reviews.
|
||||
- [`receiving-code-review`](../../skills/receiving-code-review/): Apply feedback with technical rigor.
|
||||
- [`changelog-automation`](../../skills/changelog-automation/): Keep release notes and changelogs consistent.
|
||||
@@ -1060,4 +1062,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
|
||||
|
||||
---
|
||||
|
||||
_Last updated: June 2026 | Total Skills: 1,965+ | Total Bundles: 58_
|
||||
_Last updated: June 2026 | Total Skills: 1,969+ | Total Bundles: 58_
|
||||
|
||||
@@ -1,24 +1,31 @@
|
||||
# Claude Code Skills
|
||||
# AAS Core with Claude Code
|
||||
|
||||
If you are looking for **Claude Code skills** you can install from GitHub, this repository is designed to get you from first clone to first useful prompt quickly.
|
||||
For Claude Code, the recommended AAS path is **AAS Core**: a local, agent-first control plane for complete catalog search, Claude-owned skill selection, manifest inspection, and preview-first planning.
|
||||
|
||||
Agentic Awesome Skills gives Claude Code users an installable library of `SKILL.md` playbooks, role-based bundles, and execution workflows. The goal is not just to collect prompts, but to make repeatable engineering tasks easier to invoke, review, and reuse.
|
||||
The local AAS MCP is read-only. It lets Claude search and read every catalog skill, then validate and pin Claude's chosen IDs in `aas-stack.json`; planning and any approved changes stay in the AAS CLI lifecycle.
|
||||
|
||||
Release `9.0.0` also adds a first-class Claude Code 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). The Claude plugin marketplace and direct skill installation remain supported delivery paths after you know which skills 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 Claude Code
|
||||
|
||||
Install the library into Claude Code, then invoke focused skills directly in the conversation or through the plugin marketplace path. Claude Code benefits most when you keep the prompt specific about the skill, the scope, and the intended output.
|
||||
Configure AAS Core for Claude Code, describe the task and constraints, let Claude choose exact IDs from the complete catalog, then review the composed stack and preview the CLI plan. Core does not install or mutate through MCP.
|
||||
|
||||
## Why use this repo for Claude Code
|
||||
|
||||
- It includes 1,965+ skills instead of a narrow single-domain starter pack.
|
||||
- It lets Claude search the verified local catalog without loading the full library into context.
|
||||
- It preserves Claude's exact selection without using metadata as an eligibility gate.
|
||||
- It keeps MCP discovery read-only and CLI changes approval-gated.
|
||||
- It includes 1,969+ skills instead of a narrow single-domain starter pack.
|
||||
- It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
|
||||
- It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
|
||||
- It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.
|
||||
- It covers both everyday engineering tasks and specialized work like security reviews, infrastructure, product planning, and documentation.
|
||||
|
||||
## Install Claude Code Skills
|
||||
## Direct install and plugins
|
||||
|
||||
These are alternative delivery paths for users who already know which skill payload they want.
|
||||
|
||||
### Option A: installer CLI
|
||||
|
||||
@@ -53,6 +60,14 @@ test -d .claude/skills || test -d ~/.claude/skills
|
||||
|
||||
## Example Claude Code prompts
|
||||
|
||||
With AAS Core configured:
|
||||
|
||||
```text
|
||||
Inspect this security-review project, search and read the complete AAS catalog, and choose the exact skill IDs you judge most useful. Use compose_stack with a project profile, show me the schema 2 aas-stack.json, inspect it, and preview the plan without applying it.
|
||||
```
|
||||
|
||||
After installing or activating a chosen skill, direct invocation still works:
|
||||
|
||||
```text
|
||||
Use @brainstorming to design a new billing workflow for my SaaS.
|
||||
```
|
||||
@@ -67,6 +82,7 @@ Use @create-pr to turn these changes into a clean PR summary and checklist.
|
||||
|
||||
## What to do next
|
||||
|
||||
- Start with [`aas-core.md`](aas-core.md) for setup, trust boundaries, and the stack lifecycle.
|
||||
- Start with [`bundles.md`](bundles.md) if you want a role-based shortlist.
|
||||
- Use [`workflows.md`](workflows.md) if you want step-by-step execution playbooks.
|
||||
- Compare options in [`best-claude-code-skills-github.md`](best-claude-code-skills-github.md) if you are still evaluating repositories.
|
||||
|
||||
@@ -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.
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
# Stable Skills Manifest v1
|
||||
# Stable Skills Manifest v1 for Custom Integrations
|
||||
|
||||
This page documents the `skills_index.json` manifest contract used by stable integrations.
|
||||
This page documents the legacy-compatible `skills_index.json` contract used by custom host integrations and lazy loaders.
|
||||
|
||||
For Codex and Claude Code, use [AAS Core](aas-core.md) instead of wiring a host directly to this repository manifest. Core exposes every skill in a verified local catalog through bounded, read-only MCP tools for search, inspection, and agent-owned composition. The raw manifest remains useful for integrations that do not have an AAS Core host adapter.
|
||||
|
||||
## Manifest contract (v1)
|
||||
|
||||
@@ -34,7 +36,7 @@ Stable integrations must not load every skill instruction file up front.
|
||||
- Enforce a per-turn maximum so user prompts stay below context limits.
|
||||
- Validate each resolved path stays under your configured `SKILLS_ROOT`.
|
||||
|
||||
This is the core prevention for context truncation and trajectory conversion errors in larger multi-skill hosts.
|
||||
This is the main prevention for context truncation and trajectory conversion errors in custom multi-skill hosts. It is not the AAS Core catalog or stack lifecycle contract.
|
||||
|
||||
## Why the `data/` mirror exists
|
||||
|
||||
@@ -57,6 +59,7 @@ This is the core prevention for context truncation and trajectory conversion err
|
||||
|
||||
## Related docs
|
||||
|
||||
- [`docs/users/aas-core.md`](aas-core.md)
|
||||
- [`docs/integrations/jetski-cortex.md`](../integrations/jetski-cortex.md)
|
||||
- [`docs/integrations/jetski-gemini-loader/README.md`](../integrations/jetski-gemini-loader/README.md)
|
||||
- [`docs/users/windows-truncation-recovery.md`](windows-truncation-recovery.md)
|
||||
|
||||
@@ -6,6 +6,22 @@
|
||||
|
||||
## General Questions
|
||||
|
||||
### What is AAS Core?
|
||||
|
||||
AAS Core is the versioned control plane that gives Codex or Claude complete local catalog access and turns the agent's exact selection into a reproducible project stack. The agent inspects the repository, searches and reads skills, chooses exact IDs, and uses `compose_stack` to propose `aas-stack.json`. The `aas` CLI then validates the manifest and previews an immutable plan.
|
||||
|
||||
AAS Core is the product; the approved `aas-stack.json` and immutable plan are its durable artifacts. Skills and the catalog provide content and evidence, MCP and CLI are interfaces, Workbench is a review surface, and plugins, bundles, workflows, and installers provide curation or distribution around Core. Start with [AAS Core](aas-core.md).
|
||||
|
||||
### Is AAS Core fully certified?
|
||||
|
||||
Core supports complete local catalog search and inspection, agent-owned selection, reproducible composition, manifest validation, and plan preview. Transactional apply/recovery safety remains outside the supported claim.
|
||||
|
||||
`stack apply` and `stack recover` are experimental, disabled by default, and are not supported preview safety claims. The recommended public flow stops after reviewing `stack validate` and `stack plan` output.
|
||||
|
||||
### Does AAS upload my repository or use another model?
|
||||
|
||||
No. The agent inspects the project using its normal local capabilities. AAS MCP only exposes the complete bundled or verified local catalog and validates agent-selected IDs; it does not scan the repository, rank skills, or enforce selection policy. MCP is local stdio, read-only, offline-capable, and contains no model credentials or telemetry.
|
||||
|
||||
### What are "skills" exactly?
|
||||
|
||||
Skills are specialized instruction files that teach AI assistants how to handle specific tasks. Think of them as expert knowledge modules that your AI can load on-demand.
|
||||
@@ -13,9 +29,9 @@ Skills are specialized instruction files that teach AI assistants how to handle
|
||||
|
||||
### Do I need to install every skill?
|
||||
|
||||
**No!** When you clone the repository, all skills are available, but your AI only loads them when you explicitly invoke them with `@skill-name`.
|
||||
It's like having a library - all books are there, but you only read the ones you need.
|
||||
**Pro Tip:** Use [Starter Packs](bundles.md) to focus on the skills that match your role first.
|
||||
**No.** With AAS Core, ask the agent to inspect the project and choose the exact skills from the complete catalog. On a broad direct install, all skills may be present locally while the host loads only the skills it invokes.
|
||||
|
||||
Use [Starter Packs](bundles.md) as human-curated presets when you want a fixed starting point.
|
||||
|
||||
If you want a narrower install surface for **Claude Code** or **Codex**, use the new plugin distributions documented in [plugins.md](plugins.md) instead of the full library install.
|
||||
|
||||
@@ -31,12 +47,13 @@ Start from:
|
||||
- [bundles.md](bundles.md)
|
||||
- [workflows.md](workflows.md)
|
||||
|
||||
### What is the difference between skills and MCP tools?
|
||||
### What is the difference between skills, AAS MCP, and the CLI?
|
||||
|
||||
- **Skills** are reusable `SKILL.md` playbooks that guide an AI assistant through a workflow.
|
||||
- **MCP tools** are integrations or callable capabilities that let the assistant interact with external systems.
|
||||
- **AAS MCP** is the local, read-only discovery and composition interface to AAS Core. It exposes every catalog skill, reads requested content, validates agent-selected IDs, and checks or compares manifests.
|
||||
- **The `aas` CLI** manages explicit lifecycle operations such as catalog status/update, MCP configuration, stack validation, planning, and diagnostics.
|
||||
|
||||
Use skills when you want better process, structure, and execution quality. Use MCP tools when you need access to APIs, services, databases, or other systems. Use both when you want reliable workflows plus external capabilities.
|
||||
Other MCP servers may grant access to APIs, services, databases, or hosted systems. AAS MCP has a narrower boundary: it does not install, apply, update catalogs, scan repositories, or modify configuration through tool calls.
|
||||
|
||||
For the longer explanation, read [skills-vs-mcp-tools.md](skills-vs-mcp-tools.md).
|
||||
|
||||
@@ -118,6 +135,12 @@ _Always check the Risk label and review the code._
|
||||
|
||||
## Installation & Setup
|
||||
|
||||
### How do I start with AAS Core?
|
||||
|
||||
Use the pinned `aas` binary from a release whose notes explicitly state that it includes AAS Core to preview and approve local MCP configuration for Codex or Claude. Release 14.6.0 predates Core; Core-capable packages begin with the 15.x line. Restart the host if needed, then ask the agent to search the full catalog, choose exact IDs, and compose a stack without applying it. The command template and trust boundaries are in [AAS Core](aas-core.md).
|
||||
|
||||
The package publishes separate `agentic-awesome-skills`, `aas`, and `aas-mcp` binaries. Use the explicit `aas` binary for Core lifecycle commands; the legacy `agentic-awesome-skills` entrypoint remains the direct installer.
|
||||
|
||||
### Where should I install the skills?
|
||||
|
||||
It depends on how you install:
|
||||
@@ -137,7 +160,7 @@ If you get a 404 from npm, use: `npx github:sickn33/agentic-awesome-skills`
|
||||
git clone https://github.com/sickn33/agentic-awesome-skills.git .agent/skills
|
||||
```
|
||||
|
||||
The installer CLI is the recommended path for most users because it performs a lighter shallow clone of the current library. Manual `git clone` is still the right option when you want the full repository history or plan to contribute from the same checkout.
|
||||
For direct skill distribution, the installer CLI performs a lighter shallow clone of the current library. Manual `git clone` remains appropriate when you want the full repository history or plan to contribute from the same checkout. For Codex or Claude users who want project-specific agent selection with reproducible state, start with AAS Core instead of treating a full-library install as the primary product path.
|
||||
|
||||
**Tool-specific paths:**
|
||||
|
||||
@@ -254,7 +277,7 @@ npx agentic-awesome-skills@14.3.0 --path .agents/skills --release 14.3.0 --skill
|
||||
|
||||
Remove `--dry-run` only after reviewing the plan.
|
||||
|
||||
If you prefer to assemble and review the set visually, use the hosted [Skill Workbench](https://sickn33.github.io/agentic-awesome-skills/workbench). It filters recorded risk, provenance, host compatibility, and setup evidence before generating the same release-pinned commands.
|
||||
To review a Core stack manifest or immutable plan visually, use the hosted [Skill Workbench](https://sickn33.github.io/agentic-awesome-skills/workbench). It imports the JSON in browser memory and checks the supported artifact structure; it does not assemble a stack, generate install commands, access the filesystem, or install skills.
|
||||
|
||||
The filter rules are:
|
||||
|
||||
@@ -355,9 +378,13 @@ Examples:
|
||||
|
||||
### How do I know which skill to use?
|
||||
|
||||
With AAS Core, describe the project outcome and constraints, then ask the agent to search and read the full catalog, choose exact IDs, and call `compose_stack`. Review the agent's rationale and proposed IDs before accepting the stack.
|
||||
|
||||
For manual discovery:
|
||||
|
||||
1. **Browse the catalog**: Check the [Skill Catalog](../../CATALOG.md).
|
||||
2. **Search**: `ls skills/ | grep "keyword"`
|
||||
3. **Ask your AI**: "What skills do you have for testing?"
|
||||
2. **Search**: `ls skills/ | grep "keyword"`.
|
||||
3. **Use a preset**: Start from [Bundles](bundles.md).
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
|
||||
|
||||
- It installs directly into the expected Gemini skills path.
|
||||
- It includes both core software engineering skills and deeper agent/LLM-oriented skills.
|
||||
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,965+ files.
|
||||
- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,969+ files.
|
||||
- It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
|
||||
|
||||
## Install Gemini CLI Skills
|
||||
|
||||
@@ -1,8 +1,21 @@
|
||||
# Getting Started with Agentic Awesome Skills (V14.6.0)
|
||||
# Getting Started with AAS Core
|
||||
|
||||
**New here? This guide will help you supercharge your AI Agent in 5 minutes.**
|
||||
**New here? Start with AAS Core and let your agent choose a reviewable skill stack from the complete catalog.**
|
||||
|
||||
> **💡 Confused about what to do after installation?** Check out the [**Complete Usage Guide**](usage.md) for detailed explanations and examples!
|
||||
> **Product boundary:** Codex or Claude owns skill selection. AAS Core provides complete local catalog access, reproducible composition, validation, and plan preview; apply and recovery remain experimental.
|
||||
|
||||
## Start with AAS Core
|
||||
|
||||
AAS Core is the primary product path. Codex or Claude inspects your project, searches and reads the complete catalog through the local read-only AAS MCP, chooses the exact skill IDs, and uses `compose_stack` to propose an `aas-stack.json`. You review those IDs before using the `aas` CLI to validate the manifest and preview a plan.
|
||||
|
||||
```text
|
||||
project -> agent -> full local catalog -> agent selection -> compose_stack -> aas-stack.json
|
||||
-> human review -> validate -> plan preview
|
||||
```
|
||||
|
||||
Start with the canonical [AAS Core guide](aas-core.md) to configure the MCP and run that flow. The direct installer, plugins, bundles, and manual skill invocation described below remain useful alternatives, especially for hosts without a native AAS MCP adapter.
|
||||
|
||||
> **Need more examples after setup?** Continue with the [Complete Usage Guide](usage.md).
|
||||
|
||||
---
|
||||
|
||||
@@ -15,16 +28,16 @@ AI Agents (like **Claude Code**, **Gemini**, **Cursor**) are smart, but they lac
|
||||
|
||||
---
|
||||
|
||||
## Quick Start: The "Starter Packs"
|
||||
## Alternative Path: Direct Skill Distribution and Starter Packs
|
||||
|
||||
Don't panic about the size of the repository. You don't need everything at once.
|
||||
We have curated **Starter Packs** to get you running immediately.
|
||||
|
||||
You **install the full repo once** (npx or clone); Starter Packs are curated lists to help you **pick which skills to use** by role (e.g. Web Wizard, Hacker Pack)—they are not a different way to install.
|
||||
On the direct-install path, you install the library once (npx or clone); Starter Packs are curated lists to help you **pick which skills to use** by role (e.g. Web Wizard, Hacker Pack)—they are not a different way to install.
|
||||
|
||||
If you prefer a marketplace-style install for **Claude Code** or **Codex**, use the new plugin distributions described in [plugins.md](plugins.md).
|
||||
|
||||
### 1. Install the Repo
|
||||
### 1. Install Skills Directly
|
||||
|
||||
**Option A — npx (easiest):**
|
||||
|
||||
@@ -154,7 +167,7 @@ For Claude Code, use:
|
||||
For Codex, this repository also ships a root plugin plus bundle plugins through the repo-local metadata described in [plugins.md](plugins.md).
|
||||
|
||||
**Q: Do I need to install every skill?**
|
||||
A: You clone the whole repo once; your AI only _reads_ the skills you invoke (or that are relevant), so it stays lightweight. **Starter Packs** in [bundles.md](bundles.md) are curated lists to help you discover the right skills for your role—they don't change how you install.
|
||||
A: No. With AAS Core, ask the agent to inspect the project and choose exact IDs from the complete catalog. On the legacy direct-install path, you can install the broad library while the host reads only invoked or relevant skills. **Starter Packs** in [bundles.md](bundles.md) remain human-curated discovery aids.
|
||||
|
||||
**Q: Can I make my own skills?**
|
||||
A: Yes! Use the **@skill-creator** skill to build your own.
|
||||
@@ -186,6 +199,7 @@ Need a tool-specific starting point first?
|
||||
- [Codex CLI skills](codex-cli-skills.md)
|
||||
- [Gemini CLI skills](gemini-cli-skills.md)
|
||||
|
||||
1. [Browse the Bundles](bundles.md)
|
||||
2. [See Real-World Examples](../contributors/examples.md)
|
||||
3. [Contribute a Skill](../../CONTRIBUTING.md)
|
||||
1. [Configure and use AAS Core](aas-core.md)
|
||||
2. [Browse the Bundles](bundles.md)
|
||||
3. [See Real-World Examples](../contributors/examples.md)
|
||||
4. [Contribute a Skill](../../CONTRIBUTING.md)
|
||||
|
||||
@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
|
||||
|
||||
Kiro's agentic capabilities are enhanced by skills that provide:
|
||||
|
||||
- **Domain expertise** across 1,965+ specialized areas
|
||||
- **Domain expertise** across 1,969+ specialized areas
|
||||
- **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
|
||||
- **Workflow automation** for common development tasks
|
||||
- **AWS-specific patterns** for serverless, infrastructure, and cloud architecture
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
Release `9.0.0` adds first-class plugin distributions for both **Claude Code** and **Codex**.
|
||||
|
||||
This page is the canonical explanation of what those plugins are, how they differ from a full library install, and why the repository now ships both a **root plugin** and multiple **specialized plugins**.
|
||||
This page explains how plugins fit beneath **AAS Core**, the orchestration layer for Codex and Claude Code. Plugins and direct installs deliver skill payloads; Core exposes the complete catalog and validates, records, and plans the exact stack chosen by the agent.
|
||||
|
||||
## What a plugin is in this repo
|
||||
|
||||
@@ -17,9 +17,13 @@ Plugins are useful when you want:
|
||||
|
||||
Plugins are **not** different content formats. They still ship `SKILL.md` playbooks. The difference is the packaging, install surface, and filtering.
|
||||
|
||||
## Full library install vs plugin install
|
||||
## Core orchestration vs delivery surfaces
|
||||
|
||||
You now have two valid ways to use this repository with Claude Code or Codex.
|
||||
For Codex and Claude Code, start with [AAS Core](aas-core.md) when you want the agent to choose from catalog evidence. Core exposes read-only local MCP tools and keeps validation, planning, and approved changes in the CLI.
|
||||
|
||||
Once the desired stack is clear, plugins and direct installs are two supported delivery surfaces. They do not replace Core and Core is not another plugin bundle.
|
||||
|
||||
## Full library install vs plugin install
|
||||
|
||||
### Full library install
|
||||
|
||||
@@ -132,6 +136,13 @@ Bundle-specific Codex plugins are generated alongside the root plugin so you can
|
||||
|
||||
## Which path should you choose?
|
||||
|
||||
Choose **AAS Core first** if:
|
||||
|
||||
- you want Codex or Claude Code to search and inspect the local catalog
|
||||
- you want Codex or Claude to search the complete catalog and preserve its exact selection
|
||||
- you want a reviewable `aas-stack.json` and preview plan before any change
|
||||
- you want read-only MCP discovery separated from approval-gated CLI operations
|
||||
|
||||
Choose the **full library** if:
|
||||
|
||||
- you want the biggest catalog
|
||||
@@ -155,6 +166,7 @@ The hosted [specialized plugin landing page](https://sickn33.github.io/agentic-a
|
||||
|
||||
## Related guides
|
||||
|
||||
- [AAS Core](aas-core.md)
|
||||
- [Getting Started](getting-started.md)
|
||||
- [FAQ](faq.md)
|
||||
- [Claude Code skills](claude-code-skills.md)
|
||||
|
||||
@@ -1,89 +1,108 @@
|
||||
# Skills vs MCP Tools
|
||||
# Skills, AAS MCP, and Other MCP Tools
|
||||
|
||||
If you are trying to understand the difference between **Antigravity skills** and **MCP tools**, the short version is:
|
||||
The short version is:
|
||||
|
||||
- **Skills** are reusable `SKILL.md` playbooks that tell an AI assistant how to execute a workflow.
|
||||
- **MCP tools** are integrations or callable capabilities that let the assistant interact with external systems.
|
||||
- **AAS MCP** is the local, read-only interface through which an agent retrieves the verified AAS catalog without ranking, inspects evidence, and records its exact selected IDs in a proposed stack.
|
||||
- **Other MCP tools** connect an assistant to external systems such as APIs, databases, browsers, or hosted services.
|
||||
- **The `aas` CLI** validates the durable project profile and agent-selected stack, then previews exact lifecycle operations under human control.
|
||||
|
||||
The two are complementary, not competing.
|
||||
These surfaces are complementary. AAS Core connects them around the approved `aas-stack.json` manifest.
|
||||
|
||||
## What a skill does
|
||||
|
||||
A skill gives the model better instructions for a repeated task such as:
|
||||
|
||||
- planning a feature
|
||||
- reviewing code
|
||||
- running a security audit
|
||||
- writing a README
|
||||
- debugging a failing test suite
|
||||
- planning a feature;
|
||||
- reviewing code;
|
||||
- running a security audit;
|
||||
- writing a README;
|
||||
- debugging a failing test suite.
|
||||
|
||||
In practice, a skill improves the assistant's decision-making, structure, and process for a task.
|
||||
In practice, a skill improves the assistant's decision-making, structure, and process. It remains content, not an executable capability or a grant of authority.
|
||||
|
||||
Example:
|
||||
Examples:
|
||||
|
||||
- `@brainstorming` helps the model clarify requirements before implementation.
|
||||
- `@lint-and-validate` helps the model run the right quality checks before claiming success.
|
||||
- `@lint-and-validate` helps the model run appropriate quality checks before claiming success.
|
||||
|
||||
## What an MCP tool does
|
||||
## What AAS MCP does
|
||||
|
||||
An MCP tool gives the model a capability it would not otherwise have, such as:
|
||||
AAS MCP is part of this repository's product, not an unrelated external integration. Codex or Claude uses it to call the same deterministic AAS Core that powers the CLI projections.
|
||||
|
||||
- reading from a database
|
||||
- calling GitHub APIs
|
||||
- fetching docs from a service
|
||||
- creating calendar events
|
||||
- querying an external system
|
||||
It exposes exactly:
|
||||
|
||||
In practice, an MCP tool expands what the assistant can do in the world.
|
||||
- `search_skills`;
|
||||
- `get_skill`;
|
||||
- `compose_stack`;
|
||||
- `inspect_stack`;
|
||||
- `diff_stack`;
|
||||
- the `aas://skills/{id}` resource template.
|
||||
|
||||
The agent inspects the project using its normal local capabilities, searches and reads the complete catalog, and chooses the exact skills. AAS MCP does not scan the repository itself, and Core does not rank or exclude candidates. Catalog metadata is informational only.
|
||||
|
||||
AAS MCP is local stdio, process-per-session, read-only, offline-capable, and contains no model credentials or telemetry. Its tool calls do not install or remove skills, apply a stack, update catalogs, or edit host configuration.
|
||||
|
||||
## What other MCP tools do
|
||||
|
||||
An external MCP tool may give the model a capability it would not otherwise have, such as:
|
||||
|
||||
- reading from a database;
|
||||
- calling GitHub APIs;
|
||||
- fetching documentation from a service;
|
||||
- creating calendar events;
|
||||
- querying or changing another system.
|
||||
|
||||
Those tools expand what the assistant can do in the world. Their permissions, network behavior, and write boundaries depend on each server. They are different from the deliberately narrow AAS MCP catalog/composition boundary.
|
||||
|
||||
## What the CLI does
|
||||
|
||||
The `aas` CLI is the explicit operational interface for:
|
||||
|
||||
- catalog status and updates;
|
||||
- MCP configuration;
|
||||
- validation and composition of an agent-selected stack;
|
||||
- manifest validation;
|
||||
- plan creation and read-only diagnostics.
|
||||
|
||||
The durable artifact is `aas-stack.json`, which pins catalog identity, targets, the project profile, and exact skill IDs. The agent proposes it; the user reviews it. It has no Core selection policy. `stack validate` checks it, and `stack plan` creates an immutable preview bound to the observed managed state and exact operations.
|
||||
|
||||
`stack apply` and `stack recover` exist only for controlled preview development. They are experimental, disabled by default, and are not supported or certified preview safety claims.
|
||||
|
||||
## The easiest mental model
|
||||
|
||||
Use this rule:
|
||||
- **Skills provide the operating guidance.**
|
||||
- **AAS MCP gives the agent complete catalog access and records the selection the agent makes.**
|
||||
- **`aas-stack.json` records what the user approved.**
|
||||
- **The CLI validates and previews the lifecycle.**
|
||||
- **Other MCP servers provide access to outside systems.**
|
||||
|
||||
- **Skills tell the assistant how to work.**
|
||||
- **MCP tools tell the assistant what systems it can touch.**
|
||||
## Which path should you start with?
|
||||
|
||||
If you only install tools, the assistant may have access but still behave inconsistently.
|
||||
Start with **AAS Core** when:
|
||||
|
||||
If you only install skills, the assistant may know the workflow but still lack the capability to reach the external system it needs.
|
||||
- you use Codex or Claude with local MCP support;
|
||||
- you want the agent to compose a small stack from project evidence;
|
||||
- you need complete catalog access and a reproducible manifest of the agent's exact selection;
|
||||
- you want a reviewable plan before any skill changes.
|
||||
|
||||
Together, they are much stronger.
|
||||
Start with a **direct skill or specialized plugin** when:
|
||||
|
||||
## Which one should you start with?
|
||||
- the host does not yet have a native AAS MCP configuration adapter;
|
||||
- you already know the exact skill or fixed domain pack you want;
|
||||
- you prefer manual invocation without a managed stack lifecycle.
|
||||
|
||||
Start with **skills** if:
|
||||
Add **other MCP tools** when the work needs live access to APIs, services, databases, or hosted platforms. A stack can contain skills that guide those integrations without granting the external permissions itself.
|
||||
|
||||
- you want better planning, coding, debugging, testing, or review behavior immediately
|
||||
- you are working mostly in local files and terminal flows
|
||||
- you want reusable playbooks before adding more integrations
|
||||
## Preview limits
|
||||
|
||||
Start with **MCP tools** if:
|
||||
|
||||
- your main blocker is access to external systems
|
||||
- you need the model to call APIs, query services, or interact with hosted platforms
|
||||
- you already like the model's workflow quality, but need more reach
|
||||
|
||||
Use **both** when:
|
||||
|
||||
- you want reliable workflows plus external capabilities
|
||||
- you are building agent systems, internal tooling, or multi-step operational flows
|
||||
|
||||
## How this repo fits in
|
||||
|
||||
Agentic Awesome Skills is primarily a **skill library**:
|
||||
|
||||
- installable `SKILL.md` playbooks
|
||||
- bundles for role-based starting points
|
||||
- workflows for ordered execution patterns
|
||||
- tool-specific guides for Claude Code, Cursor, Codex CLI, Gemini CLI, and others
|
||||
|
||||
Many skills in this repo also explain how to work with MCP, APIs, and other integrations, but the repository itself is centered on reusable workflow guidance rather than acting as an MCP server.
|
||||
AAS Core helps Codex and Claude search and read the complete local catalog, choose exact skill IDs, and preserve them in a reproducible stack. Metadata may be reported as unknown, but it is informational and never blocks selection or use. Apply and recovery remain experimental.
|
||||
|
||||
## Good next reads
|
||||
|
||||
- [AAS Core](aas-core.md)
|
||||
- [Getting Started](getting-started.md)
|
||||
- [FAQ](faq.md)
|
||||
- [Bundles](bundles.md)
|
||||
- [Workflows](workflows.md)
|
||||
- [AI Agent Skills](ai-agent-skills.md)
|
||||
- [Codex CLI Skills](codex-cli-skills.md)
|
||||
- [Gemini CLI Skills](gemini-cli-skills.md)
|
||||
- [Plugins for Claude Code and Codex](plugins.md)
|
||||
|
||||
@@ -1,28 +1,53 @@
|
||||
# Usage Guide: How to Actually Use These Skills
|
||||
# Usage Guide: Compose and Use an AAS Skill Stack
|
||||
|
||||
> **Confused after installation?** This guide walks you through exactly what to do next, step by step.
|
||||
> **Recommended path:** let Codex or Claude inspect the project, search and read the complete AAS catalog, and choose the exact skills. AAS Core records and validates that agent-owned selection.
|
||||
|
||||
## Primary workflow: agent-first composition
|
||||
|
||||
After configuring the local AAS MCP, ask your agent to inspect the repository and choose a stack for the outcome you want:
|
||||
|
||||
```text
|
||||
Inspect this repository and enumerate its primary capability areas. For each
|
||||
capability, search the complete AAS catalog, paginate or refine the query, and
|
||||
compare multiple plausible candidates with get_skill when available. Select at
|
||||
least one non-redundant valid skill per capability, explicitly report catalog
|
||||
gaps, and evaluate architecture/runtime, languages/frameworks, domain behavior,
|
||||
data/storage, integrations, testing/quality, security/privacy, UX/accessibility,
|
||||
deployment/operations, and maintenance workflow. Mark dimensions not applicable
|
||||
instead of silently omitting them. Do not stop at the first few matches or
|
||||
optimize for the smallest stack. Core has no semantic policy favoring a small
|
||||
stack; each manifest has a technical maximum of 128 selected skills. Only then
|
||||
use compose_stack with a project profile, inspect the schema 2 manifest returned
|
||||
in memory, and do not apply it.
|
||||
```
|
||||
|
||||
The agent must use `search_skills` and `get_skill` across the complete catalog, build a capability-to-skill coverage map, continue searching while a primary capability remains uncovered, choose the exact IDs itself, call `compose_stack`, then check the in-memory proposal with `inspect_stack` before presenting it. All 1,968 current catalog skills remain individually searchable, readable, and selectable. A client or the CLI can persist the reviewed `aas-stack.json`; an audit-enabled flow can then call `export_selection_evidence`, validate it with `inspect_selection_evidence`, and atomically publish the manifest and separate `aas-selection-evidence.json` sidecar in an `artifact-dir`. Use `aas stack plan` to preview the exact operations without materializing skills or managed state in the target.
|
||||
|
||||
Selection evidence contains the raw `search_skills` queries observed during the MCP session. Do not place secrets, credentials, private source text, or personal data in catalog queries.
|
||||
|
||||
Selection belongs to the coding agent. AAS MCP does not inspect the repository itself, rank or exclude skills, install skills, update catalogs, or change configuration. See [AAS Core](aas-core.md) for setup, the exact tool boundary, CLI commands, and preview limitations.
|
||||
|
||||
`stack apply` and `stack recover` are experimental, disabled by default, and are not supported or certified preview safety claims.
|
||||
|
||||
---
|
||||
|
||||
## "I just installed the repository. Now what?"
|
||||
## Alternative workflow: direct skill installation
|
||||
|
||||
Great question! Here's what just happened and what to do next:
|
||||
If you came in through a **Claude Code** or **Codex** plugin instead of AAS Core or a full library install, invoke individual skills in prompts. Plugins ship a fixed plugin-safe subset; AAS Core instead validates and records the exact stack the agent selected from the verified catalog in `aas-stack.json`. See [plugins.md](plugins.md) for the distribution model.
|
||||
|
||||
If you came in through a **Claude Code** or **Codex** plugin instead of a full library install, the mental model is the same: you still invoke individual skills in prompts. The main difference is that plugins ship the plugin-safe subset. See [plugins.md](plugins.md) for the install model.
|
||||
|
||||
### What You Just Did
|
||||
### What direct distribution provides
|
||||
|
||||
When you ran `npx agentic-awesome-skills` or cloned the repository, you:
|
||||
|
||||
✅ **Downloaded 1,965+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
|
||||
✅ **Downloaded 1,969+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
|
||||
✅ **Made them available** to your AI assistant
|
||||
❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
|
||||
|
||||
Think of it like installing a toolbox. You have all the tools now, but you need to **pick which ones to use** for each job.
|
||||
Direct distribution makes skill files available to the host. It does not select a project-specific stack, record desired state, or produce a preview plan; those are AAS Core responsibilities.
|
||||
|
||||
---
|
||||
|
||||
## Step 1: Understanding "Bundles" (Recommendations or Focused Installs)
|
||||
## Direct-install Step 1: Understanding Bundles
|
||||
|
||||
**Common confusion:** "Do I need to download each skill separately?"
|
||||
|
||||
@@ -32,11 +57,7 @@ Think of it like installing a toolbox. You have all the tools now, but you need
|
||||
|
||||
Bundles are **curated groups** of skills organized by role. They help you decide which skills to start using, and they can also be exposed as focused marketplace plugins for Claude Code and Codex.
|
||||
|
||||
**Analogy:**
|
||||
|
||||
- You installed a toolbox with 1,965+ tools (✅ done)
|
||||
- Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
|
||||
- You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
|
||||
Bundles provide editorial shortlists. You can either select individual skills from a bundle or install its focused marketplace plugin where supported.
|
||||
|
||||
### What Bundles Are NOT
|
||||
|
||||
@@ -73,9 +94,7 @@ If you want only one bundle active at a time in Antigravity, use the activation
|
||||
|
||||
---
|
||||
|
||||
## Step 2: How to Actually Execute/Use a Skill
|
||||
|
||||
This is the part that should have been explained better! Here's how to use skills:
|
||||
## Direct-install Step 2: Invoke a Skill
|
||||
|
||||
### The Simple Answer
|
||||
|
||||
@@ -126,7 +145,7 @@ Use @brainstorming to plan this feature
|
||||
|
||||
---
|
||||
|
||||
## Step 3: What Should My Prompts Look Like?
|
||||
## Direct-install Step 3: Write a Focused Prompt
|
||||
|
||||
Here are **real-world examples** of good prompts:
|
||||
|
||||
@@ -182,7 +201,7 @@ Here are **real-world examples** of good prompts:
|
||||
|
||||
---
|
||||
|
||||
## Step 4: Your First Skill (Hands-On Tutorial)
|
||||
## Direct-install Step 4: Your First Skill
|
||||
|
||||
Let's actually use a skill right now. Follow these steps:
|
||||
|
||||
@@ -210,9 +229,9 @@ Let's actually use a skill right now. Follow these steps:
|
||||
|
||||
---
|
||||
|
||||
## Step 5: Picking Your First Skills (Practical Advice)
|
||||
## Direct-install Step 5: Pick Skills Manually
|
||||
|
||||
Don't try to use all 1,965+ skills at once. Here's a sensible approach:
|
||||
Don't try to use all 1,969+ skills at once. Here's a sensible approach:
|
||||
|
||||
If you want a tool-specific starting point before choosing skills, use:
|
||||
|
||||
@@ -327,7 +346,7 @@ AI: [Creates tests, sets up CI/CD, deploys to Vercel]
|
||||
|
||||
### "Can I see all available skills?"
|
||||
|
||||
Yes! Three ways:
|
||||
Yes. With AAS Core, ask the agent to call `search_skills` and inspect candidates with `get_skill`. On a direct install, you can also:
|
||||
|
||||
1. Browse [CATALOG.md](../../CATALOG.md) (searchable list)
|
||||
2. Run `ls ~/.agents/skills/` (or your actual install path)
|
||||
@@ -343,7 +362,7 @@ Usually no, but if your AI doesn't recognize a skill:
|
||||
|
||||
### "Can I load all skills into the model at once?"
|
||||
|
||||
No. Even though you have 1,965+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
|
||||
No. Even though you have 1,969+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
|
||||
|
||||
The intended pattern is:
|
||||
|
||||
@@ -394,7 +413,13 @@ Use @skill-creator to help me build a custom skill for [your task]
|
||||
|
||||
## Next Steps
|
||||
|
||||
Now that you understand how to use skills:
|
||||
For the Core-first path:
|
||||
|
||||
1. Configure the local MCP with the [AAS Core guide](aas-core.md).
|
||||
2. Ask the agent to search the complete catalog, choose exact IDs, and explain its selection.
|
||||
3. Review `aas-stack.json`, validate it, and preview the plan.
|
||||
|
||||
For direct/manual use:
|
||||
|
||||
1. ✅ **Try one skill right now** - Start with `@brainstorming` on any idea you have
|
||||
2. 📚 **Pick 3-5 skills** from your role's bundle in [bundles.md](bundles.md)
|
||||
|
||||
@@ -1,26 +1,32 @@
|
||||
# Visual Quick Start Guide
|
||||
# Visual Guide: AAS Core and Skill Distribution
|
||||
|
||||
**Learn by seeing!** This guide uses diagrams and visual examples to help you understand skills.
|
||||
This guide shows the primary AAS Core workflow and the supporting catalog and distribution surfaces.
|
||||
|
||||
---
|
||||
|
||||
## The Big Picture
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────────────────────────┐
|
||||
│ YOU (Developer) │
|
||||
│ ↓ │
|
||||
│ "Help me build a payment system" │
|
||||
│ ↓ │
|
||||
├─────────────────────────────────────────────────────────────┤
|
||||
│ AI ASSISTANT │
|
||||
│ ↓ │
|
||||
│ Loads @stripe-integration skill │
|
||||
│ ↓ │
|
||||
│ Becomes an expert in Stripe payments │
|
||||
│ ↓ │
|
||||
│ Provides specialized help with code examples │
|
||||
└─────────────────────────────────────────────────────────────┘
|
||||
PROJECT
|
||||
│ inspected by Codex or Claude, not by AAS
|
||||
▼
|
||||
AGENT SEARCHES + READS COMPLETE LOCAL CATALOG
|
||||
│
|
||||
▼
|
||||
CODEX OR CLAUDE CHOOSES EXACT SKILL IDS
|
||||
│
|
||||
▼
|
||||
compose_stack ── validates · pins · never recommends
|
||||
│
|
||||
▼
|
||||
AGENT PROPOSES aas-stack.json (no selection policy)
|
||||
│
|
||||
├────────► WORKBENCH (optional browser-local review)
|
||||
▼
|
||||
CLI VALIDATE ──► CLI PLAN ──► HUMAN REVIEW
|
||||
|
||||
Supported path: stop after plan review.
|
||||
Apply and recovery remain experimental.
|
||||
```
|
||||
|
||||
---
|
||||
@@ -34,7 +40,7 @@ agentic-awesome-skills/
|
||||
├── 📄 CONTRIBUTING.md ← Contributor workflow
|
||||
├── 📄 CATALOG.md ← Full generated catalog
|
||||
│
|
||||
├── 📁 skills/ ← 1,965+ skills live here
|
||||
├── 📁 skills/ ← 1,969+ skills live here
|
||||
│ │
|
||||
│ ├── 📁 brainstorming/
|
||||
│ │ └── 📄 SKILL.md ← Skill definition
|
||||
@@ -47,7 +53,7 @@ agentic-awesome-skills/
|
||||
│ │ └── 📁 2d-games/
|
||||
│ │ └── 📄 SKILL.md ← Nested skills also supported
|
||||
│ │
|
||||
│ └── ... (1,965+ total)
|
||||
│ └── ... (1,969+ total)
|
||||
│
|
||||
├── 📁 apps/
|
||||
│ └── 📁 web-app/ ← Interactive browser
|
||||
@@ -66,7 +72,7 @@ agentic-awesome-skills/
|
||||
|
||||
---
|
||||
|
||||
## How Skills Work (Flow Diagram)
|
||||
## Alternative: Direct Skill Distribution
|
||||
|
||||
```
|
||||
┌──────────────┐
|
||||
@@ -90,7 +96,7 @@ agentic-awesome-skills/
|
||||
│
|
||||
↓
|
||||
┌──────────────┐
|
||||
│ 5. RESULT │ You get specialized help!
|
||||
│ 5. RESULT │ The agent follows the selected instructions
|
||||
└──────────────┘
|
||||
```
|
||||
|
||||
@@ -100,7 +106,7 @@ agentic-awesome-skills/
|
||||
|
||||
```
|
||||
┌─────────────────────────┐
|
||||
│ 1,965+ SKILLS │
|
||||
│ 1,969+ SKILLS │
|
||||
└────────────┬────────────┘
|
||||
│
|
||||
┌────────────────────────┼────────────────────────┐
|
||||
@@ -201,7 +207,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
|
||||
│ ├── 📁 brainstorming/ │
|
||||
│ ├── 📁 stripe-integration/ │
|
||||
│ ├── 📁 react-best-practices/ │
|
||||
│ └── ... (1,965+ total) │
|
||||
│ └── ... (1,969+ total) │
|
||||
└─────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user