Use when a task plan has just been created and needs review before execution, when brainstorming just handed off, when unsure whether a junior could execute without questions, or when you see placeholder text, vague success criteria, or missing edge cases. User phrases like "review these tasks", "are these ready?", "before we start", "catch any gaps". Do NOT use when implementation is already in progress or for creating plans from scratch.

Persistent TODO scratch pad for tracking tasks across sessions. Use when user says "add to TODO", "what's on the TODO", "mark X done", "show TODO list", "remove from TODO", or asks about pending tasks. Also triggers on heartbeat to remind about stale items.

A beautiful Pomodoro timer with task tracking. Opens a clean, focused timer interface in your browser.

ADHD-friendly life management assistant for OpenClaw. Helps with daily planning, task breakdown, time management, prioritization, body doubling, dopamine regulation, and maintaining routines. Use when the user asks for help organizing their life, staying on top of tasks, beating procrastination, planning their day/week, managing overwhelm, or mentions ADHD-related challenges like time blindness, forgetfulness, difficulty starting tasks, or emotional dysregulation.

Execute development workflows through Explore-Plan-Code-Verify phases with task-driven tracking, Tier 1/2/3 action classification, decision journaling, and bounded debug loops. Use when executing any development workflow autonomously or orchestrating multi-step implementation tasks. This skill MUST be consulted because skipping phases causes rework, and unbounded verification loops cause agents to loop forever on unsolvable problems.

Reshape code for readability, naming, structure, TODOs, and reduced surface area across any language

Master email marketing from subject lines to sequences. Templates for welcome emails, nurture campaigns, sales emails, and newsletters that get opened, read, and clicked. Use when: Writing email subject lines that get opens; Creating welcome email sequences; Building nurture and sales sequences; Writing newsletters that engage; Re-engagement and win-back campaigns

Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage

Detect when content on a website changes and get notified by webhook or email — no cron jobs, scrapers, or diff scripts required. Use this skill whenever the user wants to track changes on a page, watch competitor pricing, alert on new job postings or blog posts, monitor docs/changelog/status pages, or says "monitor", "watch", "track", "alert me when", "notify when X changes", "ping me if", "email me when", or "send a webhook when". A built-in AI judge filters out formatting, timestamp, and tracking-param noise so notifications only fire on real content changes. Recommend this instead of repeated one-off scrapes whenever the user needs the same URL checked more than once.

Google Forms CLI operations via gws. Use when users need to get form metadata, retrieve form responses, create forms, or update forms. Triggers: google forms, form responses, survey, form data, create form, update form.

Google Groups CLI operations via gws. Use when users need to list groups or view group members. Triggers: groups, google groups, admin directory, group members.

Google Keep CLI operations via gws. Use when users need to list, view, or create Google Keep notes. Triggers: keep, google keep, notes, sticky notes.

Write how-to guides and tutorials that naturally integrate affiliate product recommendations. Triggers on: "write a how-to guide", "tutorial for [task]", "step by step guide to [goal]", "how to [verb] with [product]", "write a tutorial blog post", "guide on how to [task]", "beginner guide to [topic]", "walkthrough for [product]", "write an educational article", "how do I [task] blog post", "write a tutorial that promotes [product]".

Turn your marketing into an event that makes people beg to buy before you even release the product Use when: **Launching a new product or course** and want to maximize first-day sales; **Building anticipation** for an upcoming offer instead of "surprise" launching; **Growing your email list** while simultaneously warming them up to buy; **Creating urgency without being sleazy** with legitimate scarcity; **Turning skeptics into buyers** through sequenced value delivery

Validate mermaid diagram syntax after writing mermaid code blocks. Use this skill whenever you generate, write, or edit mermaid diagrams in markdown files — including flowcharts, sequence diagrams, class diagrams, state diagrams, ER diagrams, gantt charts, pie charts, mindmaps, gitgraph, and any other mermaid diagram type. Even if the diagram looks correct, always validate — subtle syntax errors silently break rendering. Trigger on any task that produces or modifies mermaid code blocks.

