SKILLEMALL.ai

AB cm-bug-bash-facilitator

Plan, run, and debrief a structured pre-release bug bash session. Defines scope (areas, devices, user roles), invites the right participant mix (eng/PM/design/CS/sales), generates exploratory test charters, runs in-session severity triage, post-session de-duplication, fix prioritization, and the retro. Use when asked to organize a bug bash, run a pre-launch test sprint, set up a hackathon-style QA day, write test charters, triage bugs across teams, or build a bug intake form. Triggers on "bug bash", "bug hunt", "test sprint", "exploratory testing", "test charter", "session-based testing", "pre-release QA", "release readiness", "triage session", "go/no-go review".

ClawHub Agent Skills author: charlie-morrison v1.0.0 MIT-0 2 files body ≈ 5 090 tokens Open the sourceclawhub.ai analyzed 3 d ago

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

AnalyzerOperations and projectsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
93/100
safety, quality, tests
Safety 60%
100
Quality 40%
82
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
Running it twice w 4
30
Consistency w 8
40
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5090 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 67/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 30Running it twice. 10 mutating operations with no state check
  • 40Consistency. Frontmatter name (cm-bug-bash-facilitator) differs from the folder (bug-bash-facilitator)
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 70Execution cost. Instruction body is 5090 tokens
  • 100Steps. 44 steps
  • 100When it triggers. States when to use and when not to
  • 100Failures and branches. 4 branches, has a failure section
  • 100Progress reporting. Reports progress

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

  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +5Description quotes 10 example trigger phrases
  • +3Description length 671: enough signal without eating the budget
  • +4Structure: 26 headings
  • +3Step-by-step instructions: 44 items
  • +3Output format is stated explicitly
  • +4Has examples (9 code blocks)

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

External checks

ClawHub: clean
This is an instruction-only bug-bash planning skill with no code execution, credential handling, persistence, or hidden behavior.
LLM: benign (high) · VirusTotal: · 29 May 2026