Conciseness

Every line is operative ('Always round down to the closest 1000, never round up'; three exact file paths; 'Commit and push to main') with no padding or explanation of things Claude already knows. Matches the lean-and-efficient anchor exactly.

Actionability

Concrete file paths and an unambiguous rounding rule make the update step mostly executable, but it omits a specific command for fetching the star count (e.g. a gh api call) and any example of the expected format in each file ('30000' vs '30,000' vs '30k'), leaving minor gaps.

Workflow Clarity

The sequence is present (check stars, round down, update three files, commit and push) but there is no validation checkpoint — no diff review or confirmation that all three files agree — before the destructive push to main, and the batch/destructive cap limits this to 3.

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references; the body is well organized (rule, file list, final action), satisfying the simple-skill exception for a top score.

Specificity

Names the domain ('Remotion homepage GitHub star counts') and two concrete actions ('Update... star counts', 'push the change to main'), which matches the 1-2-concrete-actions anchor; it does not list several actions, so it is not a 4.

Completeness

Explicitly answers both what ('Update Remotion homepage GitHub star counts') and when ('Use when asked to refresh the displayed GitHub star count and push the change to main') with a concrete trigger phrase, matching the anchor-5 example pattern.

Trigger Term Quality

Natural phrases like 'GitHub star count', 'refresh', and 'Remotion homepage' match how a user would phrase the request; only minor synonyms (e.g. 'bump' or 'sync' stars) are missing, so it falls short of the comprehensive anchor 5.

Distinctiveness Conflict Risk

A very narrow niche — refreshing Remotion's displayed star count and pushing to main — with distinct triggers and essentially no overlap with other skills.