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 list layouts for content display. Also use when the user mentions "list layout," "list design," "vertical list," "stacked list," "blog list," "article list," "documentation list," "search results layout," or "infinite scroll
$ npx -y skills add kostja94/marketing-skills --skill list --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/listContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to design, optimize, or audit list layouts for content display. Also use when the user mentions "list layout," "list design," "vertical list," "stacked list," "blog list," "article list," "documentation list," "search results layout," or "infinite scroll
name: list description: When the user wants to design, optimize, or audit list layouts for content display. Also use when the user mentions "list layout," "list design," "vertical list," "stacked list," "blog list," "article list," "documentation list," "search results layout," or "infinite scroll list." For blog index page, use blog-page-generator. metadata: version: 1.1.1
Guides list layout design for linear, stacked content display. Lists are compact, text-heavy; users scan by title or metadata. Used for blog indexes, documentation, search results, and dense content.
**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.
| Use list when | Use grid when | |---------------|---------------| | Text-heavy; scan by title | Visual content; equal emphasis | | Many items; compact display | Fewer items; browsing | | Blog index, docs, search results | Products, templates, gallery | | F-pattern reading (top-left, left column) | Discovery, exploration |
See **grid** for grid layout; **card** for card structure.
| Element | Purpose | |---------|---------| | **Items** | Single column; stacked vertically | | **Per item** | Title, optional metadata (date, author), excerpt, link | | **Spacing** | Consistent gaps; dividers or alternating background | | **Density** | Compact (docs) vs relaxed (blog) |
| Variant | Use | |---------|-----| | **Simple list** | Title + link; minimal (nav, TOC) | | **Rich list** | Title, excerpt, date, author | Blog index | | **Table-like** | Columns for metadata (date, status) | Docs, admin | | **With thumbnail** | Small image + text | Blog with thumbnails |
| Principle | Practice | |-----------|----------| | **Scannable** | Clear titles; consistent hierarchy | | **Compact** | Less vertical space than grid | | **Link area** | Full row or title clickable | | **Metadata** | Date, author, category; secondary styling |
Users read top-left first, then scan left column. Place primary content (titles) left-aligned; metadata secondary.
If using infinite scroll for list (e.g., blog index, search results): crawlers cannot access content loaded on scroll. Provide paginated component pages or use traditional pagination for SEO-critical content. See **site-crawlability** for search-friendly infinite scroll implementation.
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,"…