Name: arn-spark-dev-setup
Rating: 66.4 (1 reviews)
Author: AppsVortex

arn-spark-dev-setup

This skill should be used when the user says "dev setup", "arn spark dev setup", "development environment", "configure dev environment", "dev container", "configure CI", "set up CI", "onboard developer", "developer setup", "set up docker", "configure development", "how do I set up this project", "development setup", "onboard me", "get this project running", "set up my machine", "new developer setup", "how do I get started", "developer onboarding", or wants to define a standardized development environment for their project (producing dev environment infrastructure files and a dev-setup document) or follow an existing environment standard to get onboarded as a new developer.

Quality

80%

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 ./plugins/arn-spark/skills/arn-spark-dev-setup/SKILL.md

Quality

Content

77%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.

A well-sequenced, actionable workflow with explicit verification and error-recovery loops and correctly used one-level reference files. Its main weaknesses are length/redundancy and a monolithic body that could push more detail into references.

Suggestions

Consolidate the 'already configured' handling so it appears once (Step 1) instead of being repeated in Error Handling, and trim option rationales and platform-basic explanations (e.g., 'Rust requires the Rust toolchain') to tighten conciseness.

Move the per-approach detail blocks (native/dev-container/docker/hybrid question lists and the probing-questions table) into a reference file, keeping only the option summary inline, to reduce the monolithic body and improve progressive disclosure.

Consider narrowing the generic trigger phrases in the description (e.g., 'how do I get started', 'set up docker', 'configure CI') or scoping them to the Arness context to reduce conflict with sibling skills.

Dimension	Reasoning	Score
Conciseness	The body is mostly focused on the workflow but runs ~350 lines with some padding: the 'already configured' case is handled redundantly in both Step 1 and Error Handling, option rationales are verbose, and it explains platform basics Claude already knows (e.g., 'Rust requires the Rust toolchain (rustup + cargo)').	2 / 3
Actionability	For an orchestration/instruction skill it gives concrete, copy-paste-ready guidance: exact AskUserQuestion prompts and option sets, named agents with specified context, explicit file Read directives, and a full CLAUDE.md config block format.	3 / 3
Workflow Clarity	Modes and steps are clearly sequenced (Define Steps 2-8, Onboard Steps O1-O4) with explicit verification checkpoints (Step 8 and Step O4 read a checklist) and error-recovery feedback loops (setup-script failure retries three times then presents manual steps).	3 / 3
Progressive Disclosure	Two real bundle files (dev-setup-template.md, dev-setup-checklist.md) are split out and clearly signaled via one-level-deep Read directives, but the body itself is a long monolithic block with substantial inline content (per-approach question lists, the probing table) that could be externalized to references.	2 / 3
	Total	10 / 12 Passed

Description

82%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.

A strong description that answers both what and when with an explicit trigger clause and abundant natural trigger terms, written in correct third person. It is held back only by somewhat abstract action wording and a few generic triggers that could collide with sibling skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('standardized development environment') and concrete artifacts ('dev environment infrastructure files and a dev-setup document') plus the define/follow actions, but the actions stay somewhat abstract rather than enumerating multiple specific concrete actions like the kinds of infrastructure files produced.	2 / 3
Completeness	It explicitly answers both what (define a standardized dev environment producing infrastructure files and a dev-setup document, or follow an existing standard to onboard) and when, via the explicit 'This skill should be used when the user says...' trigger clause.	3 / 3
Trigger Term Quality	It lists an extensive set of natural phrases a user would actually say ('dev setup', 'development environment', 'configure CI', 'set up docker', 'onboard me', 'how do I get started', 'developer onboarding'), giving strong coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The skill has a clear Arness niche, but several trigger phrases ('set up docker', 'configure CI', 'how do I set up this project', 'how do I get started') are generic and could overlap with scaffold, CI, or general onboarding skills; the body itself defers to sibling skills, confirming overlap risk.	2 / 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: AppsVortex/arness
Path: plugins/arn-spark/skills/arn-spark-dev-setup/SKILL.md
Commit: 7f87870

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