resources-page-generator
The resources-page-generator skill guides the creation and optimization of resources pages and content hubs by establishing structure for discovery and SEO. Use it when users need to build, audit, or improve a resources page, resource center, content hub, learning center, or similar content repository. The skill provides assessment of content types and audience, recommends organizational strategies through categories and filters, advises on navigation placement, and outlines internal linking and metadata approaches to support both user success and search visibility.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/resources-page-generator && cp -r /tmp/resources-page-generator/skills/pages/content/resources ~/.claude/skills/resources-page-generatorSKILL.md
# 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
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.