Results for “startup”

Shared orchestrator for AI Lab and AI Startup divisions. Use when the user asks to talk to Nosh, requests the ML orchestrator, or says "what should we do next".

Generate a Lean Canvas with sections for problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue for testing business hypotheses.

Track weekly funding rounds across configurable verticals with primary-source verification, per-round analysis, and risk assessment.

Narrates a demo video for Loki Mode, a multi-agent autonomous startup system for Claude Code, covering setup, phases, and features.

Build, review, or restructure a fundraising deck for pre-seed through Series A, with a clear narrative arc, investor-grade slide logic, and explicit asks.

Guides creating a Sequoia-style 12-slide pitch deck with slide-by-slide instructions, storytelling principles, and 30 anticipated VC questions with answer strategies.

Generate a Lean Canvas with problem, solution, metrics, cost structure, UVP, unfair advantage, channels, segments, and revenue. Use when exploring a lean startup canvas, testing a business hypothesis, or modeling a new venture.

The YC meta-game distilled from 4000+ funded companies. Demo day prep, batch dynamics, investor updates, "launch now" mentality, talking to users obsessively. This is the playbook that turned $125K checks into trillion-dollar companies. Use when "yc, y combinator, demo day, batch, investor update, office hours, launch now, talk to users, do things that don't scale, make something people want, startup school, yc application, series a prep, post-yc, yc, startup, accelerator, demo-day, fundraising, launch, users, growth" mentioned.

Persists project context across Claude Code sessions. Auto-loads project summaries on startup, tracks session progress, and saves structured state via deterministic Node.js scripts.

Identify and analyze malware persistence mechanisms on Windows systems using Sysinternals Autoruns, covering registry keys, scheduled tasks, services, drivers, and startup locations.

Guides writing Korean government funding program business plans (사업계획서) from an evaluator's perspective, covering structure, scoring emphasis, and writing principles.

This skill should be used when the user asks to "plan team structure", "determine hiring needs", "design org chart", "calculate compensation", "plan equity allocation", or requests organizational design and headcount planning for a startup.

Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", "test assumptions", "innovation accounting", "build-measure-learn", or "minimum viable experiment". Also trigger when deciding what to include in a first version, measuring startup progress, or evaluating whether to change direction on a product bet. Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.

Add EAS Observe to an Expo project for startup, navigation, and custom-event performance metrics, query them via the EAS CLI, and interpret the results.

Run a cross-division all-hands meeting that includes both AI Lab and AI Startup agents. Use when the user requests to "start an all-hands", "convene both divisions", or "run a cross-division meeting".

Generate 5–10 business idea candidates from a blank page or a founder's domain context — using pain mining, jobs-to-be-done, trend × capability mapping, constraint relaxation, adjacency search, and founder-market-fit prompts. Each candidate is a structured idea card (segment, JTBD, current alternative, why-now, distribution wedge, monetisation, "feels like"). Load when the user asks to generate business ideas, brainstorm startup ideas, find ideas to work on, says "what business should I start", "give me startup ideas", "I don't know what to build", "ideate ventures", "blank-page idea generation", "find me a startup idea", "explore business opportunities". Sub-skill of `venture-exploration`. Hard-bans "Uber for X" / "AI for X" with no specific JTBD, "everyone" segments, and idea cards missing any of the 7 required fields. Does NOT design or evaluate ideas generated — for that use `idea-evaluation`.

Provides strategic financial frameworks for startup CFOs and finance leaders, including financial modeling, unit economics analysis, fundraising strategy, cash management, and board financial packages.

Documents Notion's brand design system including color tokens, typography hierarchy, layout spacing, and component geometry across homepage, enterprise, AI, agents, startups, and pricing surfaces.

Run an AI Lab division meeting with research and build agents (no AI Startup agents). Use when the user requests to "start a lab meeting", "convene the lab", or "run a sprint retrospective for the lab".

Evaluate a raw app, startup, SaaS, internal tool, marketplace, or AI product idea before planning features. Use when the user shares a vague concept and needs pain analysis, market realism, feasibility, differentiation, risks, or a build/no-build recommendation.

This skill should be used when the user asks to "calculate TAM", "determine SAM", "estimate SOM", "size the market", "calculate market opportunity", "what's the total addressable market", or requests market sizing analysis for a startup or business opportunity.

Maintains a persistent session memory across Claude sessions by loading project state at startup, capturing errors and decisions during work, and writing structured handoff summaries at session end.

Search engine optimization for startups. Covers technical SEO, content strategy, and link building. Focus on sustainable approaches that compound over time rather than tricks that get penalized. Use when "seo, search engine optimization, organic traffic, google ranking, keyword research, backlinks, content strategy, search visibility, " mentioned.

