BC carrusel-noticiero
Convierte una noticia de IA/tech en un carrusel noticiero de Instagram de 8 slides (QUÉ PASÓ → MOTIVO → EL DATO → ¿Y A TI QUÉ? → 3 JUGADAS → REGLA DE ORO → CTA), traducida para creadoras, con temas HTML intercambiables (scrapbook por defecto) renderizados a PNG 1080×1350 con Chromium headless. La portada animada (imagen Higgsfield → video Higgsfield) se genera con ✅ de créditos y se entrega junto al titular en PNG transparente para unirlos en CapCut o Edits. Usar cuando pida "carrusel noticiero", "carrusel de noticia", "carrusel newsjacking", "convierte esta noticia de IA en carrusel", "el carrusel de la noticia de hoy". NO usar para carruseles virales genéricos (carrusel-viral-formula100k) ni para solo renderizar un guion existente (carrusel-render-formula100k).
Convierte una noticia de IA/tech en un carrusel noticiero de Instagram de 8 slides (QUÉ PASÓ → MOTIVO → EL DATO → ¿Y A TI QUÉ?
As a process C 62/100 · Has gaps — weak spots: when it triggers, failures and branches, progress reporting
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: 8. 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
- 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
- 60Tools and files. Uses tools (node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 37 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2354 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (6 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
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 773: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 37 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.