instrument-events
Skill14 starsChanged 38 days agoLicence not identifiedView on GitHub
Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.
In this repository74 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-analytics-instrumentationSkill
- agents-schemaSkill
- airbyteSkill
- airflowSkill
- analyze-account-healthSkill
- analyze-ai-topicsSkill
- analyze-chartSkill
- analyze-dashboardSkill
- analyze-experimentsSkill
- analyze-feedbackSkill
- bigquery-basicsSkill
- cloud-run-basicsSkill
- compare-user-journeysSkill
- coupler-ioSkill
- create-chartSkill
- create-dashboardSkill
- cubeSkill
- dagsterSkill
- daily-briefSkill
- data-appsSkill
- dbt-analytics-qaSkill
- dbtchartsSkill
- dbt-dagSkill
- dbt-developmentSkill
- dbt-fusionSkill
- dbt-mcp-serverSkill
- dbt-migrationSkill
- dbt-semantic-layerSkill
- dbt-to-smmlSkill
- dbt-troubleshootingSkill
- dbt-unit-testingSkill
- debug-replaySkill
- diagnose-errorsSkill
- diff-intakeSkill
- dignified-pythonSkill
- discover-analytics-patternsSkill
- discover-event-surfacesSkill
- discover-opportunitiesSkill
- droughtySkill
- Engagement ContextSkill
- engagement-status-reportSkill
- Fathom SyncSkill
- fivetranSkill
- gcloudSkill
- google-cloud-recipe-authSkill
- google-cloud-waf-cost-optimizationSkill
- google-cloud-waf-securitySkill
- hightouchSkill
- investigate-ai-sessionSkill
- looker-dashboard-mockupSkill
- lookml-content-authoringSkill
- lookml-content-authoringSkill
- metabaseSkill
- monitor-ai-qualitySkill
- monitor-experimentsSkill
- monitor-reliabilitySkill
- omniSkill
- project-reviewSkill
- Release DirectorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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
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.