telemetry
Skill17 starsChanged 23 days agoMITView on GitHub
Internal utility for the skills library itself — opt-in, local-first, privacy-respecting usage telemetry and update checks. Provides version checking, usage logging, and usage reporting for the skills in this repo. Use only when asked to view skill usage stats, configure telemetry opt-in/out, wire a skill to log its own runs, or check for skill updates.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- LeanMeanCleanApps/CleanModelContextProtocoltheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- SethGammon/Citadeltheir own version, first seen Nov 4, 2026
- microsoft/power-platform-skillstheir own version, first seen Oct 13, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use dashboard, create-skill and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
GoogleSkilldashboard
Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).
Also in 3 projects that use this
ElasticSkillcreate-skill
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- carla-simulator/carla★ 15ksame name
- openai/plugins★ 7.8ksame name
- microsoft/power-platform-skills★ 1.1ksame name
- SethGammon/Citadel★ 927same name
- egregore-labs/egregore★ 293same name
- magnus919/agent-skills★ 172same name
- mayankjain1815-commits/CITADEL★ 4same name
- LeanMeanCleanApps/CleanModelContextProtocol★ 1same name
- MMACABRE/SKILLS★ 1same name
- academysim/claude-code-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository38 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adversarial-claims-reviewerSkill
- autoresearchSkill
- browser-testing-with-devtoolsSkill
- codebase-cost-estimatorSkill
- code-review-and-qualitySkill
- content-opsSkill
- content-pipelineSkill
- conversion-opsSkill
- data-model-documentationSkill
- data-model-verificationSkill
- deployment-pipelinesSkill
- findings-ledgerSkill
- game-balancerSkill
- game-systems-designerSkill
- godot-engineerSkill
- growth-engineSkill
- iap-managerSkill
- library-investigatorSkill
- marketing-shaperSkill
- memory-extractionSkill
- outbound-engineSkill
- phaser-engineerSkill
- planning-and-task-breakdownSkill
- prompt-shaperSkill
- release-managerSkill
- revenue-intelligenceSkill
- rust-engineerSkill
- security-engineeringSkill
- securitySkill
- seo-opsSkill
- session-stateSkill
- skill-library-reviewSkill
- typescript-analyticsSkill
- typescript-data-engineeringSkill
- typescript-testing-backendSkill
- typescript-testing-frontendSkill
- web3-smart-contract-engineeringSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
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
- Very specific: line 22
All state lives under the telemetry data directory — by default ~/.ai-marketing-skills/, the upstream location, which can differ per …
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Telemetry
Internal, opt-in, local-first telemetry for the skills in this repository. It answers two questions: which skills get used (and how reliably)? and is a newer version of the library available? Every run is logged to a local file regardless of opt-in; data only leaves the machine if the user has explicitly opted in. No PII is ever collected — see README.md for the full field list and privacy commitment.
Where data lives
All state lives under the telemetry data directory — by default ~/.ai-marketing-skills/, the upstream location, which can differ per install:
| Path | Written by | Contents |
telemetry-config.json | telemetry_init.py | opted_in (bool), device_id (random UUID), created |
analytics/skill-usage.jsonl | telemetry_log.py | one JSON object per skill run (append-only) |
version-cache.json | version_check.py | last GitHub release seen + check timestamp (24h TTL) |
Each line in skill-usage.jsonl records only anonymous fields: skill name, duration (ms), success, version, OS, arch, Python version, UTC timestamp, and the random device_id. Never code, paths, repo names, or content.
Tools
| Script | Purpose | Invocation |
telemetry_init.py | Configure opt-in/out (interactive on first run) | python3 telemetry/scripts/telemetry_init.py (or --yes / --no) |
telemetry_log.py | Log one skill run (called by a skill's preamble) | see integration pattern below |
telemetry_report.py | View local usage stats | python3 telemetry/scripts/telemetry_report.py (--json, --skill <name>) |
version_check.py | Check for a newer library release | python3 telemetry/scripts/version_check.py |
Logging a skill's runs
A skill opts into telemetry by calling telemetry_log.py once at the end of its run. The script always appends to the local JSONL log, and additionally POSTs to the analytics endpoint only if the user opted in. It fails silently and never blocks execution. All four flags are required:
python3 telemetry/scripts/telemetry_log.py \
--skill my-skill-name \
--duration 4500 \
--success true \
--version 1.0.0Capture a start time before the work, compute --duration in milliseconds after, and pass --success false if the run errored. The endpoint in telemetry_log.py is a stub (ANALYTICS_ENDPOINT) — replace it with a real URL before remote send does anything.
Reading the stats
python3 telemetry/scripts/telemetry_report.py # human-readable summary
python3 telemetry/scripts/telemetry_report.py --json # machine-readable
python3 telemetry/scripts/telemetry_report.py --skill seo-ops # filter to one skillReports total runs, runs in the last 7/30 days, per-skill success rates and average durations, and the most-used skill. Reads only the local log — works the same whether or not you opted in.
Checking for updates
python3 telemetry/scripts/version_check.pyCompares a local VERSION file against the latest GitHub release, caches the result for 24h, and stays silent unless a newer version exists. It needs a VERSION file at the repo's skills root (.claude/skills/VERSION) containing the current version (e.g. 1.0.0). If that file is absent the script has no baseline and stays silent rather than reporting a false update — create the file to enable update notices.
Privacy
- Opt-in only — nothing is sent without explicit consent.
- Local-first — usage is always stored locally for your own inspection.
- No PII — no names, emails, paths, repo names, or content.
- Revocable — delete
telemetry-config.jsonfrom the telemetry data directory (by default~/.ai-marketing-skills/) and re-runtelemetry_init.py.
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.