agentleFS
geniushub-seogeniushub-seo/gsc-mcp/.cursor/rules/gsc-mcp.mdc

gsc-mcp / rules

Cursor rule7 starsChanged 3 months agoMITView on GitHub

Safely install, diagnose, and use the gsc-mcp Google Search Console tools.

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,329 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository7 other files it gives its agents.

The file

We split this gsc-mcp.mdc into the rules it gives an agent

6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this rule whenever the user asks to install gsc-mcp, diagnose it, or analyse Google Search Console data.

    line 6
  2. Very specific:

    Run gsc-mcp doctor to diagnose credentials and API access.

    line 9
  3. Distinctive:

    Never print, read, or add OAuth tokens, ADC files, or service-account key contents to configuration or chat.

    line 10
  4. Very specific:

    Before a first data query, call list_sites when the property is not unambiguous.

    line 11
  5. Distinctive:

    Treat dates as Pacific Time and avoid the newest 2–4 days unless the user explicitly accepts incomplete data.

    line 12
  6. Very specific:

    Read truncated, scan_capped, and ordering before drawing a conclusion from a top-N response.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 6,873 Cursor rule 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
gsc-mcp.mdc
---
description: Safely install, diagnose, and use the gsc-mcp Google Search Console tools.
alwaysApply: false
---

Use this rule whenever the user asks to install gsc-mcp, diagnose it, or analyse Google Search Console data.

- For installation, follow `INSTALL.md`. Tell the user to run browser-opening OAuth commands themselves.
- Run `gsc-mcp doctor` to diagnose credentials and API access. Do not use `setup --dry-run` as a credential check.
- Never print, read, or add OAuth tokens, ADC files, or service-account key contents to configuration or chat.
- Before a first data query, call `list_sites` when the property is not unambiguous.
- Treat dates as Pacific Time and avoid the newest 2–4 days unless the user explicitly accepts incomplete data.
- Read `truncated`, `scan_capped`, and `ordering` before drawing a conclusion from a top-N response.
- Sitemap `submit` and `delete` are real writes. Do not use them as a test.

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.