CtrlK
BlogDocsLog inGet started
Tessl Logo

auto-claude-setup

Complete Auto-Claude installation and setup guide for all platforms. Use when installing Auto-Claude on WSL, Windows, Linux, or macOS, setting up development environment, or troubleshooting installation issues.

69

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

The canonical home for this skill is auto-claude-setup in fernandezbaptiste/Skrillz

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, well-structured setup guide with concrete per-platform commands and a verification section. Its main weaknesses are cross-platform command repetition, pinned version strings, and References that bypass the local bundle files in favor of GitHub URLs.

Suggestions

Factor the repeated clone/cd/npm-install:all steps into a shared 'After prerequisites' block instead of repeating them under WSL, Windows, Linux, and macOS.

Point the References links at the local bundle (references/README.md, references/CONTRIBUTING.md) rather than the GitHub URLs, or note that the bundle mirrors those files.

Move the pinned 2.7.2 version strings into a single 'Current release' line so the download table does not hardcode time-sensitive versions throughout.

DimensionReasoningScore

Conciseness

The body is action-dense (tables and copy-paste commands) and avoids explaining concepts Claude already knows, but the clone/cd/npm-install:all block is repeated across four platform sections and pinned version strings (2.7.2) add time-sensitive tokens that could be tightened.

4 / 5

Actionability

Fully executable, copy-paste-ready commands for every platform (wsl --update, winget install, brew install, npm run install:all, claude setup-token) with concrete config examples covering the common cases.

5 / 5

Workflow Clarity

Steps are explicitly numbered per platform and a dedicated Verification section tests the install, but there is no validate-then-fix feedback loop; the sequence is clear enough that the gap is minor.

4 / 5

Progressive Disclosure

Well-organized into clear sections with a Related Skills and References block, but the References point to external GitHub URLs for README/CONTRIBUTING even though local copies exist in references/, a minor navigation gap.

4 / 5

Total

17

/

20

Passed

Description

87%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, third-person description that clearly answers both what the skill does and when to use it, with natural trigger terms and a distinct product-scoped niche. Minor additional action specificity would push it to full marks.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions — 'installation and setup', 'setting up development environment', 'troubleshooting installation issues' — but stops short of the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

Explicitly states both what ('Complete Auto-Claude installation and setup guide for all platforms') and when ('Use when installing Auto-Claude on WSL, Windows, Linux, or macOS, setting up development environment, or troubleshooting installation issues') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered ('installing', 'WSL', 'Windows', 'Linux', 'macOS', 'setting up development environment', 'troubleshooting'), with only minor synonym/extension gaps keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

The product-specific name 'Auto-Claude' plus enumerated platforms gives it a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.

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
fernandezbaptiste/Skrillz
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.