juicebox-core-workflow-b
Execute Juicebox enrichment and outreach workflow. Trigger: "juicebox enrich", "candidate enrichment", "talent pool".
43
45%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/juicebox-pack/skills/juicebox-core-workflow-b/SKILL.mdQuality
Discovery
40%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 identifies a specific tool (Juicebox) and provides trigger terms, which is a good start. However, it lacks concrete actions describing what the skill actually does (e.g., enrich candidate profiles with contact info, send outreach sequences, build talent pools) and the trigger terms miss many natural user phrases related to recruiting and sourcing workflows.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Enriches candidate profiles with contact information, builds talent pools, and sends personalized outreach emails using Juicebox.'
Expand trigger terms to include natural user phrases like 'find candidates', 'sourcing', 'recruiting outreach', 'people search', 'contact enrichment'.
Rewrite the 'when' clause more explicitly, e.g., 'Use when the user needs to enrich candidate data, build talent pools, or run outreach campaigns through Juicebox.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Execute Juicebox enrichment and outreach workflow' which is vague — it names a domain (Juicebox) but doesn't list any concrete actions like what enrichment entails, what outreach steps are performed, or what outputs are produced. | 1 / 3 |
Completeness | It has a 'Trigger' clause which partially addresses 'when', and a brief 'what' statement, but the 'what' is too vague to be meaningful and the trigger terms don't fully explain when Claude should select this skill over others. | 2 / 3 |
Trigger Term Quality | It includes some relevant trigger terms ('juicebox enrich', 'candidate enrichment', 'talent pool') but misses common variations users might say like 'find candidates', 'sourcing', 'outreach emails', 'recruiting pipeline', or 'people search'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Juicebox' as a specific tool provides some distinctiveness, but 'enrichment and outreach workflow' is generic enough to overlap with other CRM, recruiting, or outreach-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill presents a well-structured multi-step workflow with concrete-looking TypeScript examples and a useful error handling table. However, the code examples appear to reference a fabricated or undocumented API surface, undermining true actionability. The workflow lacks validation checkpoints between steps and references bundle files that don't exist.
Suggestions
Clarify how to initialize the `client` object (authentication, SDK installation) or reference the actual Juicebox SDK documentation — currently the API methods appear invented.
Add validation checkpoints between steps, e.g., check that `query.results.length > 0` before running comparison, and verify export job status before using the download URL.
Either create the referenced bundle files (`juicebox-core-workflow-a`, `juicebox-sdk-patterns`) or remove the references to avoid dead links.
Trim the overview paragraph and output section — the code examples already demonstrate what the workflow produces.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary framing (e.g., the overview paragraph explaining what analysis is). The code examples are fairly lean, though the console.log formatting adds some bulk. The output section restates what's already obvious from the code examples. | 2 / 3 |
Actionability | The code examples look concrete and executable in form, but they rely on an unspecified `client` object with an undocumented API (`client.analysis.query`, `client.analysis.compare`, etc.) that appears fabricated — there's no evidence this is a real Juicebox SDK API. Without knowing how to initialize the client or whether these methods actually exist, the code is effectively pseudocode dressed up as TypeScript. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced and the error handling table is a nice addition. However, there are no validation checkpoints between steps — no verification that query results are non-empty before comparison, no check that export completed successfully, and no feedback loops for error recovery beyond the table. | 2 / 3 |
Progressive Disclosure | References to `juicebox-core-workflow-a` and `juicebox-sdk-patterns` are mentioned but no bundle files exist to support them. The content is reasonably structured with clear sections, but the inline code examples are lengthy and could benefit from being split into referenced files, especially given no bundle exists. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
a04d1a2
- Reviewed
Table of Contents
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.