OB1

Claude Code adapter for the auto-capture skill. Extends auto-capture with automatic session-end hooks that capture transcripts to Open Brain without manual intervention. Use this when you want every meaningful Claude Code session to be preserved automatically — not just the ones where you remember to say "wrap up".

Capture and search thoughts against a self-hosted Open Brain over plain HTTPS, with no MCP transport involved. Use this skill in environments where Claude Code's MCP feature is disabled or the network blocks remote MCP endpoints, but the brain stack from the companion `local-brain-no-mcp` recipe is reachable on the local network. Triggers: prompts like "remember this", "save that for later", "what did I note about X", "search my brain for Y", "what thoughts touched on Z", or any explicit request to record or recall personal memory.

Use Nate Jones OB1 Agent Memory from OpenClaw with provenance, scope, review, and use-policy discipline.

Use Nate Jones OB1 Agent Memory from OpenClaw with provenance, scope, review, and use-policy discipline.

Twenty-minute conversational diagnostic for assessing a company's world-model readiness. Use when the user wants to map their company to the right world-model paradigm, identify where the highest-fidelity signal lives, audit the boundary layer between facts and interpretation, flag simulated-judgment exposure, and leave with a first/second/third build sequence. Works in plain chat and compounds when Open Brain search/capture tools are present.

Continuous learning system that extracts reusable knowledge from work sessions. Triggers: (1) /aiception command, (2) 'save this as a skill' or 'extract a skill from this', (3) 'what did we learn?', (4) after non-obvious debugging or trial-and-error discovery. Creates new skills when valuable reusable knowledge is identified. Integrates with Open Brain to prevent duplicates.

Conversation-first workflow for turning tacit work patterns into a structured operating model. Use when the user wants to map how their work actually runs, generate USER.md / SOUL.md / HEARTBEAT.md artifacts, or build an agent-ready model of rhythms, recurring decisions, dependencies, institutional knowledge, and friction. Requires base Open Brain search/capture tools plus the paired Work Operating Model recipe MCP tools.

Use when the user wants a weekly structural diff on AI, software, or another fast-moving market. Starts from 10 suggested categories and 30 suggested companies when no watchlist exists, then adapts the scan using Open Brain memory, current priorities, and prior digests. Best for prompts like "run my weekly signal diff", "what changed this week that matters to me", "track this market", or "turn this week's news into structural shifts". Optional live search upgrade: if OpenRouter access is available, prefer the Perplexity Sonar family for fresh web-grounded retrieval with citations.

Syncs Claude Code's local memory system to Open Brain. Triggers whenever memories are saved via dreaming, autodream, or explicit "remember this" requests. After every local memory file write, captures the same content to Open Brain via mcp__open-brain__capture_thought so that memories are accessible from all connected AI clients (ChatGPT, Claude Desktop, Codex) and across all devices. Trigger on: memory saves, autodream, dreaming, "remember", "save to memory", or any write to the .claude/projects/*/memory/ directory.

Design, evaluate, and improve agentic harnesses for developer tools, assistants, workflow runtimes, copilots, and AI-powered products. Use when work involves tool-use architecture, permissions, approval gates, workflow state, durability, context and memory systems, evaluation strategy, observability, operator visibility, or phased implementation plans for an AI system. Trigger when symptoms imply harness gaps too: stale context, surprising tool calls, sessions that die on crash, missing approval controls, or costs spiraling without clear visibility.

Design, evaluate, and improve agentic harnesses — the orchestration layer around LLM-powered tools, agents, assistants, copilots, workflow runtimes, and AI-driven product features. Use this skill whenever the user mentions building an agentic system, structuring tool use, adding permissions or approval gates, designing multi-step AI workflows, managing context windows or memory, making agents durable or resumable, evaluating or pressure-testing an existing harness, planning phased implementation for an AI product, reviewing agent architecture, improving agent UX or observability, or asking how to know if their harness is actually good. Also use when the user describes problems that imply harness gaps — like agents doing unexpected things, context getting stale, sessions not surviving crashes, tools running without permission, or costs spiraling — even if they do not use the word "harness."

