SKILLEMALL.ai
GitHub ↗ RU Sign in

CC scenarist

Scenario and script craft — writes and reworks the scene-by-scene scenario.json: hook, beat structure, per-scene VO, on-screen text, pacing, and the language/aspect pre-flight. Owns scenario feedback loops and the scenario quality gate. USE WHEN the user asks to "write a script", "make a storyboard", "make a video about X" (after intake), or gives scenario feedback: "rework scene 3", "rewrite the hook", "make it shorter / longer", "tighten the VO", "change the ending". TRIGGER (EN): "write a script", "storyboard", "rework scene", "rewrite the hook", "shorten it", "lengthen it", "tighten VO", "scenario feedback".

Not recommendedcritical or high security findings
alecs5am/ralphy Agent Skills author: alecs5am 5 files body ≈ 2 992 tokens Open the sourcegithub.com↗ analyzed 11 h ago

Scenario and script craft — writes and reworks the scene-by-scene scenario.json: hook, beat structure, per-scene VO, on-screen text, pacing, and the…

As a process C 56/100 · Has gaps — References files that are not bundled: ../../../docs/skills-vs-templates.md, ../intake/SKILL.md, ../editor/SKILL.md

GeneratorAI and agentsMedia and videotype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
82/100
safety, quality, tests
Safety 60%
82
Quality 40%
83
Run on models
none yet
Process rating
C
56/100
Has gaps
References files that are not bundled: ../../../docs/skills-vs-templates.md, ../intake/SKILL.md, ../editor/SKILL.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: ralphy

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Concealment
If you install

The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.

For the author

Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. The text references files that are not there: add them or drop the references.
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 · 1

  • high Concealment en-hide-from-user references/quality-gate.md:35
    Instruction to hide actions from the user
    1. No handoff. Don't tell the user "done".

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../../docs/skills-vs-templates.md
  • warning missing-ref reference to a missing file: ../intake/SKILL.md
  • warning missing-ref reference to a missing file: ../editor/SKILL.md
  • warning missing-ref reference to a missing file: ../art-director/SKILL.md
  • warning missing-ref reference to a missing file: ../../../notes/issues/done/044-user-prompt-logging-under-used.md
  • note frontmatter-key unknown frontmatter key "namespace"

Process rating: all ten parameters 56/100

Will not run. References files that are not bundled: ../../../docs/skills-vs-templates.md, ../intake/SKILL.md, ../editor/SKILL.md
  • 0Tools and files. 5 referenced file(s) missing: ../../../docs/skills-vs-templates.md, ../intake/SKILL.md, ../editor/SKILL.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 5 mutating operations with no state check
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 25 steps, 1 vague phrases
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2992 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (7 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)
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 16 example trigger phrases
  • +3Description length 619: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 25 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)
  • +4Reference files are cited in the instructions (4 of 4)

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