resources-page-generator
When the user wants to create, optimize, or audit resources page or content hub. Also use when the user mentions "resources page," "resource center," "content hub," "learning center," "resource library," "downloads," "templates," "guides," or "resource hub." For content hub planning, use content-strategy.
Best use case
resources-page-generator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to create, optimize, or audit resources page or content hub. Also use when the user mentions "resources page," "resource center," "content hub," "learning center," "resource library," "downloads," "templates," "guides," or "resource hub." For content hub planning, use content-strategy.
Teams using resources-page-generator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/resources/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How resources-page-generator Compares
| Feature / Agent | resources-page-generator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to create, optimize, or audit resources page or content hub. Also use when the user mentions "resources page," "resource center," "content hub," "learning center," "resource library," "downloads," "templates," "guides," or "resource hub." For content hub planning, use content-strategy.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Pages: Resources Guides resources page and content hub structure for discovery and SEO. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for content themes and audience. Identify: 1. **Content types**: Blog, guides, webinars, templates, tools (or standalone /tools; see **tools-page-generator**) 2. **Audience**: Buyers, users, both 3. **Funnel stage**: Top, middle, bottom ## Best Practices ### Purpose - **Help buyers buy**: Content that supports decision-making - **Help users succeed**: How-to, best practices - **SEO**: Organize for discoverability and topical authority ### Structure | Element | Purpose | |---------|---------| | **Categories** | By topic, format, or funnel stage | | **Filters** | Format (blog, guide, video), topic, date | | **Featured** | Highlight key assets | | **Search** | Help users find specific content | | **Contextual embeds** | Resource tiles on product pages | ### Navigation - **Visible**: Resources in main nav or top-level section - **Not buried**: Higher than content hubs in hierarchy - **Clear labels**: "Resources," "Learn," "Content Library" ### Organization - **Avoid junk drawer**: Intentional structure; not a catch-all - **Logical hierarchy**: Folders, tags, categories - **Internal linking**: Connect related content ### Integration - **Product pages**: Embed relevant resources (streams, tiles) - **Landing pages**: Lead magnet (ebook, template) or webinar as resource; LP exchanges value for email - **Blog**: Part of resources or separate with cross-links - **Glossary**: Link from resources ## Tools Integration - **Standalone /tools**: When many free tools; use **tools-page-generator**; toolkit hub + per-tool pages - **Resources section**: When few tools; embed tool cards in resources hub ## Output Format - **Structure** (categories, filters) - **Navigation** placement - **Content** types to include - **Internal linking** strategy - **SEO** metadata ## Related Skills - **card**: Resource card structure; thumbnail, title, format, CTA; tiles in hub - **grid**: Resource hub grid layout; tiles - **tools-page-generator**: Standalone /tools when many free tools; toolkit hub - **landing-page-generator**: Lead magnet (ebook, webinar) as LP offer; LP exchanges resource for email - **url-slug-generator**: URL slug for resource pages (e.g. /resources/guide-slug); 3-5 words - **blog-page-generator**: Blog may be part of resources - **glossary-page-generator**: Glossary as resource - **tools-page-generator**: Standalone /tools when many free tools; toolkit hub - **content-strategy**: Content hub strategy - **internal-links**: Resource page linking
Related Skills
page-metadata
When the user wants to optimize meta tags other than title, description, Open Graph, or Twitter Cards. Also use when the user mentions "hreflang," "meta robots," "viewport," "charset," "canonical meta," "other meta tags," "meta robots noindex," "meta robots nofollow," "hreflang tags," "viewport meta," or "meta charset." For title tags, use title-tag. For meta descriptions, use meta-description. For Facebook/LinkedIn previews, use open-graph. For X previews, use twitter-cards.
status-page-generator
When the user wants to create, optimize, or structure a status page. Also use when the user mentions "status page," "status.yourdomain.com," "uptime," "service health," "incident page," or "system status." For incident comms, use public-relations.
signup-login-page-generator
When the user wants to create, optimize, or audit signup and login pages. Also use when the user mentions "signup page," "login page," "registration page," "auth page," "sign up form," "create account," "student discount at signup," or "auth subdomain." For indexing/auth URLs, use indexing.
feedback-page-generator
When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.
disclosure-page-generator
When the user wants to create, optimize, or audit an affiliate, sponsor, or paid partnership disclosure page. Also use when the user mentions "disclosure," "affiliate disclosure," "sponsored content," "FTC disclosure," or "paid partnership." For sitewide page planning, use website-structure.
changelog-page-generator
When the user wants to create, optimize, or structure a changelog or release notes page. Also use when the user mentions "changelog," "release notes," "what's new," "updates," "product updates," "version history," or "changelog.yourdomain.com." For sitewide page planning, use website-structure.
use-cases-page-generator
When the user wants to create, optimize, or audit use case pages. Also use when the user mentions "use cases," "use case page," "for [role]," "by persona," "by scenario," "by business goal," "ICP pages," or "audience-specific pages." For sitewide page planning, use website-structure.
startups-page-generator
When the user wants to create, optimize, or audit a startups, education, or special program page. Also use when the user mentions "startups program," "for startups," "education discount," "student plan," "for students," or "special pricing." For education discounts, use education-program.
solutions-page-generator
When the user wants to create, optimize, or audit solutions pages. Also use when the user mentions "solutions," "solutions page," "by industry," "industry solutions," "by company size," "SMB," "enterprise," "by outcome," "business outcomes," or "how we solve X." For sitewide page planning, use website-structure.
showcase-page-generator
When the user wants to create, optimize, or audit a showcase or gallery page for user-generated content. Also use when the user mentions "showcase," "gallery," "user work," "UGC," "creator showcase," "examples," or "made with [product]." For social proof components, use testimonials-generator.
services-page-generator
When the user wants to create, optimize, or audit a services page. Also use when the user mentions "services page," "what we offer," "service offerings," "consulting services," "service page," "offerings page," "service catalog," or "professional services." For sitewide page planning, use website-structure.
products-page-generator
When the user wants to create, optimize, or audit a product listing or category page. Also use when the user mentions "product page," "product listing," "shop," "e-commerce products," "product catalog," "product grid," "product cards," or "product overview." For category SEO, use category-page-generator.