Agent skill

Gsc Assistant

Google Search Console indexing assistant. An agent skill from nicepkg/ai-workflow.

MITAuto-check passedProduct & Project Management

Install Gsc Assistant

skills CLI

$ npx skills add nicepkg/ai-workflow --skill gsc-assistant -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow gsc-assistant --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/gsc-assistant .claude/skills/gsc-assistant && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "gsc-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/gsc-assistant into .claude/skills/gsc-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsc-assistant", 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

$skill-installer install https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/gsc-assistant

Type 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.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill gsc-assistant -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow gsc-assistant --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .agents/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/gsc-assistant .agents/skills/gsc-assistant && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gsc-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/gsc-assistant into .agents/skills/gsc-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsc-assistant", 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.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill gsc-assistant -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow gsc-assistant --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/gsc-assistant .cursor/skills/gsc-assistant && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gsc-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/gsc-assistant into .cursor/skills/gsc-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsc-assistant", 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

$ gemini skills install https://github.com/nicepkg/ai-workflow.git --path workflows/content-creator-workflow/.claude/skills/gsc-assistant

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill gsc-assistant -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow gsc-assistant --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/gsc-assistant .gemini/skills/gsc-assistant && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "gsc-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/gsc-assistant into .gemini/skills/gsc-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsc-assistant", 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.

GitHub CLI

$ gh skill install nicepkg/ai-workflow gsc-assistant

Installs 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).

skills CLI

$ npx skills add nicepkg/ai-workflow --skill gsc-assistant -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .github/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/gsc-assistant .github/skills/gsc-assistant && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "gsc-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/gsc-assistant into .github/skills/gsc-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsc-assistant", 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.

skills CLI

$ npx skills add nicepkg/ai-workflow --skill gsc-assistant -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nicepkg/ai-workflow gsc-assistant --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nicepkg/ai-workflow.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/workflows/content-creator-workflow/.claude/skills/gsc-assistant .opencode/skills/gsc-assistant && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gsc-assistant" agent skill from https://github.com/nicepkg/ai-workflow/tree/main/workflows/content-creator-workflow/.claude/skills/gsc-assistant into .opencode/skills/gsc-assistant/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gsc-assistant", 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.

Facts

Skill name: gsc-assistant
GitHub stars: 285
Token cost: ~1.3k tokens
SKILL.md length: 428 words
Files: 1
Skills in repo: 61
Repo updated: Jan 20, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Google Search Console indexing assistant. An agent skill from nicepkg/ai-workflow.

Works in 2 steps: indexed.md - All indexed pages in two… → to-index.md - Pages awaiting indexing
The user wants to track page indexing status
SKILL.md covers Purpose, When to Use This Skill, Key Concepts and File Schemas, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gsc Assistant is an agent skill from nicepkg/ai-workflow. Google Search Console indexing assistant. Use when the user wants to track page indexing status, compare sitemap against GSC indexed pages, manage submission tracking, or move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list. Maintains two tracking files (indexed.md, to-index.md) with prioritization support.

Its SKILL.md is about 1.3k 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 Product & Project Management, covering Prioritization frameworks. It works with Google Search Console. The repository describes itself as: 🚀 170+ pre-built skills for Claude Code, Cursor, Codex & 14+ AI tools. Stop re-teaching your AI the same things. One command → instant domain expertise. Marketing, SEO, Trading… The licence is MIT.

When your agent uses it

The user wants to track page indexing status
Compare sitemap against GSC indexed pages
Manage submission tracking
Move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list

Example prompts

“/gsc-assistant”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

indexed.md - All indexed pages in two tables
to-index.md - Pages awaiting indexing

What it can do on your machine

Read from SKILL.md and the folder at commit d167b41. It shows what the files ask for, not the result of running them.

Tool permissions
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.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gsc Assistant loads about 1.3k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 428 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~93
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from nicepkg/ai-workflow at commit d167b41, republished under its MIT licence (© nicepkg). 428 words, ~1,332 tokens.

