CtrlK
BlogDocsLog inGet started
Tessl Logo

develop-asc-change

Design, implement, and verify behavior changes in App-Store-Connect-CLI. Use when adding or changing a command, flag, API endpoint, output format, exit code, shared CLI behavior, or when fixing or refactoring behavior that requires code and tests.

73

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

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

An exemplary instruction-only skill body: a tightly scoped RED-GREEN workflow with explicit validation gates, lean token-efficient prose, and a single well-placed one-level reference. The only improvement area is including literal executable commands for the build/test steps rather than naming them.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — every sentence instructs, nothing explains concepts Claude already knows, and it delegates authority to AGENTS.md instead of restating it. Every token earns its place.

5 / 5

Actionability

Guidance is concrete and specific: exact paths ("docs/openapi/paths.txt", "docs/openapi/latest.json"), exit code `2`, worktree-specific binary paths, and named validation gates. It stops short of a 5 because no literal copy-paste commands are given for key steps (e.g., how to run the focused test or build the binary), leaving minor gaps in executability.

4 / 5

Workflow Clarity

The sequence (design note → RED → API validation → implement → GREEN/verify → handoff) is clearly ordered with explicit validation checkpoints and feedback loops: "Run the focused test and record the expected failure before implementation" and "Rerun the focused failing test after each small fix".

5 / 5

Progressive Disclosure

The ~44-line body is well-sectioned and holds only overview-level guidance, with a single clearly signaled, one-level-deep reference (references/test-matrix.md, verified to exist and contain the promised test cases). Navigation is easy and nothing is nested or buried.

5 / 5

Total

19

/

20

Passed

Description

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

A strong description that explicitly states both what the skill does and when to use it, with concrete trigger phrases and a clearly distinct niche. The 'what' verbs and trigger synonym coverage are the only areas short of the top anchors.

Suggestions

Add a few natural trigger synonyms such as 'option', 'argument', or 'subcommand' alongside 'flag' to broaden the natural-language terms users might say.

Sharpen the 'what' with one or two more fine-grained actions (e.g., 'write RED-GREEN regression tests' or 'validate endpoints against the OpenAPI spec') to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names concrete verbs ("Design, implement, and verify") and enumerates specific change targets ("command, flag, API endpoint, output format, exit code, shared CLI behavior"), giving several specific actions with only minor coverage gaps. It falls short of a 5 because the 'what' verbs are coarser and fewer than the comprehensive multi-action examples at that anchor.

4 / 5

Completeness

It clearly answers 'what' ("Design, implement, and verify behavior changes in App-Store-Connect-CLI") and 'when' with an explicit "Use when..." clause containing concrete trigger phrases. Both halves are explicit, matching the top anchor exactly.

5 / 5

Trigger Term Quality

It includes natural phrases users would say ("adding or changing a command", "flag", "fixing or refactoring", "code and tests") with good coverage of the domain. A few natural synonyms and variations (e.g., 'option', 'argument', 'subcommand') are missing, keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to a named, specific project (App-Store-Connect-CLI) with distinct triggers around CLI behavior changes, giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rorkai/App-Store-Connect-CLI
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.