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.

70

Quality

86%

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

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

A well-organized, lean instruction skill with a clear RED-GREEN workflow, explicit validation checkpoints, concrete file and command pointers, and a genuine single-level reference. It assumes Claude's competence and avoids concept padding, with only minor actionability and disclosure gaps.

DimensionReasoningScore

Conciseness

The body is lean and efficient throughout: it assumes Claude's competence, gives concrete pointers (registry.go, shared.ContextWithTimeout, make gate commands) without explaining basic CLI or Go concepts, and every line earns its place.

5 / 5

Actionability

Mostly executable guidance with specific files, flags, exit codes, and a runnable gate block ('make format', 'make lint', 'ASC_BYPASS_KEYCHAIN=1 make test'), with only minor gaps such as the live smoke test lacking a concrete command template.

4 / 5

Workflow Clarity

A clearly sequenced RED-GREEN-verify-handoff flow with explicit validation checkpoints ('Stop and align before coding', 'record the expected failure', 'Rerun the focused failing test after each small fix', the repository gate), matching the top anchor for sequenced validation with feedback loops.

5 / 5

Progressive Disclosure

Good structure with sections split by phase and a single well-signaled one-level reference (test-matrix.md) that is a real file in ./references; only minor gaps in that some API-validation detail could itself be referenced out, but placement is appropriate.

4 / 5

Total

18

/

20

Passed

Description

83%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, well-structured description that clearly states the tool, the actions, and an explicit 'Use when...' trigger clause covering concrete change types. It is mostly distinct and only lightly padded, with minor room for tighter trigger-term synonyms.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Design, implement, and verify behavior changes') and enumerates specific change types (command, flag, API endpoint, output format, exit code), with only minor coverage gaps such as omitting documentation-generation as a distinct action.

4 / 5

Completeness

Explicitly answers both 'what' ('Design, implement, and verify behavior changes in App-Store-Connect-CLI') and 'when' ('Use when adding or changing a command, flag, API endpoint...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('adding or changing a command, flag, API endpoint', 'fixing or refactoring behavior') that users would actually say, though it lacks synonyms or shorthand variants of the tool name.

4 / 5

Distinctiveness Conflict Risk

The tool name and enumerated change types carve a clear niche, but the broad 'fixing or refactoring behavior' phrasing creates minor overlap risk with general code-change skills.

4 / 5

Total

17

/

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.

Validation16 / 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.