SKILLEMALL.ai
GitHub ↗ RU Sign in

BB project-brainstorming

Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.

athola/claude-night-market Hermes author: athola 3 files body ≈ 3 531 tokens Open the sourcegithub.com↗ analyzed 3 h ago

Guides project ideation via Socratic questioning to produce a validated brief.

As a process B 67/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
98
Quality 40%
76
Run on models
none yet
Process rating
B
67/100
Nearly there
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

How to improve

  1. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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

✓ No critical or high findings

Medium and low: 2
  • low Risky intent intent-offensive-security SKILL.md:215
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    - Red Team challenges for each approach
  • low Risky intent intent-offensive-security SKILL.md:318
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    [From Phase 3.5 - includes RS assessment, Red Team challenges, premortem]

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

Against the Agent Skills spec

  • warning description-long-hermes description is 134 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • note frontmatter-key unknown frontmatter key "alwaysApply"
  • note frontmatter-key unknown frontmatter key "complexity"
  • note frontmatter-key unknown frontmatter key "model_hint"
  • note frontmatter-key unknown frontmatter key "estimated_tokens"
  • note frontmatter-key unknown frontmatter key "progressive_loading"
  • note frontmatter-key unknown frontmatter key "dependencies"
  • note frontmatter-key unknown frontmatter key "role"

Process rating: all ten parameters 67/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
  • 30Running it twice. 5 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 85Steps. 116 steps, 2 vague phrases
  • 100Tools and files. No external tools needed
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3531 tokens
  • 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)
  • -230 emoji in the instructions: noise for the model
  • +1No license
  • +2Single-language instructions
  • +3Description length 134: enough signal without eating the budget
  • +4Structure: 23 headings
  • +3Step-by-step instructions: 116 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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