Core & tools

Core, CLI, and MCP. One reviewable workflow.

Your agent chooses the skills. AAS records and validates that selection. You review the plan before any separate installation.

AAS Core: the workflow and its contracts

Core is the local boundary for discovering skills, recording exact agent-selected IDs, validating a stack manifest, and previewing a plan. The catalog provides evidence; the coding agent makes the project-specific selection. Core does not choose a stack through a ranking or scoring policy.

Browse the skill catalog Read the full Core guide

The CLI: persistence, validation, and planning

The aas command-line tool configures the local runtime and works with explicit artifact paths. aas stack validate checks a manifest against the schema and catalog. aas stack plan writes the requested immutable plan artifact without installing skills or changing the project target. The optional audit checks consistency across artifacts.

Validation and plan examples Get started with your agent

The MCP: tools your agent can call

The local stdio MCP exposes catalog search, skill and bundle inspection, stack composition, and evidence tools to supported clients. Discovery is read-only and offline-capable. compose_stack validates the exact IDs selected by the agent and returns a manifest in process memory; the client or CLI persists it separately. A local stdio host is distinct from a public HTTPS connector.

Configure the local MCP Codex setup Claude Code setup

The complete path

1. Follow your client’s setup guide. 2. Let the agent inspect the project, search the complete catalog, and read candidates. 3. Review its exact selection and stack manifest. 4. Validate and produce a plan with the CLI. 5. Inspect the artifacts in the Workbench. Your browser shortlist is a starting list to discuss with the agent, not a validated Core stack.

Walk through the Core quick path Open the Workbench and its recorded example

From review to installation

The supported Core path is manifest validation and a non-applying plan preview. A direct installer preview is a separate handoff using reviewed IDs, an exact catalog version, and a destination you approve. It does not apply a Core plan. Check the instructions and prerequisites before any installation; apply and recovery remain experimental opt-ins outside the supported preview path.

Use the reviewed selection Compare focused plugin packs

Privacy and practical limits

AAS skills-only bundles do not independently collect telemetry. Local discovery can work offline, while your agent client, model provider, and tools you enable have their own data policies and costs. The hosted Workbench keeps imports in browser memory. Schema and integrity checks do not establish that a skill is safe or suitable for your project.

Trust & transparency Team adoption guide Privacy, trust, and limits