client-compatibility

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

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/client-compatibility/SKILL.md

Quality

Content

50%

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

The content is operationally rich, well-structured, and free of concept-explaining padding, but it settles at 2 across dimensions due to table/bullet duplication, placeholder code examples, absent validation checkpoints, and a monolithic single-file layout.

Suggestions

Collapse the redundancy between the 'VS Code Spawn Adaptations' bullets and the 'Feature Degradation Table' so each fact appears once to improve conciseness.

Provide at least one complete, runnable spawn snippet (no '...' placeholders) and add a validation step such as confirming all subagent results returned before the coordinator proceeds.

Move the per-feature degradation detail into a referenced file (e.g. references/platform-matrix.md) and keep SKILL.md as a lean overview to support progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is information-dense with operational specifics and avoids explaining known concepts, but the VS Code adaptation bullets substantially restate the Feature Degradation Table (parallelism, model selection, scribe, launch table, read_agent), so it could be tightened.	2 / 3
Actionability	Concrete parameter names and explicit 'use X / drop Y' decision rules are given, but the TypeScript examples use '...' placeholders rather than complete copy-paste-ready code, fitting the 'incomplete / pseudocode-ish' anchor.	2 / 3
Workflow Clarity	A clear detection-then-spawn-then-collect sequence exists with a tie-break rule, but there are no validation or feedback checkpoints for the parallel/batch spawn operations, which the rubric says caps workflow clarity at 2.	2 / 3
Progressive Disclosure	The ~80-line body is well-sectioned (Context, Patterns, Examples, Anti-Patterns) with a useful table, but all content is inline with no one-level-deep references, and the degradation table / VS Code detail could be split out.	2 / 3
	Total	8 / 12 Passed

Description

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 conveys a specific niche (multi-surface adaptive agent spawning) but reads as an internal capability summary rather than a user-triggered skill description. It lacks a 'Use when...' clause and natural trigger keywords, which caps most dimensions at 2.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when spawning agents across CLI, VS Code, or other Copilot surfaces, or when platform-specific spawning behavior is needed.'

Reframe around natural user terms (e.g. 'spawning subagents', 'running agents in VS Code/CLI') rather than internal jargon like 'adaptive spawning' and 'platform detection'.

List the concrete actions the skill performs (detect surface, choose spawn tool, drop incompatible parameters) to lift specificity toward 3.

Dimension	Reasoning	Score
Specificity	Names the domain ('Platform detection') and a concrete action ('adaptive spawning') plus enumerates surfaces, but does not list multiple specific concrete actions, matching the 'names domain and some actions' anchor.	2 / 3
Completeness	It states what the skill does but provides no 'when should Claude use it' trigger clause; the rubric guideline caps completeness at 2 when the 'Use when...' clause is missing.	2 / 3
Trigger Term Quality	'CLI' and 'VS Code' are real surface terms, but 'platform detection' and 'adaptive spawning' are coordinator-internal jargon a user would not naturally say, and there is no 'Use when' trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	The multi-surface spawning niche is fairly specific and unlikely to conflict broadly, but it is framed as an internal capability rather than around distinct user-facing triggers.	2 / 3
	Total	8 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: bradygaster/squad
Path: .copilot/skills/client-compatibility/SKILL.md
Commit: e23dd92

Reviewed: about 22 hours 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.