SKILLEMALL.ai
GitHub ↗ RU Sign in

DD start-1-2

Module 1.2: Visualizing Files. Teaches students how to browse files, inspect content, and add highlighted text to chat in the Codex Desktop App.

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

Module 1.2: Visualizing Files. Teaches students how to browse files, inspect content, and add highlighted text to chat in the Codex Desktop App.

As a process D 49/100 · Unfinished process — References files that are not bundled: </absolute/path/to/workspace/relative/path/file.md>

ProcedureObsidianVS CodeSoftware developmentLearningtype 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
D
76/100
safety, quality, tests
Safety 60%
82
Quality 40%
66
Run on models
none yet
Process rating
D
49/100
Unfinished process
References files that are not bundled: </absolute/path/to/workspace/relative/path/file.md>
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

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 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 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: 7. 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: </absolute/path/to/workspace/relative/path/file.md>

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: </absolute/path/to/workspace/relative/path/file.md>
  • 0Tools and files. 1 referenced file(s) missing: </absolute/path/to/workspace/relative/path/file.md>
  • 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
  • 85Steps. 86 steps, 1 vague phrases
  • 100Failures and branches. 2 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3493 tokens
  • 100Running it twice. Mutating operations check current state

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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 144: enough signal without eating the budget
  • +4Structure: 18 headings
  • +3Step-by-step instructions: 86 items
  • +4Has examples (9 code blocks)

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