new

Create a new project to start development quickly

Quality

47%

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%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 provides a clear, mostly actionable Rails scaffolding workflow with genuine tool calls, but is weakened by a missing Supporting Files section (leaving a placeholder path), redundant narration, and no explicit validation feedback loop for a destructive workflow.

Suggestions

Add the referenced 'Supporting Files' section with the real absolute path to create_rails_project.sh so Step 2's command is copy-paste ready.

Insert an explicit validation checkpoint after the setup script (verify bin/setup succeeded / server session_id returned) before proceeding to start the dev server.

Trim the dual zh/en ask_user blocks to one canonical version and cut the Example Interaction that merely re-lists the process steps.

Dimension	Reasoning	Score
Conciseness	Mostly efficient step-by-step guidance, but dual zh/en JSON blocks, a full user-facing success template, and an Example Interaction that re-narrates already-listed steps add padding that could be trimmed.	3 / 5
Actionability	Concrete tool calls (glob, terminal, file_reader) and copy-paste JSON prompts are strong, but Step 2 uses a placeholder path and cites a 'Supporting Files' section that does not appear in the file, leaving an executable gap.	3 / 5
Workflow Clarity	The sequence is clear with a directory-empty checkpoint and error handling, but as a destructive/batch operation (clones into cwd, deletes .git, installs system packages, db:prepare) it lacks an explicit validate-before-proceed feedback loop, capping it at 3.	3 / 5
Progressive Disclosure	Single well-headed file with a one-level reference to an existing script, but the cited 'Supporting Files' section is absent, leaving navigation incompletely signaled.	3 / 5
	Total	12 / 20 Passed

Description

45%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 states a clear purpose but lacks trigger guidance, concrete actions, and a distinguishing framework name. It is functional but generic, capping its completeness and distinctiveness at the midpoint.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user wants to scaffold a new Rails project or start development from a template.'

Name concrete actions and the framework, e.g. 'Scaffolds a new Rails project from a starter template, checks the environment, and starts the dev server.'

Include natural synonyms users say (scaffold, bootstrap, Rails starter) to improve trigger coverage and reduce overlap with generic project skills.

Dimension	Reasoning	Score
Specificity	It names the domain ('Create a new project') but the only actions are generic ('create', 'start development quickly') with no concrete specifics, matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It gives a clear 'what' (create a new project) but has no 'Use when...' trigger clause, so per the missing-trigger-guidance cap it cannot exceed 3.	3 / 5
Trigger Term Quality	'new project' and 'start development' are terms users might say, but coverage is thin with no synonyms (scaffold, bootstrap) or framework name, fitting 'some relevant keywords but missing common variations.'	3 / 5
Distinctiveness Conflict Risk	'Create a new project' is somewhat specific to project scaffolding but, with no framework named, could overlap with many similar scaffolding skills.	3 / 5
	Total	11 / 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: clacky-ai/openclacky
Path: lib/clacky/default_skills/new/SKILL.md
Commit: db23154

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.