CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/bug-bash-facilitator

Use when a team wants a coordinated bug bash before a release or after a big change instead of an ad-hoc 'everyone test for an hour'. Prepares the charter, data, environments and sign-up, runs roles, a shared board and live triage, scores findings and writes the same-day wrap-up.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable, well-sequenced facilitation playbook whose templates and anti-patterns make it immediately executable. Its weaknesses are mild verbosity in framing/example data and a monolithic structure with references that point at files outside this bundle, which hurts progressive disclosure.

Suggestions

Move the full pre-bash kit and debrief templates into references/ files (e.g., references/kit-template.md, references/debrief-template.md) and keep concise summaries inline in SKILL.md.

Fix the References section: references/tours.md and references/debrief.md do not exist in this bundle, so either bundle copies of those files or rewrite the pointers to unambiguously name the owning skill (e.g., the exploratory-testing skill's files) instead of this-skill-relative paths.

Trim the Overview's unfacilitated-vs-facilitated contrast and the dummy tally rows in the debrief example to cut tokens without losing the template shapes.

DimensionReasoningScore

Conciseness

The body is dense and template-driven with almost no conceptual padding Claude would already know, but the Overview's unfacilitated-vs-facilitated contrast and dummy illustrative rows (e.g., "Alice (BUG-987 high + 2 cluster lead bonuses)") are minor over-explanation that could be trimmed.

4 / 5

Actionability

Fully copy-paste-ready guidance for an instruction-only skill: the pre-bash kit markdown, minute-by-minute in-bash schedule, board schema with a five-value triage taxonomy, points table, debrief template, and async mini-charter cover the common cases end to end.

5 / 5

Workflow Clarity

Steps are explicitly sequenced with timings (1 week before, 14:00-15:30 schedule, debrief within 24 hours) and include checkpoints and feedback loops: a "do BEFORE the bash" prep checklist, the mid-bash huddle, real-time triage, and a retrospective ("What to change for next bash").

5 / 5

Progressive Disclosure

Sections are clearly organized, but the ~250-line body inlines full templates (kit, debrief) that belong in separate reference files, and the References section cites "references/tours.md" and "references/debrief.md" which do not exist in this bundle (no references/ directory), leaving navigation dangling.

3 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it explicitly states both what the skill does (charter/data/environment prep, live triage, scoring, wrap-up) and when to use it (coordinated team bug bash before a release or after a big change), in third person with concrete actions. The only weakness is modest synonym coverage for trigger terms.

DimensionReasoningScore

Specificity

"Prepares the charter, data, environments and sign-up", "runs ... a shared board and live triage", "scores findings and writes the same-day wrap-up" are multiple concrete verb+object actions covering the full facilitation lifecycle with no notable coverage gaps, matching the comprehensive-actions anchor.

5 / 5

Completeness

An explicit "Use when a team wants a coordinated bug bash before a release or after a big change" clause answers 'when' with concrete triggers, and the enumerated preparation/run/scoring/wrap-up actions answer 'what', all in third-person voice.

5 / 5

Trigger Term Quality

Natural phrases like "bug bash", "before a release", "after a big change", and "coordinated" are all present and would be said by users, but common synonyms ("bug hunt", "test sprint", "pre-release testing") are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

"Coordinated bug bash" at team scale is a clear niche trigger that is itself the differentiator from generic testing or single-tester exploratory skills, so wrong-skill triggering risk is minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page