Communitygithub.com

Varnan-Tech/opendirectory

用於部落格產生的 SEO 關鍵字研究工作流程,利用 Google Trends 數據。在撰寫部落格文章、規劃內容行事曆或為搜尋引擎優化文章時使用。可發掘突發關鍵字、建構內容結構,並產出面嚮技術與開發者受眾的 SEO 優化部落格大綱。

opendirectory 是什麼?

這項 AI 助手技能提供了一個系統化的 SEO 關鍵字研究工作流程,專為最佳化技術與開發者相關部落格內容而設計。它強制在產出任何部落格文章之前,先透過 Google Trends 數據進行關鍵字研究,從而確保內容有更高的排名潛力。技能的核心是基於 Google Trends 的「相關查詢」(RELATED_QUERIES)和「相關主題」(RELATED_TOPICS)API 呼叫,建立一個關鍵字優先級系統,其中「突發關鍵字」(Breakout Keywords)獲得最高優先級,因其成長率高達 5000% 以上且競爭極低。該技能會指引 AI 產生一個結構化的部落格大綱,包含 H2 與 H3 標題、元描述、關鍵字放置規則,以及基於關鍵字成長趨勢的品質檢查清單。它還內建了預算提醒功能,建議預設使用最少 API 呼叫次數(每次部落格 2 次呼叫),以在每個月 250 次的免費額度內最大化效率。這項技能特別適合需要持續產出內容、規劃內容行事曆,或希望針對 SEO 機會較低的題目尋找替代切入點的開發者與技術寫作者。它可與任何支援自訂技能的工具(如 Claude Code、Cursor 或 Codex)整合,只要該工具能執行 shell 命令與 API 請求。

相容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Varnan-Tech/opendirectory/tree/main/skills/google-trends-api-skills/seo-keyword-research

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

SEO 關鍵字研究技能

在撰寫部落格內容之前,先找出熱門、高潛力的關鍵字。這項技能能將普通的部落格題目轉化為能獲得排名的 SEO 優化內容。

使用時機

  • 當使用者要求撰寫部落格文章或一般文章時
  • 當使用者想要針對某個主題進行關鍵字研究時
  • 當使用者需要一份內容行事曆或內容計劃時
  • 當使用者想為現有內容進行 SEO 最佳化時
  • 任何針對技術/開發者受眾的部落格產生任務

核心原則

在產出部落格內容之前,務必先進行關鍵字研究。

不好的做法: 寫部落格 -> 期望它排名 -> 通常不會
好的做法: 研究關鍵字 -> 找到突發機會 -> 寫最佳化文章 -> 獲得良好排名

關鍵字優先級系統

在分析 Google Trends 的「相關查詢」(RELATED_QUERIES)結果時,請依下列順序為關鍵字設定優先級:

1. 突發關鍵字 — 最高優先級

  • formatted_value: "Breakout" 代表 5000% 以上的成長
  • 競爭極低(趨勢剛起步)
  • 作為主要部落格關鍵字使用
  • 立即產出內容(搶佔先機)

2. 高成長關鍵字 — 非常高優先級

  • formatted_value: "+100%" 或更高
  • 低至中等競爭
  • 作為主要或強而有力的次要關鍵字使用
  • 在 2-4 週內產出內容

3. 中等成長關鍵字 — 高優先級

  • formatted_value: "+50%" 至 "+99%"
  • 中等競爭
  • 作為內文中的次要關鍵字使用

4. 長尾關鍵字 — 策略性優先級

  • 基於問題的查詢(如何、什麼、為什麼、何時、哪裡)
  • 低競爭、高轉換率
  • 用作 H3 標題 — 目標是獲得精選摘要和語音搜尋

5. 已確立關鍵字 — 中等優先級

  • 流量穩定的熱門查詢,競爭高
  • 用在內文中,不作為主要目標

SEO 研究工作流程

第一步:關鍵字發現(1 次 API 呼叫 — 必要)

使用使用者的部落格主題查詢 RELATED_QUERIES:

curl -s "https://serpapi.com/search?engine=google_trends&q=USER_TOPIC&data_type=RELATED_QUERIES&date=today+3-m&api_key=$SERPAPI_KEY"

從回應中,提取:

  • 突發關鍵字 → 主要關鍵字候選
  • 高成長關鍵字 (+100%) → 次要候選
  • 基於問題的查詢 → H3 標題和精選摘要目標

選擇主要關鍵字:

  1. 第一個突發關鍵字(如果有的話)
  2. 否則選第一個高成長關鍵字
  3. 否則按分數選最高查詢

第二步:內容結構(1 次 API 呼叫 — 必要)

用相同主題查詢 RELATED_TOPICS:

curl -s "https://serpapi.com/search?engine=google_trends&q=USER_TOPIC&data_type=RELATED_TOPICS&date=today+3-m&api_key=$SERPAPI_KEY"

從上升中和熱門的結果中提取主題標題。這些將成為你的 H2 章節標題(選擇 3-5 個)。

