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 findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/behavioral-modes/SKILL.md

The canonical home for this skill is behavioral-modes in sickn33/antigravity-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

27%Scale 1-3

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

This skill attempts to define comprehensive behavioral modes but suffers from significant verbosity, explaining standard AI behaviors that Claude already knows (how to brainstorm, debug, review code). The content is more descriptive than actionable—it tells Claude to behave in ways it largely already would, without providing novel tooling, commands, or concrete workflows. The monolithic structure with empty sections ('Combining Modes') and underdeveloped additions (multi-agent patterns) further weaken the skill.

Suggestions

Drastically reduce content by removing descriptions of behaviors Claude already exhibits (e.g., 'ask clarifying questions', 'think systematically') and focus only on project-specific conventions or non-obvious output formats.

Split each mode into its own referenced file (e.g., modes/brainstorm.md, modes/implement.md) with SKILL.md serving as a concise index with the mode detection table and links.

Fill in the empty 'Combining Modes' section or remove it—empty sections signal incomplete content.

Add concrete, actionable integration points: specific tool calls, file paths, or commands that Claude should use in each mode rather than generic behavioral descriptions.

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 lengthy and largely describe standard AI behavior patterns that don't need explicit instruction. The multi-agent section adds content with minimal actionable value.

1 / 3

Actionability

The mode definitions provide some concrete guidance through output templates and trigger keywords, but the content is largely descriptive rather than executable. There are no actual commands, code, or tool integrations—just behavioral descriptions and formatting templates. The 'Combining Modes' section is completely empty, and the multi-agent patterns lack concrete implementation details.

2 / 3

Workflow Clarity

The mode detection table and manual switching commands provide a clear entry point, and the PEC pattern outlines a sequence. However, there's no guidance on transitioning between modes, no validation checkpoints, and the 'Combining Modes' section is empty despite being a header. The workflow for how modes interact or when to switch is missing.

2 / 3

Progressive Disclosure

All content is inlined in a single monolithic file with no references to external files for detailed mode specifications. The IMPLEMENT mode references a 'clean-code' skill but doesn't link to it. Seven distinct modes plus multi-agent patterns are all crammed into one document, making it a wall of text that would benefit greatly from splitting into separate files per mode.

1 / 3

Total

6

/

12

Passed

Description

42%Scale 1-3

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, making it more of a list of labels than actionable capabilities. The trigger terms are too generic and would likely conflict with many other skills. The 'when' clause is present but too vague to provide meaningful selection guidance.

Suggestions

Add a more explicit 'Use when...' clause with specific trigger scenarios, e.g., 'Use when the user asks to switch working modes, change approach style, or explicitly requests brainstorm/implement/debug/review/teach/ship/orchestrate mode.'

Improve distinctiveness by framing this as a meta-skill for mode-switching rather than individual task execution, e.g., 'Configures Claude's operational mode and behavioral approach rather than performing the task itself.'

Add brief concrete descriptions of what each mode changes about behavior to increase specificity, e.g., 'brainstorm mode generates many ideas without filtering; debug mode systematically traces errors.'

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 remain abstract labels rather than concrete capabilities.

2 / 3

Completeness

The 'what' is partially addressed (AI operational modes) and there is a 'Use to...' clause, but 'adapt behavior based on task type' is vague and doesn't provide explicit trigger conditions. The 'when' is implied rather than clearly specified with concrete scenarios.

2 / 3

Trigger Term Quality

The mode names like 'brainstorm', 'debug', 'review' are natural terms users might say, but they are extremely common words that overlap with many other skills. Missing variations or contextual keywords that would help distinguish this skill (e.g., 'switch mode', 'working style', 'operational mode').

2 / 3

Distinctiveness Conflict Risk

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

1 / 3

Total

7

/

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
administrakt0r/AI-Agents-Safe-Coding-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.