CtrlK
BlogDocsLog inGet started
Tessl Logo

audit-asc-pr

Audit App-Store-Connect-CLI pull requests end to end and fix concrete defects. Use when the user asks to audit or review a PR, decide whether a PR is valuable or slop, verify that a PR truly solves its issue, assess blast radius, or make a PR code-ready before merge.

76

Quality

94%

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

96%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 exceptionally actionable, well-sequenced audit workflow with explicit validation and feedback loops and no token waste. The only mild gap is progressive disclosure: the skill is a single self-contained file with no reference split, which is acceptable but does not reach the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and instruction-dense — it never explains concepts Claude already knows (what a PR, GraphQL, or a worktree is) and each line is actionable guidance, so every token earns its place.

5 / 5

Actionability

Concrete, executable guidance throughout — specific paths ('AGENTS.md', 'docs/openapi/latest.json'), commands ('Run the relevant current --help paths', 'Build a binary'), identifiers (disposable app '6759231657'), and tools ('$watch-asc-pr') — covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

Clearly sequenced phases (Establish the contract → Isolate and inspect → Verify behavior → Fix forward → Apply the merge gate → Hand off) with explicit validation checkpoints, feedback loops ('confirm the failure, implement the smallest coherent fix, and rerun', 'Re-fetch... after every push'), and a merge-gate checklist; destructive-op validation (disposable app, cleanup, preserve uncertainty) is present so no cap applies.

5 / 5

Progressive Disclosure

Well-organized into clearly signaled sections and self-contained, but there are no reference files and the body exceeds 50 lines, so the simple-skill exception does not strictly apply and the 5 anchor's signaled one-level-deep references are absent.

4 / 5

Total

19

/

20

Passed

Description

92%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, specific description that clearly conveys what the skill does and when to use it, with comprehensive concrete actions and a distinct niche. Trigger-term quality is slightly held back by domain jargon that not every user would naturally voice.

DimensionReasoningScore

Specificity

Names the domain and lists multiple concrete actions — 'audit or review a PR', 'decide whether a PR is valuable or slop', 'verify that a PR truly solves its issue', 'assess blast radius', 'make a PR code-ready before merge' — giving comprehensive coverage rather than just several with minor gaps.

5 / 5

Completeness

Explicitly states both what ('Audit App-Store-Connect-CLI pull requests end to end and fix concrete defects') and when ('Use when the user asks to audit or review a PR...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good keyword coverage with natural synonyms ('audit or review a PR') and concrete trigger clauses, but terms like 'slop' and 'blast radius' are maintainer jargon rather than universally natural phrasing, and the file-extension breadth expected of a 5 does not apply to this domain.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — App-Store-Connect-CLI pull requests — with distinct triggers, making conflict with unrelated skills minimal.

5 / 5

Total

19

/

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.