SKILLEMALL.ai

DC start-2-2

Module 2.2: Analyze Data. Teaches funnel analysis, impact estimation, ROI scenarios, and experiment readouts.

Not recommendedcritical or high security findings · low grade D
carlvellotti/claude-code-pm-course Agent Skills author: carlvellotti 6 files · 1 script body ≈ 9 702 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Module 2.2: Analyze Data. Teaches funnel analysis, impact estimation, ROI scenarios, and experiment readouts.

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

AnalyzerLearningSoftware developmentMarketingtype and topics are labelled automatically from the skill text
JSON
Technical rating
D
73/100
safety, quality, tests
Safety 60%
82
Quality 40%
59
Run on models
none yet
Process rating
C
59/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

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. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  3. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 SKILL.md:9
    Instruction to hide actions from the user
    At the start of this lesson, silently copy the bundled lesson assets into the workspace if they are not already present. Do not show command output to the student.

Files scanned: 6. 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 body-long SKILL.md body ≈ 9702 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 59/100

  • 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
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 9702 tokens: crowds the task out of the window
  • 60Steps. 246 steps, 4 vague phrases
  • 100Tools and files. No external tools needed
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 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)
  • +3Description length 109: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 246 items
  • +4Has examples (3 code blocks)

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