CtrlK
BlogDocsLog inGet started
Tessl Logo

behavioral-modes

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

56

1.10x
Quality

34%

Does it follow best practices?

Impact

96%

1.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/behavioral-modes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

42%

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 names seven operational modes but fails to explain what each mode concretely does or when Claude should select this skill versus others. The trigger terms are too generic and would likely cause conflicts with many other skills. The 'when' clause is present but too vague to be actionable for skill selection.

Suggestions

Add explicit trigger guidance, e.g., 'Use when the user asks to switch modes, change operational style, or says terms like "brainstorm mode", "let's debug", "review mode", or "ship it".'

Clarify what makes this skill distinct from general coding/debugging/review skills—emphasize that it's about switching Claude's behavioral approach or workflow style, not performing those tasks directly.

Briefly describe what each mode does concretely (e.g., 'brainstorm: generates many ideas without filtering; debug: systematically isolates root causes') to improve specificity.

DimensionReasoningScore

Specificity

Lists seven named operational modes (brainstorm, implement, debug, review, teach, ship, orchestrate), which gives some specificity, but doesn't describe what concrete actions each mode entails—they are labels rather than detailed capabilities.

2 / 3

Completeness

The 'what' is partially addressed (operational modes) and there is a 'Use to...' clause, but the 'when' guidance ('adapt behavior based on task type') is vague and doesn't provide explicit trigger conditions. It doesn't clearly tell Claude when to select this skill over others.

2 / 3

Trigger Term Quality

Includes some natural keywords like 'brainstorm', 'debug', 'review', and 'implement' that users might say, but these are extremely common terms that overlap with many other skills. Missing natural phrases users would actually say like 'change your approach', 'switch mode', or 'act as'.

2 / 3

Distinctiveness Conflict Risk

Terms like 'debug', 'review', 'implement', and 'brainstorm' are extremely generic and would conflict with virtually any coding, writing, or problem-solving skill. The description lacks a clear niche that distinguishes it from other skills.

1 / 3

Total

7

/

12

Passed

Implementation

27%

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

This skill suffers from significant verbosity, explaining behavioral patterns that Claude already understands natively (how to brainstorm, debug, review code). The output templates are largely redundant with Claude's existing capabilities. The multi-agent section adds incomplete, vague content (empty 'Combining Modes' header, undefined 'Mental Model Sync'), and the entire document would benefit from being dramatically condensed to only the non-obvious constraints and preferences.

Suggestions

Reduce to ~30-40 lines focusing only on non-obvious behavioral constraints (e.g., 'IMPLEMENT: no tutorial explanations, no verbose comments' is useful; 'BRAINSTORM: ask clarifying questions' is not).

Remove or complete the empty 'Combining Modes' section and flesh out the Multi-Agent section with concrete, actionable instructions or remove it entirely.

Split detailed mode definitions into separate reference files (e.g., modes/implement.md) and keep SKILL.md as a concise overview with the trigger table and one-line mode summaries.

Add a concrete link or path for the referenced 'clean-code skill' in IMPLEMENT mode, and remove generic behavioral descriptions that Claude already follows by default.

DimensionReasoningScore

Conciseness

The skill is excessively verbose at ~180 lines, with significant padding. It explains concepts Claude already understands (what brainstorming is, what debugging is, how to review code). The output style templates are largely things Claude can already do without instruction. The 'Multi-Agent Collaboration Patterns' section adds vague content with no actionable detail. The 'Combining Modes' section is an empty header.

1 / 3

Actionability

The mode definitions provide some concrete guidance through output templates and trigger tables, but most content is descriptive rather than instructive. There are no executable code examples, no specific commands, and the multi-agent section (EXPLORE, PEC, MENTAL MODEL SYNC) is particularly vague with no concrete implementation details. The '/brainstorm' command syntax is shown but never explained how it integrates.

2 / 3

Workflow Clarity

The mode detection table provides a clear trigger-to-mode mapping, and the PEC pattern outlines a sequence (Plan→Execute→Critic). However, there are no validation checkpoints, no feedback loops for mode transitions, and the 'Combining Modes' section is completely empty despite being a critical workflow concern. The SHIP mode checklist is good but lacks verification steps.

2 / 3

Progressive Disclosure

The content is a monolithic wall of text with no references to external files. All seven modes plus multi-agent patterns are fully inline. The 'Combining Modes' section is an empty header. There's a reference to 'clean-code skill' in IMPLEMENT mode but no link. Content would benefit greatly from splitting mode details into separate files with a concise overview.

1 / 3

Total

6

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
sickn33/antigravity-awesome-skills
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.