CC auditor-ux-app-f100k
Auditor de la construcción de UX de una app (producto, no pixel) con la doctrina de FÓRMULA 100K y 22 cicatrices reales de apps en producción. Revisa CUALQUIER etapa: brief, spec/PRD, plan de implementación o la app ya construida. Recorre la app como usuaria con el navegador del agente (URL pública o proyecto en el workspace), la puntúa contra una rúbrica de 10 dimensiones (claridad, primer minuto, los 4+1 estados, feedback honesto, no perder el trabajo, la pantalla no miente, móvil de verdad, dashboard 1-3-5, puertas de acceso y dinero, salir al mundo), entrega un informe con termómetro 0-100 y hallazgos con evidencia, y —tras tu ✅— APLICA los arreglos en los archivos. Usar cuando digan "revisa la UX de esta app", "audita mi app", "qué le falta a mi app", "revisa este spec/plan/brief antes de construir", "/audita-ux", "por qué mi app se siente a medias". NO es la skill de diseño visual (ux-elevacion-formula100k); NO construye la app desde cero (crea-tu-app-f100k).
Auditor de la construcción de UX de una app (producto, no pixel) con la doctrina de FÓRMULA 100K y 22 cicatrices reales de apps en producción.
As a process C 51/100 · Has gaps — 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: 5. 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 51/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. 3 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2634 tokens
- low 10 top-level sections: this looks like several domains in one skill
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 979: 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 6 example trigger phrases
- +4Structure: 11 headings
- +3Step-by-step instructions: 37 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.