CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-asc-pr

Audit App-Store-Connect-CLI pull requests end to end and fix concrete defects when authorized. Use for PR review, value and blast-radius assessment, issue verification, or requested fixes before merge.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 workflow skill: terse, non-obvious procedural guidance with concrete file paths, app IDs, and validation checkpoints at every phase, plus an explicit merge gate. All four dimensions sit at the top anchors with no padding or misfiled content.

DimensionReasoningScore

Conciseness

Every line is non-obvious policy or procedure ('Do not treat a flat comment list as proof that all review threads are resolved', 'Never mutate another app without explicit approval') with zero concept explanations Claude already knows — lean and efficient, matching the top anchor.

5 / 5

Actionability

Guidance is concrete and executable despite being instruction-only: exact paths ('AGENTS.md', 'docs/openapi/latest.json'), commands ('--help' paths, '$watch-asc-pr'), a specific disposable app ID ('6759231657'), and a reproduce → failing test → smallest fix → rerun protocol. Per the rubric's instruction-only note, absence of code is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

Six clearly sequenced phases (contract → isolate → verify → fix → merge gate → hand off) with explicit validation checkpoints and feedback loops: 'Reproduce each defect before changing code', 'confirm the failure... rerun the focused test', 'Re-fetch the head SHA, checks, reviews, and GraphQL threads after every push', plus a merge-gate checklist. Destructive/live operations all carry validation, so the destructive-cap rule is satisfied.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so the ~58-line body is appropriately self-contained with well-organized sections. The external pointers it does make ('AGENTS.md', '$watch-asc-pr') are clearly signaled and one level deep, and no inline content belongs in a separate file.

5 / 5

Total

20

/

20

Passed

Description

88%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 with a clear what-and-when structure, concrete actions, and an explicit 'Use for' clause. Its only weakness is limited trigger-synonym breadth ('PRs', 'ASC', 'audit') and mild overlap risk with generic PR-review skills.

Suggestions

Add natural synonyms such as 'PRs', 'audit', and 'ASC'/'App Store Connect' to broaden trigger matching.

Sharpen distinctiveness by making the trigger clause repo-anchored, e.g. 'Use when reviewing or fixing App-Store-Connect-CLI (ASC CLI) PRs'.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'audit... pull requests end to end', 'fix concrete defects', 'value and blast-radius assessment', 'issue verification', 'requested fixes before merge' — covering the full audit/fix lifecycle, matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

It answers both what ('Audit App-Store-Connect-CLI pull requests end to end and fix concrete defects when authorized') and when (explicit 'Use for PR review, value and blast-radius assessment, issue verification, or requested fixes before merge') with concrete trigger phrases, exactly the top anchor.

5 / 5

Trigger Term Quality

Natural phrases like 'PR review', 'pull requests', and 'fixes before merge' match how users would phrase requests, but synonyms are thin — no 'PRs', 'audit', or 'App Store Connect'/'ASC' variations — so it fits good-coverage-with-a-few-missing rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'App-Store-Connect-CLI pull requests' creates a clear niche, but the triggers 'PR review' and 'requested fixes before merge' are generic and could overlap with general PR-review skills when the repo is unnamed — mostly distinct with minor overlap, not minimal conflict risk.

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