opencode-skills-collection 4.0.52 → 4.0.54

package/bundled-skills/docs/users/claude-code-skills.md

@@ -1,89 +0,0 @@
-# AAS Core with Claude Code
-
-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.
-
-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.
-
-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
-
-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 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 2,108+ 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.
-
-## Direct install and plugins
-
-These are alternative delivery paths for users who already know which skill payload they want.
-
-### Option A: installer CLI
-
-```bash
-npx agentic-awesome-skills --claude
-```
-
-### Option B: Claude Code plugin marketplace
-
-```text
-/plugin marketplace add sickn33/agentic-awesome-skills
-/plugin install agentic-awesome-skills
-```
-
-The Claude marketplace plugin is a plugin-safe filtered distribution of the repo. Skills that still require portability hardening or explicit setup metadata remain available in the repository, but are excluded from the plugin until they are ready.
-
-You can also install a focused bundle plugin instead of the root plugin when you want a narrower starter surface. See [plugins.md](plugins.md) and [bundles.md](bundles.md).
-
-### Verify the install
-
-```bash
-test -d .claude/skills || test -d ~/.claude/skills
-```
-
-## Best starter skills for Claude Code
-
-- [`brainstorming`](../../skills/brainstorming/): plan features and specs before writing code.
-- [`lint-and-validate`](../../skills/lint-and-validate/): run fast quality checks before you commit.
-- [`create-pr`](../../skills/create-pr/): package your work into a clean pull request.
-- [`systematic-debugging`](../../skills/systematic-debugging/): investigate failures with a repeatable process.
-- [`security-auditor`](../../skills/security-auditor/): review APIs, auth, and sensitive flows with a security lens.
-
-## 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.
-```
-
-```text
-Use @lint-and-validate on src/routes/api.ts and fix the issues you find.
-```
-
-```text
-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.
-- Go back to the main landing page in [`README.md`](../../README.md) when you want the full installation matrix.

package/bundled-skills/docs/users/codex-cli-skills.md

@@ -1,88 +0,0 @@
-# AAS Core with Codex CLI
-
-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.
-
-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.
-
-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
-
-Configure AAS Core for Codex, then describe the real task instead of manually searching a large directory. The normal flow is:
-
-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 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 still supports direct installs and plugin distributions as delivery surfaces.
-
-## 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
-```
-
-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 Core, Codex plugins, and direct installs relate, read [plugins.md](plugins.md).
-
-### Verify the install
-
-```bash
-test -d .codex/skills || test -d ~/.codex/skills
-```
-
-## Best starter skills for Codex CLI
-
-- [`brainstorming`](../../skills/brainstorming/): clarify requirements before touching code.
-- [`concise-planning`](../../skills/concise-planning/): turn ambiguous work into an atomic execution plan.
-- [`test-driven-development`](../../skills/test-driven-development/): structure changes around red-green-refactor.
-- [`lint-and-validate`](../../skills/lint-and-validate/): keep quality checks close to the implementation loop.
-- [`create-pr`](../../skills/create-pr/): wrap up work cleanly once implementation is done.
-
-## 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.
-```
-
-```text
-Use @test-driven-development to add tests before changing this parser.
-```
-
-```text
-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.
-- Return to [`README.md`](../../README.md) for the full compatibility matrix.

package/bundled-skills/docs/users/cursor-skills.md

@@ -1,56 +0,0 @@
-# Cursor Skills
-
-If you searched for **Cursor skills** on GitHub, this repository is built to be a practical starting point: installable skills, clear usage docs, and a large library that works well with Cursor chat workflows.
-
-Agentic Awesome Skills supports Cursor through the `.cursor/skills/` path and keeps the entry point simple: install once, then invoke the skills you need in chat.
-
-## How to use Agentic Awesome Skills with Cursor
-
-Install the library into Cursor's skills directory, then call skills directly in chat with `@skill-name`. Cursor works especially well when you combine planning, implementation, and validation skills inside one conversation.
-
-## Why use this repo for Cursor
-
-- It supports Cursor directly with a dedicated install flag.
-- It works well for UI-heavy and full-stack workflows where Cursor users often want planning, implementation, validation, and debugging in one place.
-- It includes bundles and workflows, which are helpful when you do not want to hand-pick from a huge catalog immediately.
-- It is broad enough for frontend, backend, infra, testing, product, and growth work without switching repositories.
-
-## Install Cursor Skills
-
-```bash
-npx agentic-awesome-skills --cursor
-```
-
-### Verify the install
-
-```bash
-test -d .cursor/skills || test -d ~/.cursor/skills
-```
-
-## Best starter skills for Cursor
-
-- [`frontend-design`](../../skills/frontend-design/): improve UI direction and interaction quality.
-- [`react-best-practices`](../../skills/react-best-practices/): tighten React and Next.js implementation patterns.
-- [`tailwind-patterns`](../../skills/tailwind-patterns/): structure utility-first UI work cleanly.
-- [`testing-patterns`](../../skills/testing-patterns/): add focused unit and integration tests.
-- [`api-design-principles`](../../skills/api-design-principles/): define clean interfaces before implementation spreads.
-
-## Example Cursor prompts
-
-```text
-@frontend-design redesign this landing page to feel more premium and conversion-focused.
-```
-
-```text
-@react-best-practices review this component tree and fix the biggest performance problems.
-```
-
-```text
-@testing-patterns add tests for the checkout state machine in this folder.
-```
-
-## What to do next
-
-- Read [`best-cursor-skills-github.md`](best-cursor-skills-github.md) if you want a shortlist of GitHub options for Cursor-compatible skills.
-- Use [`bundles.md`](bundles.md) if you want a role-based starting point such as Web Wizard or Full-Stack Developer.
-- Open [`usage.md`](usage.md) if you want more prompt examples and execution patterns.

package/bundled-skills/docs/users/discovery-manifest.md

@@ -1,65 +0,0 @@
-# Stable Skills Manifest v1 for Custom 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)
-
-- **Canonical file:** `skills_index.json` at repository root.
-- **Mirror file:** `data/skills_index.json` must be an exact compatibility mirror of `skills_index.json`.
-- **Format:** JSON array, one object per skill.
-- **Schema:** [`schemas/skills-index.v1.schema.json`](../../schemas/skills-index.v1.schema.json)
-
-## Required fields
-
-Each manifest entry includes:
-
-- `id` – skill identifier (same as `@skill-id`).
-- `path` – relative skill folder, e.g. `skills/brainstorming`.
-- `category` – grouping used by UI/search surfaces.
-- `name` – display name.
-- `description` – short purpose/trigger summary.
-- `risk` – one of repo risk labels.
-- `source` – source of authority/trust metadata.
-- `date_added` – ISO date string or `null`.
-
-Additional fields are allowed, and `plugin` metadata is optional.
-
-## Recommended host behavior
-
-Stable integrations must not load every skill instruction file up front.
-
-- Read the manifest (`skills_index.json`).
-- Resolve only the requested `@skill-id` values from the conversation.
-- For each resolved skill, read that one `SKILL.md` lazily.
-- 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 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
-
-`data/skills_index.json` remains for downstream compatibility where clients still read from the `data/` subtree. The stable contract is that both files contain the same payload.
-
-## Quick structure example
-
-```json
-{
-  "id": "brainstorming",
-  "path": "skills/brainstorming",
-  "category": "planning",
-  "name": "brainstorming",
-  "description": "Use before any creative or constructive work.",
-  "risk": "safe",
-  "source": "official",
-  "date_added": "2026-02-27"
-}
-```
-
-## 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)