第三步:趨勢驗證(1 次 API 呼叫 — 可選)

僅在需要在多個候選關鍵字之間做選擇,或需要驗證可行性時使用:

curl -s "https://serpapi.com/search?engine=google_trends&q=KEYWORD&data_type=TIMESERIES&date=today+12-m&api_key=$SERPAPI_KEY"

比較最近 2 個月的平均值與更早 2 個月的平均值。如果近期平均值高於早期平均值,表示趨勢上升 — 可繼續進行。如果呈現下降趨勢,請考慮改用其他關鍵字。

第四步:產出部落格大綱

使用以下結構建立大綱:

標題:[主要關鍵字] — [好處/數字] [年份]
  (最多 60 個字元,必須包含主要關鍵字)

Meta 描述:(150-160 個字元,包含主要關鍵字和 1-2 個次要關鍵字)

# [H1 — 與標題相同或略作變化]

## 引言(150 字)
  - 在前 100 字內出現主要關鍵字
  - 用一個問題或痛點來吸引注意
  - 預告他們將學到的內容

## [H2:來自第二步的相關主題 1]
### [H3:來自第一步的長尾問題]
  回答該問題的內容(150-200 字)
### [H3:另一個長尾問題]
  內容(150-200 字)

## [H2:相關主題 2]
### [H3:長尾問題]
### [H3:長尾問題]

## [H2:相關主題 3]
### [H3:長尾問題]
### [H3:長尾問題]

## 結論(100 字)
  - 總結關鍵要點
  - 主要關鍵字出現一次
  - 行動呼籲

目標:總共 1500-2500 字

關鍵字放置規則

位置規則
標題包含主要關鍵字,最多 60 個字元
H1與標題相同或略作變化
H2 標題(3-5 個)使用相關主題,自然語言
H3 標題(8-12 個)使用長尾關鍵字,問題格式
第一段在前 100 字內出現主要關鍵字
內文主要關鍵字密度 1-2%,次要關鍵字密度 0.5-1%
結論主要關鍵字出現一次
Meta 描述主要關鍵字 + 1-2 個次要關鍵字,150-160 個字元

絕對不要關鍵字堆砌。 內容必須讀起來自然。Google 會懲罰不自然的重複。

品質檢查清單

在產生部落格之前,請確認:

  • 找到至少 1 個突發關鍵字或成長 +100% 的關鍵字(或合理說明使用已確立關鍵字的理由)
  • 從 RELATED_TOPICS 取得 3-5 個 H2 主題
  • 有可供 H3 標題使用的長尾關鍵字
  • 主要關鍵字夠具體,有機會獲得排名
  • 部落格結構遵循上述大綱模板
  • Meta 描述已撰寫(150-160 個字元)
  • 目標長度為 1500-2500 字

如果該主題不存在任何突發或高成長關鍵字,請告知使用者 SEO 機會有限,並建議其他有成長性的切入角度或相關主題。

預算提醒

免費額度:每月 250 次搜尋

策略每次部落格呼叫次數每月可產生部落格數量
最低(建議)2125 篇
標準383 篇
完整462 篇

預設使用 2 次呼叫(RELATED_QUERIES + RELATED_TOPICS)。僅在明確需要時才加入 TIMESERIES 或 GEO_MAP 呼叫。

需避免的常見錯誤

  1. 跳過研究 — 未檢查趨勢就撰寫會錯失突發機會
  2. 忽略突發關鍵字 — 在有突發變體可用時仍使用通用詞彙
  3. 關鍵字堆砌 — 不自然地重複關鍵字;維持密度在 1-2%
  4. 缺少長尾關鍵字 — 錯失精選摘要和語音搜尋機會
  5. 通用 H2 標題 — 務必使用 RELATED_TOPICS 數據來建立章節結構

範例腳本

如需完整的工作範例,請執行:

python scripts/blog_seo_research.py "你的部落格主題"

請參閱 scripts/blog_seo_research.py 查看實作。

參考資料

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Varnan-Tech/opendirectory

Use when the user asks to generate a blog cover image, thumbnail, or article header. Automatically uses modern typography, brand logos, and Google Search grounding to create beautiful 16:9 images with Gemini 3.1 Flash Image Preview.

Varnan-Tech/opendirectory

World-class brand strategist and naming expert. Uses an interrogation-led discovery phase to extract your brand's DNA, then applies scientific naming frameworks (Phonosemantics) and automated multi-TLD domain checking.

Varnan-Tech/opendirectory

Use when the user asks to generate or update a project's CLAUDE or AGENTS context file from a codebase scan. Writes a focused file under 100 lines containing only the non-obvious build commands, conventions, and gotchas Claude Code needs.

Varnan-Tech/opendirectory

Use when the user wants to verify cold emails, enrich a lead list, or autonomously guess email addresses from a CSV using ValidEmail.co or the open-source Reacher engine.

Varnan-Tech/opendirectory

Competitive intelligence orchestrator tracking companies across 8+ platforms (GitHub, Twitter, Reddit, HN, PH, YC Jobs) with heat scores and AI briefings.

