Name: arn-spark-ensure-config
Rating: 64.8 (1 reviews)
Author: AppsVortex

arn-spark-ensure-config

This skill should be used when the user says "ensure config", "check arn spark config", "arn-spark-ensure-config", "verify arn spark setup", "configure spark", "setup arness spark", "spark config", or wants to verify that Arness Spark configuration is present for the current project. This skill is primarily consumed as a reference by entry-point skills (arn-brainstorming, arn-spark-discover, arn-spark-arch-vision) which read the `references/step-0-fast-path.md` reference as Step 0 before proceeding with their workflow.

Quality

77%

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-ensure-config/SKILL.md

Quality

Content

72%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-structured, token-efficient orchestrator body that cleanly delegates to real reference files. It is weakest on direct actionability and in-body workflow checkpoints, since nearly all executable detail lives in the referenced documents.

Suggestions

Inline the common-path executable snippet (e.g. `bash ${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-ensure-config/scripts/cache-check.sh` plus the exit-0/exit-nonzero branches) so the body is directly actionable without opening a reference for the fast path.

Surface the validation feedback loop in the body — cache hit → return, cache miss → run Layers 1–2 → write Layer 3 cache → only then proceed — instead of delegating the entire sequence to ensure-config.md.

Add a one-line completion criterion stating what a successful run leaves behind (valid profile + `## Arness` section + `.arness/arn-spark-ensure-config.local.json` cache) so success is unambiguous from the body alone.

Dimension	Reasoning	Score
Conciseness	Lean body with no basic-concept padding; the cache-indirection rationale and fast-path note each earn their tokens by explaining non-obvious routing rather than restating what Claude already knows.	3 / 3
Actionability	Provides exact reference paths and clear per-mode routing, but no inline executable commands — the actual steps (cache-check.sh invocation, layer procedures) live entirely in the referenced files, leaving the body itself incomplete for direct execution.	2 / 3
Workflow Clarity	The cache hit/miss branching is described, but the explicit step sequence and validate→fix→retry feedback loop are delegated to ensure-config.md rather than surfaced as checkpoints in the body.	2 / 3
Progressive Disclosure	A thin overview points to well-signaled, one-level-deep references (step-0-fast-path.md and ensure-config.md, both verified real files) with content appropriately split between fast-path router and full validation.	3 / 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, trigger-rich description that clearly states both capability and invocation conditions in third person. Its main weakness is mild overlap risk from the unqualified "spark" trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain (Arness Spark config) and several actions, but the actions are mostly variations on verifying/checking config presence rather than a comprehensive set of distinct concrete operations.	2 / 3
Completeness	Explicitly answers both what ("verify that Arness Spark configuration is present for the current project") and when ("should be used when the user says… or wants to verify…") with explicit triggers, in third-person voice.	3 / 3
Trigger Term Quality	Broad coverage of natural phrases a user would say — "ensure config", "check arn spark config", "verify arn spark setup", "configure spark", "setup arness spark", "spark config" — matching the high-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	The "Arness Spark" name and arn-prefixed triggers are distinct, but the bare "configure spark" and "spark config" triggers could overlap with general Apache-Spark configuration skills.	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-ensure-config/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.