SKILLEMALL.ai

DC agent-daily-retro

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: morrison230 v1.0.0 MIT-0 8 files body ≈ 420 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

ProcedureAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
D
58/100
safety, quality, tests
Safety 60%
96
Quality 40%
0
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
When it triggers w 12
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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 · 4

✓ No critical or high findings

Medium and low: 4
  • low Dangerous commands cmd-cron-mention INSTALL.md:89
    Mentions editing / listing crontab
    crontab -e
  • low Dangerous commands cmd-cron-mention INSTALL.md:98
    Mentions editing / listing crontab
    crontab -l | grep agent_retro
  • low Dangerous commands cmd-cron-mention INSTALL.md:268
    Mentions editing / listing crontab
    crontab -l > crontab.backup
  • low Dangerous commands cmd-cron-mention INSTALL.md:292
    Mentions editing / listing crontab
    crontab -l | grep agent_retro

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

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 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
  • 100Tools and files. No external tools needed
  • 100Steps. 20 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 420 tokens
  • 100Running it twice. No mutating operations

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 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 20 items

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

External checks

ClawHub: suspicious
This skill has a coherent daily-retrospective purpose, but it asks to read private session history, persist user and agent profiles, alter core agent memory files, and enable scheduled external reporting without enough consent or scoping.
LLM: suspicious (high) · VirusTotal: · 29 May 2026