Generate setup scripts and instructions for development environments across platforms. Use when: (1) Setting up new development machines (Python, Node.js, Docker, databases), (2) Creating automated setup scripts for team onboarding, (3) Need cross-platform setup instructions (macOS, Linux, Windows), (4) Installing development tools and dependencies, (5) Configuring version managers and package managers. Provides executable setup scripts, platform-specific guides, and tool installation instructions.
Install with Tessl CLI
npx tessl i github:ArabelaTso/Skills-4-SE --skill environment-setup-assistant94
Does it follow best practices?
Validation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific capabilities with concrete technologies, includes comprehensive trigger terms developers would naturally use, has an explicit 'Use when' clause with multiple scenarios, and carves out a distinct niche around development environment setup that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generate setup scripts', 'Creating automated setup scripts', 'Installing development tools', 'Configuring version managers'. Also specifies concrete technologies (Python, Node.js, Docker, databases) and outputs (executable scripts, platform-specific guides). | 3 / 3 |
Completeness | Clearly answers both what ('Generate setup scripts and instructions') AND when with explicit 'Use when:' clause containing 5 specific trigger scenarios. The final sentence reinforces outputs provided. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'development environments', 'setup scripts', 'team onboarding', 'macOS, Linux, Windows', 'Python, Node.js, Docker', 'version managers', 'package managers', 'development tools', 'dependencies'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on development environment setup and onboarding scripts. The combination of 'setup scripts', 'development machines', 'team onboarding', and cross-platform focus creates a distinct identity unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and progressive disclosure. The main weakness is verbosity - the skill includes redundant examples and explanatory content that could be consolidated. The executable scripts are production-ready with proper error handling and verification.
Suggestions
Consolidate the four setup scenarios into a single parameterized example or table, reducing repetition while maintaining coverage
Remove explanatory comments like 'This allows managing multiple Node.js versions' - Claude knows what nvm does
Combine the 'Common Patterns' and 'Best Practices' sections which have overlapping content (e.g., both show installation checks)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains significant redundancy - multiple similar setup script examples that could be consolidated, and some explanatory text that Claude doesn't need (e.g., explaining what version managers do). The content could be tightened by 30-40% while preserving all actionable information. | 2 / 3 |
Actionability | Excellent executable code throughout with copy-paste ready bash scripts, specific commands, and complete examples. The scripts include error handling, platform detection, and verification steps that are immediately usable. | 3 / 3 |
Workflow Clarity | Clear 5-step workflow (Assess → Choose Approach → Generate → Verify → Cleanup) with explicit validation checkpoints. Scripts include verification steps with success/failure indicators, and the idempotent pattern ensures safe re-runs. | 3 / 3 |
Progressive Disclosure | Well-structured with clear navigation to external references (platform_instructions.md, tool_guides.md) using one-level-deep links. Quick Start at top, detailed scenarios in middle, and reference materials clearly signaled with anchor links. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.