juicebox-sdk-patterns

Apply production Juicebox SDK patterns. Trigger: "juicebox patterns", "juicebox best practices".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

The body is concise and highly actionable with concrete TypeScript patterns, but it lacks a sequenced workflow with validation checkpoints and fails to point readers to the bundled reference files. Fixing navigation and adding verification steps would raise the two mid dimensions.

Suggestions

Add explicit links to the bundle files in the body (e.g. under an 'Advanced' or 'Resources' section: 'See [advanced-patterns.md](references/advanced-patterns.md) for pagination and the Result monad; see [implementation-guide.md](references/implementation-guide.md) for retry and observability.') so the references are clearly signaled.

Move the long inline code that duplicates the reference files (e.g. the singleton/client detail) into those files and keep the body as a concise overview pointing to them.

Add a short sequenced workflow with validation checkpoints for batch operations, e.g. search -> dedupe by linkedin_url -> enrich -> verify credits_remaining/handling, so workflow_clarity can exceed 2.

Make the 'Resources' section useful by linking the real API docs URL (currently just 'Juicebox API Docs' with no link) and remove the dangling 'Next Steps' reference to the non-existent 'juicebox-core-workflow-a'.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, executable code with a brief, purposeful Overview and no re-explanation of concepts Claude already knows, matching 'lean and efficient; every token earns its place'; it is not score 2 because there is no padded explanation to tighten.	3 / 3
Actionability	Concrete, executable TypeScript is provided throughout (singleton client, error wrapper, search builder with a usage line, response types, mock factories), matching 'fully executable code/commands; copy-paste ready'; it is above score 2 because the examples are complete rather than pseudocode.	3 / 3
Workflow Clarity	Patterns are catalogued (Error Handling table, retry-on-429 backoff) but there is no sequenced multi-step workflow with validation checkpoints for batch operations like pagination and multi-query dedup, which caps clarity at 2; it is above score 1 because steps/patterns are listed and a retry feedback loop is present.	2 / 3
Progressive Disclosure	Two reference files exist (advanced-patterns.md, implementation-guide.md) but neither is linked or signaled in the body, and inline body content overlaps what those files hold, matching 'references present but not clearly signaled; content that should be separate is inline'; it is above score 1 because references are only one level deep and the body is sectioned, not a monolithic wall.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 distinctive and answers both what and when with an explicit trigger clause, but its capability statement is vague and its trigger coverage is narrow. Strengthening the action list and broadening trigger terms would lift the two mid dimensions.

Suggestions

Replace the single abstract verb 'Apply ... patterns' with multiple concrete actions (e.g. 'Search professional profiles, enrich candidate data, deduplicate by LinkedIn URL, and handle rate limits').

Broaden the Trigger clause with natural variations a user would actually say, such as 'juicebox search', 'juicebox candidate search', 'juicebox people search', or 'juicebox API'.

Lead with a 'Use when ...' sentence that ties the actions to the triggers, making the when-condition as explicit as the what-condition.

Dimension	Reasoning	Score
Specificity	Quotes 'Apply production Juicebox SDK patterns.' name the domain and a single action, matching the 'names domain and some actions, but not comprehensive' anchor; it is not score 1 because a concrete domain is named, and not score 3 because 'patterns' is one abstract action rather than multiple specific ones.	2 / 3
Completeness	It states what ('Apply production Juicebox SDK patterns') and gives explicit when guidance ('Trigger: ...'), satisfying 'clearly answers both what AND when with explicit triggers'; it is above score 2 because the trigger clause is explicit rather than implied.	3 / 3
Trigger Term Quality	Trigger phrases 'juicebox patterns' and 'juicebox best practices' are relevant but narrow and near-synonymous, fitting 'some relevant keywords but missing common variations'; it falls short of score 3's broad coverage and beats score 1 because the terms are user-sayable, not jargon.	2 / 3
Distinctiveness Conflict Risk	'Juicebox SDK' is a clearly named niche with distinct triggers, matching 'clear niche with distinct triggers; unlikely to conflict'; it is above score 2 because the product specificity removes real overlap with other skills.	3 / 3
	Total	10 / 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: 1628598

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