juicebox-core-workflow-a
Execute Juicebox people search with power filters and ATS export. Trigger: "find candidates", "people search", "juicebox search".
64
77%
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-a/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a reasonably strong description that clearly identifies the tool (Juicebox), the domain (people search/recruiting), and provides explicit trigger terms. Its main weakness is that the capability description could be more specific about what 'power filters' and 'ATS export' concretely involve. Overall it performs well for skill selection purposes.
Suggestions
Expand on specific capabilities: instead of 'power filters', list concrete filter types like 'filter by location, skills, experience level, company' to improve specificity.
Consider adding more trigger term variations such as 'recruiting', 'sourcing', 'talent search', 'applicant tracking' to capture broader user language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Juicebox people search) and mentions some actions (execute search, power filters, ATS export), but doesn't elaborate on what 'power filters' entails or list specific concrete actions beyond a high-level summary. | 2 / 3 |
Completeness | Clearly answers both 'what' (execute Juicebox people search with power filters and ATS export) and 'when' (explicit trigger terms listed). The 'Trigger:' clause serves as an explicit 'Use when' equivalent. | 3 / 3 |
Trigger Term Quality | Includes natural trigger terms users would say: 'find candidates', 'people search', 'juicebox search'. These are realistic phrases a user would use when needing this skill, covering both the tool name and the general action. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific tool name 'Juicebox' and the niche domain of people search with ATS export. Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a reasonably well-structured skill that provides a clear three-step workflow for Juicebox people search with concrete TypeScript examples. Its main weaknesses are the lack of client initialization/setup context, missing validation checkpoints between steps (especially before and after ATS export), and code that may be illustrative rather than truly executable against a real API.
Suggestions
Add client initialization code (import, authentication, instantiation) so the examples are truly copy-paste ready.
Add validation checkpoints: verify search result count before scoring, and confirm ATS export success with a status check or callback.
Clarify whether the scoring function is a built-in Juicebox feature or a custom utility, and if custom, note that explicitly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It jumps straight into executable code without explaining what Juicebox is, what candidate sourcing means, or other concepts Claude would already know. Every section earns its place. | 3 / 3 |
Actionability | The code examples are concrete and well-structured, but they rely on an unspecified `client` object with no setup/initialization shown. The API appears to be illustrative rather than verified—there's no import statement, no client instantiation, and the scoring function is a custom heuristic rather than a platform feature, which could confuse whether this is built-in or user-defined. | 2 / 3 |
Workflow Clarity | The three steps are clearly sequenced and logically ordered. However, there are no validation checkpoints—no verification that the search returned expected results before scoring, no confirmation that the ATS export succeeded, and no feedback loop for handling export failures or partial results. | 2 / 3 |
Progressive Disclosure | The skill references external docs and a follow-up skill (`juicebox-core-workflow-b`) for enrichment, which is good. However, with no bundle files provided, the reference to the next skill is unverifiable, and the inline content could benefit from separating the scoring logic or error handling into referenced files if the skill grows. | 2 / 3 |
Total | 9 / 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.