Download SKILL.mdSave it as .claude/skills/gsc-assistant/SKILL.md (or your agent's skills folder).

name: gsc-assistant
description: Google Search Console indexing assistant. Use when the user wants to track page indexing status, compare sitemap against GSC indexed pages, manage submission tracking, or move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list. Maintains two tracking files (indexed.md, to-index.md) with prioritization support.

GSC Assistant Skill

Purpose

This skill helps manage Google Search Console indexing status by maintaining two markdown tracking files:

indexed.md - All indexed pages in two tables:
- "Indexed Public" - URLs confirmed in GSC export data
- "Indexed With Lag" - URLs confirmed via URL Inspection (not yet in export)
to-index.md - Pages awaiting indexing:
- Difference between sitemap and total indexed URLs
- Prioritized by categories (configurable)
- Tracks submission dates

When to Use This Skill

User asks about "indexing status" or "GSC indexing"
User wants to "compare sitemap with indexed pages"
User mentions "URL inspection" or "false positives"
User needs to "track submissions" or "indexing progress"
User asks to "move indexed pages" or "update indexing status"
User wants to "generate indexing report"

Key Concepts

GSC Data Lag

Google Search Console export data has approximately 2 weeks lag. Pages that show as indexed in URL Inspection may not appear in the export yet. These are tracked separately as "Indexed With Lag".

False Positives

When checking to-index pages via URL Inspection:

If indexed: Mark as "false positive - indexed" in Submitted column
Pre-processing moves these to indexed.md (Indexed With Lag table)
The "Detected" date is inferred from when the entry was added to to-index

Priority Categories

to-index.md organizes pages by priority:

Priority 1: High-value content series
Priority 2: Recent content (current/previous year)
Priority 3: Specific content collections
Lower priorities: Archive pages, pagination, etc.

File Schemas

indexed.md

markdown

# Indexed Pages

## Indexed Public (GSC Export)

*Last updated: YYYY-MM-DD*
*Source: gsc-export.csv*

| # | URL | Last Crawled |
|---|-----|--------------|
| 1 | https://example.com/page-1/ | 2025-12-01 |
| 2 | https://example.com/page-2/ | 2025-12-02 |

## Indexed With Lag (URL Inspection Confirmed)

*Pages confirmed indexed via URL Inspection but not yet in GSC export*

| # | URL | Detected | Confirmed |
|---|-----|----------|-----------|
| 1 | https://example.com/new-page/ | 12 Dec 2025 | 12 Dec 2025 |

to-index.md

markdown

# Pages To Index

*Generated: YYYY-MM-DD*
*Total: X pages*

## Priority 1: [Category Name]

| # | URL | Submitted |
|---|-----|-----------|
| 1 | https://example.com/important-page/ | 12 Dec |
| 2 | https://example.com/another-page/ | - |

## Priority 2: [Category Name]

| # | URL | Submitted |
|---|-----|-----------|
| 1 | https://example.com/recent-post/ | - |

Workflow

Initial Setup

Import GSC export CSV to create indexed.md (Indexed Public table)
Extract sitemap URLs
Calculate difference (sitemap - indexed = to-index)
Categorize to-index pages by priority
Generate to-index.md

Show full SKILL.md (165 more words)Show less

Regular Updates

Pre-processing: Scan to-index.md for "false positive - indexed" entries
Move false positives to indexed.md (Indexed With Lag table)
Set "Detected" date from when entry was in to-index
Set "Confirmed" date to current date
Remove from to-index.md
Update counts and statistics

Manual Operations

Mark submissions: Update "Submitted" column with date
Check status: Use URL Inspection, mark result
Refresh data: Import new GSC export, recalculate

Configuration

Create working files in project directory:

project/
├── gsc-export.csv          # GSC indexed pages export
├── sitemap.xml             # Site sitemap (or use dist/sitemap.xml)
├── indexed.md              # Tracking file (generated)
└── to-index.md             # Tracking file (generated)

Commands

Generate Initial Files

"Generate indexing tracking files from GSC export and sitemap"

Pre-process False Positives

"Process false positives and update indexed list"

Update Submission Status

"Mark [URL] as submitted on [date]"

Refresh From New Export

"Update indexed list from new GSC export"

Generate Statistics

"Show indexing progress statistics"

Statistics Output

INDEXING STATUS SUMMARY
=======================

Indexed Public (GSC):     789 pages
Indexed With Lag:          12 pages
Total Indexed:            801 pages

Sitemap Total:          2,054 pages
To Index:               1,253 pages

Progress:                 39.0%

By Priority:
- Priority 1: 55 remaining (4 false positives moved)
- Priority 2: 7 remaining
- Priority 3: 290 remaining

Example Usage

User: "I just checked some URLs in GSC URL Inspection and marked them as false positive - indexed. Process those and update the tracking files."

Claude will:

Scan to-index.md for entries with "false positive - indexed"
Extract those URLs and their original detection dates
Add them to indexed.md Indexed With Lag table
Remove them from to-index.md
Update row numbers and counts
Report changes made

Files

Just SKILL.md in workflows/content-creator-workflow/.claude/skills/gsc-assistant of nicepkg/ai-workflow.

Open the folder on GitHubat commit d167b41

Compare with similar skills

Gsc Assistant 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.

Gsc Assistant compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gsc Assistant this skillnicepkg/ai-workflow	285	—	~1.3k	Automated safety check: Pass	MIT	8 mo ago
Agile Product Owneralirezarezvani/claude-skills	28k	3 repos	~3.2k	Automated safety check: Pass	MIT	1 mo ago
Prioritization Framework Advisordeanpeters/Product-Manager-Skills	7.2k	2 repos	~4.2k	Automated safety check: Pass	Custom licence	1 mo ago
Strategic Roadmap Planningdeanpeters/Product-Manager-Skills	7.2k	2 repos	~4.7k	Automated safety check: Pass	Custom licence	1 mo ago
Idea Validatoraakashg/pm-claude-skills	112	—	~2.3k	Automated safety check: Pass	MIT	2 mo ago
Triagejoa23/linear-cli	144	—	~699	Automated safety check: Pass	MIT	24 days ago

Similar skills

Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
28k GitHub starsUsed in 3 repos~3.2k tokens
Product & Project ManagementAuto-check passed
Prioritization Framework Advisor
deanpeters/Product-Manager-Skills
Picks the right prioritization framework for your stage and context instead of defaulting to RICE or ICE out of habit.
7.2k GitHub starsUsed in 2 repos~4.2k tokens
Product & Project ManagementAuto-check passed
Strategic Roadmap Planning
deanpeters/Product-Manager-Skills
Sequences prioritization, epic definition, and stakeholder alignment into a release plan that ladders up to business outcomes.
7.2k GitHub starsUsed in 2 repos~4.7k tokens
Product & Project ManagementAuto-check passed
Idea Validator
aakashg/pm-claude-skills
A skill your agent uses when the user asks to validate a product idea, stress-test an idea, evaluate whether an idea is good, or decide whether to build something.
112 GitHub stars~2.3k tokensUpdated 2 mo ago
Product & Project ManagementAuto-check passed
Triage
joa23/linear-cli
Triage and prioritize Linear backlog issues using the linear CLI.
144 GitHub stars~699 tokensUpdated 24 days ago
Product & Project ManagementAuto-check passed
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
713 GitHub stars~1.1k tokensUpdated 3 days ago
Product & Project ManagementAuto-check passed

Questions about Gsc Assistant

What does Gsc Assistant do?

Google Search Console indexing assistant. An agent skill from nicepkg/ai-workflow. Gsc Assistant is an agent skill from nicepkg/ai-workflow. Google Search Console indexing assistant.

When should I use Gsc Assistant?

Gsc Assistant fits situations like: the user wants to track page indexing status; compare sitemap against GSC indexed pages; manage submission tracking; move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list.

How do I install Gsc Assistant in Claude Code?

Run `npx skills add nicepkg/ai-workflow --skill gsc-assistant -a claude-code`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/gsc-assistant in nicepkg/ai-workflow) into .claude/skills/gsc-assistant in your project. Claude Code loads it when a task matches its description.

