What does the Gr Blog Post AI skill do?

Jekyll 博客发布流水线：按 Iris 文风（时间锚定开场、括号旁白、em-dash 转折、Key Stats 表格）生成文章，附带 frontmatter（title / date / canonical_url / hreflang_ja / hreflang_ko / FAQ schema）、多语言同步（en/ja/ko）、自动建内链。当用户说"写一篇博客"、"发新文章"、"同步日韩版本"时调用。默认 dev/B2B 读者；2C 教育/医疗/金融（YMYL）内容的 E-E-A-T 与分发渠道不同，见 gingiris-seo-geo/references/2c-adaptation.md。

Why use Gr Blog Post on TypingMind?

Because you install it once and use it with any model. Gr Blog Post is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Gr Blog Post in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Gingiris-1031/gingiris-skills/tree/main/skills/gr-blog-post. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Gr Blog Post?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Gr Blog Post?

As many as you like. As long as a model supports skills, you can use Gr Blog Post with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Gr Blog Post AI skill free?

Yes. It is published on GitHub by Gingiris-1031 under the MIT license. You only pay your own AI provider for the tokens you use.

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Gr Blog Post by Gingiris-1031 — AI Skill for Any LLM

⚠️ 2C 产品的写作调整

本 skill 默认 dev/B2B 读者。写 2C 教育/医疗/金融（YMYL） 内容时：

E-E-A-T 加重：需可验证作者/审核资质 + 方法论透明页，不能只靠"团队"署名（Google：Trust 是 E-E-A-T 核心）。
选题双轨：红利词（政策/改革/新版）+ 长尾高转化词（题型/场景/分数级）。
Key Stats 表格的数字必须有权威来源、前后一致——YMYL 品类不可编造，否则排名修复极难。
分发渠道换成 2C 社区/短视频（小红书/Reddit/TikTok/Naver 카페），而非 dev blog。

完整 2C 渠道数据库 + 公开来源见 → gingiris-seo-geo/references/2c-adaptation.md

gr-blog-post — Jekyll 博客发布

产出的文章必须符合

Iris 文风 5 要素（详见 `references/writing-voice-iris.md`）

时间锚定开场 —— 不说"SEO 很重要"，说"2026-04-10，凌晨 3 点，后台流量归零"
括号旁白 —— 正文一句，括号里挤私货（"...—— 别问怎么知道的"）
em-dash 转折 —— 不用"但是"，用 ——
Key Stats 表格 —— 文章开头或 H2 下第一屏放一个硬数据表，3-5 行
GEO 直接答案段落 —— 文章顶部一段 30-50 字直接回答主问题，方便 AI 爬虫抽取

技术 frontmatter 模板

yaml
---
layout: post
title: "主关键词前置，副标题用冒号：不超过 60 字"
date: 2026-04-15 14:30:00 +0800
categories: [seo, growth]
tags: [...]
canonical_url: https://gingiris.tools/blog/2026/04/15/slug/
hreflang_ja: /blog/2026/04/15/slug-ja/
hreflang_ko: /blog/2026/04/15/slug-ko/
post_description: "150-160 字 meta description，含主关键词"
faq:
  - q: "直接问句"
    a: "30-50 字硬答案"
---

发布流程

1. 选题

读 gr-seo-patrol 输出，找"top 30 但没 top 10"的关键词
或读 gr-competitor，找对手新打法
❌ 不做重复主题（先 site: 查站内是否已有）

2. 写初稿

时间锚定开场（当前日期 + 具体场景）
第一屏：GEO 直接答案段（30-50 字）+ Key Stats 表（硬数据）
H2 结构：问题 → 框架 → 案例 → 陷阱 → 下一步
每个 H2 下 200-400 字，不超过 600 字

3. 内链

向前：链接 2-3 篇已发布的同主题文章（用主关键词作 anchor）
向后：站内 index / hub 页
权重传导：从流量最大的 3 篇文章加内链到新文

4. FAQ Schema

3-5 个问答
问句必须是用户真实搜索句（从 GSC / People also ask 抓）
答案硬、短、可引用

