CtrlK
BlogDocsLog inGet started
Tessl Logo

arn-spark-use-cases

This skill should be used when the user says "use cases", "arn use cases", "write use cases", "define use cases", "Cockburn use cases", "actor goals", "behavioral requirements", "system behavior", "what does the app do", "describe the behavior", "use case document", "document the behavior", "define system behavior", or wants to create structured use case documents that describe the application's behavior from actor perspectives, producing a use-cases/ directory with individual Cockburn fully-dressed use case files and a README index.

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.

A well-structured, highly actionable orchestration skill with clear sequencing, validation/feedback loops, and clean one-level progressive disclosure to real reference files. The main weakness is verbosity from a repeated model-dispatch parenthetical and the largely-duplicative Agent Invocation Guide.

Suggestions

Replace the repeated 'passing the model from .arness/agent-models/spark.md as the model parameter (see .../ensure-config.md ...)' parenthetical in Steps 2b, 3, 4, 5, and 6 with a single one-line note near the first invocation, e.g. '(All agent invocations pass the model from .arness/agent-models/spark.md; see ensure-config.md Dispatch convention for fallback).' — this is the largest conciseness win.

Trim or remove the Agent Invocation Guide table, since every row restates Steps 2b-6 already detailed above; if kept, collapse it to only the deferred-topic rows (technology, screen design, features, implementation specs) that add new information.

Condense Error Handling by merging near-duplicate cases (e.g. the three 'UX specialist unavailable' entries across Steps 2b, 5, and Error Handling) into one canonical statement plus cross-references.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but it is lengthy (~360 lines) with some repetition: the model-dispatch parenthetical 'passing the model from .arness/agent-models/spark.md...' recurs verbatim in nearly every step, and the Agent Invocation Guide restates Steps 2b-6 already described above.

2 / 3

Actionability

Guidance is concrete and executable: exact Task-tool invocations, the precise context to pass each agent, literal file paths (reviews/round-N-business-review.md), template paths via ${CLAUDE_PLUGIN_ROOT}, grouping strategies, and verbatim user-facing prompts to reuse.

3 / 3

Workflow Clarity

The 8-step workflow is clearly sequenced with explicit validation checkpoints (Step 6b convergence criteria, max 2 rounds), feedback loops (review -> conflict resolution -> revise -> re-review), and error-handling coverage for risky/batch operations including partial-failure and resume.

3 / 3

Progressive Disclosure

SKILL.md is an overview that points one level deep to real, well-signaled reference files (review-protocol.md, use-case-template.md, use-case-index-template.md, expert-review-template.md) via ${CLAUDE_PLUGIN_ROOT} paths; verified these files exist in ./references/, with no nested/deep reference chains.

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.

A strong, third-person description that covers what, when, and distinctiveness with natural trigger terms and concrete artifact names. It is somewhat long but every token relates to triggering or scoping rather than padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('create structured use case documents', 'describe the application's behavior from actor perspectives', producing 'individual Cockburn fully-dressed use case files and a README index') rather than vague abstractions.

3 / 3

Completeness

It explicitly answers both 'what' (creates Cockburn fully-dressed use case files plus a README index in a use-cases/ directory) and 'when' via a long explicit 'should be used when...' trigger clause.

3 / 3

Trigger Term Quality

It provides broad natural-language coverage of phrases a user would say ('use cases', 'write use cases', 'define use cases', 'Cockburn use cases', 'actor goals', 'behavioral requirements', 'what does the app do'), matching the high-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

The Cockburn/use-case/actor-goals niche and specific trigger phrases make it clearly distinguishable from sibling skills, and it even points to a separate /arn-spark-use-cases-teams variant, reducing conflict risk.

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.