CtrlK
BlogDocsLog inGet started
Tessl Logo

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

70

Quality

85%

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

77%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 content is highly actionable and workflow-clear with concrete project-specific guidance and validation checkpoints. Its main weaknesses are repeated restatements of PR-table learnings across sections and a lack of progressive disclosure for a long, monolithic document.

Suggestions

Extract the PR precedence/lineage table into a references file (e.g. references/pr-lineage.md) and link to it one level deep, leaving only the precedence rule and the latest superseding PR inline.

De-duplicate guidance that appears in both the PR table and later sections (gaze coalescing #329121, double-buffering #327588, #330399) — state each rule once and cross-reference.

Consider splitting the runtime-wiring 13-step checklist and the validation checklist into a reference file so the SKILL.md body stays a lean overview.

DimensionReasoningScore

Conciseness

The body is dense and project-specific with no basic-concept padding, but PR-table durable learnings are restated in later sections (#329121 gaze coalescing, #330399 three times, #327588 double-buffer), creating avoidable duplication.

3 / 5

Actionability

Highly concrete instruction-only guidance — exact file paths, named functions (doesChatPetStateTrackCursor, getChatPetSpriteName, getSpriteSources), naming conventions, dimensions, CSS properties, and a 13-step runtime-wiring checklist; absence of code is justified for an art skill.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced (13-step runtime wiring) with a tri-section validation checklist containing explicit verify/run-tests checkpoints; not a destructive or batch operation so no cap applies.

5 / 5

Progressive Disclosure

No bundle files exist and the ~340-line body is a monolith with good headers but no reference-file split; the inlined 16-row PR lineage table is reference material that would benefit from a one-level-deep separate file. The under-50-line simple-skill exception does not apply.

3 / 5

Total

16

/

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.

The description is specific, complete, and highly distinct, clearly stating both what the skill does and when to use it with concrete trigger terms. It could be marginally improved with file-extension triggers, but otherwise earns top marks.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions' — giving comprehensive coverage of the domain's concrete objects.

5 / 5

Completeness

Explicitly answers both 'what' (creating/changing the enumerated art) and 'when' ('Use when creating or changing…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage with synonyms ('sprite art'/'sprite sheets', 'Stable/Insiders variants') and an explicit 'Use when' trigger, but lacks file extensions and a few common variations, stopping short of fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

Pinned to a single narrow niche — VS Code chat pet sprites under a specific repo path — with distinct triggers and minimal overlap risk.

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
posit-dev/positron
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.