CF carrusel-del-radar-f100k
Del radar al post: toma el tema más fuerte que trajeron tus radares (tendencias, virales, noticias), elige la ficha del recetario de carruseles F100K que mejor sirve al objetivo, escribe el guion y el caption, te lo manda por Telegram para tu ✅, renderiza las slides en HTML → PNG con portada de Gemini, las revisa una por una, te las manda para el ✅ final y recién entonces las publica en tu Instagram profesional (Composio). Guarda el estado de cada carrusel para retomar cuando contestes, aunque sea horas después. Activar con: «corre el carrusel del radar», «carrusel del radar», «hazme un carrusel de [tema]», «convierte el radar en carrusel», «ensayo, no publiques», o cuando la usuaria conteste a un ✅ pendiente de esta skill (1, 2, 3, ✅, «publícalo», «cambia…»). También la dispara la automatización de lunes y jueves. NO publica nunca sin ✅, NO hace historias, reels ni el carrusel noticiero.
Del radar al post: toma el tema más fuerte que trajeron tus radares (tendencias, virales, noticias), elige la ficha del recetario de carruseles F100K que…
As a process F 31/100 · No process to follow — References files that are not bundled: references/estilos-guia-maestra.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 4. 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") - warning
missing-refreference to a missing file: references/estilos-guia-maestra.md
Process rating: all ten parameters 31/100
- 0Tools and files. 1 referenced file(s) missing: references/estilos-guia-maestra.md
- 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. 4 mutating operations with no state check
- 70Execution cost. Instruction body is 4087 tokens
- 100Steps. 34 steps
- 100Consistency. Name and required fields are in place
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 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)
- +3Description length 901: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -237 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +4Structure: 15 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.