update-expected-app-size

Download updated expected app size files from Azure DevOps CI artifacts for the current branch. Use when app size tests fail in CI and the user wants to update the expected files locally. Trigger on "update app size", "download expected files", "fix app size test", or "update expected app size files".

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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-executed CI-artifact workflow skill: every step is backed by concrete commands, validation precedes the commit, and failure paths (auth, unappliable diffs, local builds) each have documented recovery. Remaining polish is minor — placeholder substitution, and splitting the naming-convention reference material out of the main body.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and repo-specific facts Claude cannot know (artifact naming pattern, diff format, file paths), with only minor trims available — the 'When to Use' section restates the description's triggers and the Background lists four example diff filenames where one or two would suffice. This fits 'efficient; minor instances of over-explanation' rather than the lean-every-token-earns-its-place anchor.	4 / 5
Actionability	Concrete, executable bash is given for every step (gh pr list, gh pr checks, az account get-access-token, curl REST calls, unzip, git apply -p1, commit), but commands carry unsubstituted placeholders ({buildId}, {artifactName}, {PR_NUMBER}) and steps like 'Look for artifacts whose names contain updated-expected-sizes' require the agent to fill in specifics, so it stops short of fully copy-paste ready.	4 / 5
Workflow Clarity	Five clearly sequenced steps with an explicit validation checkpoint (run git diff, ask the user before committing) and feedback loops for error recovery (diff fails to apply → regenerate with WRITE_KNOWN_FAILURES=1) plus two documented fallbacks, which matches the top anchor including the batch-operation validation requirement.	5 / 5
Progressive Disclosure	The skill is a single self-contained file with no bundle references and a well-organized section structure (Background, numbered Workflow, two Fallbacks). It sits above the simple-skill exception (~118 lines) and the Background's artifact-naming details and example filename lists could be split into a reference file, so it fits 'good structure; minor organization gaps' rather than the fully optimized anchor.	4 / 5
	Total	17 / 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 with an explicit what/when pair and natural trigger phrases for a clearly delineated niche. Its only weakness is that the what-clause covers just the download action, underselling the apply-and-commit workflow the skill actually walks through.

Suggestions

Broaden the what-clause to cover the full capability, e.g. 'Download updated expected app size files from Azure DevOps CI artifacts for the current branch and apply them to the repository' — this lifts specificity from one action to several.

Add missing natural trigger variants such as "app size test failed", "app size test failures", or "expected sizes" to make trigger coverage comprehensive.

Consider mentioning the .diff artifact format or the word "CI build" in the description so users describing the artifact ("apply those .diff files from CI") also match.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action ("Download updated expected app size files from Azure DevOps CI artifacts for the current branch") but omits other actions the skill performs (applying the diffs, verifying, committing), so it matches '1-2 concrete actions, not comprehensive' rather than the 'several specific actions' anchor.	3 / 5
Completeness	It clearly answers both what ("Download updated expected app size files from Azure DevOps CI artifacts for the current branch") and when ("Use when app size tests fail in CI and the user wants to update the expected files locally") plus explicit concrete trigger phrases, exactly matching the top anchor.	5 / 5
Trigger Term Quality	Four natural quoted trigger phrases ("update app size", "download expected files", "fix app size test", "update expected app size files") give good keyword coverage, but common variations like "app size test failures", "expected sizes", or "CI diff" phrasings are missing, so it falls just short of comprehensive.	4 / 5
Distinctiveness Conflict Risk	The niche is clear (app size expected files from Azure DevOps CI artifacts for a specific repo workflow) with distinct trigger phrases, so it is unlikely to fire for the wrong skill.	5 / 5
	Total	17 / 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: dotnet/macios
Path: .github/skills/update-expected-app-size/SKILL.md
Commit: 354c2a6

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