juicebox-sdk-patterns

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

Quality

65%

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-sdk-patterns/SKILL.md

Quality

Content

68%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 executable, well-organized code, but it functions as a pattern catalog rather than a sequenced workflow and fails to surface the bundled reference files that exist alongside it. Linking the references and adding validation checkpoints would materially improve it.

Suggestions

Add explicit one-level-deep links to the existing bundle files, e.g. under Resources: 'See [advanced-patterns.md](references/advanced-patterns.md) and [implementation-guide.md](references/implementation-guide.md)' and fix the dangling 'Juicebox API Docs' entry.

Add a short sequenced workflow (e.g. build query -> search -> dedup by linkedin_url -> enrich -> handle 429/401) with an explicit validate/retry checkpoint so batch search pipelines have a feedback loop.

Trim the Overview's API description to essentials, leaving the endpoints' semantics to the code and the bundled implementation guide.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and mostly lean, assuming Claude's competence with TypeScript/fetch; only the Overview's brief API description is slightly over-explanatory, fitting 'efficient; minor instances of over-explanation that could be trimmed.'	4 / 5
Actionability	It provides complete, copy-paste-ready TypeScript for the singleton client, error wrapper, request builder, types, and mock utilities with a concrete usage example, matching 'fully executable; copy-paste ready code covering common cases.'	5 / 5
Workflow Clarity	Patterns are presented as a reference table rather than a sequenced workflow, and batch operations ('Batch search pipelines') are mentioned without validation checkpoints; per the batch-operation cap this cannot exceed 3, and it fits 'steps listed but validation gaps; checkpoints missing.'	3 / 5
Progressive Disclosure	The bundle ships references/advanced-patterns.md and references/implementation-guide.md, but neither file is linked or signaled in the body — the 'Resources' section only lists 'Juicebox API Docs' with no path — so structure is minimal and references are effectively buried, matching 'minimal structure; references are buried.'	2 / 5
	Total	14 / 20 Passed

Description

61%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 distinctive and provides an explicit trigger clause, but it is thin on concrete capabilities and narrow in its trigger-term coverage. Broadening the action list and trigger synonyms would lift specificity and trigger quality.

Suggestions

Replace the generic 'Apply production Juicebox SDK patterns' with concrete actions, e.g. 'Search professional profiles, enrich candidates via LinkedIn URL, and handle rate limits and pagination with the Juicebox SDK.'

Expand the Trigger clause with natural synonyms users might say, such as 'juicebox candidate search', 'people search API', or 'juicebox enrichment'.

Keep the explicit 'Use when...' / Trigger structure but tie the triggers to the specific actions listed so the 'what' and 'when' reinforce each other.

Dimension	Reasoning	Score
Specificity	The phrase 'Apply production Juicebox SDK patterns' names the domain but the only action ('apply patterns') is generic and minimal, matching the 'names the domain but actions are minimal or generic' anchor; it does not list concrete actions like search/enrich/dedup to reach a 3.	2 / 5
Completeness	It states a clear 'what' ('Apply production Juicebox SDK patterns') and an explicit 'when' via the Trigger clause, but the 'what' is thin and the when is a narrow pair of phrases rather than comprehensive, so it lands at 'both present, when could be more specific' rather than a 5.	4 / 5
Trigger Term Quality	The Trigger clause offers 'juicebox patterns' and 'juicebox best practices', which are natural phrases, but coverage is narrow — only two near-synonymous terms with no broader variations, fitting 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	'Juicebox SDK patterns' plus product-specific trigger phrases carve out a clear, narrow niche with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	14 / 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-sdk-patterns/SKILL.md
Commit: 0540a62

Reviewed: 1 day 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.