CtrlK
BlogDocsLog inGet started
Tessl Logo

ai-devkit-setup

AI DevKit · Check local AI DevKit readiness and run setup only when status shows onboarding or harness integration gaps.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ai-devkit-setup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 body is a tight, actionable, status-driven workflow with executable commands, a verification checkpoint, and clear boundary guidance, all appropriately self-contained for a simple single-purpose skill. The only minor gap is the absence of an explicit error-recovery loop after the re-verification step.

DimensionReasoningScore

Conciseness

The body is lean, assumes Claude's competence, and avoids explaining what AI DevKit is; only the sandboxing note's rationale ('inspect and modify host-level agent configuration... access paths like ~/.pi/agent') could be trimmed slightly, keeping it just below a 5.

4 / 5

Actionability

Provides copy-paste ready, executable commands ('ai-devkit status --json', 'ai-devkit setup --agent codex,pi,claude', 'npx ai-devkit@latest') that cover the common status-check and setup cases.

5 / 5

Workflow Clarity

A clear four-step sequence (status -> identify -> setup -> re-verify) with an explicit verification checkpoint (re-run status and report changes), so the destructive-cap at 3 does not apply; it lacks an explicit error-recovery loop, which keeps it from a 5.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, and self-contained with well-organized sections (Execution Notes, numbered Workflow, Boundaries) and no need for external references, matching the simple-skill exception for a 5.

5 / 5

Total

18

/

20

Passed

Description

70%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 is specific to a named product and answers both what and when with an explicit state-based trigger, though it lists only two fairly generic actions and lacks a natural user-intent 'Use when...' phrase. Distinctiveness is strong due to the product-anchored niche.

Suggestions

Add a user-intent 'Use when...' trigger phrase (e.g., 'Use when the user wants to onboard, prepare, or repair AI DevKit') so the invocation trigger is explicit rather than state-conditioned.

Expand the action list with one or two more concrete setup actions (e.g., 'install hooks, register built-in skills, enable session tracking') to lift specificity beyond 'check readiness' and 'run setup'.

Add common synonyms such as 'install', 'configure', or 'status check' alongside 'onboarding' and 'setup' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('AI DevKit') and two concrete actions ('Check local AI DevKit readiness' and 'run setup'), matching the anchor for 1-2 concrete actions but not the several specific actions required for a 4.

3 / 5

Completeness

Clearly states what (check readiness, run setup) and gives an explicit when ('only when status shows onboarding or harness integration gaps'), but the trigger is state-conditioned rather than a natural user-intent 'Use when...' phrase, so it stops short of a 5.

4 / 5

Trigger Term Quality

Covers several natural terms a user would say ('AI DevKit', 'onboarding', 'setup', 'harness integration', 'readiness'), though a few common synonyms (e.g., 'install', 'configure', 'status check') are missing.

4 / 5

Distinctiveness Conflict Risk

Tied to a named product ('AI DevKit') with a clear onboarding/setup niche, giving minimal conflict risk; only minor overlap with general dev-environment setup skills keeps it from a 5.

4 / 5

Total

15

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
codeaholicguy/ai-devkit
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.