potato-skills
Open-source agent skills that generate essential infrastructure — pieces that connect to each other, for every department of your business.
npx skills add owersbrett/potato-skills --skill <name>Works with Claude Code · Cursor · Codex · Gemini CLI · GitHub Copilot · VS Code · Zed — any agent that reads a SKILL.md.
All skills (11)
Compose the money document of a business — Business Model & Metrics. A guided interview that locks how the company makes money and how it knows it's working — revenue streams, the actual offer/price table, pricing philosophy, cost structure and margins, unit economics, reinvestment strategy, and the success metrics that quantify the vision's horizons — then generates a standalone model site, machine contract, core tables, and MCP surface per the Business OS protocol. Triggers on "business model", "pricing doc", "revenue model", "success metrics", "unit economics", "how do we make money", "/business-model".
Instead of clearing a Claude session, journal it. Reads the current session's context and writes one beautiful, structured blog entry for your future self — a recall hook so you can pick the thread back up later. Out-of-the-box, zero setup, writes a Markdown file you own. Triggers on "journal this", "context journal", "journal the session", "/context-journal", or when a working session is wrapping up.
The advanced form of yourself. Instead of recapping a Claude session, adversarially review it — hunt the shaky decisions, risky code, and anti-patterns in the back-and-forth, research each against real best practices, and return a tight, evidenced thesis about your own recurring failure modes. Written to yourself, to make you a better developer. Triggers on "tater this", "tater the session", "review this session", "critique this session", "/context-journal-tater", or when you want the hard version of journaling.
Compose the Customer Blueprint — who the business serves, who it declines, and why they buy. A guided interview that locks evidence-backed personas (fears, motivations, aspirations, frustrations, buying triggers, objections, vocabulary), the segments explicitly refused, the buying journey, and the ongoing research method — then generates a standalone customer site, machine contract, core tables, and MCP surface per the Business OS protocol. Messaging mines this document for words; go-to-market mines it for triggers. Triggers on "customer blueprint", "customer personas", "who is our customer", "ideal customer profile", "target audience doc", "/customer-blueprint".
Compose the Go-to-Market Playbook — three playbooks in one stone. A guided interview that locks acquisition channels (chosen and declined), campaign structure and KPIs, the launch checklist, the sales motion (discovery, objections, demo, proposal, follow-up — optional if the business doesn't sell 1:1), and the customer success manual (onboarding, support tone, escalation, community) — then generates a standalone GTM site, machine contract, the leads and campaigns tables, and MCP surface per the Business OS protocol. Triggers on "go to market", "gtm", "marketing playbook", "sales playbook", "customer success manual", "launch plan", "/go-to-market".
Assemble the Business OS master site — the business intranet. Scans a workspace for Business OS modules (the eight canonical-document stones), mounts every present stone's site under one shell with unified nav, renders absent stones and empty tables as an honest ghost town, runs a coherence dashboard across all documents, and hosts the advisor — a live Claude-powered component that reads every canonical document and makes grounded recommendations on provisioning, hiring, agent use cases, Claude Code administration, and networking. Triggers on "assemble the intranet", "master site", "compose the business site", "bring the stones together", "/intranet".
Compose the Messaging & Content document of a business — what the company says, everywhere it says it. A guided interview that locks the elevator pitch at three lengths, taglines and headline patterns, a claims ledger grounding every claim in vision or customer evidence, the vocabulary (forbidden words, preferred metaphors), website copy rules, and per-channel style guides — then ships it as a Business OS module with contract, tables, MCP surface, and standalone site. Triggers on "messaging doc", "messaging framework", "elevator pitch", "content style guide", "what do we say", "copy guidelines", "/messaging".
Compose the Operating Manual of a business — how work actually happens. A guided interview that locks the planning cycle and cadence, the decision framework (who decides what, reversible vs. irreversible, when it gets written down), the meeting protocol (including the meetings this company refuses), documentation and communication norms, the roles map of every seat the business needs — filled, unfilled, or agent-fillable — and the hiring path that onboards a human or an agent into a seat. Ships as a Business OS module with a living decision log. Triggers on "operating manual", "operations doc", "how we work", "decision framework", "meeting cadence", "roles map", "hiring plan", "/operations".
Compose a complete brand-guidelines website, together. A guided automation that interviews you through every component of a brand system — logo system, color, typography, iconography, photography, components, motion, layout, voice — then generates a token-first, print-ready, single-page-scroll guidelines site with a DESIGN.md as the canonical spec. Extracted from a real production brand system. Triggers on "brand guidelines", "brand system", "design system doc", "brand book", "compose our brand", "/potatuhs-design".
Compose the Technology & Architecture document of a business. A guided interview that locks engineering principles, the stack and what each choice was traded against, the system inventory, coding standards agents inherit, deployment and security philosophy, scalability goals, and the product requirements philosophy — how features are judged, what MVP means, when to ship, how debt is paid — then generates a standalone site, machine contract, core tables, and MCP surface per the Business OS protocol. Triggers on "/technology", "tech architecture", "engineering guide", "technical architecture doc", "how we build software", "product requirements philosophy".
Compose the root document of a business — Vision & Positioning. A guided interview that locks why the company exists, the future it's building, its values, its contrarian beliefs, what it refuses to become, why-us/why-now positioning, and its product philosophy — then generates a standalone vision site, machine contract, core tables, and MCP surface per the Business OS protocol. Every other canonical document reads this one. Triggers on "vision doc", "vision and positioning", "why do we exist", "mission and values", "positioning document", "/vision".
No skills match that search.