Skip to main content
Agent Skills package Squasher-specific workflows for AI coding assistants. Use them when an assistant needs durable context for onboarding, the Squasher CLI, the hosted MCP server, or observability workflows. Skills are helper documentation for agents, not the product contract. The stable contracts are the public API, CLI behavior, MCP tool schemas, and Code Mode operation types. Install skills to help an agent choose the right Squasher surface and avoid stale setup or query guidance.

Available skills

Direct skill URLs

Agents can read all four skills and their linked reference files directly:
The dashboard setup prompt includes this URL after signup so a coding agent can map the repo, choose the right Squasher SDK or integration, make the code changes, and smoke-check the setup.

One-command setup

For local agent environments, install the Squasher skills and register the hosted Squasher MCP server in one command:
The installer adds squasher-onboard, squasher-telemetry-audit, squasher-cli, and squasher-mcp from the public skills source. It also registers https://mcp.squasher.ai/mcp for detected agent CLIs such as Codex CLI, Claude Code, Gemini CLI, and Amp. Omit -y to approve each command, or use --skills-only / --mcp-only for a narrower install.

Install

Install from the public skill index. No GitHub access is required.
The index at /.well-known/agent-skills/index.json lists every skill and its reference files. The installer downloads the same files served by the direct URLs. For project-local installation without a package manager, copy the skill folders into your repository:
If you already have a local checkout that contains these folders, install from the local path:

Use the skills

After installation, start a new agent session and ask for the skill explicitly:
The telemetry audit starts with a read-only review and requires approval for its repair plan. It does not enable future capture, increase sampling, retention, or log levels, start paid model runs, or generate synthetic production traffic.
Most assistants also activate a skill implicitly when your prompt matches its description. Explicit invocation is still useful when you are testing a new install.

Verify

Run your assistant’s skills command, if available:
Confirm that squasher-onboard, squasher-telemetry-audit, squasher-cli, and squasher-mcp appear in the list. Then test with a prompt that should not require live project data:
The answer should include: