SKILLEMALL.ai
GitHub ↗ RU Sign in

CC cinematographer

Design the MANDATORY cinematic scroll experience (every blog ships one): a full-bleed, scroll-driven background — primarily from the Scout's verified real imagery — plus the global motion choreography, so the narrative unfolds like a film as the reader scrolls. Owns the BACKGROUND layer + page-level motion (not the Designer's per-section visuals, not the Interaction centerpiece — it stages them inside the scroll). Outputs cinematographer.json (cin_xx scenes). There is no off path: a topic with no sourceable real imagery falls back to a generative-atmosphere or data-driven-spine background, never to a bare column.

QinghongLin/data2story-skill Claude Code author: QinghongLin 4 files body ≈ 4 022 tokens Open the sourcegithub.com↗ analyzed 16 h ago

Design the MANDATORY cinematic scroll experience (every blog ships one): a full-bleed, scroll-driven background — primarily from the Scout's verified real…

As a process C 53/100 · Has gaps — References files that are not bundled: ../../frontend-design-pro/references/interaction_playbook.json, assets/cinematic_imagery_manifest.json

AnalyzerSoftware developmentMedia and videoDesigntype 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
83/100
safety, quality, tests
Safety 60%
95
Quality 40%
66
Run on models
none yet
Process rating
C
53/100
Has gaps
References files that are not bundled: ../../frontend-design-pro/references/interaction_playbook.json, assets/cinematic_imagery_manifest.json
Tools and files w 18
0
Inputs and preconditions w 11
0
Progress reporting w 2
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.
  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

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash(*)
    allowed-tools: Bash(*) Read Write Glob

Files scanned: 4. 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")
  • warning missing-ref reference to a missing file: ../../frontend-design-pro/references/interaction_playbook.json
  • warning missing-ref reference to a missing file: assets/cinematic_imagery_manifest.json

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: ../../frontend-design-pro/references/interaction_playbook.json, assets/cinematic_imagery_manifest.json
  • 0Tools and files. 2 referenced file(s) missing: ../../frontend-design-pro/references/interaction_playbook.json, assets/cinematic_imagery_manifest.json
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 6 mutating operations with no state check
  • 70Execution cost. Instruction body is 4022 tokens
  • 85Steps. 28 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 620: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 28 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

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