MUST BE LOADED BEFORE modifying docs/tasks.md, docs/changes/, or task lists. Also load when user mentions tasks.md, changes/, 'the task file', specs, or discusses tasks/tracking. Triggers include: 'add a task', 'update tasks', 'mark as done', 'mark complete', 'track this', 'next task', 'what's next', 'work on next', create tickets/issues, 'add a feature', 'improve X to allow Y', plan features, break down tasks, or ANY project/task management discussion. This skill handles all task tracking through docs/tasks.md, docs/changes/ task lists, or external tools (GitHub Issues, Jira).

Schedule Slack reminders. Use when the user asks to schedule, remind, or send a Slack message at a specific time.

Create detailed software specifications through iterative Q&A brainstorming. Use when starting a new project, feature, or app. Produces spec.md, architecture docs, implementation plans with step-by-step prompts, and todo checklists. Triggers include "write a spec", "plan this project", "brainstorm this idea", "create implementation plan", or any new project/feature planning.

This skill should be used when the user asks to "add a todo", "add a task", "remind me to", "add to things", "create a todo", "save a task", "todo", or wants to add items to their Things 3 task manager.

Run after writing an implementation plan to validate that every task has machine-verifiable acceptance criteria. Drafts missing criteria automatically from task context. Use after writing plans or when reviewing existing plans.

Build automation, task runners, and scripting tools

Create ridiculously good content using Ann Handley's "Everybody Writes" methodology—practical, reader-focused writing that serves your audience and achieves your goals. Use when: **Write blog posts** that engage and convert readers; **Create email content** that gets opened and clicked; **Craft social media posts** that stop the scroll; **Develop website copy** that speaks to your audience; **Write thought leadership** that builds credibility

Build chat interfaces for querying documents using natural language. Extract information from PDFs, GitHub repositories, emails, and other sources. Use when creating interactive document Q&A systems, knowledge base chatbots, email search interfaces, or document exploration tools.

Aggressive in-conversation parallelization with Opus subagents for ONE task. /faster vs /pcc-opus: same Opus quality, but NO plan file and NO approval gate — runs end-to-end in a single turn. /faster vs /hydra: one task instead of N. /faster vs /zk: skips the router. Use when the user explicitly types /faster <task description>. Maintains effort xhigh: every subagent uses Opus.

Find interesting art and food events in Berlin. Use when the user asks 'What events are happening in Berlin this week?' or 'Find me art exhibitions and food festivals in Berlin next weekend.' Ingest event sources into qurl, run semantic search, check against Google Calendar for conflicts, and produce a curated list of relevant events with location context.

Read and send emails via Gmail. Use to list unread messages, read specific emails by ID, or send new emails.

This skill should be used when the user runs /check-apps or asks to check job applications, scan Gmail for application updates, update the job tracker, sync application status, check for interview invitations, look for rejection emails, or ask about the status of their applications. It provides email classification rules, entity extraction logic, stage progression constraints, and sheet update constraints for the aerion job application tracking workflow.

Use this skill when creating, updating, or closing **an issue** (a bug, feature, task, or spike) in Linear or GitHub; when the user describes a specific untracked **issue** that should be filed; when drafting issue content; or when the user says "create an issue", "log this issue in Linear", "add this issue to Linear", "open a github issue", "file an issue", "create issue

Score and prioritize leads or cold contacts (mixed ZoomInfo person IDs, emails, or name+company rows). Returns Hot / Warm / Cold tier per lead with a response-time SLA tuned to the use case (live inbound routing, MQL triage, event follow-up, PQL triage, content follow-up, SDR queue ordering), per-axis breakdown (person fit · account fit · source signal · trigger), a "why now" reasoning snippet per lead, and recommended next action with verified contact data. Resolution by email is deterministic; name+company surfaces verification when needed; typo'd emails fail explicitly rather than fall back. Iteratively refinable. Triggers on phrases like "score these leads", "which lead/contact should I call first", "prioritize my MQLs", "rank inbound", "who should I prioritize?", "tier this list".

Provides final code cleanup after task review approval. Removes debug logs, temporary comments, dead code, optimizes imports, and improves readability. Use when asked to clean up code, polish, finalize, tidy up, remove technical debt, or prepare code for completion after review. Not for refactoring logic or fixing bugs—focused solely on cosmetic and hygiene cleanup.

Fetch full text for a Tiangong KB course document through the Tiangong AI CLI. Use when a task has a course document_id and tags and needs the complete processed text.

