CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./Skills/agent-ops/bootstrap/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%Scale 1-3

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

This skill provides a reasonable philosophical framework and workflow structure for environment bootstrapping, but critically lacks actionable, executable guidance. The content reads more like a process description or policy document than a skill that would enable Claude to perform concrete actions. The absence of any specific commands, code examples, or tool invocations significantly undermines its utility despite decent organizational structure.

Suggestions

Add concrete, executable examples for each workflow step—e.g., show actual `git clone`, dependency install (`npm install`, `pip install -r requirements.txt`), and validation commands (`make test`, `pytest`) with expected output patterns.

Replace the abstract 'Examples' section with at least one complete worked example showing the full workflow from clone to validation, including what success and failure look like.

Consolidate the Philosophy, Avoid, Anti-Patterns, and Constraints sections into a single concise 'Guidelines' section to reduce token overhead while preserving the key rules.

Add specific validation checkpoint examples in the Workflow section, such as checking exit codes, expected file existence after clone, or specific test output patterns that indicate success vs. failure.

DimensionReasoningScore

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', and 'Anti-Patterns' sections contain fairly obvious guidance). The 'Inputs' and 'Outputs' sections are terse but lack concrete detail that would make them actionable.

2 / 3

Actionability

The skill provides no concrete commands, code snippets, or executable examples. Everything is described abstractly—'inspect 2-3 focused surfaces', 'take the smallest action', 'run the narrowest real validator'—without any specific commands like `git clone`, `npm install`, `make test`, or similar. The examples section shows user prompts but no corresponding actions or outputs.

1 / 3

Workflow Clarity

The workflow has a clear sequence (steps 1-5) and includes validation/fail-fast concepts, which is good. However, the steps are abstract rather than concrete—there are no specific commands, no explicit validation checkpoints with actual tool invocations, and the feedback loop ('rerun the relevant validation after fixes') is mentioned but not demonstrated with concrete examples.

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—the constraints and anti-patterns could be more concisely integrated rather than occupying separate sections.

2 / 3

Total

7

/

12

Passed

Description

100%Scale 1-3

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

DimensionReasoningScore

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

Has a clear niche focused on 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

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

10

/

11

Passed

Repository
jscraik/Agent-Skills
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.