CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

vscode-review

Review fallow's VS Code extension behavior, activation, commands, views, downloads, and LSP-client integration. Use when changes touch editors/vscode.

73

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

A lean, well-structured dispatch skill with an unambiguous read → review → verdict workflow and an explicit output contract. Its weaknesses are that all review methodology is delegated to files not present in the bundle and no inline examples cover common review cases.

Suggestions

Inline a brief review checklist or example verdict output (e.g., 'CONCERN: activation event registered in package.json but not handled in extension.ts') so the skill stays actionable even when the referenced .agents files are unavailable.

Vendor the referenced agent and rules content into the skill bundle (e.g., references/vscode-reviewer.md and references/vscode-extension.md) and point the 'Read:' list at those paths, since the current .agents/ paths do not exist in the bundle.

DimensionReasoningScore

Conciseness

Every line is functional — a read list of exact paths, focus areas, and an output contract — with no explanations of concepts Claude already knows and nothing to trim.

5 / 5

Actionability

"Read:" provides exact file paths and "End with `APPROVE`, `CONCERN`, or `BLOCK`" provides exact output tokens, but the actual review methodology is fully delegated to files outside the skill and no inline examples cover the common cases.

4 / 5

Workflow Clarity

The sequence — read the two listed files, review with the stated focus ("extension UX, activation behavior, command wiring, and editor integration quality"), end with a verdict — is unambiguous; as a single-purpose, non-destructive review skill under 50 lines, the simple-skill exception applies and no validation checkpoints are needed.

5 / 5

Progressive Disclosure

References are clearly signaled in a "Read:" list and one level deep, but both targets (".agents/agents/vscode-reviewer.md", ".agents/rules/vscode-extension.md") point outside the skill bundle, which contains no files, leaving the skill non-self-contained.

4 / 5

Total

18

/

20

Passed

Description

92%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.

A strong description: it names the domain, enumerates concrete review areas, and provides an explicit path-based 'Use when' trigger, making it clearly distinct from other skills. The only gap is a few missing natural synonyms (e.g., 'language server', 'extension host').

DimensionReasoningScore

Specificity

Enumerates six concrete review areas — "behavior, activation, commands, views, downloads, and LSP-client integration" — giving comprehensive, specific coverage of the extension surface rather than vague language.

5 / 5

Completeness

Explicitly answers both what ("Review fallow's VS Code extension behavior, activation, commands, views, downloads, and LSP-client integration") and when ("Use when changes touch editors/vscode") with a concrete, specific trigger phrase.

5 / 5

Trigger Term Quality

"VS Code extension", "LSP-client", and the path trigger "editors/vscode" are natural terms a developer would use, but synonyms such as "language server" or "extension host" are missing, so coverage is good rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to "fallow's VS Code extension" with a path-specific trigger ("editors/vscode"), giving it a clear niche with minimal risk of triggering for the wrong skill.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fallow-rs/fallow

Path

.claude/skills/vscode-review/SKILL.md

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.