exa-core-workflow-b
Execute Exa secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "exa secondary workflow", "secondary task with exa".
Overall
score
34%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill exa-core-workflow-bActivation
7%This description fails to communicate what the skill actually does, relying entirely on placeholder terminology like 'Core Workflow B' and 'secondary use case.' The trigger phrases are artificial constructs rather than natural language users would employ. Without concrete actions or meaningful context, Claude cannot make informed decisions about when to select this skill.
Suggestions
Replace 'Core Workflow B' and 'secondary use case' with specific, concrete actions the skill performs (e.g., 'Searches web sources, retrieves citations, summarizes findings').
Add natural trigger terms users would actually say when needing this functionality, based on the real capabilities of the Exa secondary workflow.
Include a clear 'Use when...' clause that describes actual scenarios or user needs, not just the skill's internal naming convention.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'Core Workflow B' and 'secondary use case' without describing any concrete actions. There are no specific capabilities listed - only placeholder-style terminology. | 1 / 3 |
Completeness | While it attempts to answer 'when' with trigger phrases, the 'what' is completely missing - 'Core Workflow B' and 'secondary use case' provide no meaningful information about what the skill actually does. | 1 / 3 |
Trigger Term Quality | The trigger phrases 'exa secondary workflow' and 'secondary task with exa' are artificial and unlikely to be naturally spoken by users. No natural keywords describing actual functionality are present. | 1 / 3 |
Distinctiveness Conflict Risk | The 'exa' branding provides some distinctiveness, but 'secondary workflow' is generic enough to potentially conflict with other workflow-related skills. The lack of specific functionality makes it hard to distinguish from similar vague skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
30%This skill is essentially a template with no actual content - all code blocks are empty placeholders and the Error Handling section is mislabeled. While the structure and progressive disclosure are well-organized, the complete lack of actionable instructions makes this skill unusable in its current form.
Suggestions
Replace all placeholder comments with actual executable TypeScript code showing real Exa API calls and implementations
Add genuine error handling content - either replace the comparison table with actual error scenarios and recovery code, or move the table to a more appropriate section
Include concrete examples of inputs and expected outputs for each step to make the workflow actionable
Add validation checkpoints between steps (e.g., 'Verify API response status before proceeding to Step 2')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is reasonably lean, but the content is mostly placeholder comments rather than actual implementation. The comparison table in 'Error Handling' section is misplaced and doesn't actually cover error handling. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code, commands, or concrete guidance. Claude cannot act on these instructions. | 1 / 3 |
Workflow Clarity | While steps are numbered, they contain no actual content explaining what to do. No validation checkpoints exist, and the 'Error Handling' section is actually a comparison table, not error handling guidance. | 1 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate references to related skills (exa-install-auth, exa-core-workflow-a, exa-common-errors), and external documentation links. Navigation is straightforward. | 3 / 3 |
Total | 7 / 12 Passed |
Validation
75%Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
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.