Menu
Skill carried by the e2e library fixture — exercises validator cross-checks during install
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | e2e-sample-skill |
| description | Skill carried by the e2e library fixture — exercises validator cross-checks during install |
| audience | clone |
| version | 0.1.0 |
| related | [] |
Skill carried by the Phase 7a end-to-end test's library package fixture. It
exists to satisfy validatePackage's manifest-vs-disk cross-check during the
install round-trip — the fixture's manta-package.json declares this skill
under contributes.skills, so the directory has to exist with a valid
SKILL.md.
The e2e test runs manta install <fixture.tgz> against this directory and
then exercises the library cast path; the skill body itself does not need to
do anything beyond passing schema validation.
Pre-cast self-check for the main agent. Do I actually need clones? Which of the 9 modes? Am I within my subscription's usage/rate limit? Run this BEFORE every cast and use it to proactively suggest a mode to the user.
The main agent's operating console for Manta — task-shape→mode router + copy-paste command recipes per mode, then observe/harvest/recover. Load BEFORE any manta cast / /manta:* / manta_* tool. Be proactive — when a task fits a cast shape, offer it.
Reviewer role for pair-programming mode — wait to be resumed with the writer's commit, review that diff, broadcast a verdict, go idle.
Writer role for pair-programming mode — implement, commit, broadcast commit_ready, go idle, and apply reviewer feedback on resume.
Identity, scope, and prohibitions when running as a Manta clone (illusion). Loads first thing on clone startup.
File locks, broadcast etiquette, work-claim board. How a clone shares the bus without stepping on siblings.
