Conciseness

The body is lean and instructive throughout: a component table ("Wrap every middle band in it", "colSpan/rowSpan for emphasis"), terse copy rules ("one sentence, under 20 words, concrete... never 'powerful', 'seamless' or 'next-generation'"), and executable TSX with no padding. It never explains concepts Claude already knows (React, routing, CSS variables), matching the 5-anchor "every token earns its place" rather than 4, where over-explanation would still be present.

Actionability

The main scaffold is copy-paste ready (full LandingHero/LandingSection/InstallBanner TSX and a complete renderLink implementation with "pass one shared renderLink so internal links use the router"), plus concrete limits like "at most two hero actions" and "give the most expressive component colSpan={2} rowSpan={2}". It falls short of 5 because BentoGrid, CodeShowcase, and FeatureGrid appear only as table rows and the scaffold leaves "{/* BentoGrid of live tiles */}" as a placeholder, deferring those props to external doc URLs.

Workflow Clarity

The build sequence is explicit and numbered ("Default order... 1. LandingHero... 5. InstallBanner" with "Drop a band rather than filling it with filler"), wiring steps follow, and the "Review checklist" provides explicit validation checkpoints ("Every link resolves", "At 375px wide the hero stacks", "Nothing animates under prefers-reduced-motion"). This matches the 5-anchor's checklist-for-complex-processes criterion; no destructive or batch operations exist that would require a fix-and-retry loop or impose the cap at 3.

Progressive Disclosure

Structure is good: a component table, clear section headers, and a well-signaled one-level-deep delegation ("Read each one's page before using a prop you have not seen here: https://ui.lobehub.com/skills/components/awesome/<kebab-name>.md") that externalizes per-component prop detail. It is not 5 because the ~150-line body inlines detailed sections (AgentSkillCard content rules, full copy rules) that could live in local reference files, and navigation relies on external URLs rather than a bundled, discoverable reference set — matching the 4-anchor ("good structure; minor organization gaps") over the 3-anchor, since references are clearly signaled and nothing is buried.

Specificity

Quotes like "Compose a product or documentation home page from the @lobehub/ui/awesome landing components: LandingHero, AgentSkillCard, LogoMarquee..." and "Covers page structure, the lobedocs homePage hook, router links, theming the accent gradient, and a review checklist" enumerate nine concrete components and several concrete sub-tasks, matching the comprehensive multi-action anchor. It exceeds the 4-anchor ("several specific actions; minor gaps") because coverage spans components, wiring, theming, and validation with no obvious omission.

Completeness

The 'what' is explicit ("Compose a product or documentation home page from the ... landing components") and the 'when' is explicit ("Trigger on build a home page, landing page, docs home...") with concrete trigger phrases, matching the 5-anchor exactly. It is not a 4 because the 'when' clause is not merely present but enumerates specific user phrasings rather than a generic 'Use when working with...' statement.

Trigger Term Quality

"Trigger on build a home page, landing page, docs home, marketing page, hero section, redesign home, lobedocs homePage, 首页, 落地页, 官网首页" gives comprehensive natural-phrase coverage including synonyms (home page / docs home / marketing page), a product-specific term (lobedocs homePage), and multilingual variants. It fits the 5-anchor ("comprehensive coverage of natural terms including synonyms") rather than 4 because even likely user phrasings like "redesign home" and CJK terms are included.

Distinctiveness Conflict Risk

Component names and "lobedocs homePage" carve a clear niche, but broad triggers like "build a home page", "marketing page" and "hero section" could overlap with other site-building or UI skills, matching the 4-anchor ("mostly distinct; minor overlap risk with closely related skills"). It is not 5 because those generic landing/home triggers are not uniquely tied to @lobehub/ui; not 3 because the framework-specific terms anchor it well.