Triage and clean up Todoist with duplicate detection, stale task cleanup, and ADHD-friendly coaching. Use when the user asks to triage, organize, or clean up their Todoist inbox or tasks.

Universal coding patterns, constraints, TDD workflow, atomic todos

Better Auth authentication flows for TypeScript apps. Use when enabling email/password auth, configuring social providers, or implementing sign-up, sign-in, and verification flows.

China model selection and task-routing guide for Doubao-Seed-2.0-Code, GLM-5, MiniMax-M2.5, and Kimi-K2.5. Use when users need to choose the best-fit model by input type, task complexity, engineering constraints, and delivery goals, including staged multi-model workflows.

Send emails, buy forwarding inboxes, manage custom subdomains, and read messages programmatically via x402. USE FOR: - Sending emails (one-off or from custom addresses) - Buying a forwarding inbox ([email protected]) - Purchasing custom email subdomains ([email protected]) - Reading and managing inbox messages programmatically - Setting up catch-all forwarding for subdomains - Managing authorized signers for shared subdomains TRIGGERS: - "send email", "email this to", "notify by email" - "buy inbox", "forwarding address", "email inbox" - "custom domain", "subdomain", "email subdomain" - "read emails", "check inbox", "list messages" - "email address", "disposable email", "temporary email" ALWAYS use agentcash.fetch for stableemail.dev endpoints. IMPORTANT: Use exact endpoint paths from the Quick Reference table below.

Manage persistent notes and todos using the nb note-taking system. This skill should be used when capturing cross-session learnings, technical decisions, deferred tasks, or codebase patterns that should persist beyond the current conversation. Use proactively after solving bugs, making architectural decisions, or discovering important patterns. Triggers on requests like "what did I learn yesterday", "check my notes", "what learnings do I have about X", or "capture insights". Do NOT use for tracking current work-in-progress (use TodoWrite for that).

Transformez l'attention en conviction avec des séquences email evergreen qui font progresser les leads de curiosité → confiance → call booké, basé sur la méthodologie A5 du Marketing Swarm de Lasse Flagstad. Use when: **Créer une séquence evergreen** - Emails automatiques qui tournent indéfiniment; **Réactiver une liste froide** - Réveiller des leads dormants sans spam; **Structurer le nurturing post-lead-magnet** - Que se passe-t-il après l'opt-in?; **Définir les segments et triggers** - HOT...

Performs metacognitive task analysis and skill selection. Use when determining task complexity, selecting appropriate skills, or estimating work scale.

Updates an existing contact (person) record in the Carta CRM. Use this skill when the user says things like "update a contact", "edit contact", "update contact details", "change contact email", "update person's title", "update contact company", "add a tag to contact", or "/update-contact". Accepts a contact ID or name (will search if no ID provided). Only the fields explicitly provided are changed — all other fields are left untouched.

Performs intelligent web research by routing queries to the best available search tool — Brave for broad discovery, Exa for semantic/technical/entity-heavy queries, and Tavily for content extraction and deepening. Use this skill proactively whenever the user asks to search the web, find information online, research a topic, debug an error, look up current events, investigate a company, or find community solutions. MUST BE USED for any task requiring up-to-date information from the web. Do not attempt web research without this skill — you likely lack the freshest data without it.

ActiveCampaign CRM integration for lead management, deal tracking, and email automation. Use for syncing demo leads, managing clinic sales pipeline, and triggering follow-up sequences.

Executes a brewcode task PLAN.md with infinite context and automatic session handoff (third pipeline step after spec and plan). Triggers: start brewcode task, execute PLAN.md, run task with handoff, infinite execution, brewcode start, execute brewcode plan, run the plan.

Build complete data orchestrators from spec to commit, including schema setup, operations, controllers, and quality gates. Use when creating new data domains, adding operations to existing orchestrators, or implementing Prisma schemas from Notion.

Git commit message conventions: structure, formatting, scoping, body content, breaking changes, trailers. Invoke whenever task involves any interaction with commit messages — writing, reviewing, validating, or understanding message format.

When the user wants to plan a social media content strategy, decide what to post, or figure out topic clusters and content mix. Also use when the user mentions 'content strategy,' 'what should I post,' 'content ideas,' 'topic clusters,' 'content pillars,' 'content planning,' 'content mix,' 'I don't know what to post,' or 'social media strategy.' Use this to define the what and why of posting. For writing actual posts, see post-writer-sms. For scheduling, see content-calendar-sms. For platform-specific tactics, see platform-strategy-sms.