How do I install Gsc Assistant in Codex?

Run `npx skills add nicepkg/ai-workflow --skill gsc-assistant -a codex`. Or copy the skill folder (workflows/content-creator-workflow/.claude/skills/gsc-assistant in nicepkg/ai-workflow) into .agents/skills/gsc-assistant in your project. Codex loads it when a task matches its description.

Can I use Gsc Assistant in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nicepkg/ai-workflow --skill gsc-assistant -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsc-assistant, .gemini/skills/gsc-assistant, .github/skills/gsc-assistant and .opencode/skills/gsc-assistant in your project.

What does Gsc Assistant need to run?

SKILL.md names no scripts, command-line tools or credentials: Gsc Assistant is instructions for the agent only.

Does Gsc Assistant access the network?

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.

Is Gsc Assistant safe to install?

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.

What licence does Gsc Assistant use?

Gsc Assistant is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gsc Assistant use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gsc Assistant?

Skills that share tags, products or a category with Gsc Assistant: Agile Product Owner (alirezarezvani/claude-skills, 28k stars), Prioritization Framework Advisor (deanpeters/Product-Manager-Skills, 7.2k stars), Strategic Roadmap Planning (deanpeters/Product-Manager-Skills, 7.2k stars) and Idea Validator (aakashg/pm-claude-skills, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gsc Assistant?

nicepkg (a GitHub organization) maintains it in nicepkg/ai-workflow, which has 285 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on January 20, 2026.

Source: nicepkg/ai-workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gsc Assistant

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

GSC Assistant Skill

Purpose

When to Use This Skill

Key Concepts

GSC Data Lag

False Positives

Priority Categories

File Schemas

indexed.md

to-index.md

Workflow

Initial Setup

Regular Updates

Manual Operations

Configuration

Commands

Generate Initial Files

Pre-process False Positives

Update Submission Status

Refresh From New Export

Generate Statistics

Statistics Output

Example Usage

Files

Compare with similar skills

Similar skills

More from nicepkg/ai-workflow

Related

Questions about Gsc Assistant