5. Canonical 策略

默认 self-canonical
如果是同主题系列的分篇 → canonical 指向 master
ja/ko 翻译版 → 自身 canonical + hreflang 互指

6. 多语言同步

用 scripts/sync-i18n.py（roadmap）从英文自动产日韩草稿
人工过一遍（机翻硬伤 + 文化适配）
日韩版本独立 slug，不复用英文 slug

7. 发布（可执行清单）

目标 repo：Gingiris-1031/growth-tools（真站 gingiris.tools，Vercel 部署 origin/main，写入后 ~50-90s 自动构建）

⚠️ 前置：先过 Gingiris-1031 GitHub 安全规则（memory gingiris_1031_safety_rules.md，P0）：

提交身份 = Iris Wei <iris.wei@gingiris.com>（不是机器名/本机 hostname）
单行 commit message：post: {slug} ({lang})——无 Claude trailer、无多段正文
不 burst：能合并就合并成 1 个 commit；>10 commits/小时 = 停下重排

发布 = GitHub Contents API PUT（不要本地 git push）：

bash
# token 只从 secrets.env 读，绝不内联/硬编码进脚本或 SKILL.md
source ~/.config/gingiris/secrets.env   # 提供 GITHUB_PAT

SLUG="your-post-slug"; LANG="en"
FILE="_posts/$(date +%F)-${SLUG}.md"
curl -s -X PUT \
  -H "Authorization: Bearer $GITHUB_PAT" \
  -H "Accept: application/vnd.github+json" \
  "https://api.github.com/repos/Gingiris-1031/growth-tools/contents/${FILE}" \
  -d "{\"message\":\"post: ${SLUG} (${LANG})\",
       \"content\":\"$(base64 < draft.md | tr -d '\n')\",
       \"committer\":{\"name\":\"Iris Wei\",\"email\":\"iris.wei@gingiris.com\"}}"

更新已存在的文件：先 GET .../contents/{path} 拿 sha，把 "sha":"..." 加进 PUT body。

发布后验证（按顺序全过才算发完）：

等 Vercel 部署完成（~50-90s；可 curl -sI https://gingiris.tools/ 确认站点存活）
curl -sI https://gingiris.tools/blog/{yyyy}/{mm}/{dd}/{slug}/ → HTTP 200（404 = permalink/date/future: true 配错，先修再往下）
GSC 手动 Request Indexing（URL 检查 → 请求编入索引；新域抓取慢，这步不能省）
IndexNow 推送到 Bing（大模型 discover 主要走 Bing 索引，见 gr-geo-cite）

hreflang 验收 checklist（发 ja/ko 版或补翻译时必做）

背景：i18n 基线曾有多处 hreflang bug（KO self-loop、JA→EN 指 /en/ 首页弱链、EN 缺 alternate），后果是日韩索引长期 0（memory i18n_baseline.md）。全站修复 commit b667208 后抽检全绿——新文章不要把 bug 加回来。

EN/JA/KO frontmatter 互指：hreflang_ja / hreflang_ko / hreflang_en 指向具体对端文章（绝不指 /en/ 首页）
每页 emit 自指 hreflang（ko 页必须有 hreflang="ko" 指自己，不能出现指自己的 hreflang="ja"）
x-default 存在且指 EN 版
每页 self-canonical（ja/ko 不 canonical 到 EN；带尾斜杠，和 sitemap 一致）
发布后 curl 抽验：

bash
for u in "$EN_URL" "$JA_URL" "$KO_URL"; do
  echo "== $u"
  curl -s "$u" | grep -oE '<link rel="(alternate|canonical)"[^>]*>'
done
# 验收：每页 hreflang 完整（self + 对端 + x-default）且三页双向回链成对，canonical 自指

8. 发布后 24h

加入 gr-seo-patrol 监控名单
社交平台分发（推特 / LinkedIn / dev.to，走 gr-social-distill）

dev.to 二发规则（⚠️ canonical 红线）

