SKILLEMALL.ai
GitHub ↗ RU Sign in

DC start-gsd-1

Learn GSD lesson 1 through its file-backed planning and build workflow. Use when the student types /start-gsd-1.

The skillemall take

The skill promises to teach GSD lesson 1 through file-backed planning and workflow. In reality: 2 files with 2743 tokens, but half the links are broken (broken_references_missing_files flagged true). The audit found a high-risk concealment issue—something's hidden or masked in the code. Quality scored 72, process scored 59. No sandbox run, no model testing.

For educational content, this is critical: a student runs /start-gsd-1, hits broken links everywhere, and doesn't complete the lesson. High concealment risk plus broken files make this unusable. Don't install it.

Not recommendedcritical or high security findings · low grade D
carlvellotti/claude-code-pm-course Claude Code author: carlvellotti 2 files body ≈ 2 743 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Learn GSD lesson 1 through its file-backed planning and build workflow.

As a process C 59/100 · Has gaps — References files that are not bundled: expense-splitter/PROJECT_BRIEF.md, expense-splitter/.planning/STATE.md

ProcedureAI and agentsLearningOperations and projectstype 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
75/100
safety, quality, tests
Safety 60%
77
Quality 40%
72
Run on models
none yet
Process rating
C
59/100
Has gaps
References files that are not bundled: expense-splitter/PROJECT_BRIEF.md, expense-splitter/.planning/STATE.md
Tools and files w 18
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".

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. 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 · 2

  • high Concealment en-hide-from-user SKILL.md:25
    Instruction to hide actions from the user
    ACTION: Before greeting the learner: silently run `fspm progress`. If it shows a learner name, greet them by it and continue. If it shows no name and no declined marker, run `fspm onboard` and follow
Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Read Write Bash AskUserQuestion Skill

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

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: expense-splitter/PROJECT_BRIEF.md
  • warning missing-ref reference to a missing file: expense-splitter/.planning/STATE.md

Process rating: all ten parameters 59/100

Will not run. References files that are not bundled: expense-splitter/PROJECT_BRIEF.md, expense-splitter/.planning/STATE.md
  • 0Tools and files. 2 referenced file(s) missing: expense-splitter/PROJECT_BRIEF.md, expense-splitter/.planning/STATE.md
  • 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
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 40 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2743 tokens
  • 100Running it twice. Mutating operations check current state
  • low 12 top-level sections: this looks like several domains in one skill

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 112: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 40 items
  • +4Has examples (3 code blocks)

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