When working on Convex code, **always read convex/_generated/ai/guidelines.md first** for important guidelines on how to correctly use Convex APIs and patterns. The file contains rules that override what you may…
Plans and executes safe Convex schema and data migrations using the widen-migrate-narrow workflow and the @convex-dev/migrations component. Use this skill when a deployment fails schema validation, existing documents need backfilling, fields need adding or removing or changing type, tables need splitting or merging, or a zero-downtime migration strategy is needed. Also use when the user mentions breaking schema changes, multi-deploy rollouts, or data transformations on existing Convex tables.
Audits and optimizes Convex application performance across hot-path reads, write contention, subscription cost, and function limits. Use this skill when a Convex feature is slow or expensive, npx convex insights shows high bytes or documents read, OCC conflict errors or mutation retries appear, subscriptions or UI updates are costly, functions hit execution or transaction limits, or the user mentions performance, latency, read amplification, or invalidation problems in a Convex app.
Sets up Convex authentication with user management, identity mapping, and access control. Use this skill when adding login or signup to a Convex app, configuring Convex Auth, Clerk, WorkOS AuthKit, Auth0, or custom JWT providers, wiring auth.config.ts, protecting queries and mutations with ctx.auth.getUserIdentity(), creating a users table with identity mapping, or setting up role-based access control, even if the user just says "add auth" or "make it require login.
Wrap create_briefing_note and update_briefing_note with topic taxonomy enforcement, participants list normalization, content size pre-flight, and auto-linking of related taskIds / missionIds mentioned in the content. Use this skill whenever the user says "write briefing note", "briefing", "decision note", "create briefing", "save briefing" -- even if they don't say "briefing-write" explicitly.
Check and respond to peer messages from other orchestrators, and (in autonomous mode) also list + pick the next unblocked todo task. Use this skill whenever the user says "check messages", "read messages", "any messages", "peers", "inbox", "new messages" -- even if they don't say "check-messages" explicitly.
List the tasks assigned to the current orchestrator, sorted by priority and dependency-aware, while keeping the response under the 60 KB cap by always requesting the lite projection with a default limit. Use this skill whenever the user says "check tasks", "my tasks", "what tasks", "pending tasks", "task list", "todo list", "what should I work on", "backlog" — even if they don't say "check-tasks" explicitly.
End-of-day routine: close tasks with their time, leave the repository and the disk clean, write the diary, harvest friction, and hand over to tomorrow. Use this skill whenever the user says "close day", "end of day", "fin de journée", "bonne nuit", "wrap up", "call it a day", "close session", "daily close", or mentions ending their work session -- even if they don't say "close-day" explicitly.
This skill should be used when the user asks to "start the day", "morning plan", "daily planning", "what's on my plate today", "plan today", "session start", "daily start", or mentions wanting to organize their day or review pending tasks -- even if they don't say "daily-start" explicitly.
Pre-format every outbound peer message into the v2 telegraphic grid so it satisfies the fleet hooks (no-task-in-message marker, signature, ship-24-7, no time-estimates) on the first try AND removes the narrative slot that invites chronological prose. Use this skill whenever the user says "send a message", "DM <orch>", "broadcast", "reply to <orch>", "tell <orch> X" -- even if they don't say "dispatch-message" explicitly.
Compose and dispatch a Claude Code subagent (the `Agent` tool) with the correct brief template marker pre-injected so the `enforce-brief-template` hook never blocks. Use this skill whenever the user says "dispatch a subagent", "agent for X", "spawn agent", "delegate to subagent" — even if they don't say "dispatch-subagent" explicitly.
Close a VantagePeers task with an auto-assembled proof-token completionNote so the evidence-bound-done hook never blocks. Use this skill whenever the user says "complete task <id>", "mark done", "close <id>", "finish task", "task done", "wrap task", "close task", or asks to move a task to done/review -- even if they don't say "dispatch-task-complete" explicitly.
Create a VantagePeers task for another orchestrator with a properly-formed description (VERIFICATION + TESTS + IRP blocks + delegation triplet on batch ops + auto allow-no-notify marker on multi-task dispatch) so the enforce-task-quality + enforce-pi-task-doctrine + enforce-create-task-notify-followup hooks never block. Use this skill whenever the user says "create task for <orch>", "dispatch task", "queue work for <orch>", "ask <orch> to do X" — even if they don't say "dispatch-task-create" explicitly.
Single skill covering the full VantagePeers fix-pattern lifecycle — create a pattern from a recurring incident, log fix attempts, validate fixes with proof, link patterns to issues, and search/list existing patterns with envelope-safe defaults. Use this skill whenever the user says "fix pattern", "create fix pattern", "add fix attempt", "validate fix", "link issue to pattern", "search fix patterns", "list fix patterns" — even if they don't say "fix-pattern-cycle" explicitly.
Browse VantagePeers peer-message history with day/sender filters, envelope-safe defaults, broadcast read-receipt audits, and safe mark-as-read / delete operations, so orchestrators can audit conversations without the unread-inbox tunnel vision of check-messages. Use this skill whenever the user says "messages history", "show past messages", "messages from <peer>", "messages on day N", "broadcast status", "who read the broadcast", "mark messages read", "delete a message" -- even if they don't say "messages-history" explicitly.
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".
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.