For Agents · MCP

Your task.
The right skill.

The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.

No local installationNo M11 loginRead-only

Broad task

Load 5–10 and go

SEO, Sales, Agents or another broad area → one bundle call → work.

MCP endpoint: https://skills.m11.ch/mcp

Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.

Task Packs

Marketing Foundation

Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.

Marketing Launch

Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.

Agent Audit Essentials

Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.

Conversion and Activation Review

Review the journey from landing page and lead capture through registration, first value and transparent upgrades.

Campaign Content and Brand Review

Plan a campaign, draft its channel content and review the work against actual brand guidance.

Content and Launch Planning

Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.

Customer, Market and Community Research

Understand customer needs, compare competitors and plan a community around real member value.

Lead Magnet to Lifecycle Nurture

Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.

API Contract and Observability

Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.

Data Analysis Foundation

Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.

B2B Outreach Foundation

Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.

Choose an area

01 · Category

What the MCP returns at this step

42 · Business · Product Strategy

Before You Build / Product Risk

Review demand, alternatives and risk signals before building a product.

produktrisikopruefungbefore-you-build

Before You Build / Product Risk · Original SKILL.md

---
name: before-you-build
description: "Review product risk before coding by checking demand, alternatives, channels, switching costs, and failure signals."
category: product
risk: safe
source: community
source_repo: bin1874/before-you-build-skill
source_type: community
date_added: "2026-07-02"
author: bin1874
tags: [product-validation, planning, ai-coding, risk-review]
tools: [claude, cursor, codex, gemini, antigravity]
license: "MIT"
license_source: "https://github.com/bin1874/before-you-build-skill/blob/main/LICENSE"
---

# Before You Build

## Overview

Before You Build helps an AI coding workflow pause before implementation and check whether the feature, product, or tool is worth building. It focuses on product risk rather than code structure: who needs the thing, what they use today, why they would switch, how distribution works, and what evidence would make the project safer to start.

The upstream project ships a standalone skill repository and an `npx` installer for several coding assistants.

## When to Use This Skill

- Use when a user asks an AI coding assistant to build a new app, feature, internal tool, SaaS, or side project.
- Use when the idea sounds plausible but the buyer, workflow, distribution path, or switching reason is still vague.
- Use before writing code so the assistant can turn the request into sharper assumptions, risk checks, and validation steps.

## How It Works

### Step 1: Identify the Build Bet

Restate the product or feature in one concrete sentence. Name the intended user, the job they are trying to finish, and the current workaround or competitor.

### Step 2: Check the Main Risks

Review the idea across demand, workflow fit, willingness to switch, distribution, pricing, data access, and operational burden. Prefer specific doubts over generic brainstorming.

### Step 3: Decide the Next Small Test

Suggest the smallest useful validation step before implementation. This could be a buyer conversation, landing page test, manual concierge workflow, prototype, waitlist, paid pilot, or narrow internal trial.

### Step 4: Continue or Stop

If the risk is acceptable, move into implementation with the assumptions written down. If the risk is high or evidence is weak, recommend a smaller experiment instead of building the full version.

## Examples

### Example 1: SaaS Feature Request

```text
User: Build a dashboard for AI trend monitoring.

Before coding, check:
- Which role needs this dashboard every week?
- What source do they use today?
- What decision changes because of the dashboard?
- Would they pay for alerts, reports, or workflow integration?
- What is the smallest manual report that proves repeat use?
```

### Example 2: Internal Tool

```text
User: Build an internal CRM for our small team.

Before coding, check:
- What breaks in the current spreadsheet or existing CRM?
- How many people will use it daily?
- What data must be imported or kept in sync?
- What process change is required after launch?
- Can a no-code workflow prove the need first?
```

## Best Practices

- ✅ Ask for the user, job, current alternative, and switching reason before implementation.
- ✅ Separate product risk from engineering risk so the team does not solve the wrong problem well.
- ✅ Recommend small validation steps when the idea has weak demand evidence.
- ✅ Keep product names, numbers, and claims grounded in what the user provides.
- ❌ Do not present a generic checklist as proof that an idea is validated.
- ❌ Do not fabricate market size, revenue, competitor traction, or buyer quotes.

## Limitations

- This skill does not replace customer research, legal review, financial advice, or domain expert review.
- It cannot prove demand by itself; it helps the assistant surface assumptions and choose a smaller validation step.
- If the user already has strong evidence and a clear spec, keep the review short and move into implementation.

## Security & Safety Notes

- This skill is safe to run as a planning layer because it does not require credentials, external network access, or file mutation.
- If paired with an installer or repository fetch, only install from the upstream repository or npm package you trust.