Startup skill router: maps any incoming request to the correct skill using Quick Lookup table and _manifest.json. Loaded automatically at session start. Triggers on: every new request — this is the dispatch layer, not a user-facing skill. NOT for: executing tasks directly — always routes to a domain-specific skill.

Financial leadership for startups and scaling companies. Financial modeling, unit economics, fundraising strategy, cash management, and board financial packages. Use when building financial models, analyzing unit economics, planning fundraising, managing cash runway, preparing board materials, or when user mentions CFO, burn rate, runway, fundraising, unit economics, LTV, CAC, term sheets, or financial strategy.

Score an unbuilt business idea on desirability, viability, feasibility, distribution wedge, why-now, founder-market-fit, market size, alternatives, defensibility, capital intensity, and regulatory/ethical risk — and return a GO / ITERATE / KILL verdict with kill criteria and a next kill test. Load when the user asks to evaluate a business idea, score a startup idea, screen an idea, decide whether to pursue this venture, do an idea review, or says "is this a good business idea", "should I build this", "evaluate this startup", "screen this idea", "go/no-go on this idea", "kill or pursue". Sub-skill of `venture-exploration`. Calls `fermi` for sizing, `assumption-mapping` for hidden beliefs, optional `pre-mortem` / `adversarial-hat` for high-stakes ideas. Does NOT evaluate built products — for that use `reality-check`.

Orchestrator for the pre-decision business-idea lifecycle — generate ideas, model them, evaluate them, validate them with customers, and only then hand off to product-soul / brainstorming. Routes through `idea-generation`, `business-modeling`, `idea-evaluation`, and `customer-discovery`. Load when the user asks to explore business ideas, find a startup idea, evaluate a venture, validate an idea, says "what business should I start", "should I build this", "is this a good business", "I have a startup idea", "evaluate this venture", "model this business", "validate this idea", "Mom Test this", "Lean Canvas this", "Business Model Canvas", "Value Proposition Canvas", "go/no-go on this idea". Pre-decision suite — once one idea is committed, hands off to `product-soul`. Does NOT design features (use `brainstorming`) or audit built products (use `reality-check`).

Use for writing, reviewing, debugging, migrating, or testing Python application configuration built with pydantic-settings. Trigger for BaseSettings, SettingsConfigDict, environment names, dotenv, secrets directories, nested settings, CLI sources, custom source precedence, and secret-safe startup configuration. Do not use for ordinary Pydantic model validation, direct os.environ access in a small script, or external secret manager administration.

Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.

Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.

Email has the highest ROI of any marketing channel. $36 for every $1 spent. Yet most startups treat it as an afterthought - bulk blasts, no personalization, landing in spam folders. This skill covers transactional email that works, marketing automation that converts, deliverability that reaches inboxes, and the infrastructure decisions that scale. Use when: keywords, file_patterns, code_patterns.

Drafts Right of First Refusal and Co-Sale Agreements for venture-backed and closely-held companies. Establishes ROFR mechanics, tag-along/co-sale rights, transfer restrictions, and permitted transfer carve-outs aligned with NVCA standards. Use when drafting ROFR agreements, co-sale agreements, tag-along rights, share transfer restrictions, or investor protective provisions in venture capital, private equity, or startup financing transactions.

Product strategy, market validation, commercial filtering, and MVP definition for Nick's workflow. Use when turning vague ideas into product plans, evaluating startup opportunities, identifying real market gaps, deciding if an idea should be killed before build, prioritizing features, shaping positioning, defining monetization, or judging whether a concept is strong enough to deserve design and engineering effort. Focus on painful problems, clear buyers, credible wedges, practical validation, and realistic paths to revenue.

Build the smallest, highest-signal context package for an AI coding task — goal, constraints, repo facts, boundaries, and a verification plan. Load when prompts are underspecified, the agent is missing key files or decisions, the user says "use the right context", "here's the repo", or when work is drifting due to missing constraints. Also triggers on "context engineering", "gather context", "what do you need from me", "before you start". Not for cross-session continuity (use memory-startup/memory-recall).

Complete user guide for the IoM (Implant-over-Middleware) C2 framework. Covers architecture concepts, basic operations, startup parameters, authentication configuration, troubleshooting, documentation resources, and community feedback. Trigger conditions: use this skill when the user asks about how IoM works, command usage, architecture concepts, configuration methods, how to troubleshoot issues, where to find documentation, or how to file an issue. Should also trigger for questions like "how do I connect", "what is a session", "I got an error", or "is there documentation".

Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "UX experiment", "collaborative design", "outcome over output", "design studio method", "assumption mapping", or "lightweight research". Also trigger when reducing design documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.