Conciseness

The body is a lean redirect: every line earns its place — where the component moved, a copy-paste install command, what to ask the agent, and an explicit note that 'This compatibility entry contains no component rules and is no longer maintained.' The only borderline clause ('the component layer for AI agents') is a one-phrase descriptor that aids navigation rather than padding.

Actionability

The install command 'npx skills add kostja94/bricks --skill component-builder' is fully executable and copy-paste ready, and the follow-up instruction 'Ask the agent to use component-builder to build a new Social Share' is concrete and unambiguous. For a redirect stub, the single common case is completely covered.

Workflow Clarity

This is a simple, single-purpose skill (redirect to the successor), and the single action is unambiguous: install the successor skill and ask the agent to use it. The simple-skill exception applies; there are no destructive or batch operations that would require validation checkpoints.

Progressive Disclosure

The body is under 50 lines with a clear heading, and the one external reference (the Social Share reference in Bricks) is clearly signaled with a direct link — one level deep with no nesting. Content is appropriately split: nothing that belongs elsewhere is inlined.

Specificity

It names the domain ('Social Share construction') and one or two concrete actions ('install and use component-builder to build a new Social Share'), matching anchor 3. It is not a 4 because it does not list several specific capabilities — appropriate for a deprecated entry, but not comprehensive coverage.

Completeness

The 'what' is clear — a deprecated compatibility entry redirecting to Bricks — but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. The instruction to install component-builder is a redirect directive, not a trigger condition.

Trigger Term Quality

'Social Share' is a natural term a user would say, but common variations and synonyms ('share buttons', 'share links', 'social sharing') are absent, matching anchor 3 ('Some relevant keywords but missing common variations or synonyms'). It does not reach anchor 4's 'good keyword coverage'.

Distinctiveness Conflict Risk

'Social Share construction' is a distinct niche, but the description explicitly names the successor ('component-builder', 'Bricks'), creating overlap risk: it could trigger on generic component-building queries intended for the successor skill. This fits anchor 3 ('Somewhat specific but could still overlap with similar skills') better than anchor 4.