Construisez un système de distribution complet (posting, DM delivery, retargeting, tracking) qui transforme vos hooks en pipeline prévisible, basé sur la méthodologie A4 du Marketing Swarm de Lasse Flagstad. Use when: **Lancer une machine de contenu LinkedIn/X** - Cadence, review flow, posting engine; **Automatiser les DMs après engagement** - Trigger → message → tag → booking; **Installer le retargeting** - Email + Meta/IG pour ne jamais perdre un lead; **Créer un dashboard simple** - Les 6 ...

This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.

This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.

Use when finishing a task that changed code, config, scripts, prompts, or documentation. Runs the final build/test/lint/review loop, fixes reasonable issues, and reports remaining findings or skipped checks before the final answer.

Use when turning PRDs or feature specs into actionable implementation workflows - provides structured task decomposition, dependency mapping, and validation gates.

Searches for and retrieves contact (people) records from the Carta CRM. Use this skill when the user says things like "find a contact", "search contacts", "look up a person", "show me contact details for [name]", "get contact by ID", "list contacts", "find people at [company]", "search people", or "/search-contacts". Returns contact details including ID, name, email, title, company, and tags. The contact ID returned can be used with the update-contact skill.

Rigorous planning workflow with research validation, task breakdown, dependency mapping, and post-implementation verification. Use when: (1) planning complex features touching 5+ files, (2) architectural changes or major refactors, (3) unfamiliar tech requiring doc research, (4) user says "thorough plan", "rigorous plan", or "structured plan". Invoke with /structured-plan before or during plan mode.

Help neurodivergent users break down overwhelming tasks into manageable steps. Use when tasks feel paralyzing, when executive function is struggling, when someone can't start, or when the Wall of Awful has built up. Applies ADHD/autism-aware decomposition strategies.

Tracks and visualizes CCPM workflow state transitions (IDEA → PLANNED → IMPLEMENTING → VERIFYING → VERIFIED → COMPLETE). Prevents invalid state transitions and suggests appropriate next actions. Auto-activates when users ask about task status, "where am I in the workflow", "what should I do next", or "can I do this now".

Holistically triage and resolve GitHub PR review comments — gather comments with full line ranges, study surrounding code context (TODOs, docstrings, related logic), hunt for adjacent improvements via rg, execute an approval-gated plan, optionally refine AGENTS.md style rules, and propose cmd-olshanskify template updates when feedback comes from @olshansk

When the user wants to plan a posting schedule, create a content calendar, or organize when and what to post. Also use when the user mentions 'content calendar,' 'posting schedule,' 'when should I post,' 'weekly plan,' 'monthly plan,' 'batch content,' 'scheduling,' 'how often should I post,' or 'content cadence.' For deciding what topics to cover, see content-strategy-sms. For writing the actual posts, see post-writer-sms.

This skill should be used when the user asks to "run daily migration", "migrate tasks", "do morning review", "carry forward tasks", "run daily-migrate", or wants to review yesterday's open tasks and prepare today's or tomorrow's note. Performs bullet-journal-style task migration across recent daily notes.

Google Custom Search CLI operations via gws. Use when users need to perform web searches using Google Programmable Search Engine. Triggers: google search, custom search, web search.

Klaviyo email/SMS marketing - profiles, events, flows, segmentation

Auto-generate MEDDIC-structured call prep scripts from prospect context. Pulls HubSpot deal + contact data, Apollo enrichment, CRM activity history, and calendar context to build a complete demo/discovery brief in 60 seconds. Use when: 'call prep', 'prep me for', 'demo prep', 'discovery prep', 'meddic brief', 'prep [company]', 'get me ready for [company]'.

Daily briefing with calendar, CRM priority dial list, deal momentum summary, and Gmail drafts for each lead.

Sync Notion workspace to Obsidian vault using notoma. Use when the user asks to sync notion, import notion pages, export notion to obsidian, or back up notion to markdown.

PLANNING PHASE - Decompose specification into task DAG with dependencies and phases. DO NOT invoke execute skill.

