juicebox-core-workflow-a
Execute Juicebox people search with power filters and ATS export. Trigger: "find candidates", "people search", "juicebox search".
83
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 concise and functional description that clearly identifies the tool (Juicebox), the domain (people search), and provides explicit trigger terms. Its main weakness is that the capabilities could be more specific—listing concrete actions like filtering by role, location, or company, or describing what ATS export entails would strengthen it. Overall it performs well for skill selection purposes.
Suggestions
Expand the capability list with more specific actions, e.g., 'filter candidates by role, location, company, and skills' to improve specificity.
Consider adding more trigger term variations such as 'recruiting', 'sourcing candidates', 'talent search', or 'applicant tracking' to capture broader user intent.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Juicebox people search) and mentions some actions (power filters, ATS export), but doesn't elaborate on what specific actions are performed beyond these brief mentions. | 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 is present and explicit. | 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. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct due to the specific product name 'Juicebox' and the niche of people search with ATS export. Unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized and concise, with a clear three-step workflow and useful error handling table. However, the code examples feel like plausible pseudocode rather than verified executable snippets against a real SDK, and the workflow lacks validation checkpoints between steps (e.g., verifying search returned adequate results before scoring, confirming export success).
Suggestions
Add a validation checkpoint between Step 1 and Step 2 (e.g., check result count, handle empty results) and after Step 3 (e.g., confirm export status).
Clarify whether the TypeScript code uses an actual Juicebox SDK or is illustrative pseudocode; if a real SDK exists, reference the exact package name and import.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. No unnecessary explanations of what Juicebox is or how APIs work. Every section delivers actionable content without padding. | 3 / 3 |
Actionability | The code examples are concrete and illustrative, but they appear to be pseudocode against an assumed client API rather than verified executable code. The `client.search()` and `client.export()` methods reference an API shape that may not match the actual Juicebox SDK, making them not truly copy-paste ready. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced (search → score → export), but there are no validation checkpoints. No verification that the export succeeded, no check on result quality before exporting, and no feedback loop for handling the error cases listed in the table. | 2 / 3 |
Progressive Disclosure | Content is well-structured with a clear overview, sequential steps, an error handling table, external resource links, and a pointer to the next workflow. For a skill of this size, the organization is appropriate with one-level-deep references. | 3 / 3 |
Total | 10 / 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
c8a915c
- 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.