developer-setup

One-time onboarding for the developer workflow — installs github-workflow missions, creates the commitments workspace, registers per-repo projects, writes calibration memories. Excludes itself until its marker file is deleted.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/developer-setup/SKILL.md

Quality

Content

65%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 highly actionable with concrete, copy-paste-ready setup blocks and a clear step sequence, but it is padded in places and lacks explicit validation/verification checkpoints before irreversible marker-writing and batch project registration steps.

Suggestions

Add an explicit validation/confirmation step before Step 7 (e.g., verify each mission and project file was created, confirm with the user) before writing the .developer-setup-complete marker.

Move the large memory_write and mission_create content blocks into a references/ file and reference it one level deep to improve progressive disclosure and token efficiency.

Dedupe the companion-skills table against the requires.skills list so the same skill roster is not described twice.

Dimension	Reasoning	Score
Conciseness	Mostly efficient step-by-step structure, but the long inline 'goal:' strings and large memory_write content blocks carry redundant detail, and the companion-skills table overlaps with the requires.skills list.	3 / 5
Actionability	Fully executable guidance: concrete memory_write and mission_create blocks with complete goal text, cron cadences, and project_id values that are copy-paste ready across common cases.	5 / 5
Workflow Clarity	A clear 7-step sequence exists, but irreversible/batch operations (writing the setup-complete marker, registering projects, creating missions) lack explicit validate-then-confirm checkpoints; per the rubric, missing validation for batch operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ all absent), so there is nothing to navigate; the large inline mission_create and memory_write blocks that could live in separate reference files are instead inlined, giving some structure but no real file-level disclosure.	3 / 5
	Total	14 / 20 Passed

Description

56%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 and action-rich about what the skill does, but omits explicit trigger guidance and natural keyword phrasing within the description field itself, relying on a separate activation block for triggers.

Suggestions

Add an explicit 'Use when...' clause to the description with natural trigger phrases (e.g., 'Use when a developer wants to set up their GitHub/commitment workflow for the first time').

Surface 1-2 natural keywords in the description text (e.g., 'developer onboarding', 'set up my repos') so the description alone signals when to use the skill.

Keep the concrete action list but trim the marker-file detail from the description to keep it concise; the self-exclusion behavior can stay in the body.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('installs github-workflow missions', 'creates the commitments workspace', 'registers per-repo projects', 'writes calibration memories'), giving comprehensive coverage of what the skill does.	5 / 5
Completeness	Has a clear 'what' (installs, creates, registers, writes) but no explicit 'when'/'Use when...' clause in the description; the trigger guidance is absent from the description field itself.	3 / 5
Trigger Term Quality	The description text itself contains no natural user-facing trigger phrases; the actual keywords ('developer setup', 'dev workflow') live in activation.keywords rather than the description, leaving only generic phrasing in the description itself.	2 / 5
Distinctiveness Conflict Risk	The 'one-time onboarding for the developer workflow' niche is reasonably distinct with only minor overlap risk against related developer/github skills; the marker-file exclusion note adds specificity.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nearai/ironclaw
Path: skills/developer-setup/SKILL.md
Commit: 2831516

Reviewed: 8 days 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.