CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-spark-scaffold

This skill should be used when the user says "scaffold", "arn scaffold", "set up the project", "create project", "initialize project", "bootstrap project", "create the skeleton", "install dependencies", "configure the project", or wants to create a working project skeleton from architecture decisions with installed dependencies, configured build tools, and a UI toolkit ready for development.

74

Quality

92%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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 well-sequenced, highly actionable workflow with proper validation checkpoints and clean one-level-deep reference usage. Its main weakness is mild verbosity in the explanatory rationale around pillars and toolkit options, which assumes too little of Claude's competence.

Suggestions

Tighten the pillar-implication prose in Step 1 and Step 2 (e.g. 'a design fidelity pillar means the component library must allow full visual customization') to one-line guidance; trust Claude to derive the implications.

Trim the per-option justification text in the CSS framework and component-library option lists to a terse pillar-fit tag, removing explanatory clauses.

Condense the 'Profile-aware recommendations' paragraph into a compact rule set (if learning → pre-styled; if non-technical → mainstream) rather than a narrative explanation.

DimensionReasoningScore

Conciseness

Mostly efficient and well-structured, but several passages explain concepts a capable model already knows — e.g. extended rationale on pillar implications ('a design fidelity pillar means the component library must allow full visual customization') and per-option justifications in the CSS/component-library lists — that could be tightened without losing clarity.

2 / 3

Actionability

Provides concrete, executable guidance: explicit AskUserQuestion prompts with named option sets, named agents (arn-spark-scaffolder, arn-spark-tech-evaluator) with model dispatch, exact reference paths, staging-directory mechanics, and a build-verify step with retry thresholds.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow with an explicit validation checkpoint in Step 4 (walking the scaffold checklist), failure triage into critical vs non-critical, and a feedback loop ('If it fails after 3 attempts, present the error and suggest the user investigate manually').

3 / 3

Progressive Disclosure

The body is an overview that delegates detail to two real, clearly signaled, one-level-deep references (scaffold-checklist.md and scaffold-summary-template.md via blockquote Read directives), both present in ./references/, with content appropriately split out of the main file.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and explicitly signals both what the skill does and when to use it, with little risk of conflicting with sibling skills. It is an exemplar of the 'Use when...' pattern.

DimensionReasoningScore

Specificity

Lists concrete deliverables such as a 'working project skeleton from architecture decisions with installed dependencies, configured build tools, and a UI toolkit ready for development', naming multiple specific outcomes.

3 / 3

Completeness

Explicitly answers both what (create a working project skeleton with dependencies, build tools, and UI toolkit) and when via the explicit 'This skill should be used when the user says...' trigger clause.

3 / 3

Trigger Term Quality

Strong coverage of natural phrases a user would actually say — 'scaffold', 'set up the project', 'create project', 'initialize project', 'bootstrap project', 'create the skeleton', 'install dependencies', 'configure the project'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (project scaffolding from an architecture vision) with distinct trigger phrases, making it unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
AppsVortex/arness
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.