CtrlK
BlogDocsLog inGet started
Tessl Logo

sync-asc-skills

Check rorkai/app-store-connect-cli-skills against the current ASC CLI surface and correct proven drift when authorized. Use for skill-drift questions, post-release syncs, or checks of command, flag, output, auth, and workflow examples.

69

Quality

87%

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

86%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 tight, well-structured instruction-only skill: safe-by-default authority gating, a drift-evidence checklist, explicit validation of every changed example, and a precise handoff report. The main gaps are the absence of a failure-recovery loop for validation and slightly under-specified mechanical steps (resolving versions, exact commands).

DimensionReasoningScore

Conciseness

Lean and imperative throughout ("Do not update skills merely because a newer CLI version exists", "Record exact help or runtime evidence for every edit"); it assumes Claude's competence and delegates conventions to AGENTS.md with no padding or concept explanations to trim.

5 / 5

Actionability

Mostly concrete guidance — "Run the current CLI's `--help` at each relevant command path", "open a separate draft PR... with the CLI commit or release used as evidence" — but few literal copy-paste commands, and steps like resolving the source commit or latest release are left to the reader.

4 / 5

Workflow Clarity

A clear four-phase sequence (establish → prove drift → update minimally → hand off) with real validation gates ("Validate every changed command example against current... help and the relevant schema", "Run the skills repository's validators", "report any path not executed"), but no explicit validate-fail-fix-retry feedback loop, so it sits at the 4 rather than 5 anchor.

4 / 5

Progressive Disclosure

Under 50 lines with no bundle files needed; sections are well-organized and the only external pointer (AGENTS.md) is one level deep and clearly signaled, which satisfies the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

82%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: third person, concrete what, and an explicit, specific "Use for" trigger clause tied to a named repository. The only soft spot is that the capability list itself is just two actions rather than a fuller inventory.

Suggestions

Enumerate one or two more concrete capabilities in the what-clause (e.g., "inventory command, flag, output, and auth claims" or "validate changed examples against help and schemas") to lift specificity.

Add a common synonym trigger such as "stale or outdated skill documentation" and spell out "App Store Connect" once so users who don't say "ASC" or "drift" still match.

DimensionReasoningScore

Specificity

Names the domain ("rorkai/app-store-connect-cli-skills", "current ASC CLI surface") and two concrete actions ("Check... against" and "correct proven drift"), but does not list several specific actions as the 4 anchor requires.

3 / 5

Completeness

Explicitly answers both what ("Check rorkai/app-store-connect-cli-skills against the current ASC CLI surface and correct proven drift when authorized") and when ("Use for skill-drift questions, post-release syncs, or checks of command, flag, output, auth, and workflow examples") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"skill-drift questions, post-release syncs, or checks of command, flag, output, auth, and workflow examples" covers the natural phrases for this niche well, but misses common synonyms like "stale", "outdated", or the spelled-out "App Store Connect".

4 / 5

Distinctiveness Conflict Risk

A named repository and a narrow drift-sync workflow give it a clear niche with distinct triggers; minimal risk of firing for unrelated skills.

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

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.