Varnan-Tech/opendirectory

Give it your product URL or description. It finds your top 5 competitors, runs three-track PR research across all of them (editorial, podcasts, communities), identifies which channels appear most frequently, looks up the journalist or host for each, and returns a tiered outreach list with story angles and ready-to-send cold pitch drafts tailored to your product. Use when asked to find PR opportunities, discover where competitors got featured, build a media outreach list, find which journalists cover my space, or get pitch templates for press coverage.

Varnan-Tech/opendirectory

Generate high-converting, deep-dive growth case studies in MDX format. Use this skill when asked to write a case study or blog post about a company's growth, tech stack, or product-led strategy. It handles the full pipeline (researching the company via Tavily, generating a 16:9 cover image, quality checking the draft, uploading assets to cloud storage, and pushing directly to the target repository).

Varnan-Tech/opendirectory

Scans your project for outdated npm, pip, Cargo, Go, or Ruby packages. Runs a CVE security audit. Fetches changelogs, summarizes breaking changes with Gemini, and opens one PR per risk group (patch, minor, major). Includes Diagnosis Mode for install conflicts. Use when asked to update dependencies, check for outdated packages, open dependency PRs, scan for package updates, audit for CVEs, or flag breaking changes in upgrades. Trigger when a user says "check for outdated packages", "update my dependencies", "open PRs for dependency updates", "scan for CVEs", or "which packages need upgrading".

Varnan-Tech/opendirectory

Generates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture. Uses graphify to build a knowledge graph first, then writes accurate docs from it. Use when asked to write docs, generate a README, document an API, update stale docs, create an API reference from code, add an architecture section, or document a project in any language. Trigger when a user says their docs are missing, outdated, or wants to document their codebase without writing it manually.

Varnan-Tech/opendirectory

Evaluates expired domain candidates against a target niche, scores them by topical relevance, historical activity level, and history cleanliness, then outputs a ranked shortlist with explainable reasoning and risk flags.

Varnan-Tech/opendirectory

Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked by impact × effort, and sketches an ideal README. Trigger when user says "roast my repo", "audit my README", "dx audit", "developer experience review", "score my GitHub project", "before launch checklist", or "make my repo shareable".

Varnan-Tech/opendirectory

Drafts and designs a complete HTML email newsletter from a topic or content brief. Outputs paste-ready HTML for Loops, Mailchimp, Beehiiv, Resend, or any standard email platform. Includes subject line options and plain-text fallback. Trigger when a user says "write a newsletter", "draft an email newsletter", "create an HTML email", "design an email for my subscribers", or "write a newsletter about [topic]".

Varnan-Tech/opendirectory

Takes a GitHub PR URL or the current branch and writes a plain-English explanation of what it does and why, then posts it as a PR comment. Use when asked to explain a PR, summarize a pull request, write a plain-English description of a PR, add a summary comment to a PR, or understand what a PR changes. Trigger when a user says "explain this PR", "summarize this pull request", "what does this PR do", "add a comment explaining the PR", or shares a GitHub PR URL and asks what it does.

Varnan-Tech/opendirectory

Audit how often LLMs recommend your brand vs competitors and generate a GEO action plan.

Varnan-Tech/opendirectory

Takes a competitor's public GitHub repo URL, fetches their open issues via the GitHub REST API, filters noise locally, clusters issues into 6 demand categories, computes a demand score per issue and per cluster, and outputs a ranked demand gap report with a GTM messaging brief. Use when asked to scan a competitor's GitHub issues, find what their users are begging for, turn GitHub complaints into product positioning, identify competitor feature gaps, or generate messaging from real user demand. Trigger when a user says "scan competitor issues", "what are users asking for on X repo", "find demand gaps in Y", "turn GitHub issues into messaging", or "what should I build based on competitor complaints".

Varnan-Tech/opendirectory

Find recurring confusion in your repo's GitHub Discussions, rank it by urgency, and draft the actual docs fixes and content angles — with verbatim community quotes and source links as evidence.

Varnan-Tech/opendirectory

Generates a professionally designed case study PDF for B2B SaaS sales and marketing. Supports 7 page layouts, 9 style presets, 1-4 page output. Trigger when user says "create a case study", "write a customer story", "make a case study PDF", "design a success story", "turn this customer win into a PDF".

Varnan-Tech/opendirectory

Generates data visualization charts (bar, line, area, pie, doughnut, scatter, radar, treemap) as PNG using Apache ECharts v6. 1080×1080px default, 5 style presets, highlight annotations. Trigger when user says "create a chart", "visualize data", "make a bar chart", "line graph", "pie chart", "data visualization", "chart this data", "plot", "graph", or "visualize these numbers".

Varnan-Tech/opendirectory

Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a nurture asset", or "make a PDF report".

Varnan-Tech/opendirectory

Fetches low-star App Store and Google Play reviews, clusters them into broken-promise patterns, and generates a ranked copy brief with positioning opportunities.

相關技能