agentleFS
Sign inStart free
jeftekharijeftekhari/google-analytics/skills/remove-analytics/SKILL.md

remove-analytics

Skill2 starsChanged 9 months agoMITView on GitHub

Safely remove Google Analytics from a project. Cleans up all tracking code, dependencies, and environment variables.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask the user to confirm they want to remove analytics:

    line 13
  2. Distinctive:

    Import statements for analytics utilities

    line 27
  3. Distinctive:

    Remove the code or file

    line 36
  4. Very specific:

    Remove analytics-related packages: npm uninstall @types/gtag.js (or equivalent)

    line 41
  5. Very specific:

    Remove environment variables from .env.example

    line 42
  6. Distinctive:

    Update any documentation that references analytics

    line 43

≈ “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

Remove Analytics Skill

You are removing Google Analytics from this project. This is a destructive action - confirm with the user before proceeding.

Step 1: Confirm Intent

Ask the user to confirm they want to remove analytics:

"This will remove all Google Analytics tracking from your project. This action will:

  • Remove gtag scripts and components
  • Remove analytics utility files
  • Remove related environment variables from .env.example
  • Remove npm packages if any

Type 'yes' to confirm."

Step 2: Find All Analytics Code

Search for:

  • Files containing gtag, dataLayer, GoogleAnalytics
  • Import statements for analytics utilities
  • Script tags with googletagmanager.com
  • Environment variables: GA_, GTAG_, MEASUREMENT_ID
  • Package.json dependencies: @types/gtag.js, react-ga4, vue-gtag, etc.

Step 3: Remove Code

For each finding:

  1. Show the file and code to be removed
  2. Remove the code or file
  3. Clean up any orphaned imports

Step 4: Clean Up

  • Remove analytics-related packages: npm uninstall @types/gtag.js (or equivalent)
  • Remove environment variables from .env.example
  • Update any documentation that references analytics

Step 5: Summary

Provide a summary of:

  • Files deleted
  • Files modified
  • Packages removed
  • Environment variables removed
  • Any manual steps needed (like removing actual env values)

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