project-setup

Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

87%

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 concise, actionable five-step procedure with concrete API calls and file templates, but the batch mission-install step lacks a verification/feedback loop, capping workflow clarity.

Suggestions

Add a verification checkpoint after Step 4 — confirm each mission_create succeeded before setting workflow_installed: true (e.g., list missions or check creation status).

Make the mission_create call concrete with the actual name/goal/cadence values per template rather than only the signature.

Keep the lean section structure; it already avoids concept re-explanation and unnecessary verbosity.

Dimension	Reasoning	Score
Conciseness	The body is lean and instruction-forward with no re-explanation of concepts Claude already knows; each step and code block earns its place, matching the 'lean and efficient' anchor.	3 / 3
Actionability	It gives concrete, executable guidance — a real GitHub API call, exact file-path templates with frontmatter, and explicit placeholder-replacement steps — meeting the 'concrete code/commands, copy-paste ready' bar.	3 / 3
Workflow Clarity	The five steps are clearly sequenced with a Step-1 API validation checkpoint, but the batch install of six missions (Step 4) has no verification that mission_create succeeded; the batch-operation guideline caps this at 2.	2 / 3
Progressive Disclosure	No bundle files are present; the skill is self-contained with five well-organized sections and its single cross-skill reference ('Follow the github-workflow skill's install procedure') is clearly signaled and one level deep.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 distinctive, naming three concrete actions in a clear niche, but it omits any explicit 'use when' trigger guidance, which caps its completeness and trigger-term coverage.

Suggestions

Append a 'Use when…' clause (e.g., 'Use when the user wants to track a new GitHub repo and set up its workflow automation.') to raise completeness and trigger-term quality.

Add natural trigger variations the user would actually say ('add a repo', 'track a repository', 'set up workflow for a repo').

Keep the third-person imperative voice as-is — it correctly avoids first/second-person phrasing.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'creates workspace entity, installs workflow automation missions, and includes in dev brief scope' — matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2 anchor.	3 / 3
Completeness	It clearly answers what the skill does but lacks any 'when should Claude use it' clause; per the judging guidelines a missing explicit trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant domain terms ('GitHub repository', 'tracked project', 'workflow automation') but offers few natural phrasing variations a user would say and no explicit trigger guidance, fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The niche — adding a repo as a tracked project with installed workflow missions and dev-brief inclusion — is distinct and unlikely to overlap with unrelated skills, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	10 / 12 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/project-setup/SKILL.md
Commit: 800b781

Reviewed: 2 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.