juicebox-common-errors

Diagnose and fix Juicebox API errors. Trigger: "juicebox error", "fix juicebox", "debug juicebox".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

Actionable and well-stocked with concrete code and limits, but the body repeats error information across three overlapping sections and its external reference structure is broken: it points to a nonexistent bundle while the actual reference files go unlinked. Batch/error workflows also lack validation feedback loops.

Suggestions

Consolidate the Error Reference table, Debugging Guide, and Error Handling table into a single source of truth for each error code to remove restated causes/fixes and reduce token cost.

Fix the Next Steps pointer: replace the nonexistent "juicebox-debug-bundle" with explicit links to the real reference files (e.g. See [implementation.md](references/implementation.md) and [implementation-guide.md](references/implementation-guide.md)).

Add a short numbered diagnostic workflow with an explicit validate→fix→retry checkpoint, especially for batch operations like bulk search and dataset upload where quota/rate-limit recovery needs feedback.

Dimension	Reasoning	Score
Conciseness	The same error codes, causes, and fixes are restated across the Error Reference table, the Debugging Guide prose, and the Error Handling table (e.g. 401/403/429/408 each appear multiple times); mostly efficient but could be tightened by consolidating.	2 / 3
Actionability	It provides an executable TypeScript error classifier, a copy-paste curl diagnostic, and concrete numeric limits (30 req/min, 50MB, 100K rows, 60s timeout) with specific fixes per code, matching the fully-executable anchor.	3 / 3
Workflow Clarity	The skill is organized as reference material with scenario/recovery patterns but no clearly sequenced diagnostic workflow; batch operations (bulk search, dataset upload) lack explicit validate→fix→retry checkpoints, capping it at 2.	2 / 3
Progressive Disclosure	The body is sectioned, but its only pointer ("See juicebox-debug-bundle") names a bundle that does not exist, while the real reference files (implementation.md, implementation-guide.md) are never linked from the body; references present but not clearly signaled.	2 / 3
	Total	9 / 12 Passed

Description

90%

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 concise, third-person description with explicit trigger guidance and a clear, distinctive Juicebox niche. Its only weakness is that the capability statement is brief, naming only two actions rather than enumerating the concrete operations the skill supports.

Dimension	Reasoning	Score
Specificity	The description names the domain and two actions ("Diagnose and fix Juicebox API errors") but does not list multiple specific concrete actions like the score-3 anchor; it stays at the "names domain and some actions, not comprehensive" level.	2 / 3
Completeness	It states what the skill does ("Diagnose and fix Juicebox API errors") and provides explicit "when" guidance via the "Trigger:" clause, satisfying both halves required for a 3.	3 / 3
Trigger Term Quality	The explicit Trigger clause lists natural phrases a user would actually say ("juicebox error", "fix juicebox", "debug juicebox"), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The narrow Juicebox-specific domain with distinctive trigger terms makes it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
Commit: c89430d

Reviewed: 5 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.