coderabbit-core-workflow-b
Execute CodeRabbit secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "coderabbit secondary workflow", "secondary task with coderabbit".
Overall
score
33%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill coderabbit-core-workflow-bActivation
15%This description fails to communicate any meaningful information about what the skill actually does. It relies entirely on placeholder-like terminology ('Core Workflow B', 'secondary use case') without describing concrete capabilities. The trigger terms are artificially constructed rather than reflecting natural user language.
Suggestions
Replace abstract terms like 'Core Workflow B' and 'secondary use case' with specific, concrete actions the skill performs (e.g., 'Generates code review summaries', 'Analyzes pull request comments').
Add natural trigger terms that describe the actual domain and operations, such as specific file types, programming concepts, or user goals this skill addresses.
Rewrite the 'Use when' clause to reference observable user needs or requests rather than internal workflow concepts (e.g., 'Use when user asks for code review feedback' instead of 'complementing primary workflow').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'secondary workflow', 'secondary use case', and 'complementing primary workflow' without describing any concrete actions or capabilities. No specific operations are mentioned. | 1 / 3 |
Completeness | The 'what' is essentially missing - 'Core Workflow B' and 'secondary use case' provide no meaningful information about capabilities. While there is a 'Use when' clause, it references undefined concepts ('secondary use case', 'primary workflow') making it ineffective. | 1 / 3 |
Trigger Term Quality | Includes some trigger phrases like 'coderabbit secondary workflow' and 'secondary task with coderabbit', but these are artificial constructs rather than natural terms users would say. Missing any domain-specific keywords that describe actual functionality. | 2 / 3 |
Distinctiveness Conflict Risk | Extremely generic terms like 'secondary workflow' and 'complementing primary workflow' could apply to virtually any skill. Without describing actual functionality, there's no way to distinguish this from other CodeRabbit or workflow-related skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
22%This skill is essentially a template or skeleton with no actionable content. All code blocks are empty placeholders, making it impossible for Claude to execute any workflow. The structure suggests good intentions but delivers no concrete guidance, examples, or executable code.
Suggestions
Replace all placeholder code comments with actual executable TypeScript code showing real CodeRabbit API calls and operations
Add concrete validation steps between workflow stages (e.g., 'Verify API response status before proceeding to Step 2')
Include at least one complete, copy-paste ready example with real input/output values
Transform the Error Handling section from a comparison table into actual error handling code with specific error types and recovery strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured but includes placeholder comments instead of actual code, and some sections like the comparison table add little value. The prerequisites and overview are brief but the empty code blocks waste tokens. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code. Claude cannot perform any concrete action from this skill - it describes structure without providing real instructions. | 1 / 3 |
Workflow Clarity | While steps are numbered, they contain no actual content explaining what to do. There are no validation checkpoints, no feedback loops for error recovery, and the 'Error Handling' section is just a comparison table with no actual error handling guidance. | 1 / 3 |
Progressive Disclosure | The structure with sections and references to other skills (coderabbit-install-auth, coderabbit-common-errors) is reasonable, but the external documentation links and cross-references don't compensate for the lack of substantive content in the main file. | 2 / 3 |
Total | 6 / 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.