juicebox-debug-bundle

Collect Juicebox debug evidence. Trigger: "juicebox debug", "juicebox support ticket".

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/juicebox-pack/skills/juicebox-debug-bundle/SKILL.md

Quality

Content

75%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 content is highly actionable with concrete executable code and a strong diagnostic table, but progressive disclosure is weak: the real reference file is orphaned and a referenced skill does not exist. Fixing navigation and reducing bash/TS redundancy would raise the score.

Suggestions

Link the existing references/implementation-guide.md from the body (e.g. under a 'Detailed implementation' section) and either create or remove the dangling `juicebox-common-errors` reference in Next Steps.

Move the TypeScript 'Automated Health Check' into the implementation guide (or drop it) to remove overlap with the bash collection script and tighten conciseness.

Add an explicit validation step to the workflow, e.g. after running the script, verify the .tar.gz contains summary.txt, quota.json, datasets.json before analyzing.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete code and a useful diagnostic table, but the 'Automated Health Check' TypeScript section substantially overlaps the bash script's health/quota checks and could be trimmed, fitting the 4-anchor for efficient-with-minor-over-explanation.	4 / 5
Actionability	It provides copy-paste-ready executable bash and TypeScript, specific jq analysis commands, and a symptom-to-fix table covering common cases, matching the 5-anchor for fully executable guidance.	5 / 5
Workflow Clarity	There is a clear sequence (collect bundle, extract, run analysis commands, consult the diagnostic table) and the Common Issues table acts as a diagnostic checkpoint, but there are no explicit validate-then-proceed feedback loops, matching the 4-anchor with minor validation gaps.	4 / 5
Progressive Disclosure	The existing bundle file references/implementation-guide.md is never linked from the body, while 'Next Steps' points to a non-existent juicebox-common-errors skill, and full scripts/TS are inlined rather than split out; this broken, buried navigation fits the 2-anchor better than the 3-anchor's merely-unclear signaling.	2 / 5
	Total	15 / 20 Passed

Description

77%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.

The description is well-structured with explicit trigger guidance and a distinct product niche, but the capability statement is thin and generic. Adding 1-2 concrete actions would lift specificity.

Suggestions

Name 1-2 concrete capabilities beyond 'collect', e.g. 'Collect Juicebox debug evidence: API connectivity, dataset health, quota usage, and rate-limit state into a diagnostic archive.'

Add a couple of natural trigger synonyms (e.g. 'juicebox not working', 'juicebox API error') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Juicebox debug') but offers only one minimal, generic action ('Collect Juicebox debug evidence') rather than enumerating concrete capabilities; it sits just below the 3-anchor which expects 1-2 concrete actions.	2 / 5
Completeness	It explicitly states what it does ('Collect Juicebox debug evidence') and provides explicit concrete trigger phrases ('Trigger: ...'), satisfying both what and when per the 5-anchor; the missing-'Use when' cap does not apply since explicit trigger guidance is present.	5 / 5
Trigger Term Quality	It lists two natural phrases a user would actually say ('juicebox debug', 'juicebox support ticket') with good coverage, though a few synonyms or variants are missing, matching the 4-anchor rather than the comprehensive 5-anchor.	4 / 5
Distinctiveness Conflict Risk	The product-specific 'Juicebox' niche combined with distinct trigger phrases gives minimal conflict risk with other skills, matching the 5-anchor for a clear niche.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/juicebox-pack/skills/juicebox-debug-bundle/SKILL.md
Commit: 8585d6d

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.