CC audios-venta-f100k
Escribe guiones de AUDIOS DE VENTA (notas de voz comerciales, audios de cierre en DM, voicenotes de objeción, audios de seguimiento, audios de aplicación a high ticket) para grabar en WhatsApp / Instagram DM / Telegram. Convierte una oferta ya construida en una secuencia hablada de máximo 50 segundos que cierra la venta en privado. Activar SIEMPRE que se pida 'haz un audio de venta', 'guion para nota de voz', 'audio para cerrar en DM', 'voicenote para vender', 'audio de cierre', 'audio de seguimiento', 'audio para esa prospecta', 'audio para responder objeción', 'audio de aplicación', 'audio para que compre', 'guion de audio de IG', 'audio de bienvenida a high ticket', o cualquier variación que combine vender + formato hablado privado 1-on-1. NO usar para guiones de video público (guionizacion-formula100k), VSL ni landing (vsl-expert-f100k), ni construir la oferta (constructor-ofertas-f100k).
Escribe guiones de AUDIOS DE VENTA (notas de voz comerciales, audios de cierre en DM, voicenotes de objeción, audios de seguimiento, audios de aplicación a…
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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: 2. 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 62/100
- 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
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2375 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 905: 120–800 characters recommended
- +4No input/output examples
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 14 headings
- +3Step-by-step instructions: 54 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.