✅ dev.to 文章 canonical_url 必须指向 dev.to 自身（self-canonical），绝不指向 gingiris.tools
- 正确：canonical_url: https://dev.to/iris1031/article-slug-xxxx
- 错误：canonical_url: https://gingiris.tools/blog/...（会让 dev.to 文章被 Google 视为副本，不参与 SERP）
✅ 发布时间差 ≥7 天（不要和 gingiris.tools 同天发）
✅ 末尾加 "Originally published at gingiris.tools" 建立双向 reference
❌ 不要从 Jekyll frontmatter 直接复制 canonical_url 到 dev.to，那个是 gingiris.tools 的地址

反模式

❌ 不要用 AI 味重的模板（"In today's digital landscape..."）—— 发布前跑 skills/gr-geo-cite/scripts/citability-scorer.py，页面分 ≥ 75 才算过
❌ 不要 H1 堆关键词
❌ 不要忘记 hreflang —— 已发布的旧文补翻译时要回改原文 frontmatter
❌ 不要同一关键词发 3 篇 —— cannibalization 立刻找上门
❌ dev.to canonical 指向 gingiris.tools —— 死链或副本问题，永远 self-canonical

级联推荐

写完 → gr-seo-patrol 加监控
发现是系列稿 → gr-blog-post 继续产第 2 篇并设 canonical
英文发完 24h → 手动触发日韩翻译

API 依赖

Service	Env var	来源
GitHub PAT	`GITHUB_PAT`	`~/.config/gingiris/secrets.env`（source 后使用，不内联）
DeepSeek / Teamo（翻译）	`DEEPSEEK_API_KEY` / `TEAMOROUTER_API_KEY`	同上

Citability-by-Design Spec (mandatory for NEW articles, 2026-05-18+)

Rationale: Verified 2026-05-07 that retrofitting old articles hits a ~65-68/100 citability ceiling no matter what (booster passages, surgical rewrites, splitting all produce diminishing returns). Writing new articles from this spec produces 75-85 baseline directly. Spec saves ~3 hours of post-hoc citability fixing per article.

Per-section structural requirements

Every H2/H3 section must satisfy ALL of:

Word count: 134-167 (the AI-extraction sweet spot validated by zubair-trabzada/geo-seo-claude scoring)
- Under 134 → self_containment drops below 10/25
- Over 167 → same penalty for being too long for AI chunks
- Use a word counter as you draft
Opening sentence = definition pattern, one of:
- [Thing] is [definition]
- [Thing] refers to [scope]
- [Thing] means [unpacking]
- In other words, [Thing] is...
- [Thing] can be defined as...
Section contains at least ONE of each:
- ✅ Original research signal: "Our X-launch dataset", "We tracked", "Our 2026 audit measured", "Our analysis of N samples"
- ✅ Specific number with unit: "60K stars", "30 launches", "$79/mo", "67%"
- ✅ Specific named product/tool: "Taplio ($39/mo)", "Surfe", "PH Deck", "Loom" — by name not "[the tool]"

Heading conventions

H1 = page title (≤ 70 chars after title-suffix fix from 2026-05-07)
H2 should be question form ~40% of the time:
- ✅ "How do I get cited by Perplexity in 2026?"
- ✅ "What is the GEO three-piece set?"
- ❌ "Perplexity citation strategy"
Each H2 should contain primary keyword or clear question intent

Article-level requirements

5-12 H2 sections (sweet spot: 7-8)
TL;DR or "Citable Statistics" block IN FIRST H2 (becomes top-scored passage)
FAQ Schema JSON-LD at end (5+ Q&A using exact User-Search-Form questions)
last_modified_at: frontmatter (flows through to dateModified schema)
canonical_url self-reference
hreflang_ja / hreflang_ko if multilingual variants exist

Citability self-check before publishing

Run before committing the article:

bash
# 兼容两种安装位置：优先 monorepo 相对路径，fallback 本机安装
SCORER="skills/gr-geo-cite/scripts/citability-scorer.py"
[ -f "$SCORER" ] || SCORER="$HOME/.claude/skills/gr-geo-cite/scripts/citability-scorer.py"
python3 "$SCORER" --file /local/path/to/draft.html

