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:lchenrique/politron-ide --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, which provides some specificity. However, it lacks concrete explanations of what each mode does and provides only vague guidance on when to use the skill. The trigger terms are a mix of natural language and jargon, creating moderate overlap risk with other development-focused skills.

Suggestions

Expand the description to briefly explain what behavior changes each mode triggers (e.g., 'brainstorm: generates multiple ideas without filtering; debug: systematic error diagnosis')

Add explicit trigger guidance with natural phrases users would say, such as 'Use when user says let me brainstorm, help me debug, review my code, or teach me about...'

Clarify how this skill differs from task-specific skills (e.g., a dedicated debugging skill) to reduce conflict risk

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 'Use to...' clause, but 'adapt behavior based on task type' is vague and doesn't provide explicit trigger guidance for when to select this skill.	2 / 3
Trigger Term Quality	Includes some natural terms like 'brainstorm', 'debug', 'review' that users might say, but 'operational modes' is jargon and missing common variations like 'help me think through', 'fix this bug', 'check my code'.	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 keywords and output templates. However, it's verbose with template examples that could be condensed, lacks executable code, and has incomplete sections (Combining Modes is empty). The multi-agent collaboration section feels tacked on without clear integration into the main mode system.

Suggestions

Remove or significantly condense the 'Output style' template blocks - Claude can generate appropriate formats without verbose examples

Complete the empty 'Combining Modes' section or remove it entirely

Add a concrete example showing mode detection in action (e.g., user input → detected mode → behavioral change)

Link the referenced 'clean-code' skill properly or inline the essential standards

Dimension	Reasoning	Score
Conciseness	The skill contains some unnecessary verbosity in output style examples and explanations. The mode descriptions could be tighter - Claude doesn't need extensive 'Output style' templates for each mode, and some behavioral bullets are redundant.	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 to do conceptually but doesn't provide copy-paste ready implementations or specific commands.	2 / 3
Workflow Clarity	The PEC (Plan-Execute-Critic) pattern mentions a workflow but lacks explicit validation checkpoints. Mode detection table is clear, but there's no guidance on how to transition between modes or handle edge cases when multiple triggers are present.	2 / 3
Progressive Disclosure	Content is reasonably structured with clear sections per mode, but it's a monolithic document that could benefit from splitting detailed mode specifications into separate files. The 'Combining Modes' section is empty, and references to 'clean-code' skill aren't linked.	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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Reviewed: 11 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.