CD constructor-miniapps-f100k
Construye mini-apps y herramientas reales sin ser programadora, con la metodología FÓRMULA 100K. Usar SIEMPRE que alguien pida: "quiero que construyas una mini app web llamada X", "constrúyeme una app", "hazme una mini-app", "es mi primera app", "crea una herramienta", "una calculadora web", "un quiz que dé un resultado", "un generador de X", "una auditoría exprés", "una extensión de Chrome", "una app con mi API/IA", "un mini-SaaS", "clona esta web/app", "publícala en Vercel", "dame el link de mi app". Empieza SIEMPRE por el brief de 5 preguntas y, si no hay motivo real para más, entrega una app de UN SOLO ARCHIVO HTML que funciona con doble clic, probada en el navegador del agente y enviada por Telegram — sin llaves de IA, sin base de datos, sin login. La publica en *.vercel.app solo con la cuenta de Vercel de la usuaria conectada y su ✅. NO usar para landings de venta puras ni para diseñar la estrategia del lead magnet (cazador-lead-magnets-f100k).
Construye mini-apps y herramientas reales sin ser programadora, con la metodología FÓRMULA 100K.
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 100Steps. 46 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2808 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 964: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +5Description quotes 15 example trigger phrases
- +4Structure: 13 headings
- +3Step-by-step instructions: 46 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.