CtrlK
BlogDocsLog inGet started
Tessl Logo

economy-mode

Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.

60

Quality

71%

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 ./.squad/skills/economy-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is highly actionable and well-sequenced with clear scope boundaries, scoring well on actionability, workflow clarity, and progressive disclosure; its only real weakness is repetitive restatement of the Layer 0/1/2 priority rule.

Suggestions

State the Layer 0/1/2 precedence rule once (e.g. in Context) and reference it from the spawn workflow and Anti-Patterns instead of repeating it three times.

Add a one-line verification check after writing/removing `economyMode` in `.squad/config.json` (e.g. re-read the file to confirm) to harden the config-mutation workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the Layer 0/1/2 priority rule is restated in the Context, the spawn workflow steps 1-3, and the Anti-Patterns section, so it could be tightened.

2 / 3

Actionability

Copy-paste-ready acknowledgment strings with emoji, an exact economy model selection table, precise config paths, and a concrete config schema JSON block give fully executable guidance.

3 / 3

Workflow Clarity

On Session Start, On User Phrase Trigger, On Every Agent Spawn, and On Deactivation are clearly numbered and sequenced, with a STOP section bounding scope; operations are state mutations rather than destructive/batch ops, so the absence of a validation loop does not cap the score.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the skill is single-purpose and organized into well-labeled sections (SCOPE, Activation Methods, table, workflow, Config Schema, Anti-Patterns) that are easy to navigate.

3 / 3

Total

11

/

12

Passed

Description

57%

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 and distinctive within its niche, but it states only one action and lacks an explicit "Use when..." trigger clause with natural cost-saving keywords, which caps both completeness and trigger quality at 2.

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when the user asks to save costs, reduce costs, or use economy mode for a session."

Surface the natural trigger phrases ("save costs", "go cheap", "reduce costs") from the body into the description to raise trigger-term coverage.

List a second concrete action (e.g. writing `economyMode: true` to config) to move specificity from one action to multiple.

DimensionReasoningScore

Specificity

"Shifts Layer 3 model selection to cost-optimized alternatives" names a clear domain and one concrete action, but does not list multiple specific actions as the score-3 anchor requires.

2 / 3

Completeness

The description states what it does and gives a state condition ("when economy mode is active"), but lacks an explicit "Use when..." trigger clause; per the guidelines a missing trigger clause caps completeness at 2.

2 / 3

Trigger Term Quality

"economy mode" is a natural term a user might say, but "cost-optimized alternatives" leans technical and common variations like "save costs", "reduce costs", or "go cheap" (which appear in the body) are missing from the description.

2 / 3

Distinctiveness Conflict Risk

"Layer 3 model selection" scoped to "economy mode" carves a clear niche with distinct triggers that is unlikely to overlap with unrelated skills.

3 / 3

Total

9

/

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
bradygaster/squad
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.