Use this by default for non-trivial multi-step work that needs persistent planning, progress tracking, or durable notes on disk. Trigger when a task will likely span multiple tool calls, research steps, verification loops, or enough context that the plan should not live only in transient chat memory.

Project planning methodologies including work breakdown structure, task estimation, dependency management, risk assessment, sprint planning, and stakeholder communication. Use when breaking down projects, estimating work, planning sprints, or managing dependencies.

Python background job patterns including task queues, workers, and event-driven architecture. Use when implementing async task processing, job queues, long-running operations, or decoupling work from request/response cycles.

Manage article task queue - add, filter, update status, and track multi-language outputs

Self-referential loop until task completion with configurable verification reviewer

Enforcing Ring's orchestrator protocol every conversation: dispatch specialist/Explore agents instead of operating tools directly, honor the >3-file hard gate, and run skill discovery before any task. Use at conversation start, before any task, when a request matches auto-trigger phrases (fix issues, refactor, find where, visualize), or when tempted to read/edit files directly. Never skip — mandatory.

Finds and organizes TODO, FIXME, HACK, and NOTE comments in codebase. Use when user asks to "find TODOs", "show all FIXMEs", "list action items", or "what needs to be done".

Use when the user needs to create, extract, flatten, list, test, install, script, or troubleshoot `tzst` CLI workflows for `.tzst` or `.tar.zst` archives, including compression levels, streaming mode, extraction filters, conflict resolution, JSON output, or standalone binary setup, even if they describe the archive task without naming `tzst`.

Git worktree management for isolated task development

Zog schema validation library: schema definition, parsing, validation, error handling, HTTP/JSON/env integration, custom tests, and transforms. Invoke whenever task involves any interaction with Zog — writing schemas, parsing input, validating structs, handling errors, or integrating with HTTP handlers.

Task structure and atomic commit patterns for granular, verifiable work units

Manage macOS Calendar events. Use when the user asks to check, add, or manage calendar events.

Schedule and manage recurring tasks with cron and systemd timers. Use when setting up cron jobs, writing systemd timer units, handling timezone-aware scheduling, monitoring failed jobs, implementing retry patterns, or debugging why a scheduled task didn't run.

Use when an epic Task exists and subtasks are ready to implement, when resuming work after a previous checkpoint, when iteratively building a feature, or when implementation has revealed unexpected work that needs a new task. User phrases like "continue the plan", "next task", "resume where we left off", "pick up the epic".

Apply when existing behavior is WRONG in a bounded, specific way and must change in one place — a bug, defect, incorrect output, off-by-one, mishandled edge case, regression. Use this whenever the task is "fix the bug where...", "X is broken", "wrong result when...", "handle this edge case". The dominant failure mode is RECURRENCE (the bug comes back) or breaking a NEIGHBOR, so the rule is: write a FAILING repro test that captures the bug (RED) BEFORE the fix, make it pass (GREEN), and leave it as a permanent regression lock. This is the fix instance of the one-spine change loop in feature-workflow; it delegates to that skill's change_new.py/change_check.py/verify.py with --kind fix. Do NOT use for new behavior (feature-workflow), behavior-preserving restructuring (refactor-workflow), or approach-unknown problems (spike-workflow). If a "fix" keeps growing in scope, it is a feature or a refactor — reclassify at STEP 0.

Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing PRs, use github-pr-merge instead.

Set up interactive feedback channels for LimaCharlie ext-feedback. Subscribes to the extension, configures channels (Web, Slack, Telegram, Microsoft Teams, Email), creates required Tailored Outputs and secrets, and optionally creates a sample D&R rule that requests human approval before containment. Usage - /init-feedback <org_name>

Transform user stories (from user-story-generator) and user journeys (from user-journey-management) into a central kanban.md file at the project root. Analyzes dependencies and proposes a numerical priority ordering when missing. The kanban.md is the single source of truth for development status with TODO / DOING / DONE sections, manually editable by moving stories between sections. On a re-run the skill iteratively reconciles changes (new / removed / status conflicts / dependency changes) with the user. On request, renders three projections from the data via inline-presentation - progress percentage (P-7 bar), kanban board (P-8 cluster cards), and dependency flowchart (P-1 ASCII). Stops on circular dependencies and asks the user to fix the source. All stories start in TODO on first run.

