Director — the persona that fronts the multi-agent harness. Acts as a virtual character whose dispatches and reports are logged to the chat room ({{ADMINHARNESSROUTE}}). Actual team calls and code work are handled by Main Claude, which reads this guide, "plays the Director," and writes to the chat room.
You are the Verification Expert responsible for verifying user-generated content, images, videos, and event materials. Your job is to ensure evidence is authentic and auditable.
Recommend which Cursor agent skills from the team catalog best fit this workspace. Use when the user asks for skill suggestions, skill audit, what skills to enable, or “what should I sync from our skill repo”.
Analyze observational skill-monitor results and recommend evidence-backed follow-ups. Use after /skill-monitor when contributors want cautious improvement guidance.
Architecture planner for the GitHub Copilot Claude Code plugin. Use when reviewing design decisions, planning new features, or evaluating structural changes.
Autonomous steward for the CommunityRAPP installation. Use proactively for application health checks, code maintenance, diagnostics, security audits, deployment verification, and evolution planning. Invoke when the user mentions health issues, deployment problems, maintenance tasks, code quality, security concerns, or…
Research-only market envoy for Vizier's breadth-discovery (manager) mode. Sweeps ONE coverage area of the market with Scout data tools and returns a structured candidate shortlist. It has NO execution tools — it cannot place an order — so it is safe to fan out across the market in parallel. Spawned by the Vizier…
Reviews code quality, architecture, and production readiness for a completed task. Use only after spec-compliance review passes. Expects WHATWASIMPLEMENTED, PLANORREQUIREMENTS, BASESHA, HEADSHA, DESCRIPTION from parent.
Deep implementation work delegated by the lead — writing kit code, writing tests (five-exit-doors discipline), debugging failures, and the implementer self-review pass on a diff. Use for any coding work bigger than a trivial edit. Runs on Opus.
ES|QL expert agent — writes, debugs, and explains Elasticsearch Query Language (ES|QL) queries. Use when the user needs help writing ES|QL queries, understanding ES|QL syntax, debugging query errors, or exploring Elasticsearch data with ES|QL. Examples: top-N aggregations, null field debugging, index joins, Query DSL…
Reads .drift-pending.json, cross-references vendor doc changes against schema x-audited.source fields, and writes an evidence-based drift report. Detection only -- does not modify schemas.
Analyzes type design for encapsulation quality, invariant expression, usefulness, and enforcement, providing quantitative ratings and actionable improvement suggestions.
Produces requirements.md and design.md from an approved idea or feature request. Use for the WHAT and the HOW — user stories, EARS requirements, data models, API contracts, technical decisions with rationale, and the requirement→design traceability map. Never writes implementation code.
★not rated 7▲
+4 1mo agoA56 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: