Blog Strategy
AgriciDaniel/claude-blog
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/blog-strategy .claude/skills/blog-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "blog-strategy" agent skill from https://github.com/Infrasity-Labs/dev-gtm-claude-skills/tree/main/.claude/skills/blog-strategy into .claude/skills/blog-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Infrasity-Labs/dev-gtm-claude-skills/tree/main/.claude/skills/blog-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/blog-strategy .agents/skills/blog-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "blog-strategy" agent skill from https://github.com/Infrasity-Labs/dev-gtm-claude-skills/tree/main/.claude/skills/blog-strategy into .agents/skills/blog-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/blog-strategy .cursor/skills/blog-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "blog-strategy" agent skill from https://github.com/Infrasity-Labs/dev-gtm-claude-skills/tree/main/.claude/skills/blog-strategy into .cursor/skills/blog-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git --path .claude/skills/blog-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/blog-strategy .gemini/skills/blog-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "blog-strategy" agent skill from https://github.com/Infrasity-Labs/dev-gtm-claude-skills/tree/main/.claude/skills/blog-strategy into .gemini/skills/blog-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/blog-strategy .github/skills/blog-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "blog-strategy" agent skill from https://github.com/Infrasity-Labs/dev-gtm-claude-skills/tree/main/.claude/skills/blog-strategy into .github/skills/blog-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills blog-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/blog-strategy .opencode/skills/blog-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "blog-strategy" agent skill from https://github.com/Infrasity-Labs/dev-gtm-claude-skills/tree/main/.claude/skills/blog-strategy into .opencode/skills/blog-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "blog-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
blog-strategyBlog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…
Blog Strategy is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for GEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience. Use when user says "blog strategy", "content strategy", "blog positioning", "what should I blog about"…
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Content strategy, AI search optimization and Web search. It works with OpenAI, Perplexity, Reddit and YouTube. The repository describes itself as: Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and… The licence is MIT.
11 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 02cfefb. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Blog Strategy loads about 3.8k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 1,018 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Infrasity-Labs/dev-gtm-claude-skills at commit 02cfefb, republished under its MIT licence (© Infrasity-Labs). 1,018 words, ~3,836 tokens.
.claude/skills/blog-strategy/SKILL.md (or your agent's skills folder).Develops comprehensive blog strategies that build topical authority for Google rankings while establishing brand presence for AI citation platforms. Includes topic cluster architecture, AI citation surface strategy, content scoring targets, and GEO-specific optimization plans.
Research discipline references (v1.8.0):
skills/blog/references/research-quality.md - 5-dim rubric, pre-flight trap classes, cross-source clustering, freshness floorsskills/blog/references/synthesis-contract.md - 6 LAWs for synthesis outputAuto-loaded inputs (v1.8.0): when DISCOURSE.md exists at the project root (from /blog discourse), load it for cross-platform discourse signal alongside this skill's authority-source planning.
Strategy planning should consider the FLOW 5-surface model (owned site, SERP plus AI Overviews, AI assistant citations, local pack, communities and video). Local-pack work is delegated to claude-seo; everything else lives inside claude-blog. Full mapping in skills/blog/references/flow-alignment.md.
For evidence-led audience-avatar, keyword-research, and content-prioritization prompts that feed strategic planning, see /blog flow find.
Gather context through questions or project analysis:
Research competitors' blogs:
Map competitor visibility across AI platforms. Use WebSearch to find how competitors appear in AI-generated responses for target keywords.
## Competitive AI Citation Map
| Query | ChatGPT Cites | Perplexity Cites | AI Overview Cites | Gap? |
|-------|--------------|-----------------|-------------------|------|
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |
| [keyword] | [competitor/none] | [competitor/none] | [competitor/none] | [Yes/No] |Score each competitor's AI visibility:
Identify AI citation gaps: queries where no competitor is cited. These represent the highest-opportunity targets for new content.
Note: only 12% overlap between platforms. A competitor strong on ChatGPT may be absent from Perplexity. Analyze each platform independently.
Define 2-3 audience segments:
### Audience Segment: [Name]
- **Role**: [Job title / description]
- **Pain points**: [What problems do they have?]
- **Search behavior**: [What do they Google?]
- **AI behavior**: [What do they ask ChatGPT/Perplexity?]
- **Content preferences**: [Long guides? Quick answers? Video?]
- **Buying stage**: [Awareness / Consideration / Decision]Design 3-5 content pillars based on audience needs and competitive gaps. For each pillar, build the full hub-and-spoke cluster model.
### Pillar: [Topic Area]
- **Purpose**: Build authority in [topic]
- **Primary keywords**: [3-5 keywords]
- **Content types**: Pillar guide, supporting posts, comparisons, FAQ
- **Unique angle**: [What first-hand experience/data can you provide?]
- **Estimated posts**: [N] to achieve topic coverage
- **AI citation potential**: [High/Medium/Low] - [why]For each pillar, design the complete hub-and-spoke structure:
### Cluster Architecture: [Pillar Topic]
┌──────────────────┐
│ Pillar Page │
│ 3,000-4,000w │
└────────┬─────────┘
│
┌─────────────────┼──────────────────┐
│ │ │
┌──────▼──────┐ ┌─────▼──────┐ ┌───────▼──────┐
│ Spoke #1 │ │ Spoke #2 │ │ Spoke #3 │
│ 1,500-2,500│ │ 1,500-2,500│ │ 1,500-2,500 │
└──────┬──────┘ └─────┬──────┘ └───────┬──────┘
│ │ │
└────────────────┼───────────────────┘
(cross-links between spokes)For each cluster, specify:
how-to-guide, listicle, case-study, comparison, pillar-page,
product-review, thought-leadership, roundup, tutorial,
news-analysis, data-research, faq-knowledge### Cluster Build Plan: [Pillar Topic]
| # | Spoke Topic | Template | Target Keyword | Word Count | Internal Links |
|---|------------|----------|---------------|-----------|----------------|
| P | [Pillar title] | pillar-page | [keyword] | 3,000-4,000 | Links to all spokes |
| 1 | [Spoke title] | how-to-guide | [keyword] | 1,500-2,500 | Pillar + Spokes 2,3 |
| 2 | [Spoke title] | comparison | [keyword] | 1,500-2,500 | Pillar + Spokes 1,3 |
| 3 | [Spoke title] | listicle | [keyword] | 1,500-2,500 | Pillar + Spokes 1,2 |
| ... | ... | ... | ... | ... | ... |Reference: references/internal-linking.md for hub-and-spoke model and anchor text rules.
The December 2025 Core Update rewards first-hand experience. Plan how to demonstrate genuine expertise:
| Signal Type | Implementation |
|---|---|
| Original data | Conduct surveys, analyze proprietary data, run experiments |
| Case studies | Document real client/project results with metrics |
| Build in public | Share process, learnings, and failures transparently |
| Expert interviews | Feature practitioners with first-hand knowledge |
| Tool reviews | Test products personally, share screenshots and results |
| Industry analysis | Provide unique perspective on public data |
Plan how to maximize AI citation across platforms. 80% of LLM citations come from outside the top 100 organic results. Traditional SEO alone is insufficient.
Structure every piece of content for AI citability:
| Channel | AI Citation Impact | Priority Action |
|---|---|---|
| YouTube | 0.737 correlation (strongest) | Companion videos for pillar posts |
| 450% citation surge | Authentic participation in 3-5 subreddits | |
| Review platforms | 2.6-3.5x multiplier | Maintain profiles on G2, Capterra (B2B) |
| Wikipedia/Wikidata | Credibility tiebreaker | Build notability, create Wikidata entry |
| Industry publications | Tier 2-3 citation source | Guest posts, expert commentary |
Reference: references/geo-optimization.md for detailed GEO tactics.
Set quality standards that all blog content must meet:
### Content Quality Standards
| Metric | Target | Measured By |
|--------|--------|-------------|
| Blog quality score | 80+ | `/blog analyze` |
| E-E-A-T compliance | Named author + 8+ tier 1-3 sources | Manual review |
| AI citation readiness | Answer-first + FAQ + citation capsules | `/blog analyze` |
| Visual minimum | 2+ charts + 3+ images per post | Asset count |
| Internal links | 5+ per post (within cluster) | Link audit |
| Schema markup | Article + FAQ + relevant type | Structured data test |
| Word count | 1,500+ for spokes, 3,000+ for pillars | Word count tool |Every post should be scored before publishing. Posts below 80 quality score should be revised before going live.
Plan passage-level citability across all content, tailored to each AI platform.
| AI Platform | Favors | Optimization Focus |
|---|---|---|
| ChatGPT | Recency, brand authority, conversational clarity | Update posts within 30 days, clear entity definitions |
| Perplexity | Citations, source diversity, structured answers | Tier 1-3 sources, numbered lists, data tables |
| Google AI Overviews | Structured data, schema, topical authority | FAQ schema, HowTo schema, complete topic clusters |
Strategy by platform:
Reference: references/geo-optimization.md for platform-specific optimization guides.
AI visibility requires off-site presence (88-92% of AI citations come from off-site signals). Plan brand presence:
| Channel | AI Impact | Strategy |
|---|---|---|
| YouTube | 0.737 correlation (strongest) | Companion videos for pillar posts, how-tos, demos |
| 450% citation surge | Authentic participation in 3-5 subreddits, share insights not links | |
| Review platforms | 2.6-3.5x citation multiplier | Maintain profiles on G2, Capterra, TrustRadius (B2B) |
| Wikipedia/Wikidata | Credibility tiebreaker | Build notability through earned media, create Wikidata entry |
| Industry publications | Tier 2-3 citation source | Guest posts, expert commentary, study contributions |
| Social media | Brand mentions | LinkedIn thought leadership, Twitter/X insights |
Budget allocation recommendation: 40% owned content / 60% earned media and distribution.
Reference: references/distribution-playbook.md for detailed channel tactics and templates.
### Metrics to Track
#### Traditional SEO
- Organic traffic (monthly)
- Keyword rankings (top 10, top 3)
- Domain authority / Domain Rating
- Internal link coverage
- Core Web Vitals
#### AI Citation Metrics (New)
- Share of Voice in ChatGPT responses (manual tracking)
- AI Overview citation rate (Google Search Console)
- Perplexity mentions (manual tracking)
- AI referral traffic (GA4: source contains chatgpt, perplexity, claude)
- Brand mention volume (branded search + web mentions)
#### Content Quality
- Blog quality score via `/blog analyze` (target: 80+)
- Content freshness (% of posts updated within 30 days)
- Visual element coverage (charts + images per post)
- Citation tier quality (% tier 1-3 sources)
#### Business Impact
- Blog-attributed leads/conversions
- Email subscribers from blog
- Content-assisted revenueOutput format:
# Blog Strategy: [Business Name]
## Executive Summary
[2-3 sentences on the strategic direction]
## Audience
[Segment summaries]
## Content Pillars & Cluster Architecture
[3-5 pillars with full hub-and-spoke cluster plans]
[Internal linking map for each cluster]
[Template assignments for each piece]
## Competitive Positioning
[How we differentiate - what unique value we bring]
[Competitive AI Citation Map showing gaps to exploit]
## AI Citation Surface Strategy
[On-site optimization checklist]
[Off-site presence plan with priority channels]
[Platform-specific GEO tactics]
## Content Quality Standards
[Scoring targets for all content]
[E-E-A-T compliance requirements]
## Distribution Channels
[Priority channels with specific tactics]
## Content Velocity
- New posts: [N]/week
- Freshness updates: [N]/month
- Visual elements: [N] charts + [N] images per post
## 90-Day Roadmap
### Month 1: Foundation
- [ ] Publish [Pillar 1] guide + [N] supporting spokes
- [ ] Set up YouTube channel / Reddit profiles
- [ ] Establish measurement dashboard
- [ ] Complete competitive AI citation audit
### Month 2: Expansion
- [ ] Publish [Pillar 2] guide + [N] supporting spokes
- [ ] First freshness update cycle
- [ ] Begin Reddit/YouTube distribution
- [ ] Launch off-site presence on review platforms
### Month 3: Optimization
- [ ] Audit all posts with `/blog analyze` (target: 80+ score)
- [ ] Optimize lowest-scoring posts
- [ ] Publish [Pillar 3] guide
- [ ] Review AI citation metrics across all platforms
- [ ] Adjust strategy based on data
## Measurement
[KPIs and tracking approach - traditional SEO + AI citation metrics]
## Reference Documents
- `references/internal-linking.md` - Hub-and-spoke model, anchor text rules
- `references/distribution-playbook.md` - Channel tactics and templates
- `references/geo-optimization.md` - GEO platform-specific optimization
- `references/content-templates.md` - 12 content templates with structures
## Next Steps
1. Run `/blog calendar` to create the first month's editorial calendar
2. Run `/blog brief` for the first pillar page
3. Run `/blog write` to generate the first article
4. Set up AI citation monitoring for target queries© Infrasity-Labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/blog-strategy of Infrasity-Labs/dev-gtm-claude-skills.
Open the folder on GitHubat commit 02cfefb
Blog Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Blog Strategy this skillInfrasity-Labs/dev-gtm-claude-skills | 136 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Blog StrategyAgriciDaniel/claude-blog | 2.3k | — | ~4.4k | Automated safety check: Pass | MIT | |
| AI Search Optimizationsocial-media-skills/skills | 134 | — | ~2k | Automated safety check: Pass | MIT | |
| SEO AgiLeoYeAI/openclaw-master-skills | 2.2k | — | ~6.4k | Automated safety check: Notes | MIT | |
| Geo Fundamentalswasp-lang/wasp | 19k | 9 repos | ~861 | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 540 | — | ~2.5k | Automated safety check: Pass | MIT |
AgriciDaniel/claude-blog
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…
social-media-skills/skills
A skill your agent uses to get a brand and its content CITED and RECOMMENDED by AI answer engines — the GEO (Generative Engine Optimization) / AI-search-visibility skill.
LeoYeAI/openclaw-master-skills
Write SEO pages that rank in Google AND get cited by LLMs (ChatGPT, Perplexity, Claude).
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
liangdabiao/GEO-Content-Optimizer-Skill
完整的 GEO(生成式引擎优化)服务流水线:给一个产品官网 URL 和介绍材料, 做站点诊断与 AI 答案采样、生成带验收标准的执行工单、产出可直接部署的资产 (llms.txt / JSON-LD / 定义块 / FAQ / 内容大纲与初稿)、自动验收工单是否闭环、 并打包成可直接发给客户的交付物。可按周期复跑,做长期 GEO 运营与月报。
Infrasity-Labs/dev-gtm-claude-skills
Generates a fully structured SEO content outline (not a finished brief) and exports it as a formatted .docx Word document.
Infrasity-Labs/dev-gtm-claude-skills
Generates a fully structured SEO content brief for a target keyword and optionally pushes it to a Notion database.
Infrasity-Labs/dev-gtm-claude-skills
Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and…
Infrasity-Labs/dev-gtm-claude-skills
Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check.
Infrasity-Labs/dev-gtm-claude-skills
Generates a 3-month SEO performance HTML report for any domain using DataForSEO data.
Infrasity-Labs/dev-gtm-claude-skills
Email triage system that handles both one-time setup and recurring triage in a single skill.
Works with
Categories
Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI…. Blog Strategy is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. Blog strategy development including topic cluster architecture with hub-and-spoke design, audience mapping, competitive landscape analysis, AI citation surface strategy across ChatGPT/Perplexity/AI Overviews, distribution channel planning (YouTube, Reddit, review platforms for GEO), content scoring targets, measurement framework, and content differentiation through original research and first-hand experience.
Blog Strategy fits situations like: user says blog strategy; content strategy; blog positioning; what should I blog about.
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a claude-code`. Or copy the skill folder (.claude/skills/blog-strategy in Infrasity-Labs/dev-gtm-claude-skills) into .claude/skills/blog-strategy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a codex`. Or copy the skill folder (.claude/skills/blog-strategy in Infrasity-Labs/dev-gtm-claude-skills) into .agents/skills/blog-strategy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill blog-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/blog-strategy, .gemini/skills/blog-strategy, .github/skills/blog-strategy and .opencode/skills/blog-strategy in your project.
SKILL.md names no scripts, command-line tools or credentials: Blog Strategy is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Blog Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Blog Strategy: Blog Strategy (AgriciDaniel/claude-blog, 2.3k stars), AI Search Optimization (social-media-skills/skills, 134 stars), SEO Agi (LeoYeAI/openclaw-master-skills, 2.2k stars) and Geo Fundamentals (wasp-lang/wasp, 19k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Infrasity-Labs (a GitHub user) maintains it in Infrasity-Labs/dev-gtm-claude-skills, which has 136 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on June 28, 2026.
Source: Infrasity-Labs/dev-gtm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.