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.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for content themes and audience.
Identify:
| 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 |
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
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/resources · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/resources"
cp -r "skills/pages/content/resources" ".claude/skills/resources"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.