How do I install the Gsc SEO Autopilot skill?

Run npx skillmds@latest add dqhieu/gsc-seo-autopilot in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gsc SEO Autopilot safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsc SEO Autopilot?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsc SEO Autopilot free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsc SEO Autopilot?

dqhieu (@dqhieu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsc SEO Autopilot by dqhieu — Agent Skill

Name: Gsc SEO Autopilot
Author: dqhieu

Gsc SEO Autopilot

Automated weekly SEO pipeline -- GSC monitoring, keyword expansion, blog content creation for any website. Use for SEO analysis, content briefs, quick wins, weekly reports. Arguments: auto, init, weekly, quick-wins, brief, publish.

dqhieu Updated Sep 17, 2026

File contents

GSC SEO Autopilot

Automated SEO pipeline: GSC monitoring, keyword expansion, quick wins, and blog content creation. Works with any website.

Arguments

Route based on the first argument provided by the user:

Argument	Reference File	Description
`auto`	`references/cmd-auto.md`	Full pipeline: GSC analysis + keyword expansion + blog creation
`init`	`references/cmd-init.md`	Interactive config setup wizard
`weekly`	`references/cmd-weekly.md`	GSC performance report
`quick-wins`	`references/cmd-quick-wins.md`	Find low-hanging SEO opportunities
`brief <keyword>`	`references/cmd-brief.md`	Generate content brief for a keyword
`publish <keyword>`	`references/cmd-publish.md`	Write a single blog post for a keyword

Default (no argument): Run auto pipeline.

Procedure: Read the matching reference file and follow its instructions.

Config Loading

Every command MUST start by reading seo-config.yaml from this skill's directory:

~/.claude/skills/gsc-seo-autopilot/seo-config.yaml

If missing, inform user and suggest running /gsc-seo-autopilot init.

Keywords Everywhere (MCP)

Keyword data comes from the hosted Keywords Everywhere MCP server. Auth is handled by the MCP client, so no API key is read at run time. If the mcp__keywords-everywhere__* tools are unavailable, skip keyword expansion and fall back to WebSearch -- never fail the run.

Tools

Tool	Required args	Returns	Credits
`get_related_keywords`	`keyword`, `num`	`data`: array of keyword strings	2 per keyword returned
`get_pasf_keywords`	`keyword`, `num`	`data`: array of "People Also Search For" strings	2 per keyword returned
`get_keyword_data`	`kw`, `country`, `currency`, `dataSource`	`data[]`: `{keyword, vol, cpc:{currency,value}, competition, trend[]}`	1 per keyword
`get_domain_keywords`	`domain`, `country`, `num`	`data[]`: `{keyword, estimated_monthly_traffic, serp_position}`	2 per keyword
`get_credit_balance`	--	array with one integer	free

Every argument is required -- none have defaults. Note that get_related_keywords and get_pasf_keywords take only keyword and num; country, currency, and dataSource do not apply to them and are used solely by get_keyword_data.

Limits and cost

get_keyword_data accepts a maximum of 100 keywords per call. Chunk longer lists.
num accepts up to 10,000, but expansion costs 2 credits per keyword returned. Pass ke_related_limit from config -- never a large literal.
Check get_credit_balance before a run that expands many seeds.

Map config values to arguments: ke_country -> country, ke_currency -> currency, ke_data_source -> dataSource, ke_related_limit -> num.

Blog Writing

Follow references/blog-writing-guide.md. Do NOT delegate to external skills.

Setup

GSC MCP server (see README)
Keywords Everywhere MCP server (optional, see README)
seo-config.yaml in skill directory (run /gsc-seo-autopilot init or copy seo-config.example.yaml)

---name: gsc-seo-autopilotdescription: Automated weekly SEO pipeline -- GSC monitoring, keyword expansion, blog content creation for any website. Use for SEO analysis, content briefs, quick wins, weekly reports. Arguments: auto, init, weekly, quick-wins, brief, publish.---# GSC SEO AutopilotAutomated SEO pipeline: GSC monitoring, keyword expansion, quick wins, and blog content creation. Works with any website.## ArgumentsRoute based on the first argument provided by the user:| Argument | Reference File | Description ||----------|---------------|-------------|| `auto` | `references/cmd-auto.md` | Full pipeline: GSC analysis + keyword expansion + blog creation || `init` | `references/cmd-init.md` | Interactive config setup wizard || `weekly` | `references/cmd-weekly.md` | GSC performance report || `quick-wins` | `references/cmd-quick-wins.md` | Find low-hanging SEO opportunities || `brief <keyword>` | `references/cmd-brief.md` | Generate content brief for a keyword || `publish <keyword>` | `references/cmd-publish.md` | Write a single blog post for a keyword |**Default (no argument):** Run `auto` pipeline.**Procedure:** Read the matching reference file and follow its instructions.## Config LoadingEvery command MUST start by reading `seo-config.yaml` from this skill's directory:```~/.claude/skills/gsc-seo-autopilot/seo-config.yaml```If missing, inform user and suggest running `/gsc-seo-autopilot init`.## Keywords Everywhere (MCP)Keyword data comes from the hosted Keywords Everywhere MCP server. Auth is handled by the MCPclient, so no API key is read at run time. If the `mcp__keywords-everywhere__*` tools areunavailable, skip keyword expansion and fall back to `WebSearch` -- never fail the run.### Tools| Tool | Required args | Returns | Credits ||------|--------------|---------|---------|| `get_related_keywords` | `keyword`, `num` | `data`: array of keyword strings | 2 per keyword returned || `get_pasf_keywords` | `keyword`, `num` | `data`: array of "People Also Search For" strings | 2 per keyword returned || `get_keyword_data` | `kw`, `country`, `currency`, `dataSource` | `data[]`: `{keyword, vol, cpc:{currency,value}, competition, trend[]}` | 1 per keyword || `get_domain_keywords` | `domain`, `country`, `num` | `data[]`: `{keyword, estimated_monthly_traffic, serp_position}` | 2 per keyword || `get_credit_balance` | -- | array with one integer | free |Every argument is required -- none have defaults. Note that `get_related_keywords` and`get_pasf_keywords` take **only** `keyword` and `num`; `country`, `currency`, and `dataSource`do not apply to them and are used solely by `get_keyword_data`.### Limits and cost- `get_keyword_data` accepts a maximum of **100 keywords per call**. Chunk longer lists.- `num` accepts up to 10,000, but expansion costs 2 credits per keyword *returned*. Pass `ke_related_limit` from config -- never a large literal.- Check `get_credit_balance` before a run that expands many seeds.Map config values to arguments: `ke_country` -> `country`, `ke_currency` -> `currency`,`ke_data_source` -> `dataSource`, `ke_related_limit` -> `num`.## Blog WritingFollow `references/blog-writing-guide.md`. Do NOT delegate to external skills.## Setup1. **GSC MCP server** (see README)2. **Keywords Everywhere MCP server** (optional, see README)3. **seo-config.yaml** in skill directory (run `/gsc-seo-autopilot init` or copy `seo-config.example.yaml`)

Frequently asked questions