agentleFS
super0510super0510/GrowthLint/.claude/skills/generate-analytics-spec/SKILL.md

generate-analytics-spec

Skill2 starsChanged 8 months agoMITView on GitHub

Generate a complete analytics tracking plan with event taxonomy, code snippets, and QA checklist.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the analytics spec generator:

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/generate-analytics-spec

Generate a complete analytics tracking plan tailored to your site's detected pages and interactions.

Usage

/generate-analytics-spec <url>

Instructions

  1. Run the analytics spec generator:
cd /Users/sdm/Desktop/GrowthLint && python3 -c "import growthlint.cli; growthlint.cli.app()" -- generate-spec "$URL"
  1. Also check current integration health:
cd /Users/sdm/Desktop/GrowthLint && python3 -c "import growthlint.cli; growthlint.cli.app()" -- check-integrations "$URL"
  1. Enhance the spec with AI-powered additions:
    • Implementation code snippets: For each event, provide the exact code for the detected analytics tool (GA4 gtag, Segment analytics.track, PostHog posthog.capture, etc.)
    • Dashboard suggestions: What dashboards should be created? What metrics to track on each?
    • Funnel definition: Based on the detected pages, define the conversion funnel stages and which events mark each transition
    • Alert recommendations: What anomaly alerts should be set up? (e.g., "Alert if signup rate drops 20% day-over-day")
  2. Output as a complete, copy-pasteable tracking plan document.

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.