behavioral-modes

AI operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate). Use to adapt behavior based on task type.

Install with Tessl CLI

npx tessl i github:sickn33/antigravity-awesome-skills --skill behavioral-modes

What are skills?

Review — 50%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear concept (operational modes) and lists the available modes, but lacks specificity about what each mode does and provides only vague guidance on when to use it. The trigger terms are reasonable but incomplete, and the description could easily conflict with more specific coding or review skills.

Suggestions

Expand the 'Use to...' clause into explicit 'Use when...' triggers, e.g., 'Use when user asks to brainstorm ideas, implement features, debug issues, review code, teach concepts, ship/deploy, or coordinate complex tasks.'

Add brief descriptions of what each mode enables, e.g., 'brainstorm (generate ideas freely), implement (write production code), debug (diagnose and fix issues)' to improve specificity.

Include common user phrasings and variations like 'fix bugs', 'code review', 'explain how', 'deploy', 'coordinate' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists seven named operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate) which are domain-specific actions, but doesn't explain what each mode actually does or what concrete behaviors they enable.	2 / 3
Completeness	The 'what' is partially addressed (AI operational modes), and there's a 'Use to...' clause, but 'adapt behavior based on task type' is vague and doesn't provide explicit trigger guidance for when Claude should select this skill.	2 / 3
Trigger Term Quality	Includes some natural keywords like 'brainstorm', 'debug', 'review', and 'implement' that users might say, but 'operational modes' is technical jargon and common variations like 'coding', 'fix bugs', 'explain', or 'deploy' are missing.	2 / 3
Distinctiveness Conflict Risk	The concept of 'operational modes' is somewhat distinctive, but terms like 'debug', 'review', and 'implement' could easily overlap with coding, code review, or debugging-specific skills.	2 / 3
	Total	8 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a useful framework for behavioral modes with clear trigger detection and output templates. However, it suffers from incomplete sections (Combining Modes is empty), lacks executable examples, and could be more concise. The multi-agent patterns section feels tacked on without integration into the main workflow.

Suggestions

Complete the empty 'Combining Modes' section or remove it to avoid confusion

Add executable code examples for at least one mode (e.g., a mermaid diagram example for BRAINSTORM mode)

Link to the referenced 'clean-code' skill explicitly with a file path

Consolidate the output style templates—consider moving detailed templates to a separate reference file and keeping only brief examples inline

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but includes some redundancy (e.g., repeated output style templates, verbose mode descriptions). The IMPLEMENT mode section appropriately warns against verbosity but the skill itself could be tighter.	2 / 3
Actionability	Provides concrete output templates and trigger keywords, but lacks executable code examples. The guidance is more descriptive than instructive—it tells Claude what behavior looks like rather than providing copy-paste commands or code.	2 / 3
Workflow Clarity	Mode detection table and PEC cycle provide some workflow structure, but transitions between modes lack explicit validation checkpoints. The 'Combining Modes' section is empty, leaving multi-mode workflows unclear.	2 / 3
Progressive Disclosure	Content is organized with clear headers and sections, but everything is inline in one file. References to 'clean-code skill' suggest external dependencies but no links are provided. The 'Combining Modes' section is empty, indicating incomplete structure.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.