Designs, evaluates, and improves agentic harnesses for developer tools, assistants, workflow runtimes, copilots, and AI-powered products. Applies when work involves defining or reviewing tool-use architecture, permissions, workflow state, durability, context and memory systems, evaluation strategy, observability, user experience, or phased implementation plans for an agentic system.

Use when a user asks to read, analyze, summarize, or extract from a heavyweight file such as PDF, DOCX, PPTX, XLSX, CSV, or TSV. Convert the file into markdown or CSV first, generate a lightweight index, and only spend model tokens on the compressed artifact. Trigger on requests like "read this PDF", "look through this spreadsheet", "summarize this deck", or any time raw file ingestion would waste tokens.

Use in Claude Code when a user asks to read, analyze, summarize, or extract from a heavyweight file such as PDF, DOCX, PPTX, XLSX, CSV, or TSV. Convert the file into markdown or CSV first with the bundled script, generate a lightweight index, and only spend model tokens on the compressed artifact.

Use in Claude Desktop when a user asks to read, analyze, summarize, or extract from a heavyweight file such as PDF, DOCX, PPTX, XLSX, CSV, or TSV. Avoid raw ingestion of bulky files. Ask for a converted markdown or CSV artifact first, or give the user exact conversion commands to run outside Claude Desktop.

Use in Codex when a user asks to read, analyze, summarize, or extract from a heavyweight file such as PDF, DOCX, PPTX, XLSX, CSV, or TSV. Convert the file into markdown or CSV first with the bundled script, generate a lightweight index, and only spend model tokens on the compressed artifact.

Operator-first competitive analysis workflow for competitor profiling, pricing and packaging comparisons, positioning maps, SWOTs, and strategic recommendations. Use for prompts like "analyze our competitors", "benchmark our pricing", "map the market", "who are we up against", or "build a SWOT". Best when you have a company or product, ideal customer profile, and competitor set or permission to discover it. Optional Open Brain search and capture can pull prior notes and store the final brief.

Investor-first workflow for drafting a structured deal memo, IC memo, partnership memo, or acquisition-style brief from existing diligence materials. Use for prompts like "draft a deal memo", "turn this diligence packet into a memo", or "write the IC draft". Best when you already have research findings, model review notes, meeting outputs, and supporting documents. Optional Open Brain search and capture can pull prior context and store the final memo or recommendation summary.

Investor-first workflow for reviewing an existing financial model, forecast, or sensitivity analysis. Use for prompts like "review this model", "stress test these assumptions", "what breaks in this forecast", or "is this model decision-ready". Best when you have a spreadsheet export, pasted assumptions, key drivers, and the decision the model supports. Optional Open Brain search and capture can pull prior model context and store the final review memo.

Workflow for turning meeting transcripts or notes into decisions, action items, unresolved questions, risks, and follow-up artifacts. Use for prompts like "summarize this meeting", "extract action items", "what did we decide", or "draft the follow-up". Best when you have notes or a transcript, attendee context, and the reason the meeting happened. Optional Open Brain search and capture can pull surrounding context and store the final synthesis or decisions.

Decision-grade workflow for synthesizing a source set into clear findings, contradictions, confidence markers, gaps, and next questions. Use for prompts like "synthesize these sources", "turn this research into a brief", "what are the key findings", or "where do these sources disagree". Best when you have a research question, a defined audience, and a set of source materials. Optional Open Brain search and capture can pull prior context and store the final synthesis.

Automatically capture ACT NOW items and a session summary to Open Brain when a work session is ending. Use when wrapping a brainstorm, parking a project, finishing a Panning for Gold run, or otherwise closing a session with decisions worth remembering. Use the Open Brain capture tool available in the current client (often named `capture_thought`; prefixes vary by connector). This is a behavioral protocol, not a background hook.

Use when processing voice transcripts, brain dumps, stream-of-consciousness notes, or any raw multi-topic capture. Extracts every idea thread, then evaluates each one with deep brainstorming, then captures results to Open Brain. Trigger on transcripts, exports, "process this", "pan for gold", "brain dump", "what did I say", or multi-topic markdown files.

Explain exactly when this skill should fire, what inputs it expects, and what problem it solves.