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 find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market
$ npx -y skills add kostja94/marketing-skills --skill research-sources --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/research-sourcesContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market
name: research-sources description: When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research. metadata: version: 1.1.1
Guides selecting and organizing information sources for marketing research: content ideation, competitor monitoring, and industry tracking. Use this skill when planning where to gather signals for content, competitive intelligence, or market trends.
**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 case | Purpose | |----------|---------| | **Content ideation** | Topic ideas, trends, gaps for blog, newsletter, social | | **Competitor monitoring** | Product updates, positioning, pricing, reviews | | **Industry tracking** | Market shifts, funding, layoffs, regulatory changes |
| Category | Format | Use | |----------|--------|-----| | **News** | Real-time, daily | Breaking news, announcements | | **Blogs** | Company, analyst | Deep dives, product updates | | **Newsletters** | Curated, weekly/daily | Trends, summaries; low effort | | **Events** | Conferences, webinars | Industry pulse, networking | | **Data** | Layoffs, market cap, funding | Quantitative signals | | **Community** | Forums, Q&A | Real questions, pain points | | **Archives** | Wayback, Internet Archive | Historical content, competitor changes |
**Selection criteria**: Authority, freshness, coverage, language/locale. Prefer 10–15 high-quality sources over 50+ low-signal ones.
| Category | Examples | |----------|----------| | **News** | TechCrunch, VentureBeat, MIT Technology Review | | **Blogs** | Google AI Blog, OpenAI Blog, company blogs | | **Newsletters** | TLDR AI, Ben's Bites, The Batch (DeepLearning.AI) | | **Data** | Layoffs.fyi, Crunchbase, Companies Market Cap | | **Archives** | Internet Archive, Wayback Machine | | **Community** | Reddit, Quora, Stack Overflow; regional (e.g. Qiita for Japan) |
**Note**: Add locale-specific sources via **localization-strategy**; avoid long URL lists.
| Use case | Source types | |----------|--------------| | **Content ideation** | News, blogs, newsletters, community (Reddit, Quora, Stack Overflow) | | **Competitor monitoring** | Competitor blogs, review sites, social, funding databases | | **Industry tracking** | News, newsletters, events, layoff/funding data |
**Avoid**: Long URL lists that go stale. Use category framework + a few examples; update periodically.
| Skill | How research sources feed in | |-------|------------------------------| | **keyword-research** | Newsletters, community for long-tail and question keywords | | **competitor-research** | Competitor blogs, review platforms, funding data | | **content-marketing** | News, blogs for topic ideas; events for timely content | | **content-strategy** | Industry trends for pillar/cluster planning |
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,"…