juicebox-core-workflow-b
Execute Juicebox enrichment and outreach workflow. Trigger: "juicebox enrich", "candidate enrichment", "talent pool".
54
45%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
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 is too vague about what concrete actions the skill performs — it merely names a workflow without detailing steps or outputs. While it includes some trigger terms and the Juicebox brand name adds mild distinctiveness, the lack of specific capabilities and a proper 'Use when...' clause significantly weakens its utility for skill selection among many options.
Suggestions
List specific concrete actions the skill performs, e.g., 'Searches candidate profiles, enriches contact information (email, phone, LinkedIn), and sends personalized outreach sequences via Juicebox.'
Replace the 'Trigger:' keyword list with a proper 'Use when...' clause, e.g., 'Use when the user needs to enrich candidate profiles, build talent pools, or run outreach campaigns through Juicebox.'
Add more natural trigger term variations such as 'sourcing', 'recruiting pipeline', 'contact enrichment', 'outreach emails', or 'people search' to improve matching coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Execute Juicebox enrichment and outreach workflow' which is vague — it names a domain (Juicebox) but doesn't describe any concrete actions like what enrichment entails, what outreach steps are performed, or what outputs are produced. | 1 / 3 |
Completeness | It has a weak 'what' (execute enrichment and outreach workflow) and does include a 'Trigger' clause that partially serves as a 'when', but the trigger clause is just a keyword list rather than an explicit 'Use when...' statement explaining the circumstances for selection. | 2 / 3 |
Trigger Term Quality | It includes some relevant trigger terms ('juicebox enrich', 'candidate enrichment', 'talent pool') that a user might say, but coverage is limited — missing natural variations like 'sourcing', 'recruiting', 'outreach campaign', 'contact info', or 'people search'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Juicebox' provides some distinctiveness as a specific tool, but 'enrichment and outreach workflow' is generic enough that it could 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 provides a reasonable multi-step workflow with TypeScript code examples, but falls short on actionability because the code lacks initialization/setup context (no imports, no client setup). Workflow clarity suffers from missing validation between steps — enrichment results aren't checked before pool creation, and pool creation isn't verified before outreach launch. The content is moderately concise but could be tightened.
Suggestions
Add client initialization code (import, SDK package name, authentication setup) so the examples are truly executable end-to-end.
Add validation checkpoints between steps: verify enrichment results before pool creation, and confirm pool exists before launching outreach.
Remove the overview sentence since the step-by-step instructions already convey the workflow clearly.
Consider showing how to handle partial enrichment failures (e.g., filter out profiles with insufficient data before adding to pool).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary filler like the overview sentence restating what the steps already show. The error handling table and next steps section add minor bloat but aren't egregious. | 2 / 3 |
Actionability | The code examples look concrete but are not truly executable — they reference an undefined `client` object and `profiles` variable with no setup/initialization shown. There's no import, no client instantiation, and no indication of what SDK or package to use. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (enrich → pool → outreach), but there are no validation checkpoints. No verification that enrichment succeeded before creating the pool, no check that the pool was created before launching outreach, and no feedback loop for partial enrichment failures. | 2 / 3 |
Progressive Disclosure | There's a reference to external resources and a pointer to `juicebox-common-errors`, but the main content is all inline with no clear separation of quick-start vs. advanced usage. The error handling table could be in a separate reference file. | 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
3e83543
- 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.