Bootstrap a VantagePeers mission with the full IRP task chain (plan → execute → verify → ship) wired with dependencies in a single skill invocation. Use this skill whenever the user says "bootstrap mission", "start a mission for X", "scaffold IRP for X", "create mission with tasks" — even if they don't say "mission-bootstrap" explicitly.
The only sanctioned way to open a pull request. In one invocation it does three atomic acts: (1) runs gh pr create with the fixed marker # via-open-pr appended, (2) creates exactly one reviewer (Eta) review task citing PR number, head SHA, and repo, (3) notifies channel eta,pi with the v2 telegraphic grid. Use this skill whenever the user says "open a PR", "create a PR", "raise a pull request", "gh pr create" — even without naming open-pr explicitly.
Pi-signed merge of an Eta-APPROVED fleet client-facing PR — wraps the 7-hook gauntlet (enforce-pi-authorization + enforce-vr-consult + enforce-create-task-notify-followup + enforce-friction-field) into one atomic skill that passes first-try.
Process reproductible de recherche pricing pour tout produit/service ElPi Corp. 4 axes parallèles avec gate approval competitors. Subagent B = 2 phases (candidates list → approval Laurent → deep scrape Firecrawl). Output multi-format pour comparison table landing + articles blog "Notre app vs competitor".
Search VantagePeers for stored memories. Use this skill whenever the user says "recall", "remember", "what do we know about", "search memory", "look up", "find in memory", or asks about past decisions, context, or stored knowledge -- even if they don't say "recall" explicitly.
Force any gate/review request for an artifact NOT versioned in git (a gitignored hook, an adversarial probe/sonde, a local one-off script, or an announced-but-not-transported VR content pair) to transport the replayable artifact itself via create_briefing_note — never just ratios + a sha256. A reviewer cannot refute what they cannot replay. Use this skill whenever the user says "gate this", "send for review", "ask Eta/Omega/Pi to review", "request a verdict on X" -- even if they don't say "request-gate" explicitly, whenever the artifact in question lives outside git.
The reviewer's routine for rendering a verdict on a GitHub pull request. Use this whenever you are asked to "review PR", "gate PR", "render a verdict", "re-gate", or issue an APPROVED / REVISE on a pull request — even if the words "review-pr" are not said. It mechanizes the flow rule "update before verdict": the reviewer brings the PR up to the current base BEFORE gating, then gates the head it OBTAINED, so a verdict is never invalidated by a base that moved.
Daily standup report -- what was done, what's in progress, blockers, git status. Use this skill whenever the user says "standup", "status report", "daily report", "what did you do", "progress report", "sitrep", "report", "where are you", or asks about current work status -- even if they don't say "standup" explicitly.
Guarantee a VantagePeers task exists and is really started before any work action (edit, mutating command, sub-agent build), and record real elapsed time on completion. Use this skill whenever you are about to start working — "start work", "begin task", "pick up task", "I'm going to edit/build/deploy" — or when the enforce-work-under-task hook blocks an action for lack of an active task.
Audit every fleet Vercel project for VERCEL_FORCE_NO_BUILD_CACHE on Production, Preview and Development, write a conformity report with paste-ready remediation commands, and notify the owner of each non-conformant project. Use this skill whenever the user says "vercel env audit", "audit vercel projects", "vercel build cache", "cache poisoning audit", "check VERCEL_FORCE_NO_BUILD_CACHE" -- even if they don't say "vercel-env-audit" explicitly.
Write a daily AI Diary entry in Pi's voice for perfectaiagent.xyz. Use this skill whenever the user says "diary", "write diary", "daily entry", "Pi's diary", "journal entry", "day entry", or asks to document what happened today — even if they don't say "diary" explicitly.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.