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.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A lean, well-organized instruction skill with a clear validated workflow and no token waste. Its main weakness is actionability — guidance stays abstract without concrete commands or examples — and the progressive-disclosure pointer does not line up with the actual reference bundle.

Suggestions

Add at least one concrete, executable example per mode (e.g. a sample clone+install+test command sequence) to move guidance from abstract to actionable.

Correct or align the archived-reference path in the Progressive Disclosure section with the real ./references/ files (contract.yaml, evals.yaml, task-profile.json), and name the specific file to load for each task type.

Tie the 'Inputs' and 'Outputs' lists to the workflow steps so each step references which input it consumes and which artifact it produces.

DimensionReasoningScore

Conciseness

Lean and efficient with no concept-explaining filler; it does not explain what a toolchain or dependency is and every line earns its place, matching the score-3 anchor.

3 / 3

Actionability

Guidance is mostly process-level and abstract ('Take the smallest action that advances the confirmed goal', 'Inspect 2-3 focused surfaces') with no concrete commands or worked examples, so it instructs direction without being fully copy-paste actionable.

2 / 3

Workflow Clarity

The numbered 5-step workflow is clearly sequenced with an explicit validation feedback loop — 'Stop at the first failed gate' and 'Rerun the relevant validation after fixes before claiming completion' — meeting the score-3 anchor.

3 / 3

Progressive Disclosure

It signals deferred context and one-level references exist under ./references/, but the cited path 'Infrastructure/references/deferred-skill-context/agent-ops-bootstrap/' does not match the actual bundle files (contract.yaml, evals.yaml, task-profile.json), so navigation to the real files is not clearly signaled.

2 / 3

Total

10

/

12

Passed

Description

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.

A strong, concise description that states concrete capabilities and an explicit 'Use when' trigger with natural user phrasing. It cleanly answers both what the skill does and when to invoke it within a distinct niche.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'Create, diagnose, and validate' plus 'clone a repo, install toolchains, install dependencies, and prove the project runs' — matching the score-3 anchor listing several specific actions.

3 / 3

Completeness

Explicitly answers both 'what' ('Create, diagnose, and validate a local dev bootstrap') and 'when' ('Use when the user asks to clone a repo...'), satisfying the score-3 anchor with explicit triggers.

3 / 3

Trigger Term Quality

Uses natural phrasings a user would actually say ('clone a repo', 'install toolchains', 'install dependencies', 'prove the project runs'), giving good coverage of common variations rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The 'local dev bootstrap' niche is bounded and the explicit trigger clause narrows scope, making it unlikely to fire for the wrong skill; not generic enough to conflict broadly.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

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.