new

Create a new project to start development quickly

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./lib/clacky/default_skills/new/SKILL.md

Quality

Content

50%

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

The skill provides a well-sequenced, concrete Rails-scaffolding workflow, but its most critical command is a non-executable placeholder pointing to an absent 'Supporting Files' section, and it carries redundant narration plus missing success-verification on a destructive batch step. It is functional but has clear hardening gaps.

Suggestions

Replace the '<absolute path ... from Supporting Files>' placeholder with the real path (scripts/create_rails_project.sh) or add an actual 'Supporting Files' section — the current reference points to a section that does not exist, making the key command non-executable.

Add an explicit success-verification checkpoint after the setup script (check exit code / confirm 'Project setup complete' output) before starting the dev server, rather than proceeding on the assumption the script succeeded.

Trim redundancy: the 'Example Interaction' section narrates the process steps with no new information and 'Error Handling' repeats Step 2's auto-install details — consolidate to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with no concept-explanation padding, but the 'Example Interaction' section merely narrates the process steps with no new information and the 'Error Handling' section repeats Step 2's auto-install details, so it could be tightened (anchor 2).	2 / 3
Actionability	Concrete commands are present (glob, terminal, file_reader), but the central script invocation is a non-executable placeholder — '<absolute path to create_rails_project.sh from Supporting Files>' — leaving a key detail missing (anchor 2, not the copy-paste-ready anchor 3).	2 / 3
Workflow Clarity	Steps are clearly sequenced with some checkpoints (empty-directory confirmation, server session_id check), but the destructive/batch setup (auto-installing system packages, re-initializing git) proceeds to server start without an explicit success-verification gate, so per the feedback-loop guideline workflow clarity is capped at 2.	2 / 3
Progressive Disclosure	Section structure is clear and the bundle (scripts/create_rails_project.sh) is only one level deep, but the reference points to a 'Supporting Files' section that does not exist in the document and never names the real scripts/ path, so the reference is present but not clearly signaled (anchor 2).	2 / 3
	Total	8 / 12 Passed

Description

50%

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 conveys a single concrete action but is generic, omits the Rails domain entirely, and lacks any explicit 'Use when...' trigger clause. It reads as adequate but unoptimized for skill selection.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user wants to scaffold a new Rails project from a starter template', to satisfy the 'when' half of completeness.

Name the domain and concrete actions — mention Rails scaffolding, dependency/environment setup, and dev-server launch instead of the generic 'new project'.

Include natural trigger variations such as 'new Rails project', 'scaffold a Rails app', and '/new' to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	"Create a new project" names a concrete action but gives no domain (Rails is never mentioned) and only a single action, matching anchor 2 rather than the multi-action anchor 3 or the vague anchor 1.	2 / 3
Completeness	The description states what the skill does but includes no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"new project" and "start development" are natural user terms, but the description offers no common variations (e.g. "/new", "scaffold a Rails app"), fitting anchor 2's 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	It is narrower than the catch-all 'helps with code and documents' (anchor 1) but the generic 'new project' phrasing could still overlap with other scaffolding skills, matching anchor 2.	2 / 3
	Total	8 / 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: clacky-ai/openclacky
Path: lib/clacky/default_skills/new/SKILL.md
Commit: 4aea278

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