behavioral-modes
tessl i github:sickn33/antigravity-awesome-skills --skill behavioral-modesAI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.
Validation
75%| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 12 / 16 Passed | |
Implementation
50%This skill provides a useful framework for behavioral modes with clear trigger patterns and output templates. However, it suffers from incomplete sections (Combining Modes is empty), lacks executable examples, and mixes basic single-agent modes with advanced multi-agent patterns without clear separation. The content would benefit from tighter focus and validation checkpoints for mode transitions.
Suggestions
Complete the empty 'Combining Modes' section or remove it - incomplete sections reduce trust in the skill
Add explicit mode transition validation (e.g., 'Before switching from BRAINSTORM to IMPLEMENT, confirm user has selected an approach')
Move the Multi-Agent Collaboration Patterns to a separate MULTI-AGENT.md file and reference it, as it's a distinct advanced topic
Replace descriptive output templates with actual executable examples showing Claude responding in each mode
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary verbosity (e.g., explaining what each mode is 'for' when the trigger table already covers this), but overall maintains reasonable efficiency. The output style examples are helpful but could be more condensed. | 2 / 3 |
Actionability | Provides concrete output templates and trigger patterns, but lacks executable code examples. The guidance is more descriptive than prescriptive - tells Claude what behavior looks like rather than providing copy-paste ready implementations. | 2 / 3 |
Workflow Clarity | The PEC (Plan-Execute-Critic) pattern shows good workflow thinking, but most modes lack explicit validation checkpoints. The 'Combining Modes' section is empty, and there's no guidance on when/how to transition between modes during a task. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections per mode, but it's a monolithic file with no references to external documentation. The Multi-Agent section feels tacked on and could be a separate file. The empty 'Combining Modes' section suggests incomplete structure. | 2 / 3 |
Total | 8 / 12 Passed |
Activation
50%The description identifies a clear concept (operational modes) and lists the available modes, which provides some specificity. However, it lacks concrete explanations of what each mode does, explicit trigger guidance for when Claude should select this skill, and natural language variations users might use. The description is functional but would benefit from more detail to help Claude distinguish when to use this meta-skill versus task-specific skills.
Suggestions
Expand the 'Use when...' clause with explicit triggers like 'when user asks to switch modes, change approach, or specifies a task type like brainstorming or debugging'
Add brief explanations of what each mode enables (e.g., 'brainstorm: generates multiple ideas without filtering; implement: focuses on working code')
Include natural language variations users might say, such as 'let's think through this', 'ship it', 'teach me how this works'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists seven specific operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate) which names the domain and actions, but doesn't explain what each mode actually does or what concrete behaviors they enable. | 2 / 3 |
Completeness | The 'what' is partially addressed (lists modes), and there's a brief 'when' clause ('Use to adapt behavior based on task type'), but the when guidance is vague and doesn't provide explicit triggers for when to select this skill. | 2 / 3 |
Trigger Term Quality | Includes some natural keywords like 'brainstorm', 'debug', 'review' that users might say, but missing common variations and natural phrases users would use (e.g., 'help me think through', 'fix this bug', 'code review'). | 2 / 3 |
Distinctiveness Conflict Risk | The concept of 'operational modes' is somewhat distinctive, but terms like 'debug', 'review', and 'implement' could easily overlap with dedicated debugging, code review, or implementation skills. | 2 / 3 |
Total | 8 / 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.