CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

setup-project

Configure Claude Code for this project - detects languages and sets up rules, skills, and validators

Quality

80%

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 ./plugins/pragma/skills/setup-project/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 and well-structured, with executable commands and strong validation/feedback loops for its destructive and batch operations. The main improvement room is minor conciseness trimming and potentially externalizing the large inline rule template.

DimensionReasoningScore

Conciseness

Largely efficient with concrete bash/code blocks and little concept-explaining, though the <base directory> explanation is restated in prose after the code block and some example output is repeated, leaving minor trim opportunities.

4 / 5

Actionability

Fully executable guidance throughout: concrete bash commands, exact file paths, YAML frontmatter examples, an upsert-rules table, and assembled-file-shape examples that cover common monorepo cases copy-paste ready.

5 / 5

Workflow Clarity

A clearly sequenced 10-step workflow with explicit validation checkpoints (Step 0 STOP-on-fail, legacy-file marker checks, ask-before-overwriting user content) and feedback loops for the destructive/batch operations of overwriting and deleting config files.

5 / 5

Progressive Disclosure

Well-organized into clear sections with clearly signaled one-level-deep references to plugin resources ($PLUGIN_ROOT/claude-md/...); no bundle files exist under ./references, ./scripts, or ./assets, and the inline local-supplements template is large enough that it could arguably live externally.

4 / 5

Total

18

/

20

Passed

Description

66%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 distinctive, clearly stating what the skill does, but it omits any explicit 'when to use' trigger guidance, which caps its completeness. Adding a 'Use when…' clause with natural trigger phrases would lift it from good to strong.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up Claude Code on a new or existing project, or when the user asks to configure project rules, skills, or validators.'

Include natural synonyms users might say, such as 'initialize', 'bootstrap', or 'configure Claude Code for a repo'.

Mention monorepo/multi-language support in the description since it is a core capability highlighted in the body.

DimensionReasoningScore

Specificity

Names the domain ('Configure Claude Code for this project') and several concrete actions ('detects languages', 'sets up rules, skills, and validators'), with only minor coverage gaps, matching the 'lists several specific actions' anchor.

4 / 5

Completeness

The 'what' is clear (configure Claude Code, detect languages, set up rules/skills/validators) but there is no explicit 'when'/'Use when…' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage ('Configure Claude Code', 'project', 'languages', 'rules, skills, validators') but lacks natural 'Use when…' phrasings and common synonyms, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

It targets a distinct niche (project configuration with rules/skills/validators) with only minor overlap risk against generic config skills, matching the 'mostly distinct' anchor.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

peteski22/agent-pragma

Path

plugins/pragma/skills/setup-project/SKILL.md

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.