google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search…
When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card
$ npx -y skills add kostja94/marketing-skills --skill card --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/cardContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card
name: card description: When the user wants to design, optimize, or audit card layouts for content display. Also use when the user mentions "card layout," "card component," "card grid," "product cards," "template cards," "tool cards," "feature cards," "gallery cards," "integration cards," or "card design." For grids, use grid. metadata: version: 1.1.1
Guides card layout design for scannable, responsive content display. Cards are self-contained containers that group related content; used in grids for blog posts, products, templates, tools, features, galleries, and integrations.
**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.
| Element | Purpose | |---------|---------| | **Container** | Border, background, shadow; consistent padding | | **Image / Thumbnail** | Visual anchor; consistent aspect ratio (1:1, 4:3 common) | | **Title** | Clear; keyword-rich where relevant | | **Description / Metadata** | Supporting text; date, author, category | | **CTA** | Action button or link; "View," "Use," "Connect," etc. |
**Principle**: One card = one topic. Keep each card focused for scannability.
| Type | Typical Elements | Page Skill | |------|------------------|------------| | **Product card** | Image, name, price, CTA (Add to cart, View) | **products-page-generator** | | **Template card** | Thumbnail, name, short description, "Use" or "Preview" CTA | **template-page-generator** | | **Tool card** | Name, one-line benefit, CTA to tool page | **tools-page-generator** | | **Feature card** | Name, benefit, optional screenshot | **features-page-generator** | | **Gallery / Showcase item** | Thumbnail, title, creator, link | **showcase-page-generator** | | **Integration card** | Logo, name, short description, "Connect" or "Install" | **integrations-page-generator** | | **Blog / Article card** | Cover image, title, excerpt, date, author | **blog-page-generator**, **article-page-generator** | | **Resource card** | Thumbnail, title, format (guide, webinar), CTA | **resources-page-generator** |
| Principle | Practice | |-----------|----------| | **Visual hierarchy** | Title > description > CTA; clear flow | | **Scannability** | Minimal text; benefit-led copy | | **Consistency** | Same structure across all cards in a grid | | **Action clarity** | One primary CTA per card; avoid choice overload |
| Layout | Best for | Skill | |--------|----------|-------| | **Grid** | Visual content (products, templates, gallery); equal emphasis | **grid** | | **List** | Text-heavy (blog index, docs); compact; scan by title | **list** | | **Masonry** | Varying heights; image gallery, portfolio | **masonry** | | **Carousel** | Limited space; testimonials, logos, featured rotation | **carousel** |
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search…
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…
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…
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic,"…
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4,"…
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker,"…