SKILLEMALL.ai

DD start-vin-obsidian-workflows

Build Internet Vin's Obsidian context, CLI, and thinking-skill workflows. Use when the student types /start-vin-obsidian-workflows.

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

Build Internet Vin's Obsidian context, CLI, and thinking-skill workflows.

As a process D 47/100 · Unfinished process — References files that are not bundled: vin-obsidian-workflows/my-vault/, vin-obsidian-workflows/my-commands.md, vin-obsidian-workflows/my-vault/The%20Death%20Spiral.md

ProcedureObsidianAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
D
71/100
safety, quality, tests
Safety 60%
77
Quality 40%
62
Run on models
none yet
Process rating
D
47/100
Unfinished process
References files that are not bundled: vin-obsidian-workflows/my-vault/, vin-obsidian-workflows/my-commands.md, vin-obsidian-workflows/my-vault/The%20Death%20Spiral.md
Tools and files w 18
0
Inputs and preconditions w 11
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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  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 · 2

  • high Concealment en-hide-from-user SKILL.md:27
    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

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 8415 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: vin-obsidian-workflows/my-vault/
  • warning missing-ref reference to a missing file: vin-obsidian-workflows/my-commands.md
  • warning missing-ref reference to a missing file: vin-obsidian-workflows/my-vault/The%20Death%20Spiral.md
  • warning missing-ref reference to a missing file: vin-obsidian-workflows/CLI_HANDOFF.md

Process rating: all ten parameters 47/100

Will not run. References files that are not bundled: vin-obsidian-workflows/my-vault/, vin-obsidian-workflows/my-commands.md, vin-obsidian-workflows/my-vault/The%20Death%20Spiral.md
  • 0Tools and files. 4 referenced file(s) missing: vin-obsidian-workflows/my-vault/, vin-obsidian-workflows/my-commands.md, vin-obsidian-workflows/my-vault/The%20Death%20Spiral.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 40Result and completion. Does not say what the result is
  • 40Execution cost. Instruction body is 8415 tokens: crowds the task out of the window
  • 85Steps. 76 steps, 1 vague phrases
  • 100Failures and branches. 14 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 14 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (5 tags): a typed call is more reliable

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 131: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 76 items
  • +4Has examples (10 code blocks)

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