SKILLEMALL.ai
GitHub ↗ RU Sign in

CD imagineer

Fan out MANY candidate interactive concepts from the data + narrative — the ideation pool the Editor curates a hero + supporting set from. Deliberate over-generation: one concept per finding worth making hands-on, each declaring its archetype, purpose, what the reader produces, and an honest feasibility (node-checked against the Analyst's client_model). Builds NOTHING on-page — img_xx concepts are internal and never reach HTML. Outputs imagineer.json after the Analyst, before the Editor.

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

Fan out MANY candidate interactive concepts from the data + narrative — the ideation pool the Editor curates a hero + supporting set from.

As a process D 47/100 · Unfinished process — References files that are not bundled: ../references/topic_profile.json, ../../frontend-design-pro/references/abstract_excellence.json, ../../frontend-design-pro/references/interaction_playbook.json

AnalyzerSoftware developmentData and analyticsAI and agentstype 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%
95
Quality 40%
63
Run on models
none yet
Process rating
D
47/100
Unfinished process
References files that are not bundled: ../references/topic_profile.json, ../../frontend-design-pro/references/abstract_excellence.json, ../../frontend-design-pro/references/interaction_playbook.json
Tools and files w 18
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.
  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: 2. 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: ../references/topic_profile.json
  • warning missing-ref reference to a missing file: ../../frontend-design-pro/references/abstract_excellence.json
  • warning missing-ref reference to a missing file: ../../frontend-design-pro/references/interaction_playbook.json

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: ../references/topic_profile.json, ../../frontend-design-pro/references/abstract_excellence.json, ../../frontend-design-pro/references/interaction_playbook.json
  • 0Tools and files. 3 referenced file(s) missing: ../references/topic_profile.json, ../../frontend-design-pro/references/abstract_excellence.json, ../../frontend-design-pro/references/interaction_playbook.json
  • 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. 5 mutating operations with no state check
  • 100Steps. 29 steps
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3044 tokens

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 492: enough signal without eating the budget
  • +4Structure: 8 headings
  • +3Step-by-step instructions: 29 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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