antigravity-awesome-skills

Carries strong trust indicators from repository metadata

For Codex and Claude, start with the AAS Core guide: configure the local MCP, ask the agent to inspect the project and choose exact IDs from the full catalog, review the proposed aas-stack.json, then run CLI validation and planning. The MCP and validation are read-only. Planning writes only the requested plan artifact; it does not materialize skill payloads or AAS managed state in the target.

Use direct installation when your host does not yet have a native AAS Core adapter, when you already know the exact skill IDs, or when you deliberately prefer manual selection:

• Specialized plugins when the job has a clear domain.
• Full library install when you want every skill available in a local skills directory.
• Bundles and workflows when you want role-based recommendations or ordered execution playbooks.

Direct skill install

# Antigravity: preview an exact, agent-selected set before writing.
npx agentic-awesome-skills --antigravity --skills brainstorming,systematic-debugging --dry-run

# Antigravity CLI slash commands (agy): ~/.gemini/antigravity-cli/skills/<skill>/SKILL.md
npx agentic-awesome-skills --agy

The npm installer uses a shallow, release-pinned clone by default so first-run installs stay lighter than a full repository history checkout while matching the published npm package version. Use --tag main only when you intentionally want the current repository tip.

Antigravity watches ~/.agents/skills and may load enough installed instructions to exhaust its context, slow startup, trigger truncation errors, or enter a crash loop. For that target, the installer stops before cloning or writing unless you provide --skills, a metadata filter, or the explicit --all override. The bare npx agentic-awesome-skills command uses the same protected Antigravity target.

The recommended flow is to ask Codex or Claude with the read-only AAS Core MCP configured to inspect the project, search the complete catalog, and choose exact skill IDs. AAS MCP selects and validates IDs but does not install them; the agent or user then previews the direct installation with the command above and repeats it without --dry-run after review.

Other direct-install targets retain the legacy-compatible full-catalog behavior when no selectors are supplied. The CLI prints the catalog's risk summary first: a full install includes critical and authorized-use-only offensive instructions. Installation copies files; it does not execute their commands, but an agent may act on an installed skill later. Prefer an exact reviewed set:

npx agentic-awesome-skills audit --skills brainstorming,backend-dev-guidelines
npx agentic-awesome-skills --skills brainstorming,backend-dev-guidelines --dry-run

If you deliberately accept the context and crash-loop risk, the complete Antigravity catalog remains available through explicit consent:

npx agentic-awesome-skills --antigravity --all

The audit reads the selected skill directories without executing them and reports command, network, credential, filesystem, privileged, destructive, symlink, and binary signals. It is a review aid, not a safety certificate. See Security, trust, and antivirus alerts.

Focused single-skill install with GitHub CLI (preview)

GitHub CLI can preview and install one exact skill for Copilot and other supported hosts. Use an exact SKILL.md path in this large, mirrored repository so the selected source is unambiguous and discovery stays fast:

gh skill preview sickn33/agentic-awesome-skills skills/brainstorming/SKILL.md
gh skill install sickn33/agentic-awesome-skills skills/brainstorming/SKILL.md \
  --agent github-copilot --scope user --pin v14.2.0

gh skill support is currently a GitHub CLI preview and may change. Install a focused skill or plugin surface for the job; do not use --all unless you intentionally want every discovered canonical and mirrored skill.

Verify the install

test -d ~/.agents/skills && echo "Skills installed in ~/.agents/skills"

Run your first skill

Use @brainstorming to plan a SaaS MVP.

Prefer plugins for Claude Code or Codex?

• Use a specialized plugin when you want a focused marketplace-style distribution.
• Use the full-library plugin only when you want the widest plugin-safe catalog.
• Read Plugins for Claude Code and Codex for full-library plugin install vs specialized plugin install vs direct skills install.

Keep the root README short; use the dedicated docs for recovery and platform-specific guidance.

• If you are confused after installation, start with the Usage Guide.
• For Core setup, trust boundaries, stack manifests, and preview status, use the AAS Core guide.
• On native Windows, AAS_ADAPTER_WINDOWS_ACL_FAILED refers to the configuration path checked with PowerShell Get-Acl, not the cache and not icacls; do not approve until preview returns an approval digest.
• If you integrate agentic-awesome-skills into a host, read the discovery contract first: Stable Skills Manifest v1.
• For Windows truncation or context crash loops, use docs/users/windows-truncation-recovery.md.
• For Linux/macOS overload or selective activation, use docs/users/agent-overload-recovery.md.
• For OpenCode or other .agents/skills installs, prefer a reduced install such as npx agentic-awesome-skills --path .agents/skills --category development,backend --risk safe,none.
• For plugin install details, host compatibility, and marketplace-safe distribution, use docs/users/plugins.md.