## Common Pitfalls

- **Problem:** The assistant repeats the product pitch instead of challenging the assumptions.
**Solution:** Ask for current alternatives, switching triggers, and a validation step before code.

- **Problem:** The review becomes too broad and blocks progress.
**Solution:** Pick the riskiest assumption and test only that first.

- **Problem:** The idea is treated as a startup even when it is a small internal workflow.
**Solution:** Scale the risk review to the project size and only ask questions that change the build decision.

## Related Skills

- `@saas-mvp-launcher` - Use when moving from validation into MVP planning and launch execution.
- `@ux-research-methodology` - Use when the next step needs structured user research.

When to use

Review demand, alternatives and risk signals before building a product.

What you get

The complete original guidance with attribution and declared limits.

How it works

Clarify the evidence and task scope, then use the source guidance within actual authorization.

Requirements

Product hypothesis, target users, alternatives evidence and decision owner.

Delivery and review notes

Original frontmatter declares MIT; its notice and named author are preserved. Referenced runtimes, scripts, integrations and sibling skills are not bundled or installed. Brief obvious-danger screening only; no functional test or comprehensive safety certification. Loading this text authorizes no external action.

Starting prompt

Use Before You Build / Product Risk for [TASK]. Clarify Product hypothesis, target users, alternatives evidence and decision owner. Identify evidence gaps and missing dependencies. Do not claim results, approval or execution without evidence.

Not for

Treating this attributed guidance as installed software, professional certification or authorization for external actions.

What M11 added

German routing and delivery limits. Original attribution: bin1874. Original frontmatter declares MIT; its notice and named author are preserved. Referenced runtimes, scripts, integrations and sibling skills are not bundled or installed. Brief obvious-danger screening only; no functional test or comprehensive safety certification. Loading this text authorizes no external action.

Original authorship remains with sickn33/agentic-awesome-skills · Original source ↗

Original license & copyright

MIT License

Copyright (c) 2026 Pawel Huryn

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Source SHA-256: 2a10be8167abb531d31261a14a57162059901617ce267959aa63c2d2e094b5e9
Snapshot checked: 2026-09-28T17:05:37.111Z

Find a skill.Get to work.

All skills

Multi-Agent Orchestration

AI Context Window Audit

AI Agent Architecture Audit

AI Skill Discovery

Lead Magnet Strategy

Ideal Customer Profile

Go-to-Market Strategy

Marketing Campaign Ideas

Product Growth Loops

Competitor Analysis

North Star Metric

Product Positioning

Product Vision

Go-to-Market Motion Selection

Customer Feedback and JTBD Analysis

PESTLE Market Environment Analysis

Customer Journey Mapping

Ansoff Growth Options

Data Analysis Validation

Dataset Profiling

Statistical Analysis Guidance

Programmatic SEO Planning

Landing Page and Form Conversion Review

Paywall and Upgrade Planning

Signup and Registration Review

User Onboarding and Activation

Popup and Modal Planning

Email Sequence Copy and Flow

Marketing Campaign Planning

Marketing Content Drafting

Brand Voice and Content Review

Marketing Performance Reporting

Sales Company Research

Company and Contact Enrichment

Website Information Architecture

Content Strategy and Editorial Roadmap

Product Launch Planning

Customer Research and Voice of Customer

Community Growth and Member Experience

Competitor Research Profiles

Roadmap and Release Communication

Lifecycle Email Sequences

API Contracts and Interface Design

Observability and Instrumentation Planning

Agent Context and Session Handoff

Product Discovery Sprint

Deal Quality Scoring

Enrichment Waterfall Design

Customer Retention Playbook

Sales Coaching Practice

Revenue Cohort Analysis

Intent Signal Scoring

Customer Identity Matching

Segment Activation Planning

Sales Call Review

Retention Dashboard Design

Sales Coaching Competencies

Offer Delivery Design

Offer Value Communication

Service Productization

Conversion Hypothesis Prioritization

Braze Engagement Guidance

Brand Voice Guide Design

Content Pipeline Orchestration

Website Brand Profile

Buyer Objection Clarification

Klaviyo Integration Guidance

Offer Bonus Planning

Klaviyo Marketing Review

Cross-Platform Advertising Review

Expertise Business Model

LinkedIn Advertising Guidance

TikTok Advertising Guidance

Evidence Research Brief

Cinematic Video Prompts

Visual Prompt Model Adaptation

Visual Prompt Diagnostics

Short Film Development

Find a skill.
Get to work.