ValentinNikolaev/agent-skills / agent-plugins/skills/github-pages-content
github-pages-content
VerifiedOrganize GitHub Pages content, reader tasks, navigation, copy, and local search from verified repository sources. Use for Pages content work, not general product information architecture.
GitHub Pages: Content
Turn repository evidence into a small, findable Pages site whose structure matches real reader tasks.
Stay inside the Pages boundary
- Establish the repository's readers, public URL shape, existing routes, documentation sources, and first successful task before proposing structure.
- Treat README files, maintained docs, examples, schemas, changelogs, contribution guidance, security policy, and license as evidence. Do not invent missing content.
- Prefer links or generated imports over copied canonical facts.
- Design for static generation and client-side behavior. Do not prescribe server search, personalization, accounts, or analytics unless another authorized system provides them.
- Preserve existing public routes and anchors; content reorganization does not authorize URL breakage.
- When the request also requires implementing framework, route, build, or deployment changes, hand those concerns to
github-pages-createand keep this skill focused on the content model.
Read the contract
Read references/pages-content-contract.md before designing or restructuring the site's content, navigation, labels, or search.
For a handoff to design or implementation, use the family's shared format. Tie it to the inspected revision and relevant working files. Keep a small task's handoff inline rather than creating mandatory ledgers.
Produce a reviewable content plan
Record:
- intended readers and their priority tasks;
- source-of-truth files and freshness for each proposed page or section, including verified Wiki material when available;
- current and proposed page hierarchy;
- global, local, utility, and contextual navigation;
- route and anchor preservation requirements, including heading changes that alter generated slugs, for the implementation owner;
- content gaps, duplicates, and unsupported claims;
- search behavior when the content scale justifies it;
- concise copy rules derived from repository terminology and branding.
Omit empty destinations. Prefer one complete page over a shallow collection of placeholders.
If repository evidence or the current route inventory is unavailable, label the result provisional. Provide the smallest useful candidate structure plus the exact files, routes, or configuration needed to turn it into a verified plan; do not present guessed pages or mappings as final.
Verify the result
- Every page must serve a named reader task and trace material claims to repository evidence.
- Navigation labels must predict their destinations and remain consistent with headings and search terms.
- Check applicable reader journeys. Mark absent nested docs, search, or changed legacy routes
not applicablewith a reason. Do not add features just to satisfy a checklist. - A reader must be able to complete the primary task without guessing prerequisites or crossing broken links.
- Search, when present, must be local or explicitly authorized, keyboard reachable, and tested with representative repository terms.
- Report unresolved content ownership, freshness, route, and terminology questions rather than guessing.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |