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.

43

Quality

43%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/behavioral-modes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%Weight 40%Scale 1-3

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

The content over-explains response formatting Claude already knows and offers templates over executable guidance. Mode detection is clear but workflows lack checkpoints and one section is empty.

Suggestions

Strip the verbose output-style example dialogue and emoji templates; keep only the behavior directives that add information Claude does not already know.

Fill or remove the empty 'Combining Modes' section and add explicit validation/checkpoints where modes transition for risky operations.

Replace abstract directives ('Think systematically') with concrete, actionable steps the agent should actually perform in each mode.

DimensionReasoningScore

Conciseness

The body is padded with verbose output-style templates, emoji headers, and example dialogue that teach Claude response formatting it already knows, e.g., 'Let's explore this together. Here are some approaches...'.

1 / 3

Actionability

Behaviors are abstract directives ('Think systematically', 'Be thorough but constructive') with illustrative template blocks rather than executable commands or concrete code, leaving guidance incomplete.

2 / 3

Workflow Clarity

The Mode Detection table gives a clear trigger→mode sequence, but there are no validation checkpoints and the 'Combining Modes' section is an empty header with no content.

2 / 3

Progressive Disclosure

The skill is a single long monolithic file with no references or navigation aids; sections are organized but content that could be split (full output templates, multi-agent patterns) is inline.

2 / 3

Total

7

/

12

Passed

Description

52%Weight 40%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 is specific in enumerating modes but vague on when to use it and highly likely to conflict with narrower, dedicated skills. It reads as a generic behavioral overlay rather than a clearly bounded trigger.

Suggestions

Add an explicit 'Use when...' clause naming concrete user triggers (e.g., 'Use when the user asks to switch working style or explicitly requests brainstorm/debug/review mode').

Narrow the trigger language so it does not fire for ordinary coding, debugging, or review requests that dedicated skills already cover.

Reframe to third-person concrete actions tied to specific user phrasings rather than 'adapt behavior based on task type'.

DimensionReasoningScore

Specificity

Enumerates concrete modes ('brainstorm, implement, debug, review, teach, ship, orchestrate'), listing multiple specific actions rather than vague language.

3 / 3

Completeness

It states what the skill does but lacks an explicit 'Use when...' trigger clause — 'when' is only implied via 'based on task type', which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

The clause 'Use to adapt behavior based on task type' is generic framing, not natural user keywords; the mode names are relevant but lack common user-said variations.

2 / 3

Distinctiveness Conflict Risk

The modes (debug, review, teach, implement) are broad and would conflict with many dedicated skills, and 'adapt behavior based on task type' is near-universal.

1 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

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.