CtrlK
BlogDocsLog inGet started
Tessl Logo

client-compatibility

Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces

56

Quality

64%

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-templates/skills/client-compatibility/SKILL.md

The canonical home for this skill is client-compatibility in bradygaster/squad

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

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

The body is well-structured, concise, and actionable with concrete parameter-level guidance and a useful degradation table. Minor gaps are pseudocode-style examples and the absence of any external reference files.

Suggestions

Replace `...` placeholders in the TypeScript examples with complete, copy-pasteable call sites so they score toward fully executable.

Consider moving the Feature Degradation Table or SQL Caveat into a reference file once the skill grows, to keep SKILL.md as a lean overview.

Add an explicit "verify subagent results" checkpoint after parallel fan-out to strengthen workflow clarity for batch-style spawning.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (e.g. "Drop `agent_type`", "Skip it"), with only minor instances of over-explanation such as "Do not apologize or explain the limitation", fitting score 4 rather than the fully-trimmed 5.

4 / 5

Actionability

Concrete drop/keep parameter lists and a degradation table give mostly executable guidance; code examples use `...` placeholders and comments rather than copy-paste-ready code, keeping it at 4 instead of 5.

4 / 5

Workflow Clarity

The detect-platform (CLI/VS Code/Fallback) -> adapt-spawning sequence is clear and the degradation table acts as a checklist; no explicit validation loop is present but adaptive spawning is not a destructive/batch data operation, so the cap-at-3 rule does not apply.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with no bundle directories, well-organized into Context/Patterns/Examples/Anti-Patterns; at ~85 lines it slightly exceeds the simple-skill 50-line threshold, so it sits at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 to a clear niche and uses third-person voice, but it lacks an explicit "Use when..." trigger clause and natural trigger phrases, which caps both completeness and trigger-term quality at the midpoint.

Suggestions

Append a "Use when..." clause naming concrete triggers, e.g. "Use when spawning agents across CLI, VS Code, JetBrains, or GitHub.com surfaces."

Add natural user-facing synonyms (e.g. "Copilot surfaces", "platform-specific spawning") to broaden trigger coverage.

List one or two more concrete actions (e.g. "detects available tools and switches spawning parameters") to lift specificity toward 4-5.

DimensionReasoningScore

Specificity

Names the domain ("Platform detection") and 1-2 actions ("detection", "adaptive spawning") but coverage is not comprehensive, matching the score-3 anchor; not minimal enough for 2 nor multi-action comprehensive enough for 4.

3 / 5

Completeness

It clearly states what the skill does ("Platform detection and adaptive spawning") but provides no explicit when/trigger guidance; the rubric caps completeness at 3 when a "Use when..." clause is missing.

3 / 5

Trigger Term Quality

"CLI" and "VS Code" are natural terms a user might say, but there is no "Use when..." clause and common variations/synonyms are missing, placing it at 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The niche (adaptive spawning across CLI/VS Code/other surfaces) is specific and mostly distinct with only minor overlap risk versus closely related orchestration skills, fitting the score-4 anchor better than the fully-distinct 5 or the broad 3.

4 / 5

Total

13

/

20

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.

Validation — 15 / 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.