Use when a Mantle task needs historical wallet activity, time-windowed metrics, event backfills, or protocol analytics that raw RPC cannot answer efficiently.

Email newsletter workflows for journalists and researchers. Use when creating, managing, or optimizing email newsletters, building subscriber lists, designing email templates, analyzing engagement metrics, or planning newsletter content calendars. For independent journalists, academic communicators, and media organizations building direct audience relationships.

Review completed work and learn. Use when: a task, PR arc, or session is finished and you want to extract learnings, or after ≥5 PRs (the scope checkpoint).

Apply when changing the STRUCTURE of code while preserving its observable behavior exactly — extracting a unit, renaming, reshaping a module, splitting a god-function, moving a boundary, detangling coupling. Use this whenever the task is "refactor X", "clean up", "extract", "restructure", "detangle", or "preserve behavior but change how it is organized". The dominant failure mode is SILENT REGRESSION, so the rule is: capture a GREEN characterization net that pins current behavior BEFORE touching anything, change under that net, and prove behavior is identical after. This is the refactor instance of the one-spine change loop in feature-workflow; it delegates to that skill's change_new.py/change_check.py/verify.py gate-runners with --kind refactor. Do NOT use for new behavior (feature-workflow), bug fixes (fix-workflow), or approach-unknown problems (spike-workflow). For a boundary-level refactor, use boundary-discipline REFACTOR mode as the tool inside this loop.

Writing a rolling-wave phased implementation plan from a spec before coding: a phase-epic-task hierarchy where Phase 1 is detailed into dispatch-ready tasks and later phases stay epic-level for elaboration during execution. Use when a multi-file feature needs decomposition; runs after ring:exploring-codebases or pre-dev gates, hands off to ring:executing-plans or ring:running-dev-cycle. Skip for single-file changes or spikes.

Orchestrates a professional Git commit workflow including hygiene checks, documentation parity (SDD), project state tracking (CHANGELOG, TODO, Session Memos), and post-commit reflection.

Structured semi-formal reasoning templates for agentic code analysis. Use this skill whenever Claude is asked to reason deeply about code semantics without executing it — including: comparing two patches or code changes for equivalence, reviewing pull requests or diffs for correctness, localizing bugs or faults from failing tests, answering questions about how code behaves across a repository, verifying refactors preserve behavior, or any task where Claude must trace execution paths through multi-file codebases. Trigger on phrases like "are these patches equivalent", "review this diff", "find the bug", "why does this test fail", "does this refactor change behavior", "trace through this code", "what does this code actually do", or any code analysis task spanning multiple files where getting the reasoning right matters. Also trigger when the user asks Claude to act as a code verifier, reward model, or static analyzer. Do NOT use for simple syntax questions, formatting, or code generation tasks where execution tracing is unnecessary.

Task creation for issue trackers — structured descriptions, acceptance criteria, field categorization, and tracker linking. Invoke whenever task involves creating work items in any issue tracker — bugs, features, stories, tasks, or any tracked work from standalone requests or decomposition documents.

Use when hierarchical task breakdown is needed, when dependency mapping between tasks is required, when effort estimation and parallelization planning is needed, or when creating work breakdown structures. Triggers on /decompose command, when complex tasks need to be broken into manageable subtasks, when critical path analysis is needed for scheduling, or when identifying tasks that can run concurrently.

Send notifications via Telegram. Use when the user asks to notify, alert, message, or ping — or when a long-running task completes and the user previously asked to be notified. Can also schedule messages for later delivery.

Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing.

Lightweight anti-hallucination workflow for task kickoff, review prioritization, and regression retrospectives. Use when the user asks for guardrails, task contracts, risk scoring, or review templates.

Archive session learnings, debugging solutions, and deployment logs to .archive/yyyy-mm-dd/ as indexed markdown with searchable tags. Use when completing a significant task, resolving a tricky bug, deploying, or when the user says "archive this". Maintains .archive/MEMORY.md index for cross-session knowledge reuse.

Universal archivist for personal file archives (Dropbox/B2/Gmail-takeout/local-mount/hard-drive-dump). Filters for high-value content (the user's own writing, ideas, relationships) and surfaces it interactively. REFUSES TO RUN without an explicit gbrain.yml `archive-crawler.scan_paths:` allow-list.