agentleFS
Sign inStart free
gomarble-aigomarble-ai/marketing-agent/skills/search-console-master-skill/SKILL.md

search-console-master-skill

Skill15 starsChanged 37 days agoMITView on GitHub

Use when analyzing Google Search Console data: organic search analysis, GSC data interpretation, opportunity scoring.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  1. Distinctive:

    All organic query, impression, CTR, and position data MUST come from Google Search Console.

    line 23
  2. Distinctive:

    Order: Run the GSC Analysis Protocol first.

    line 36
  3. Very specific:

    Guardrails: Follow references/guardrails.md before any organic/SEO recommendation.

    line 37
  4. Distinctive:

    No data = no guess: If GSC access or data is missing, do not infer keywords or estimate traffic—ask for access or stop.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Outside the GoMarble app. This methodology is GoMarble's own, kept in sync with the GoMarble connector.

  • GoMarble connector tools for this skill: gsc_list_properties, gsc_get_performance_overview, gsc_get_search_analytics, gsc_get_advanced_search_analytics, gsc_get_search_by_page_query, gsc_compare_search_periods, gsc_check_indexing_issues, gsc_inspect_url, gsc_inspect_url_enhanced, gsc_batch_url_inspection, gsc_get_site_details, gsc_get_sitemaps, gsc_list_sitemaps_enhanced, gsc_get_sitemap_details.

Organic Search (Google Search Console) – Master Skill

Skill Objective

Turn raw Search Console data into:

  • Revenue opportunities
  • Ranking leverage
  • Paid + Organic crossover insights
  • Actionable prioritization, not SEO busywork

HARD SOURCE-OF-TRUTH RULE

All organic query, impression, CTR, and position data MUST come from Google Search Console.

  • No synthetic keywords.
  • No model-estimated demand.
  • No substitutions.

Available Skills

#SkillPathPurpose
1GSC Analysis Protocolreferences/gsc-analysis-protocol.mdExtraction, normalization, intent/value, opportunity scoring, page-level intelligence

Rules

  • Order: Run the GSC Analysis Protocol first. All recommendations must use Google Search Console data only.
  • Guardrails: Follow references/guardrails.md before any organic/SEO recommendation.
  • No data = no guess: If GSC access or data is missing, do not infer keywords or estimate traffic—ask for access or stop.

When This Skill Is Triggered

Route here when user intent includes:

  • "organic growth"
  • "SEO opportunities"
  • "Search Console analysis"
  • "why organic traffic dropped"
  • "what content should we create"
  • "organic vs paid overlap"
  • "where should we focus SEO effort"

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free