bootstrap

Create, diagnose, and validate a local dev bootstrap. Use when the user asks to clone a repo, install toolchains, install dependencies, and prove the project runs.

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./Skills/agent-ops/bootstrap/SKILL.md

Quality

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 a strong skill description that clearly communicates its purpose and trigger conditions. It uses third person voice, lists specific concrete actions, includes natural trigger terms, and has an explicit 'Use when' clause. The description is concise yet comprehensive, covering the full lifecycle of local dev setup from cloning to validation.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'create, diagnose, and validate a local dev bootstrap', 'clone a repo, install toolchains, install dependencies, and prove the project runs'. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (create, diagnose, and validate a local dev bootstrap) and 'when' (explicit 'Use when' clause specifying clone a repo, install toolchains, install dependencies, prove the project runs).	3 / 3
Trigger Term Quality	Includes natural keywords users would say: 'clone a repo', 'install toolchains', 'install dependencies', 'dev bootstrap', 'project runs'. These cover common variations of how users would describe setting up a local development environment.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche of local development environment bootstrapping. The combination of cloning, toolchain installation, dependency installation, and validation is distinct and unlikely to conflict with other skills like general coding or deployment skills.	3 / 3
	Total	12 / 12 Passed

Implementation

35%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like an abstract operating philosophy than actionable guidance. While it has reasonable structure, validation principles, and progressive disclosure references, it critically lacks any concrete commands, code examples, or specific tool usage that would make it executable. The workflow steps are too abstract to guide Claude through an actual bootstrap process.

Suggestions

Add concrete, executable examples in the Workflow section — e.g., actual `git clone`, `nvm install`, `npm install`, `npm test` commands showing a real bootstrap sequence with expected outputs.

Replace the abstract 'Examples' section with at least one complete input→output example showing the exact steps taken, commands run, and validation evidence produced.

Add specific validation commands for common ecosystems (e.g., `python -m pytest --co -q` for Python, `npm test` for Node) rather than the abstract 'run the narrowest real validator'.

Consolidate the overlapping 'Avoid', 'Constraints', and 'Anti-Patterns' sections into a single concise 'Guardrails' section to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some sections that are somewhat generic and don't add much Claude-specific value (e.g., 'Philosophy', 'When To Use', 'Avoid' sections contain fairly obvious guidance). The 'Anti-Patterns' and 'Constraints' sections overlap conceptually. However, it's not egregiously verbose.	2 / 3
Actionability	The skill provides no concrete commands, code examples, or executable steps. The workflow is entirely abstract ('Inspect 2-3 focused surfaces', 'Take the smallest action'). There are no specific tool invocations, no example shell commands for cloning/installing/validating, and the 'Examples' section just shows user prompts without corresponding actions or outputs.	1 / 3
Workflow Clarity	The workflow has a logical sequence (classify → inspect → act → stop on failure → revalidate) and the Validation section mentions fail-fast and rerun-after-fix patterns, which is good. However, the steps are abstract with no concrete commands or validation checkpoints tied to specific tools. For a task involving potentially destructive operations (installing toolchains, modifying environments), the lack of specific validation commands caps this at 2.	2 / 3
Progressive Disclosure	The skill references a deferred context directory (`Infrastructure/references/deferred-skill-context/agent-ops-bootstrap/`) and instructs to load only what's needed, which is good structure. However, no bundle files are provided to verify these references exist, and the main content itself could benefit from splitting detailed constraint/anti-pattern guidance into a reference file rather than inlining it all.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	10 / 11 Passed

Repository: jscraik/Agent-Skills
Commit: 4c78f98

Reviewed: about 22 hours 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.