Name: environment-setup-guide
Rating: 46.400000000000006 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

environment-setup-guide

Guide developers through setting up development environments with proper tools, dependencies, and configurations

Quality

48%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/environment-setup-guide/SKILL.md

The canonical home for this skill is environment-setup-guide in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

52%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 skill is highly actionable with a clear sequenced workflow, but it is severely verbose and monolithic, inlining large amounts of common-knowledge material and worked examples that should live in separate reference files.

Suggestions

Move the three full worked examples (Node.js, Python, Docker) and the setup script template into separate reference files linked from a concise overview, applying one-level-deep progressive disclosure.

Cut explanations of concepts Claude already knows (what Homebrew/virtualenv are, generic command-not-found advice) and keep only project-specific or non-obvious guidance.

Add inline validation->fix->retry checkpoints around destructive/batch steps (e.g., npm run migrate in setup.sh) instead of relegating errors to a separate troubleshooting section.

Dimension	Reasoning	Score
Conciseness	The ~480-line body inlines full install/venv/docker procedures and command-not-found troubleshooting that Claude already knows, with several padded sections (How It Works + 3 full Examples + Best Practices + Common Pitfalls) that restate the same setup flow.	2 / 5
Actionability	It provides concrete, mostly copy-paste-ready commands and templates (brew/apt/choco installs, docker-compose.yml, setup.sh) covering common cases, with minor placeholders like 'your-repo/project.git' and 'your-api-key-here'.	4 / 5
Workflow Clarity	A clear 5-step sequence (Identify, Check, Install, Configure, Verify) with per-example verification steps is present, but there are no inline validate->fix->retry feedback loops for risky operations such as migrations or PATH edits.	4 / 5
Progressive Disclosure	No bundle files exist and the entire body is one monolithic file; content that belongs in separate references (three worked examples, setup script template, troubleshooting catalog) is fully inlined with zero one-level-deep local references.	2 / 5
	Total	12 / 20 Passed

Description

45%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 states a clear purpose in third person but lacks a 'when to use' trigger clause and relies on generic actions, leaving it broadly applicable rather than sharply triggered.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., onboarding, new machine, troubleshooting environment issues, writing setup docs).

Replace generic phrasing with concrete actions such as 'install runtimes and package managers, configure environment variables, and verify the setup'.

Include natural synonyms users say ('dev environment', 'onboarding', 'new laptop setup') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'setting up development environments with proper tools, dependencies, and configurations' names the domain and a few categories, but the only action ('setting up'/'guide through') is generic with no concrete actions like installing, configuring env vars, or verifying.	2 / 5
Completeness	It clearly states what the skill does but includes no 'Use when...' or equivalent trigger clause; per the rubric, a missing explicit 'when' caps completeness at 3.	3 / 5
Trigger Term Quality	'setting up development environments' is a natural phrase a user would say, but the description misses common synonyms and variations like 'onboarding', 'new machine setup', or 'dev env'.	3 / 5
Distinctiveness Conflict Risk	'development environments' is a recognizable niche, but 'tools, dependencies, and configurations' is broad and could overlap with project-init or onboarding skills.	3 / 5
	Total	11 / 20 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/environment-setup-guide/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.