How to install resources-page-generator
npx skills add https://github.com/kostja94/marketing-skills --skill resources-page-generatorFull instructions (SKILL.md)
Source of truth, from kostja94/marketing-skills.
name: resources-page-generator description: 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. metadata: version: 1.0.1
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:
- Content types: Blog, guides, webinars, templates, tools (or standalone /tools; see tools-page-generator)
- Audience: Buyers, users, both
- 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
More from kostja94/marketing-skills and the wider catalog.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
robots-txt
When the user wants to configure, audit, or optimize robots.txt. Also use when the user mentions "robots.txt," "crawler rules," "block crawlers," "AI crawlers," "GPTBot," "allow/disallow," "disallow path," "crawl directives," "user-agent," "block Googlebot," "fix robots.txt," "robots.txt blocking," or "search engine crawling." For indexing, use indexing.
schema-markup
When the user wants to add or optimize structured data (Schema.org, JSON-LD). Also use when the user mentions "schema," "structured data," "JSON-LD," "rich results," "rich snippets," "Google rich snippets," "featured snippet schema," "add schema to page," "missing structured data," "schema validation error," "Schema Markup Validator," "Google Rich Results Test," "FAQ schema," "Article schema," "Organization schema," "JobPosting," "HowTo," "Event," "SoftwareApplication," "BreadcrumbList," "WebSite," "Recipe," "Product," or "Dataset." For SERP feature types and zero-click patterns, use serp-features. For AI search visibility strategy (not markup), use generative-engine-optimization. For HowTo step sections (placement, copy, vs FAQ), use howto-section-generator.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document," "SEO dashboard," "keyword tracking," "ranking monitoring," "indexing report," or "backlink monitoring." For GSC API, use google-search-console.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.