
Use when testing per-client skill rules
Use when validating frontmatter keys
Use when testing unreachable skills
Use when testing valid context and agent configuration
Use when testing custom agent validation
Use when testing valid model configuration
Use when testing per-client skill rules
Use when testing agent without context validation
Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 385 rules.
Use when testing argument hints
Use when user asks to review code for quality and security issues.
Use when you need pull-request review help
Use when testing context without agent validation
Use when analyzing code quality
Use when validating name-directory matching
Use when testing boolean type validation
Use when testing per-client skill rules
Use when testing per-client skill rules
Use when testing injection limit validation
Use when testing invalid agent validation
Use when testing per-client skill rules
Use when testing per-client skill rules
Use when user asks to 'lint agent configs', 'validate skills', 'check CLAUDE.md', 'validate hooks', 'lint MCP'. Validates agent configuration files against 385 rules across 10+ AI tools.
Use when testing unknown tool validation
Use when deploying to production environment
Use when greeting users
Deploys to production
Use when looking up documentation
Use when testing invalid model validation
Use when testing boolean type validation
Use when validating vague skill names
Use when testing per-client skill rules
Use when testing per-client skill rules
No frontmatter here.
Use when validating windows paths
Use when testing valid hooks
Use when validating deep references
Use when validating indexed arguments
Use when testing invalid context validation
Use when testing hooks validation
Use when user wants to review code
Anticipation patterns and self-scheduling for proactive behavior. Use when deciding what to do next, before meetings, after deploys, during quiet periods, or when the agent loop needs a playbook. Keywords: anticipate, proactive, idle, self-schedule, meeting prep
Sweep open PRs across all repos: triage, rebase stale branches, fix review comments, report what's ready for owner to merge. Use when idle loop detects open PRs, on cron schedule, or when asked to check PRs. Keywords: PR sweep, open PRs, stale PRs, review comments, rebase, triage, merge ready
Monthly self-improvement brief for Cairn. Queries error_patterns, action_exemplars, experiment_windows, and session_journal to synthesize what Cairn learned, where it failed, and 3 concrete proposals for Avi to approve. Run on the 1st of each month. Keywords: growth brief, monthly review, self-improvement, what did cairn learn, how is cairn doing, monthly report
Detect agent-cairn PRs that have stalled (no activity >=90 min) and classify the failure mode to route to appropriate recovery agent.
Formalized learning loop that captures learnings, errors, and corrections to Cairn's memory system for continuous improvement. Use when: self-review, self-improve, learning loop, what did I learn, improve myself, reflect, what went wrong, error patterns, metacognition, weekly review, log this learning, should I log this. Keywords: self-review, self-improve, reflect, learn, errors, corrections, patterns, metacognition, soul, review, learning
Use when agent should review its own output before responding, or when asked to double-check work. Keywords: self-review, double-check, verify, validate, review output
Use when asked to create a new skill, write a SKILL.md, add a capability, build a skill, or make a new prompt-based tool. Also use when importing or adapting an external skill. Keywords: create skill, new skill, SKILL.md, build skill, add capability, write skill, make skill, import skill, adapt skill
Decision support with memory-backed context. Retrieves past decisions, journal history, and relevant facts before answering questions that involve a choice or tradeoff. Keywords: should I, which is better, tradeoff, compare, decide, choose, option, alternative, pros and cons, recommend
Post-install skill adaptation: read a newly installed SKILL.md, fix environment-specific references (paths, accounts, tool names), assign the skill to relevant agent types, and propose an AGENTS.md update. Triggered automatically after cairn.installSkill completes.
Manage Telegram notification batching and delivery to forum topics. Use when running digest crons, configuring notification preferences, or routing alerts to Telegram.
Autonomous coding workflow: branch, code, test, draft PR. Use when starting a coding task from the idle loop or continuing an incomplete session. Keywords: coding, implement, fix, bug, PR, CI, test, review, worktree, autonomous
Assess trust and safety of external SKILL.md files before importing into Cairn. Use when asked to vet, review, import, or check an external skill. Keywords: vet, vetting, trust, safety, review skill, check skill, import skill, external skill, security review
Generate content drafts when a PR is merged or significant code ships. Produces a Twitter/X thread, blog post outline, and changelog entry from PR title, changed files, and commit messages. Keywords: content, tweet, blog, changelog, announce, write about, PR merged, shipped, released, draft post, social, thread
Use when creating PRs, monitoring CI, addressing review comments, or shipping code. Keywords: create PR, push, CI, review, merge, ship
Use when reviewing agent security, prompt injection defenses, input sanitization, LLM security hardening, or SSRF protection. Keywords: prompt injection, agent hardening, input sanitization, LLM security, SSRF, defense in depth
Use when user asks for a digest, summary of updates, what's new, catch me up, or daily briefing. Keywords: digest, summary, updates, what's new, catch up, briefing
Use when performing GitHub operations: PRs, issues, CI, releases, or any gh CLI task. Keywords: github, gh, PR, pull request, issue, CI, actions, release, merge, review, repo
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, Docs, Tasks, Chat, People, and Classroom via the `gog` command
Scan files or text for hardcoded secrets, API keys, tokens, PEMs, passwords, and connection strings. Use when importing external skills, vetting content, or auditing for credential leaks. Keywords: scan, secrets, credentials, api key, token, password, PEM, leak, vet, audit
Use when asked to validate a skill, check a SKILL.md, enhance a skill, lint skills, review skill quality, or fix skill issues. Runs structural and quality checks on Cairn skill files. Keywords: enhance skill, validate skill, check skill, lint skill, review skill, skill quality, fix skill, skill issues, SKILL.md check
Use when asked about system health, server resources, infrastructure status, or 'how is the server doing'. Comprehensive host-level health report: CPU, memory, disk, database, Go process, TLS cert, SSE clients, poller health. For provider-specific checks use /provider-status instead. Keywords: system health, server, cpu, memory, disk, database, db size, wal, process memory, process, sse clients, poller, infrastructure, resources, uptime
Use when user asks to search the web, research a topic, find information online, or needs current data. Keywords: search, google, look up, find, research, news, what is, how to, latest
Send push notifications via Telegram (primary) or Gotify (fallback). Use when: notify, push notification, alert me, send notification, ping me, push alert, telegram, gotify, browser closed, user offline, task complete, approval needed, critical error, digest ready. Keywords: notify, push, alert, telegram, gotify, notification
Structured multi-source research methodology. Enables web search, memory, file reading, and deep search for comprehensive investigation. Keywords: research, investigate, explore, analyze, gather, study
Use when user asks to review code, check for bugs, review a PR, audit code quality, or find security issues. Keywords: review, audit, check, bugs, security, style, PR
Use when user asks to deploy, build and ship, release, or push to production. Keywords: deploy, release, ship, build, push, production
Use when building joi schemas, validating input data, defining custom types, conditional validation with .when(), cross-field references, custom error messages, or writing joi extensions. Standalone package that integrates with the @hapi ecosystem.
Use when building @hapi/hapi servers, routes, plugins, auth schemes, HTTP APIs, request lifecycle, caching, stale-while-revalidate, server methods, views, startup sequences, or response marshalling.
First-run onboarding: learns user name, use case, and communication style