Set Up Agent Skills

Everything below is the prompt itself. Copy it as it is, or point your agent at the raw Markdown: https://php-testo.github.io/docs/ai/prompts/skills.md

Make the AI skills that ship with Testo available to the agents working on this project. Work through the steps in order and report the result.

Testo bundles a skill per scenario — writing tests, data providers, test doubles, async tests, benchmarks, coverage, mutation testing, migrating from PHPUnit, authoring plugins, editing testo.php. llms.txt says what the API offers; a skill says when to reach for what and where the pitfalls are, and several of them carry ready-made scripts. They live inside the installed package, so an agent only sees them once they are laid out where it looks.

That layout is the job of the llm/skills Composer plugin.

1. Collect the agent directories

Claude Code reads .claude/skills/, Cursor reads .cursor/skills/, other agents have their own conventional paths. Ask which agents work on this project and look at what the repository already has — those paths become the aliases below.

The layout to aim for: one real directory (.agents/skills, tool-agnostic) with a link per agent pointing at it, so every agent reads the same files. A single-agent project can just as well make that agent's own path the target.

2. Pre-allow the plugin

Composer asks for permission to run a plugin, and an agent's shell run is not the place to discover an interactive prompt. Add the entry to composer.json before installing:

{
    "config": {
        "allow-plugins": {
            "llm/skills": true
        }
    }
}

3. Install and configure in one line

composer require --dev llm/skills
composer skills:init --quick --no-interaction \
    --target=.agents/skills --alias=.claude/skills --alias=.cursor/skills

skills:init writes skills.json at the project root and syncs right away — the flags decide what lands in the file:

• --quick takes every remaining answer from the detected project layout and confirms once; --no-interaction makes it final, which is what you want in a scripted run.
• --target=PATH — the real skills directory (default .agents/skills).
• --alias=PATH — repeatable, one per agent path; passing it at all replaces the detected list.
• --trust=PATTERN — repeatable, for the project's own skill-shipping vendors. Testo is on the built-in trusted list, and so is any package required directly, so plain Testo setups need none.
• --no-auto-sync — opt out of re-syncing after composer install / update. Auto-sync is on by default; leave it on so skills follow the installed versions.
• --no-discovery — consider only packages that declare extra.skills. Discovery is on by default, which is how a package that merely ships SKILL.md files is picked up.
• --force — re-run over an existing skills.json. Without it the command refuses to overwrite one, so check whether the file is already there and report what it says instead of forcing it.

Left alone in a project with no configuration, the plugin makes the same offer by itself on the next composer install / update — one confirmation. That path needs an interactive terminal, so run the command explicitly.

4. Verify

composer skills:show             # what is synced, what is skipped, and why
composer skills:update           # re-sync by hand; --dry-run previews

The step is done when the target directory holds the testo-* skill directories and every alias path resolves to the target. A [skip] not trusted line names a donor waiting for a --trust pattern; a directory that already holds real files of its own is reported rather than replaced, and has to be resolved by hand.

Local edits survive a sync: only files the donor actually ships get overwritten, so a local.md dropped next to a bundled skill stays put.

5. Commit the config, ignore the payload

skills.json belongs in git next to composer.json — it is what makes the setup reproducible for the whole team. The target directory and the alias links are generated from vendor/ and rebuilt by auto-sync, so recommend adding them to .gitignore; ask before committing them instead, since a team that wants skills available without running Composer may prefer them tracked.

6. Report

Report what skills.json declares, which agent paths are wired to the target, that the testo-* skills are present, and anything skills:show skipped along with the reason.