groq-core-workflow-b
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill groq-core-workflow-bExecute Groq secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "groq secondary workflow", "secondary task with groq".
Validation
75%| 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 | |
Implementation
42%This skill has good structural organization and appropriate cross-references to related skills, but critically fails on actionability by providing only placeholder code comments instead of executable examples. The 'Error Handling' section is mislabeled (it's a comparison table) and the workflow lacks validation checkpoints for what appears to be an API-based operation.
Suggestions
Replace all placeholder comments (e.g., '// Step 1 implementation') with actual executable TypeScript code showing real Groq API calls
Rename or replace the 'Error Handling' section with actual error handling guidance, including common errors and recovery steps
Add validation checkpoints after API calls (e.g., 'Verify response status before proceeding')
Include at least one complete, copy-paste ready example with real Groq API usage patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes placeholder comments instead of actual code, and the comparison table in 'Error Handling' section doesn't actually explain error handling. Some sections add structure without substance. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code. Claude cannot follow these instructions because there are no concrete commands or real examples to execute. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Setup → Process → Complete), but there are no validation checkpoints, no feedback loops for error recovery, and the 'Error Handling' section is actually a comparison table rather than error handling guidance. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate references to related skills (groq-install-auth, groq-core-workflow-a, groq-common-errors), and external documentation links. Content is well-organized for a skill of this size. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
22%This description fails to communicate what the skill actually does, relying entirely on placeholder-like terms ('Core Workflow B', 'secondary use case') that provide no meaningful information. While it attempts to follow the structure of a good description with trigger phrases and a 'Use when' clause, the content is too abstract to enable Claude to make informed skill selection decisions.
Suggestions
Replace 'Core Workflow B' and 'secondary use case' with specific, concrete actions the skill performs (e.g., 'Processes audio transcriptions', 'Generates embeddings for search').
Add natural trigger terms users would actually say when needing this functionality, based on the real tasks it accomplishes.
Rewrite the 'Use when' clause to describe actual scenarios or user requests that should trigger this skill, not abstract workflow relationships.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'Core Workflow B' and 'secondary use case' without describing any concrete actions. There is no indication of what the workflow actually does. | 1 / 3 |
Completeness | The 'what' is essentially missing - 'Core Workflow B' and 'secondary use case' tell us nothing about actual functionality. While there is a 'Use when' clause, it references undefined concepts making it ineffective. | 1 / 3 |
Trigger Term Quality | Includes some trigger phrases like 'groq secondary workflow' and 'secondary task with groq', but these are artificial constructs rather than natural terms users would say. 'Groq' is mentioned but no natural task-related keywords are provided. | 2 / 3 |
Distinctiveness Conflict Risk | The 'groq' keyword provides some distinctiveness, but 'secondary workflow' is generic and could conflict with any other secondary/complementary skill. Without knowing what it does, overlap risk is hard to assess but likely moderate. | 2 / 3 |
Total | 6 / 12 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.