Menu
Review product and feature risk before an AI coding agent starts implementation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Use Xquik for X data and confirmation-gated X actions: tweet search, user lookup, follower export, media download, monitors, webhooks, MCP, and SDK workflows.
Use this skill when the user wants to produce a short video (5–120 seconds). Supports any video type: product ads, TikTok/Instagram/YouTube content, brand videos, explainers, social clips. USE FOR: video production, AI video, make a video, product video, brand video, promotional clip, explainer video, short video.
RouterOS /app YAML format for container applications (7.21+ builtin app, 7.22+ custom YAML creation). Use when: writing or validating RouterOS /app YAML files, working with MikroTik container apps, building docker-compose-like definitions for RouterOS, creating /app store schemas, debugging /app validation errors, or when the user mentions /app, tikapp, or RouterOS container YAML.
RouterOS /container subsystem for running OCI containers on MikroTik devices. Use when: enabling containers on RouterOS, setting up VETH/bridge networking for containers, managing container lifecycle via CLI or REST API, building OCI images for RouterOS, configuring container environment variables, troubleshooting container issues, or when the user mentions RouterOS container, /container, VETH, device-mode container, or MikroTik Docker.
RouterOS v7 domain knowledge for AI agents. Use when: working with MikroTik RouterOS, writing RouterOS CLI/script commands, calling RouterOS REST API, debugging why a Linux command fails on RouterOS, or when the user mentions MikroTik, RouterOS, CHR, or /ip /system /interface paths. Scope: RouterOS 7.x (long-term and newer) only — v6 is NOT covered and accuracy for v6 problems will be low.
MikroTik netinstall-cli for automated RouterOS device flashing. Use when: automating netinstall, writing scripts that invoke netinstall-cli, building netinstall tooling, understanding etherboot/BOOTP/TFTP protocols, working with RouterOS package files (.npk), using modescript or configure script, or when the user mentions netinstall, etherboot, or device flashing.
| name | before-you-build |
| description | Review product and feature risk before an AI coding agent starts implementation. |
Don't ask AI to build it yet. Ask why it might fail first.
Use this skill before building or changing a product, feature, SaaS, AI app, side project, or startup idea.
Use it when the user asks:
No API keys or external services are required.
If live evidence would improve the review, ask the user whether they want you to search for similar products, competitor complaints, communities, or demand signals.
First, do not write code, scaffold a project, recommend a tech stack, or create an implementation plan.
Review whether the idea should move into implementation at all.
If the idea is too broad, ask the user to complete this sentence:
This tool is for [specific people], in [specific situation], to solve [specific problem].
If the current alternative is missing and the review would be too speculative, ask:
How do they solve this today, and why is that not good enough?
Ask at most two questions before giving a constrained review.
Then produce a short Quick Reality Check:
## Quick Reality Check
Assumption:
- [State the assumption if any.]
Verdict:
- Don't build yet / Build smaller / Build only if / Build small
Biggest risk:
- [The most important likely failure mode.]
Most likely problem:
- [Demand / distribution / pricing / positioning / retention / trust.]
What to validate first:
- [One concrete test before implementation.]
Smallest useful version:
- [A narrower version worth testing.]
For a new product idea, check whether the user has a narrow buyer, specific situation, painful problem, current alternative, and reachable distribution channel.
For a feature request, check whether it comes from repeated demand, a paying segment, a retention blocker, or only a loud edge case.
For a requirement change or pivot, check whether the change improves validated demand or only expands scope.
For a learning or portfolio project, do not judge by startup standards. Keep the scope small and focus on the learning artifact.
Do not reward vague AI app ideas with implementation plans.
Do not treat "a competitor exists" as proof of demand.
Do not treat friends saying "cool idea" as validation.
Do not turn the review into a long questionnaire.
Do not block all building. The useful outcome may be "build smaller" or "validate this narrow version first."
Full project: https://github.com/bin1874/before-you-build-skill