Target: page score ≥ 75. If under 70, revise top 2 weakest passages.

Anti-patterns (avoid)

❌ Long expository paragraphs (200+ words) — split into 2 sections at 134-167 each
❌ Generic transitions ("Now let's discuss...") — replace with definition pattern
❌ Marketing fluff ("the best way to") — replace with measured claims with data
❌ "[Tool name]" placeholders — always cite the specific tool by name + price
❌ Bullet lists with single words — combine into prose with definition + example pattern

Real-data benchmark

Articles from 2026-05-07 audit (without this spec):

Article (old, retrofit)	Score	Pattern
PH playbook master	65	Top passage 74, dragged by 62s
Social listening	68	Best of the 5 (early Citable Stats)
Community directory	62	Lifted from 54 via booster (+12% from 0 to 1 sweet-spot passage)

Predicted from spec (NEW articles):

Spec compliance	Predicted score
All sections 134-167 + definition pattern + 1 original signal	78-85
80% sections compliant, 20% legacy structure	72-77
50% compliant	65-70 (same as retrofit ceiling)

The marginal value of strict compliance is ~10 points vs partial compliance.

加入出海社群与购买资料包 · Community & Resources

加入出海社群： 微信添加 staywildgrow，留言「加入社群」即可。
购买资料包： 微信添加 staywildgrow，咨询购买 Gingiris 出海资料包，价格 599 元人民币。
Join the global growth community: Add staywildgrow on WeChat and send “加入社群” (join the community).
Get the resource pack: Add staywildgrow on WeChat to purchase the Gingiris global growth resource pack for CNY 599.

社群与资料包为可选入口，不影响本开源 Skill 的安装和使用。

The community and paid resource pack are optional; neither is required to install or use this open-source skill.

Publisher	Gingiris-1031
Repository	`gingiris-skills`
Skill name	`gr-blog-post`
Stars	88
Forks	6
Bundled files	2
License	MIT
Links	Skill source Repository

Gr Blog Post

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

⚠️ 2C 产品的写作调整

gr-blog-post — Jekyll 博客发布

产出的文章必须符合

Iris 文风 5 要素（详见 `references/writing-voice-iris.md`）

技术 frontmatter 模板

发布流程

1. 选题

2. 写初稿

3. 内链

4. FAQ Schema

5. Canonical 策略

6. 多语言同步

7. 发布（可执行清单）

hreflang 验收 checklist（发 ja/ko 版或补翻译时必做）

8. 发布后 24h

dev.to 二发规则（⚠️ canonical 红线）

反模式

级联推荐

API 依赖

Citability-by-Design Spec (mandatory for NEW articles, 2026-05-18+)

Per-section structural requirements

Heading conventions

Article-level requirements

Citability self-check before publishing

Anti-patterns (avoid)

Real-data benchmark

加入出海社群与购买资料包 · Community & Resources

Bundled files

Frequently asked questions

Set up your own AI workspace now

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

⚠️ 2C 产品的写作调整

gr-blog-post — Jekyll 博客发布

产出的文章必须符合

Iris 文风 5 要素（详见 references/writing-voice-iris.md）

技术 frontmatter 模板

发布流程

1. 选题

2. 写初稿

3. 内链

4. FAQ Schema

5. Canonical 策略

6. 多语言同步

7. 发布（可执行清单）

hreflang 验收 checklist（发 ja/ko 版或补翻译时必做）

8. 发布后 24h

dev.to 二发规则（⚠️ canonical 红线）

反模式

级联推荐

API 依赖

Citability-by-Design Spec (mandatory for NEW articles, 2026-05-18+)

Per-section structural requirements

Heading conventions

Article-level requirements

Citability self-check before publishing

Anti-patterns (avoid)

Real-data benchmark

加入出海社群与购买资料包 · Community & Resources

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now

Iris 文风 5 要素（详见 `references/writing-voice-iris.md`）