blog-write
Skill0 starsChanged 3 months agoMITView on GitHub
SEO記事を、Search Console優先のキーワード調査、外部SEOツール補助調査、構成、執筆、レビュー、修正版Markdown保存まで一連で作成する。記事テーマや狙いたい内容を入力されたときにユーザーが明示的に実行する。
- Reads credentials
8 other projects use a version of this.
Adopted by
Most recently taken up by
- gaznil/seo-skills-by-gazniltheir own version, first seen Nov 16, 2026
- gaznilmuzammil12-prog/seo-skills-by-gazniltheir own version, first seen Nov 16, 2026
- pivoshenko/pivoshenko.aitheir own version, first seen Nov 12, 2026
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- AgriciDaniel/claude-blogtheir own version, first seen Oct 25, 2026
- Postman-Devrel/devrel-claude-code-skillstheir own version, first seen Jul 28, 2026
Used with
Projects with it also use blog-brand, blog-cannibalization and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
gaznilmuzammil12-progSkillblog-brand
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".
Also in 4 projects that use this
gaznilmuzammil12-progSkillblog-cannibalization
Detect keyword cannibalization across blog posts by extracting primary keywords from titles and headings, clustering semantically similar targets, and flagging posts competing for the same search intent. Supports local-only mode (grep-based) and DataForSEO API mode (Page Intersection endpoint at ~$0.01/call). Outputs severity-scored report with merge or differentiate recommendations. Use when user says "cannibalization", "keyword overlap", "competing pages", "duplicate keywords", "cannibalize".
Also in 4 projects that use this
timruebenachSkillseo-maps
Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".
Also in 3 projects that use this
timruebenachSkillseo-cluster
SERP-based semantic topic clustering for content architecture planning. Groups keywords by actual Google SERP overlap (not text similarity), designs hub-and-spoke content clusters with internal link matrices, and generates interactive visualizations. Optionally executes content creation if claude-blog is installed. Use when user says "topic cluster", "content cluster", "semantic clustering", "pillar page", "hub and spoke", "content architecture", "keyword grouping", or "cluster plan".
Also in 3 projects that use this
- +8 more from gaznilmuzammil12-prog
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- AgriciDaniel/claude-blog★ 2.7ksame name
- coopersimson96/ai-content-system★ 17same name
- pivoshenko/pivoshenko.ai★ 6same name
- megastep/codex-skills★ 4same name
- Postman-Devrel/devrel-claude-code-skills★ 4same name
- alpit-patel/seo-aeo-geo-kit★ 2same name
- gaznil/seo-skills-by-gaznil★ 0same name
- gaznilmuzammil12-prog/seo-skills-by-gaznil★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- seo-analyzeSkill
- setup-brandSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 37
Search Console、外部SEOツール、GA4の値、および <paths.brand>prohibited-claims.md に挙がる自社の性能値・保証・価格・対応範囲・比較優位を推測しない。
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SEO記事制作ワークフロー
ユーザー入力:
$ARGUMENTS
実行指示
このワークフローは、SEO記事を最終Markdownまで作成するためのものです。
config/site-config.mdを読み、ブランド表記、業種、対象読者、記事カテゴリ、CV目的、対象property、MCP名、参照・保存先パスを確定する。未記入の場合は/setup-brandの実行を促す。- ユーザー入力を整理し、テーマ、対象読者、対象地域、CV目的、想定文字数、与えられたキーワードを抽出する。
- 情報が不足している場合、
config/site-config.mdのtarget_audienceとdefaultsを前提に合理的な仮定を置き、成果物に明記して進める。 <paths.brand>company-facts.md、<paths.brand>writing-rules.md、<paths.brand>prohibited-claims.md、<paths.company_info>**/*.md、<paths.existing_articles>**/*.md、<paths.keyword_history>を読む。config/site-config.mdのarticle_categoriesを使い、新規記事の想定カテゴリを1つに決める。<paths.keyword_history>を使い、同一キーワードだけでなく近い検索意図の既存・予定記事がないか確認する。keyword-researcherを呼び、Search Console調査を最優先で実施し、外部SEOツールで外部需要・競合・関連語を補助確認する。取得できない場合は、失敗理由をレポートへ残し、推測値を用いずに以後の構成を「要再調査」として進める。- 調査結果を
<paths.output>research/<slug>-research.mdに保存する。 content-plannerを呼び、ユーザー提供画像が<paths.output>source-images/<slug>/にある場合はそれを優先した構成案と画像設計を作成して<paths.output>outlines/<slug>-outline.mdに保存する。blog-writerを呼び、ユーザー提供画像がある場合は使う画像だけを<paths.output>images/<slug>/にコピーし、Markdown本文中の適切な使用位置へローカル画像として埋め込んだ初稿を<paths.output>drafts/<slug>-draft.mdに保存する。必要に応じて画像MCPで選んだ画像も同じ保存先へダウンロードして使う。seo-reviewerを呼び、レビューを<paths.output>reviews/<slug>-review.mdに保存する。BLOCK判定でない場合はblog-writerを再度呼び、修正版を<paths.output>final/<slug>.mdに保存する。BLOCK判定の場合も、修正可能な範囲の原稿を<paths.output>final/<slug>-pending-verification.mdに保存し、確認事項を明示する。- ユーザーへの最終報告は、保存したファイルのパス、採用キーワード、公開前確認事項の要約に限定する。
制約
.claude/、.mcp.json、.env、認証情報は編集しない。<paths.output>以外へ成果物を書かない。<paths.company_info>**/*.mdは会社情報・内部資料・調査メモとして参照するが、公開前確認が必要な主張は断定しない。<paths.keyword_history>に同一または近い検索意図のキーワードがある場合は、新規作成・リライト・別角度化の判断を明記する。- Search Console、外部SEOツール、GA4の値、および
<paths.brand>prohibited-claims.mdに挙がる自社の性能値・保証・価格・対応範囲・比較優位を推測しない。 - ユーザー提供画像は
<paths.output>source-images/<slug>/に置かれる前提で扱う。元画像は編集せず、記事で使う画像だけを<paths.output>images/<slug>/にコピーして本文へ埋め込む。 - ストック画像を使う場合はライセンス上必要なクレジットを残し、画像ファイルを
<paths.output>images/<slug>/に保存する。別の対応表は作らず、Markdown本文中の画像ブロックと直前コメントで使用位置が分かるようにする。 - 自社の実物・実績を紹介するカテゴリの記事では、ストック画像が実物の写真と誤認されない扱いにする。
- CMS公開、問い合わせ送信、外部アップロードを行わない。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

