The-Utopia-Studio
- 488 skills
- 0 followers
- 2 repo stars
- 3 days ago last updated
- ▌ Environment · the-utopia-studio bundleThis skill should be used when the user asks "what's the config", "show me the configuration", "what variables are set", "environment config", "service config", "railway config", or wants to add/set/delete variables, change build/deploy settings, scale replicas, connect repos, or delete services.
- ▌ So What Stress Test · the-utopia-studio bundleFires when a fellow wants a whole idea pressure-tested fast across five business questions — "is this worth doing", "pressure-test this", "poke holes in this", "stress test my idea", "so what?". Runs So what / Who pays / What's the wedge / What's the moat / What kills it, then returns a per-question verdict table and an overall Pass / Redesign / Kill, refusing to pass any question answered on opinion. Do NOT fire to score a problem on the 8-dimension gate (use problem-quality-scorecard), for the 5-lens adversarial teardown that ends in one probe (use concept-council), or to deep-dive only the wedge (use wedge-five-questions).
- ▌ Value Based Pricing · the-utopia-studio bundleSet the price and the charging metric for a validated product — anchor the number at 10–20% of the MEASURED incremental value, and charge on the outcome / asset / decision the customer gets, never on seats or tiers. Emits a value-priced model. Fires on "how should we price this", "what do we charge", "per seat or per outcome", "set the price", "what's the number". Not for brainstorming which revenue model to bet on across the product (that is `monetization-strategy`, exploratory; this commits ONE value-anchored number on ONE metric), not for structuring the whole pilot deal — scope, success metrics, kill criteria (that is `pilot-six-term-sheet`; this produces the price and metric that become its term 2 and term 6), not for measuring the value in the first place (that is `current-state-map`, which prices the status quo this consumes).
- ▌ Null Hypothesis Test · the-utopia-studio bundleFalsification pass for the load-bearing beliefs under a chosen plan or wedge. Restates each assumption as a null hypothesis (the belief is FALSE), designs the single cheapest observation whose failure would disprove it, and ranks every assumption by P(wrong) x impact-if-wrong so the fellow shoots at the most-likely- fatal belief first. Fires on "what has to be true", "how would I disprove this", "what's the riskiest assumption", "what could kill this", "which belief do I test first". Output is an Assumption -> Null -> Disproof table with a pre-committed kill signal on every row. NOT the go/no-go on whether the problem is worth building at all (problem-quality-scorecard), NOT bottom-up sizing (bottoms-up-quantification), NOT the priced workflow map (current-state-map), NOT a narrative failure story (pre-mortem).
- ▌ Pilot Six Term Sheet · the-utopia-studio bundleTurn a would-be pilot into a six-term paid-pilot sheet — scope, price (paid or prepaid), the signed data-rights clause, success metrics, kill criteria, and conversion terms priced now — and refuse to call anything a pilot unless all six terms are non-empty. Fires on "pilot terms", "structure the deal", "paid pilot", "pilot term sheet", "structure the pilot so it isn't a free trial". Not for brainstorming or validating which revenue model to bet on (that is `monetization-strategy`, exploratory; this commits one basis to price the conversion term now), not for drafting the data-rights legal language (that is `data-rights-clause`, section 06; this carries the clause as term 3 and routes there), not for testing whether the thing will get adopted at all (that is `wedge-five-questions`).
- ▌ Wedge Five Questions · the-utopia-studio bundlePressure-test ONE proposed wedge against five pass/fail thresholds (standalone value, forced cadence, travel, structural expansion, scoreable adoption) and return a 5-row verdict that calls it a real wedge only on 5/5. Fires on "is this a wedge", "is my wedge sharp enough", "what's my wedge", "the smallest thing that forces adoption", "will this actually get adopted". Not for defensibility over years (use moat-design-canvas), not for scoring the whole idea across eight dimensions (use problem-quality-scorecard), not for the one-glance so-what gut check (use so-what-stress-test).
- ▌
- ▌ Efecto Graphic Design · the-utopia-studioDesign graphic assets with Efecto — presentations, pitch decks, event posters, email headers, blog images, open graph cards, business cards, resumes, menus, infographics, invitations, newsletters, and documents. Use when asked to "design a poster", "create a pitch deck", "make a presentation", "design a business card", or any graphic design task. Requires Efecto MCP server.
- ▌
- ▌ Company Moc · the-utopia-studioBuild a Map of Content (MOC) for a company in an Obsidian vault — an ideas-first knowledge graph built from primary sources (decks, transcripts, standards, reports), with a hub note and linked child notes. Use when asked to "build a MOC", "map this company", "create a knowledge graph on X", or to update an existing company MOC after a new call or document drop.
- ▌ Agent Prd · the-utopia-studioInterview the user and produce an Agent PRD — the planning document that must exist before any agent code is written. Use when the user wants to build, scope, spec, or plan a new agent, generator, critic, pipeline stage, harness, or autonomous system; when they say "new agent", "agent PRD", "spec this agent", "plan this agent", "I want to build an agent that...", or ask what questions they should answer before starting. Also use when an existing agent is being rebuilt or a stage is being added to a pipeline. Do not use for writing agent implementation code — this skill produces a document only.
- ▌ Business Narrative Builder · the-utopia-studio bundleConstructs a structured narrative linking a company's qualitative business story to quantitative valuation drivers (revenue growth, target margin, reinvestment efficiency, cost of capital, failure risk). Classifies the company within a 6-stage corporate life cycle and sizes the total addressable market. Use when starting a company analysis, building a valuation narrative, assessing competitive position, sizing TAM, or when user mentions business narrative, story to numbers, life cycle stage, or company analysis.
- ▌ User Buyer Decider Map · the-utopia-studio bundleSplits a buying situation into four distinct people — user (feels the pain, touches the product), buyer (owns the budget line), decision-maker (final signature / veto), champion (spends internal capital to push it) — each pinned to ONE title, ONE budget (or an explicit none), ONE why-now. Fires on "who's the actual buyer", "who decides", "map the stakeholders", "map the buying committee", "the user loves it but who signs the cheque", "who's our champion and who can veto us". Output is a filled Stakeholder-Role Map that feeds the buyer-clarity row of problem-quality-scorecard. NOT the 8-dimension go/no-go (problem-quality-scorecard), NOT ranking which unmet need to build first (unserved-needs-finder), NOT a demographic day-in-the-life persona (proto-persona), NOT simulating users before interviews (synthetic-users).
- ▌ Evidence Driven Testing · the-utopia-studioRecords visual proof while testing UI behavior — screen recording with structured test/assertion annotations — then posts the video and a results summary to the PR and tracker issue. Use whenever a UI change needs verifiable evidence that it works, instead of prose claims.
- ▌ Usability Test Protocol · the-utopia-studio bundleRun a moderated usability session on a working prototype and return findings tied to the screen, not the user. Fires when a fellow says "run a usability test", "watch a user try it", "usability protocol", "can a first-time user complete X", or "see where they get stuck". Product runs, Engineering watches muted, Design notes; the task is framed as a goal not an instruction, the user is kept in user mode (no leading, no explaining, no "do you like it"), and every finding is scored on observed task success (behaviour 0.7), never stated preference (opinion 0.1). Output is a Usability Findings sheet — each defect tied to a step, counted across users, severity by frequency × blocking. NOT for building the prototype (use `first-mocks`; this tests what that builds), NOT for shadowing an expert to capture their judgment (use `tacit-knowledge-interview`; that mines expertise, this tests your design), and NOT for testing demand or willingness to pay (a user can complete every task and still never want it — route to `wiz
- ▌ Valuation Reconciler · the-utopia-studio bundleSynthesizes intrinsic (DCF) and relative (multiples) valuation outputs into a final value estimate and investment recommendation. Reconciles divergent valuations, reverse-engineers what the market is pricing in (implied growth, implied ROIC), computes margin of safety, and produces a buy/sell/hold recommendation with catalysts. Use when combining multiple valuation approaches, making investment recommendations, reconciling DCF with multiples, or when user mentions reconcile valuations, investment recommendation, margin of safety, implied growth rate, or what is the market pricing in.
- ▌
- ▌
- ▌ Problem Quality Scorecard · the-utopia-studio bundleNumeric go/no-go gate that scores ONE product problem 1-5 on eight evidence-backed dimensions (frequency, budgeted pain, severity, data exhaust, structural persistence, buyer clarity, wedge sharpness, founder asymmetry), sums to /40, and returns pass (>=32) / redesign (28-31) / kill (<28). Fires on "should I build this", "score this problem", "go or no-go", "is this problem good enough", "rate this problem". Output is a filled 8-row scorecard with a money-or-behaviour citation on every row. NOT for broad risk mapping across GTM/strategy/team (use identify-assumptions-new), NOT the five qualitative whole-idea questions (so-what-stress-test), NOT the per-unit size ratio (physics-floor-gap), NOT the wedge-only deep dive (wedge-five-questions).
- ▌
- ▌ Growth Strategy · the-utopia-studio bundleBuild or update a growth strategy document for a named Utopia Studio fellow (portfolio company) — covering value proposition, target segments with named example customers, business model, collaboration tiers, growth flywheel, and a 6-month GTM plan (e.g. 'give me a growth strategy for [Fellow]', 'build a v1 growth strategy for X', 'update the GTM plan for Y'). Applies Utopia's real brand system (Special Black / Brick Red, TWK Lausanne, stacked wordmark, /// mark) via the docx skill. Do NOT use for partner-facing decks (use utopia-partnership-deck) or investor/board decks — those follow different templates and different research inputs.
- ▌ Prioritization · the-utopia-studioFramework-driven feature and initiative prioritization using RICE, ICE, or weighted scoring. Grounds prioritization in strategic pillars and demands evidence-based scoring. Trigger phrases: "prioritize features", "prioritization", "rank these initiatives", "RICE score", "ICE score", "what should we build next", "prioritize my backlog"
- ▌ Intrinsic Valuation Dcf · the-utopia-studio bundlePerforms discounted cash flow valuation using the appropriate model variant (DDM, FCFE, or FCFF) with configurable growth stages. Produces year-by-year cash flow projections, terminal value, equity bridge (subtract debt, add cash, subtract option value), per-share intrinsic value, and sensitivity analysis. Use when valuing a company intrinsically, building a DCF model, estimating fair value, or when user mentions DCF, discounted cash flow, intrinsic value, terminal value, or free cash flow valuation.
- ▌ Continuous Discovery Engine · the-utopia-studio bundleStands up ONE living opportunity tree fed by three live inputs and keeps it current after launch. Fires when a fellow says "set up discovery", "continuous discovery", "opportunity tree", "keep learning after launch", or "discovery after launch". Returns an opportunity tree (outcome → opportunities → solutions → tests) wired to customer interviews, production traces, and eval telemetry — each feed stamped with its evidence rung, its cadence, and a named synthesis owner. NOT for scoring one signal's rung (use evidence-ladder), picking which probe tests one question (use probe-matrix), or running a single customer interview (use tacit-knowledge-interview).
- ▌ Vercel React Best Practices · the-utopia-studio bundleReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
- ▌ Compound System Architecture · the-utopia-studio bundleFires when a fellow is ready to design how the AI product is actually built — "architect the product", "how do we build the AI system", "design the AI system", "what's the system architecture", "what does the stack look like". Returns a compound-system architecture (input → router → retrieve/reason/act → validate & guardrails → output over a data layer), a 40/20/30/10 effort-allocation plan, and named model-swap points, then kills any monolithic one-big-prompt design. Do NOT fire to write the pass/fail scope (use eval-first-spec), to render the HTML/SVG picture (use design/architecture-diagram), or to argue defensibility (use moat-design-canvas).
- ▌ Cost Of Capital Estimator · the-utopia-studio bundleComputes cost of equity (CAPM), cost of debt (synthetic rating), and weighted average cost of capital (WACC) for any company in any currency. Handles emerging market risk premiums, bottom-up beta estimation, and multi-country operations. Use when estimating discount rates, computing WACC, determining hurdle rates, analyzing cost of equity or debt, or when user mentions cost of capital, WACC, beta, equity risk premium, country risk premium, or discount rate.
- ▌ Variance Strategy Selector · the-utopia-studio bundleGiven a current win probability and a downside asymmetry flag, recommends a variance-seeking, neutral, or variance-minimizing posture and emits a numeric multiplier (typically 0.8-1.3) for downstream consumers to apply to boom-bust scores, position sizes, or bet sizes. Favorites minimize variance; underdogs maximize it. Reusable across fantasy sports lineup construction, portfolio allocation, poker bankroll decisions, racing strategy, and any decision where the agent controls a variance knob. Use when user mentions variance strategy, underdog variance, variance seeking, variance minimizing, risk posture, boom bust, must-win variance, favorite strategy, or when a decision module needs a single scalar to bias toward or away from high-variance options.
- ▌ Capital Structure Optimizer · the-utopia-studio bundleAnalyzes a company's debt-equity mix and determines the optimal capital structure that minimizes WACC. Computes WACC at each debt ratio from 0% to 90%, identifies the minimum, and recommends whether to add or reduce debt with specific debt type matching (maturity, currency, fixed vs floating). Use when analyzing capital structure, optimizing debt levels, evaluating leverage, or when user mentions optimal debt ratio, capital structure, leverage optimization, debt capacity, or recapitalization.
- ▌ Relative Valuation Multiples · the-utopia-studio bundleValues a company relative to comparable firms using price multiples (PE, PBV, EV/EBITDA, EV/Sales). Implements the four-step framework (define, describe, analyze, apply) with both simple peer comparison and sector regression approaches. Use when valuing a company relative to peers, analyzing multiples, selecting comparable companies, or when user mentions PE ratio, EV/EBITDA, relative valuation, comparable companies, trading multiples, or price-to-book.
- ▌ Agent Persona Builder · the-utopia-studioDesign persistent AI agent personas with distinct voices, durable memory, and clear operating rules. Use when the user wants to build an internal AI agent for a portco or fund workflow, asks 'help me create an agent for X', mentions building an agent persona, wants to formalize a recurring AI workflow as a named agent (e.g. 'Ada the DD analyst'), or asks how to design agents that don't sound generic. Based on Jack & Jill's agent-builder methodology — 25 questions across 5 phases, producing SOUL.md (personality), AGENTS.md (operating manual), MEMORY.md (cross-session knowledge), and BOOTSTRAP.md (first-boot orientation).
- ▌ Manifesto · the-utopia-studio bundleWrite or critique a company manifesto, mission page, founding essay, or "why we exist" document. Use when someone asks for a manifesto, a vision statement, a values page, an "about" or "mission" page with real conviction, a founding blog post, a charter, or a principles document. Also use to audit an existing one for hedging, empty values, and missing stakes. Grounded in a study of 36 tech manifestos from manifestos.tech (Tesla, SSI, Mozilla, Anduril, Obsidian, Linear, Anthropic, Physical Intelligence and others).
- ▌ Kmjp Social · the-utopia-studioGenerate LinkedIn posts and X (Twitter) threads for Karan Pinto (@kmjp). Use this skill whenever Karan shares raw notes, ideas, vault entries, article links, observations, or rough thinking and wants it turned into social content. Trigger on any request like "write a post about this", "turn this into a LinkedIn post", "make me a thread", "draft something for LinkedIn/X/Twitter", "social content for this", or when Karan pastes notes and wants them published. Also trigger if the request is about creating content from context already in the conversation. Always produces BOTH a LinkedIn post AND an X thread unless explicitly told otherwise.
- ▌ Ada · the-utopia-studio bundleRun technical due diligence as Ada — The Utopia Studio's DD analyst. Use when the user asks to 'run DD', 'review this startup', 'audit this repo', 'check this portco', mentions a technical due diligence report, asks 'is this technically sound?', or says 'run DD on [company]'. Ada is skeptical, evidence-driven, and never accepts founder claims at face value. She composes repo-scanner, security-auditor, devops-advisor, cost-optimizer, integration-linker, and technical-dd into a structured 5-phase audit and produces a branded TDD .docx report with P0-P3 risk severities. Distinct voice from generic Claude — leads with the verdict, quantifies risk, calls out unknowns explicitly.
- ▌ Greploop · the-utopia-studio bundleIteratively improves a PR (GitHub) or MR (GitLab) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Triggers Greptile review, fixes all actionable comments, pushes, re-triggers review, and repeats. Use when the user wants to fully optimize a PR/MR against Greptile's code review standards.
- ▌ Hallmark · the-utopia-studio bundleAnti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.
- ▌ UI Polish · the-utopia-studio bundleDesign engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
- ▌ Khalil · the-utopia-studio bundleBuild investor-ready pitch decks as Khalil — The Utopia Studio's deck builder. Use when the user asks to 'build a deck', 'turn these notes into slides', 'pitch deck from these notes', 'investor presentation', 'syndication deck', 'co-investor deck', 'help [portco] with their deck', or shares founder meeting notes and wants a deck. Khalil is storytelling-first, audience-obsessed, and brand-disciplined. He always asks who's reading the deck before drafting. He composes business-narrative-builder, competitive-analysis, datapack-builder, pitch-deck, and ib-check-deck into a structured deck workflow. Hard rules: never Inter font, never purple gradients, never generic Sequoia templates, never buries the ask.
- ▌ Call Scorecards · the-utopia-studio bundleUse this skill when sales call quality is inconsistent, coaching feedback is vague, reps and managers disagree on what a good call is, or the user asks to \"build a call scorecard\", \"score this call\", \"review my rep's calls\", or \"make coaching more consistent\". It builds behavior-based scorecards for each key conversation type (prospecting, discovery, demo, pricing, close) and uses them to score real calls, localize where reps get stuck, and run chunked practice. Also fires when the user pastes a call transcript and wants it graded.
- ▌ Earned Autonomy · the-utopia-studio bundleUse this skill when deciding how much a GTM agent may do without a human looking, when a workflow is ready to run on a schedule, when outreach should stop requiring per-item approval, and when something has gone wrong and autonomy needs pulling back. Produces a level per task with the evidence required to move up and the triggers that drop it automatically. Trigger phrasings: "can I let the agent send", "when do I stop reviewing every draft", "how much should I automate", "the agent made a mistake, now what", "is this workflow ready to run unattended".
- ▌ First Mocks · the-utopia-studio bundleTurns a concept into the cheapest concrete artefact a human can react to, via the no-code make-sequence: Crazy 8s → paper/Miro flow → digital mock → clickable hybrid in v0 or Figma Make, built in one afternoon. Fires on "mock it up", "run Crazy 8s", "clickable prototype", "turn this idea into something I can click", "get from a rough idea to a prototype in an afternoon". Output is a Clickable-Prototype Plan: the ONE thing the mock must provoke a reaction to, the fidelity band, the no-code ceiling, and the hand-off to a real reaction. NOT which experiment to run (probe-matrix), NOT running the test session (usability-test-protocol), NOT the visual / UI craft — colour, type, distinctive components — which it ROUTES to impeccable / shape / design and never restates. Bans jumping to code.
- ▌ New · the-utopia-studio bundleThis skill should be used when the user says "setup", "deploy to railway", "initialize", "create project", "create service", or wants to deploy from GitHub. Handles initial setup AND adding services to existing projects. For databases, use the database skill instead.
- ▌ Agent Design · the-utopia-studio bundleFires when a fellow is designing ONE production agent and asks what it should be built from — "design an agent for X", "what tools and memory does this agent need", "spec the agent", "our agent isn't getting smarter / never remembers corrections — how do we build its memory". Returns a four-part agent spec — role (one owned decision) · tools (the commodity shell) · memory layer (CLAUDE.md · skills · lessons.md · trace archive, loaded at birth) · eval — where the memory layer is the only part the fellow owns and therefore the only part that compounds. Do NOT fire for the agent's voice / persona / signature phrases (use meta/agent-persona-builder), the multi-agent fleet or hand-offs (use workflow-design), writing its golden cases / autonomy level / cost budget (use eval-first-spec — this skill routes there and carries the number), or the post-launch ship-observe-learn-refine loop and autonomy-raise (use refine-flywheel).
- ▌ Probe Matrix · the-utopia-studio bundleRoutes the ONE question a fellow needs answered to the cheapest probe that is HONEST about that question, using the probe honesty contract (paper/sketch, Wizard-of-Oz, concierge, agent-concierge — each honest about some things and lying about others). Fires on "how do I test this cheaply", "which experiment", "what's the cheapest way to learn X", "which probe", "how do I validate this". Output is a probe selection + plan: the question, the chosen probe, why it is honest about this question, what it will still lie about, cost, and a pre-registered pass/fail read-out — and it REFUSES a probe that lies about the very thing being tested, naming the honest one instead. NOT the how-to for running a probe (use the runbooks paper-sketch-probe / wizard-of-oz-probe / concierge-probe / agent-concierge-probe), NOT the build/no-build gate on the problem itself (problem-quality-scorecard), NOT how to score a signal you already hold (evidence-ladder).
- ▌ Repo Scanner · the-utopia-studioScans a GitHub repository to understand its tech stack, hosting, monitoring, integrations, and current production readiness. Use when the user asks to "audit", "check", or "scan" their repo. Don't use for code review or bug detection.
- ▌ Sketch Prompt · the-utopia-studio bundleConverts any block of text into a conceptual sketch image. Takes raw text, extracts the central idea, generates an image prompt, and produces the final image using ComfyUI + Flux.1 Schnell locally. Use when the user pastes text, notes, or ideas and wants a visual concept. Trigger on "sketch this", "turn this into a sketch", "visualize this", "make a sketch", "image for this", "sketch prompt", or when the user drops text and wants it converted into a conceptual illustration.
- ▌ V1 Launch Bar · the-utopia-studio bundleGate a built v1 to go / no-go on two recorded tests — a true stranger reaches first correct value in ≤60 seconds unaided, AND the learn-from-corrections mechanism is wired and proven to compound (the thing 95% of enterprise pilots never deliver). Output is a recorded-evidence go / no-go checklist. Fires on "are we ready to launch", "is v1 good enough", "launch bar", "go/no-go on v1", "should we ship this pilot". Not the ongoing post-launch loop or cadence (use refine-flywheel), not pilot price / terms / commercial success metric (use pilot-six-term-sheet), not defining what "working" means or the golden-set + cost spec before code (use eval-first-spec).
- ▌ Outreach Execution · the-utopia-studio bundleUse this skill when a signal, account list, or named contact needs outreach — it loads sender voice and past approved messages, picks the right path for the situation, and drafts a multi-step sequence anchored on a real hook. It encodes production sender-assignment and approval rails: tiered senders, automatic executive multi-threading on large accounts, and a hard rule that AI-drafted sequences to senior executives are never auto-sent. Every sequence is staged with a written rationale for human approval, and approved copy feeds back into the voice library. Includes references for email/LinkedIn/breakup frameworks and objection handling.
- ▌ Revops Forecasting · the-utopia-studio bundleRevenue forecasting methodology, forecast categories, pipeline analysis, and predictability for B2B revenue teams. Use when the user mentions forecasting, revenue forecast, sales forecast, forecast accuracy, forecast categories, commit, best case, upside, pipeline coverage, weighted pipeline, forecast cadence, capacity planning, quota modeling, forecast call, deal inspection, or forecast variance. Also trigger when someone says 'we can't predict our number,' 'our forecast is always wrong,' 'how much will we close this quarter,' 'we can't see our pipeline,' 'deals go stale,' or 'we need better dashboards.' Also trigger on pipeline visibility, pipeline reporting, sales dashboards, pipeline hygiene, stale deals, pipeline health, big deal alerts, or pipeline quality score. BOUNDARY: Covers forecast methodology, accuracy, and pipeline visibility/reporting. For CRM-specific dashboard implementation, see revops. For metrics and benchmarks, see gtm-metrics.
- ▌ Pitch Deck · the-utopia-studio bundleGenerate investor-ready pitch decks as branded PPTX files from founder meeting notes, uploaded decks, DD reports, and strategy docs. Use this skill whenever the user mentions building a pitch deck, turning notes into slides, creating an investor deck, preparing for a co-investor presentation, or helping a portfolio company with their deck. Also trigger when the user uploads Granola meeting notes, founder call transcripts, or company materials and asks for a deck, slides, or presentation for investors. Covers co-investor syndication decks and founder coaching decks. Even if the user just says 'build a deck from these notes' or 'make this into a pitch deck' or 'help [company] with their deck', use this skill.
- ▌ Cost Optimizer · the-utopia-studioIdentifies cloud cost issues, unused resources, and billing optimization opportunities. Use when the user asks about "costs", "billing", "AWS invoice", "cloud spending", "reduce costs", or "optimize resources". Don't use for monitoring setup, deployment, or security.
- ▌ Devops Advisor · the-utopia-studioAudits infrastructure setup — database config, caching, performance, and scaling patterns. Provides concrete detection commands and improvement steps. Use when the user asks about "infrastructure", "database setup", "caching", "scaling", "performance", or "architecture". Don't use for CI/CD setup (use deployment-engineer), monitoring (use monitoring-setup), or security (use security-auditor).
- ▌ Diagram Design · the-utopia-studio bundleCreate technical and product diagrams — architecture, flowchart, sequence, state machine, ER / data model, timeline, swimlane, quadrant, nested, tree, layer stack, venn, pyramid — as standalone HTML files with inline SVG. Ships with a neutral editorial skin and a first-run gate that prompts users to customize the style guide (colors, fonts) from their own website before generating. Includes annotation-callout primitive and optional sketchy variant.
- ▌ Invent By Hand · the-utopia-studio bundleInvent an original product concept before the machine hands you the generic one — onion the stated idea to its invariant core need, diverge and keep the strange child, anchor every concept to your proprietary YODA corpus, then run the generic-prompt test (if the one-line prompt a competitor would type reaches your concept, it isn't yours yet). Returns an invented concept + rationale. Fires on "what should we actually build", "invent the solution", "make it non-obvious", "give me a concept a competitor couldn't just prompt for", "what's the product idea here". Not for carving and adoption-testing the first slice (use wedge-five-questions, run it next), not for finding the proprietary data the concept stands on (use yoda-data-sourcing, run it first), not for designing a cheap experiment to validate an already-chosen idea (use concierge-probe / probe-matrix, section 04).
- ▌ Deploy · the-utopia-studio bundleThis skill should be used when the user wants to push code to Railway, says "railway up", "deploy", "deploy to railway", "ship", or "push". For initial setup or creating services, use new skill. For Docker images, use environment skill.
- ▌ Domain · the-utopia-studio bundleThis skill should be used when the user wants to add a domain, generate a railway domain, check current domains, get the URL for a service, or remove a domain.
- ▌ Efecto Social Media · the-utopia-studioDesign social media assets with Efecto — Instagram posts, carousels, stories, YouTube thumbnails, TikTok covers, Twitter/X images, LinkedIn slides, Pinterest pins, and Facebook graphics. Use when asked to "design a post", "create a carousel", "make a thumbnail", "design social media", or any social content task. Requires Efecto MCP server.
- ▌ Concept Council · the-utopia-studio bundleFirst-contact teardown of a raw product idea. Fires when a fellow says "here's my idea", "tear this apart", "rip this concept apart", "what am I missing", or "what should I build first". Convenes five adversarial lenses, names the one load-bearing gap, and returns a Gap Map plus one First-Probe Brief costing under a week. NOT for an already-scoped concept you want stress-tested against the five so-whats (use so-what-stress-test) or scored numerically across eight dimensions (use problem-quality-scorecard).
- ▌
- ▌ Dataset Builder · the-utopia-studio bundleTurn field artefacts into a labelled dataset and 20+ golden cases — the seed of the eval suite that gates the build. Attaches a ground-truth label to every real artefact, scores each label on the evidence ladder, and clears each case through four gates (provenance, ground-truth, unreachable, held-out) so a foundation model cannot pre-pass its own memorised test. Fires on "make our own dataset", "create golden cases", "label this", "turn our field logs into a test set the model hasn't seen", "seed the eval suite". Not for finding which sources are proprietary in the first place (use yoda-data-sourcing, section 03), not for composing the labelled cases into the four-band spread / autonomy level / cost budget of a scoreable spec (use eval-first-spec, section 07), not for splitting an expert's teachable procedure from show-only judgment (use explicit-vs-tacit-capture, section 03).
- ▌ Design Critique · the-utopia-studio bundle냉철한 디자인 비평 스킬. 15년 경력 수석 디자이너 페르소나로 UX, 비즈니스 목표, 시각적 원칙을 기준으로 제출된 디자인(이미지, 코드, URL, 기획안)을 분석한다. 4개 평가 기준 + 날카로운 질문 2개 + 우선순위 액션 플랜 3개를 고정 포맷으로 출력. 브랜드 디자인 시스템이 존재하면 이탈 여부를 반드시 검증한다. 트리거: '비평해줘', '리뷰해줘', '뭐가 문제야', '피드백 줘', '크리틱해줘', '어떻게 생각해'.
- ▌ Eval First Spec · the-utopia-studio bundleTurn a validated wedge into the scope you can SCORE — a one-sentence job, 20 pass/fail golden cases drawn from real artefacts, an L0–L4 autonomy level with a failure taxonomy and a derived acceptable failure rate per mode, and a cost-per-outcome budget to the cent. Fires on "spec the build", "define scope", "scope the v1", "write the spec", "how do we know it works". Not for the component pipeline or effort split (use compound-system-architecture), not for pilot price / terms / commercial success metrics (use pilot-six-term-sheet), not for whether the thing gets adopted at all (use wedge-five-questions).
- ▌ Evidence Ladder · the-utopia-studio bundleWeights a pile of "validation" by what people DID, not what they said. Takes interview quotes, sign-ups, LOIs, pilots, payments and places each on one ladder — money moved 1.0, behaviour observed 0.7, artefact shown 0.5, verbal commitment 0.3, opinion 0.1 — then returns a weighted evidence table, the weight of the load-bearing claim, and for every low signal the cheapest probe that raises it a rung. Fires on "how strong is this signal", "score the interview", "did they actually validate", "weight this evidence", "is this real validation". NOT a build gate on a problem (use problem-quality-scorecard), NOT a picker for which test to run next (use probe-matrix), NOT a transcript summary (use summarize-interview). This is the reference skill the rest of the module cites for the ladder.
- ▌ Prompt Engineer · the-utopia-studioMakes a repository AI-native by creating AGENTS.md, .cursorrules, and documentation that helps any AI agent understand the codebase. Follows the WHAT/WHY/HOW framework from best practices. Use when the user asks to "make repo AI-ready", "add cursor rules", "create AGENTS.md", "set up for AI coding", or "make agents work better". Don't use for deployment (use deployment-engineer), monitoring (use monitoring-setup), or code organization (use repo-structurer).
- ▌ Metrics · the-utopia-studio bundleThis skill should be used when the user asks about resource usage, CPU, memory, network, disk, or service performance. Covers questions like "how much memory is my service using" or "is my service slow".
- ▌ Refine Flywheel · the-utopia-studio bundleStands up the post-launch loop for a shipped AI product — ship behind sign-off → observe tweak-time (how much the customer edits before accepting) → learn by re-running the WHOLE eval set on every model release → refine by promoting autonomy only as a scored eval result, never by feel. Fires on "what happens after launch", "improve the product", "set up the loop", "a new model dropped, should we upgrade", "can we raise the autonomy / drop the sign-off yet". Returns a filled flywheel cadence doc. NOT for which metrics/North Star/retention to track (use metrics-that-matter), NOT for turning one trace into a discovery interview (use trace-to-interview), NOT for writing the eval set or autonomy ladder in the first place (use eval-first-spec — this re-runs what that created).
- ▌ Repo Structurer · the-utopia-studioCleans up and structures a repository for production. Adds README files to every directory, modularizes code, removes dead files, and makes the repo LLM-smart. Use when the user asks to "clean up", "structure", "document", or "organize" their repo. Don't use for code review or bug fixing.
- ▌
- ▌ Workflow Design · the-utopia-studio bundleFires when a fellow needs to coordinate MORE THAN ONE agent to get the work done — "design the workflow", "orchestrate the agents", "set up the fleet", "how do the agents work together", "which agents do I need and when do they spawn", "multi-agent setup". Returns a workflow + fleet map: the multi-step orchestration, a spawn-by-rule fleet (researcher, analyst, prototyper, drafter, critic) each with an observable spawn trigger, and a Think/Build/Admin surface assignment (Claude.ai / Claude Code / Cowork), then kills a single-agent design where a fleet is needed and any spawn rule with no trigger. Do NOT fire to spec ONE agent's role/tools/memory (use agent-design), to design the product's internal request-time pipeline of input→router→reason→validate (use compound-system-architecture), or to write the pass/fail eval (use eval-first-spec).
- ▌ Account Tier Scoring · the-utopia-studio bundleUse this skill when you want a production-grade account scoring system instead of a vibes-based one: it tiers every account onto a Bronze/Silver/Gold/Diamond ladder, scoring pre-conversion accounts on intent signals + ACV potential and trials/customers on activation depth + expansion headroom. It encodes the judgment that makes scoring trustworthy — a hard self-serve gate with LinkedIn headcount verification, an enterprise persona gate, anonymous-signal and social-engagement caps, prior-relationship floors, and never-demote rules — with every threshold exposed as a tunable default. Each run produces a verified tier tag and ACV tag, a prepended signal-stack snapshot in account memory, a CRM lead-score sync, and correctly routed Gold/Diamond alerts with per-stakeholder engagement recommendations.
- ▌ Cold Offer Architect · the-utopia-studio bundleUse this skill when the thing being sold to strangers isn't landing, or before writing a single line of cold copy — to build a new cold-traffic offer, audit an existing one against a hard bar, or diagnose why one that reads fine gets no replies. Covers cold email, cold DM, cold ads, and cold mail: any audience with zero trust and no reason to believe you. Produces an architected offer plus a pass/fail score against eight binary criteria. Trigger phrasings: "my offer isn't converting", "low reply rate", "nobody's booking", "fix my offer", "what should I offer", "score this offer", "is this offer any good", "we changed the copy and nothing happened".
- ▌ Email Deliverability · the-utopia-studio bundleUse this skill when emails hit spam, open rates drop, a domain or IP gets blocklisted, or a sender wants a deliverability audit before scaling volume. Triggers: "why are we going to spam", "audit my email setup", "open rates dropped", "we got blocklisted", "warm up this domain", "check my deliverability". Produces a severity-ranked audit or a root-cause diagnosis with a recovery plan and the thresholds to monitor.
- ▌ Technical Dd · the-utopia-studio bundleGenerate investment-grade Technical Due Diligence reports for The Studio (Utopia Capital). Use this skill whenever the user mentions technical due diligence, TDD, tech DD, technical assessment, technical evaluation of a company, or wants to assess whether a startup's technology works, is well-built, can scale, and what the technical risks are. Also trigger when the user uploads company materials (pitch decks, technical docs, corporate profiles) and asks for a due diligence analysis, technical review, or investment assessment focused on technology. This skill produces branded .docx reports suitable for sharing with co-investors or the company itself. Even if the user just says 'run DD on this company' or 'assess this startup' or 'review these materials', use this skill — it's the standard workflow for technical evaluation at The Studio.
- ▌ Four Lenses Test · the-utopia-studio bundleScores a specific concept across the four build-risk lenses — Desirability, Usability, Feasibility, Viability — where each lens is graded ONLY by its named tool (onion+JTBD+Kano for Desirability, a watched usability observation for Usability, a dev spike for Feasibility, ICE anchored to measured value for Viability) and run by its dual-track owner (Product/Design discovery beside Engineering delivery). Fires on "is this desirable / usable / feasible / viable", "should we build it", "run the four lenses", "go or no-go on this concept", "is this worth building". Output is a filled Four-Lens Scorecard: per-lens tool, owner, evidence + ladder weight, score, and an AND gate that KILLS the go if any single lens fails, every claim tagged [Fact]/[Assumption]/[Hypothesis]. NOT for the full problem→vision→strategy→roadmap spine (use product-frame-stack), NOT for scoring the PROBLEM on 8 dimensions (use problem-quality-scorecard), NOT for the five-question so-what gut check on the whole idea (use so-what-stress-test).
- ▌ Guardrail Design · the-utopia-studio bundleFires when a fellow needs to decide how an AI product is stopped from doing the wrong thing — "design the guardrails", "when does a human sign off", "how do we handle failures / bad outputs", "what confidence threshold should we auto-approve at", "where do we put the human in the loop". Returns a guardrail spec: every failure mode placed on a cost-of-error × volume matrix, a three-layer stack (rules in code → confidence threshold → human sign-off) sized per mode, a derived confidence threshold, and a human-sign-off trigger for every high-cost / low- confidence path. Do NOT fire to derive the acceptable failure rate or pick the autonomy level (use eval-first-spec), to lay out the whole component pipeline (use compound-system-architecture), or to decide whether a human can now be REMOVED because accuracy has held (use refine-flywheel).
- ▌ Monitoring Setup · the-utopia-studioConfigures error tracking (Sentry), product analytics (PostHog), health monitoring, and alerting. Provides verification commands and concrete output templates. Use when the user asks to "set up monitoring", "add error tracking", "configure Sentry", "add analytics", or "set up alerts". Don't use for deployment (use deployment-engineer), security (use security-auditor), or integration linking (use integration-linker).
- ▌ Security Auditor · the-utopia-studioAudits repository security — hardcoded secrets, dependency vulnerabilities, environment variable management, and authentication patterns. Use when the user asks to "check security", "find secrets", "audit dependencies", or "secure my repo". Don't use for code review, deployment, or monitoring.
- ▌
- ▌ Efecto Web Design · the-utopia-studioDesign web pages and app UIs with Efecto — create sessions, build layouts with JSX and Tailwind CSS, manage artboards, and push real-time design changes via MCP tools. Use when asked to "design a page", "build a landing page", "create a website", "design a dashboard", "make a UI", or any visual design task. Requires Efecto MCP server.
- ▌
- ▌
- ▌ Templates · the-utopia-studio bundleThis skill should be used when the user wants to add a service from a template, find templates for a specific use case, or deploy tools like Ghost, Strapi, n8n, Minio, Uptime Kuma, etc. For databases (Postgres, Redis, MySQL, MongoDB), prefer the database skill.
- ▌ Proof · the-utopia-studio bundleWeb-first skill for working with Proof documents via proofeditor.ai. Use when a Proof URL is shared, when creating collaborative docs in Proof, or when an installed Proof preference says new docs should live there.
- ▌ Salim · the-utopia-studio bundleCoach Studio fellows through the Cobuild curriculum as Salim — Utopia's fellow coach. Use when a fellow says 'I'm stuck', 'what should I do next?', 'review my [discovery/PRD/pitch]', 'I'm in M[X] and...', 'help me think through [problem]', 'can you check my [JTBD/canvas]?', or any pedagogy-style question. Salim is Socratic — he asks before telling, never produces artifacts the fellow should produce themselves, and is disciplined about Discovery before Build. He's module-aware (M1-M9) and points fellows to the right skills and frameworks. Outputs persistent cobuild logs to Proof.
- ▌ Deal Velocity Engineer · the-utopia-studio bundleDiagnose and fix deal velocity problems. Sales cycle diagnostics, stage exit criteria, pipeline deflation, zombie deal elimination, multi-threading, mutual action plans, AI-driven deal scoring, revenue intelligence integration (Gong/Chorus), and compression tactics with sourced benchmarks. Trigger on 'deal velocity,' 'sales cycle too long,' 'deals stalling,' 'pipeline velocity,' 'stage exit criteria,' 'zombie deals,' 'pipeline deflation,' 'deals stuck,' 'multi-threading,' 'mutual action plan,' 'deal inspection,' 'pipeline hygiene,' 'cycle time,' 'stage conversion,' 'deals die in negotiation,' 'we keep slipping deals,' 'reps can't close,' or 'pipeline is bloated but nothing closes.' Connects stage gates, deal scoring, inspection cadence, and pipeline deflation into the operating cadence. Includes modern AI/automation patterns (HubSpot Breeze, Salesforce Agentforce, predictive pipeline management). BOUNDARY: For forecast methodology see revops-forecasting. For pipeline visibility and dashboards see gtm-metrics
- ▌ Pitch Deck Web · the-utopia-studio bundleBuild a responsive, interactive pitch-deck website from a brand book + a PRD/example deck. Use when the user asks to "build a pitch deck", "make an investor deck", "create a sales deck", generate a deck site from a brand book, or scaffold a deck from a PRD or existing slides. Pulls brand tokens (colors, typography, voice) from a brandbook-builder-style repo, runs a guided brief (investor vs sales, copy approval, image/logo intake, reference mining), then scaffolds a Vite + React + TS + Tailwind + motion deck site mirroring the utopia-os-deck section-scroll pattern.
- ▌ Data Rights Clause · the-utopia-studio bundleDraft the data-rights clause for a fellow's first paid pilot. Run the three-part test — the data must be workflow exhaust, must compound with use, and must be covered by a clause signed at pilot
- ▌ Fellow Path Router · the-utopia-studio bundleRoutes a fellow through the Icarus module by situation type, not by tearing down one idea. Fires on "where do I start", "I already have a product / traction — which stages apply to me", "onboard me to Icarus", "which stages should I skip", "I have a mature product, what's my path". Classifies the fellow as Type A (blank page), B (traction, no moat), or C (mature product) on the evidence ladder, then returns a keep / trim / subtract / leap stage ledger and a think:build:test ratio tied to that type's dominant risk. Do NOT fire to tear down or grade one idea (use concept-council or so-what-stress-test), to assess the fellow's own skill level (use fellow-level-ladder), or to draw the platform build-vs-buy line (use platform-vs-venture).