SKILLEMALL.ai

BB council

Send an idea to the Council of the Wise for multi-perspective feedback. Spawns sub-agents to analyze from multiple expert perspectives. Auto-discovers agent personas from agents/ folder.

sundial-org/awesome-openclaw-skills Agent Skills author: sundial-org 7 files body ≈ 928 tokens Open the sourcegithub.com analyzed 2 d ago

Send an idea to the Council of the Wise for multi-perspective feedback.

As a process B 75/100 · Nearly there — weak spots: inputs and preconditions, progress reporting

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
98
Quality 40%
70
Run on models
none yet
Process rating
B
75/100
Nearly there
Inputs and preconditions w 11
0
Progress reporting w 2
0
Failures and branches w 10
55
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 README.md:43
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)
    > Send this to the council: I'm building a CLI tool that uses AI to help with bug bounty hunting — automated recon, AI-assisted analysis, human-in-the-loop for key decisions. Target: HackerOne program
    quoted
  • low Risky intent intent-offensive-security README.md:47
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
    ## 🏛️ Council of the Wise — AI Bug Bounty Tool

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")
  • note frontmatter-key unknown frontmatter key "credits"

Process rating: all ten parameters 75/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 55Failures and branches. 1 branches
  • 60Result and completion. Output format stated, no completion criterion
  • 85Steps. 21 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 928 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)
  • -41 reference files, but SKILL.md never points to them: the model will not open them
  • +1No license
  • +2Single-language instructions
  • +3Description length 186: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 21 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)

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