Name: sync-asc-skills
Rating: 71.2 (1 reviews)
Author: rorkai

sync-asc-skills

Audit and update rorkai/app-store-connect-cli-skills against the current ASC CLI surface. Use when the user asks whether ASC agent skills need updates, requests a post-release skills sync, or wants command, flag, output, auth, or workflow examples checked for drift.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

The content is a lean, well-structured instruction-only workflow with concrete commands and explicit validation gates; the main gap is the absence of an explicit error-recovery feedback loop and copy-paste-ready examples. Progressive disclosure is appropriate for a short, self-contained skill.

Suggestions

Add an explicit validate→fix→retry feedback loop in the Update minimally section (e.g., 'If a validator or example fails, fix and re-run before proceeding') to push workflow_clarity toward 5.

Include one or two short copy-paste-ready command invocations (e.g., a sample `asc <command> --help` drift-check snippet) to make the guidance fully executable and raise actionability.

Optionally surface a couple of natural synonyms ('stale', 'out of date') in the description triggers for broader trigger-term coverage.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive with no padding and no explanation of concepts Claude already knows; every section (Establish sources, Prove drift, Update minimally, Automation contract, Hand off) earns its place. It is not a 4 because there are no noticeable instances of over-explanation to trim.	5 / 5
Actionability	Concrete, specific guidance is present (run `--help` at each command path, use `asc search`/`asc schema`/`asc capabilities`, validate against a built or released `asc` binary, run the skills repo validators, open a draft PR). It is not a 5 because there are no copy-paste-ready examples covering common cases, and not a 3 because the named commands and steps are genuinely executable rather than pseudocode.	4 / 5
Workflow Clarity	A clear sequence (Establish sources → Prove drift → Update minimally → Hand off) carries explicit validation checkpoints (prove drift before editing, validate every changed command example, run validators) and checklists (the drift "Check for" list and the hand-off report list). It is not a 5 because an explicit validate→fix→retry feedback loop for error recovery is not stated, and not a 3 because validation is explicitly present so the destructive/batch cap does not apply.	4 / 5
Progressive Disclosure	The body is under 50 lines, no bundle files exist, and no external references are needed, so the simple-skill exception applies: well-organized sections alone warrant a 5. Sections are clearly headed and easy to navigate. It is not a 4 because organization is clean with no buried or inlined reference material.	5 / 5
	Total	18 / 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.

The description is strong: it states a precise what, an explicit and multi-trigger when, and a highly distinct niche with low conflict risk. Trigger-term coverage is good rather than comprehensive, leaving a small amount of room for synonyms.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ("rorkai/app-store-connect-cli-skills against the current ASC CLI surface") and lists several concrete actions (audit, update, check command/flag/output/auth/workflow examples for drift), with only minor coverage gaps. It is not a 5 because the action list is not fully comprehensive and not a 3 because more than 1-2 specific actions are stated.	4 / 5
Completeness	It explicitly answers both what ("Audit and update rorkai/app-store-connect-cli-skills against the current ASC CLI surface") and when ("Use when the user asks whether ASC agent skills need updates, requests a post-release skills sync, or wants ... examples checked for drift") with concrete trigger phrases. This matches the top anchor exactly; it is not a 4 because the 'when' is already explicit and specific.	5 / 5
Trigger Term Quality	Natural trigger phrases users would actually say are present ("ASC agent skills need updates", "post-release skills sync", "examples checked for drift"), giving good keyword coverage. It falls short of 5 because common synonyms like "out of date" or "stale" are missing, and exceeds 3 by including several genuine natural-language triggers.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (syncing one named skills repo against the ASC CLI surface) with distinct, narrow triggers and minimal overlap risk with other skills. It is not a 4 because the targeting is specific enough that conflict with unrelated skills is unlikely.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rorkai/App-Store-Connect-CLI
Path: .agents/skills/sync-asc-skills/SKILL.md
Commit: e66125d

Reviewed: 3 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.