Productivity & Automation for Claude Code

Enhanced web browsing for Claude Code. Handles search, scraping, login flows, and dynamic pages via Playwright. Use for any task requiring real browser interaction.

Review markdown documents with an interactive TUI and let Claude address feedback automatically.

Gives Claude Code a multi-agent coordination layer over MCP — an atomic shared blackboard (locked propose/validate/commit), permission gating with HMAC/Ed25519-signed tokens, federated token-budget tracking, and append-only audit-log queries. Backed by an orchestrator with 32 framework adapters (LangChain, AutoGen, CrewAI, Gemini, and more).

Plays a Mr. Meeseeks voice line whenever Claude is waiting for you.

Use when the user needs academic paper retrieval — searching scientific literature by author/year/journal, finding paper chunks for RAG-style citations, or expanding original text around a known paper offset. Provides six Sciverse tools (search_papers, semantic_search, list_catalog, list_paper_relations, read_content, get_resource) via the sciverse-mcp-server MCP server.

From zero knowledge to hero website. Four skills and 57 commands: design (siteasy), SEO, defect inspection, and a whole-site /audit orchestrator running 14 parallel sub-agents. GEO for AI search, stack-aware design-system generator, interactive live variant mode, report export, WCAG 2.2, image strategy, accessible forms, parallax, and motion.

Drive a goal to completion autonomously while enforcing backpressure (lint, tests, benchmarks, reviews, manual testing, PR monitoring) at every step.

Self-learning AI agents that improve over time. Features agent memory (tracks last 100 executions), pattern recognition, community standards contribution, and workflow optimization. Includes security, quality, deployment, infrastructure, and compliance workflows.

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".

Generate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".

Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".

Documentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".

Render agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.

Support engineer — ticket workflow design, SLA architecture, knowledge base, escalation paths, and support operations at scale

Contract & Policy Drafter — NDA, MSA, employment agreements, SLAs, vendor contracts

Draft a contract or policy document from a description

Review and redline a contract — risk and missing clauses

AI Operations Team — Budget: LLM spend tracking, model cost optimization, budget alerts, and token efficiency audits across AI workloads.

Audit AI spend — per-model cost breakdown, top consumers, waste identification, optimization levers.

Design cost reduction strategies — model tiering, prompt compression, caching, batch inference.

Map AI cost topology — billing attribution, team-level spend, forecast vs actuals, alert gaps.

Cache skill: cache-evict

Cache skill: cache-recon

Chaos skill: chaos-design

Contract Clause Analyst — redlining, risk scoring, negotiation playbooks

Generate negotiation playbook for a contract type

Contribute a discovery back to the upstream tonone repo — new skill, improved agent prompt, better routing rule. Use when you hit a gap, found a better pattern, or built something reusable that others would benefit from.

Design and implement an AI feature integration — model selection, architecture pattern, system prompt, data flow, error handling, cost estimate. Use when asked to "add AI to this", "LLM integration", "add Claude/GPT", or "AI-powered feature".

Build a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".

Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".

OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".

Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.

Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".