Name: environment-setup-guide
Rating: 51.2 (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

56%

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/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

63%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 executable examples and a sensible multi-step workflow, but it is over-long and monolithic — it inlines extensive reference material Claude already knows and uses no progressive disclosure to separate files.

Suggestions

Move the three full worked examples (Node/Python/Docker install commands, docker-compose.yml, setup.sh) into reference files and keep SKILL.md as a concise overview that links to them.

Cut re-explanation of common knowledge (Homebrew/Chocolatey bootstrap commands, what a venv is) and trust Claude's competence to reduce the body well under 100 lines.

Tighten the Verify step with concrete pass/fail criteria (expected version strings, required env-var checks) rather than generic 'run version checks' guidance.

Dimension	Reasoning	Score
Conciseness	At ~480 lines the body is noticeably verbose: it re-explains installation of well-known runtimes (full Homebrew, Chocolatey, Docker install curl commands) and pads with three complete worked examples plus Do/Don't lists, generic pitfalls, and external link lists that Claude largely already knows.	2 / 5
Actionability	The three worked examples (Node.js, Python, Docker) and the setup.sh template provide fully executable, copy-paste-ready commands and config (docker-compose.yml, .env contents) covering the common cases.	5 / 5
Workflow Clarity	A clear five-step sequence (Identify → Check current → Install → Configure → Verify) is present with an explicit verification step and a Troubleshooting section providing error-recovery feedback, but the verify step is generic ('run version checks') without concrete pass/fail criteria.	4 / 5
Progressive Disclosure	The document has reasonable section structure but is monolithic: three full examples, a complete docker-compose, a full setup script, and platform install guides are all inlined in SKILL.md with no bundle/reference files, so content that belongs in separate files is inline.	3 / 5
	Total	14 / 20 Passed

Description

50%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 conveys a clear purpose and domain but lacks explicit trigger ('Use when...') guidance and uses generic action language. It sits at the midpoint across all dimensions: competent but not distinctive.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when onboarding to a project, switching machines, or setting up a dev environment from scratch').

Replace the generic verb 'Guide developers through' with specific actions like 'Install runtimes and package managers, configure environment variables, and verify the setup'.

Include natural synonyms users say ('dev environment', 'onboarding', 'setup') to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain ('setting up development environments') and enumerates concrete components ('tools, dependencies, and configurations'), but the action verb is generic ('Guide... through setting up') rather than listing multiple specific actions like installing, configuring, and verifying.	3 / 5
Completeness	It clearly answers the 'what' (guide developers through environment setup) but provides no explicit 'when' / 'Use when...' trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	It includes natural phrases a user might say ('setting up development environments', 'tools', 'dependencies', 'configurations'), but misses common variations and synonyms like 'dev setup', 'onboarding', 'install', or 'dev environment'.	3 / 5
Distinctiveness Conflict Risk	'Setting up development environments with tools, dependencies, and configurations' is a recognizable niche but very broad, with real overlap risk against project-onboarding, install, and per-language setup skills.	3 / 5
	Total	12 / 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/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.