mcpbeat

Resources Page Generator

kostja94/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.

836 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/kostja94/marketing-skills --skill resources-page-generator

The instruction itself

11 sections, as written by the author

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

How to use it

Copy the folder

Take kostja94/resources-page-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.