SKILLEMALL.ai

CC tutorial-viral-f100k

Orquesta un tutorial viral faceless (sin cara) de FÓRMULA 100K: de una idea o guion a un kit listo para montar. Fase 1 guion con marcas [PANTALLA]/[CARD]/[CTA]; Fase 2 brief de grabación (voz real + pantallas que graba la usuaria); Fase 3 genera cards, mockups y B-roll con Higgsfield o Gemini y capturas tipo tutorial en PNG; Fase 5 entrega GUION.md, BRIEF_GRABACION.md, MANIFEST.md (qué card entra en qué palabra) y un .zip de recursos por Telegram para montarlo en CapCut. En este agente no renderiza ni edita el video; opcional: un borrador juntando clips generados en Higgsfield. Activar cuando se diga: 'tutorial viral', 'explicación viral faceless', 'video sin cara', 'hazme un tutorial de X', 'video tipo screen recording con captions', '/tutorial <tema>'. NO usar para talking-head reels, carruseles, stories ni miniaturas.

ClawHub Agent Skills author: Fórmula 100K v1.0.0 MIT-0 1 file body ≈ 4 267 tokens Open the sourceclawhub.ai↗ analyzed 9 d ago

Orquesta un tutorial viral faceless (sin cara) de FÓRMULA 100K: de una idea o guion a un kit listo para montar.

As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorTelegramLearningtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
94
Quality 40%
64
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • 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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read Write Edit AskUserQuestion Skill
  • low Dangerous commands cmd-privilege SKILL.md:391
    Privilege escalation / world-writable permissions (documentation table row)
    | `npm install` falla en Remotion | Correr `sudo chown -R $(whoami) ~/.npm` y reintentar |
    table

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 52/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
  • 70Execution cost. Instruction body is 4267 tokens
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 47 steps
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. No mutating operations
  • low 13 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (8 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 832: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -5TODO / placeholder text left in the skill
  • +1No license
  • +2Single-language instructions
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 47 items
  • +4Has examples (10 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.

External checks

ClawHub: suspicious
The skill mostly supports creating faceless tutorial kits, but its instructions conflict about local video rendering and include install and privileged troubleshooting commands that need careful review.
LLM: suspicious (medium) · 17 Sept 2026