Agent skill

Telemetry

by evloghq in evloghq/evlog

Answer questions about how the evlog CLI is used in production and surface interesting findings from the telemetry dashboard's MCP.

MITAuto-check passedDevOps & Cloud

Install Telemetry

skills CLI
$ npx skills add evloghq/evlog --skill telemetry -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install evloghq/evlog telemetry --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/evloghq/evlog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/evi/agent/skills/telemetry .claude/skills/telemetry && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
telemetry
GitHub stars
1.9k
Token cost
~553 tokens
SKILL.md length
268 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Answer questions about how the evlog CLI is used in production and surface interesting findings from the telemetry dashboard's MCP.

  • Tasks that involve Observability
  • SKILL.md covers The tools, What is interesting and Form
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Telemetry is an agent skill from evloghq/evlog. Answer questions about how the evlog CLI is used in production and surface interesting findings from the telemetry dashboard's MCP. Load this when asked about CLI usage, telemetry, adoption, flags, or "what's happening in the CLI", and when the digest needs its CLI usage section.

Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Observability. It works with Model Context Protocol. The repository describes itself as: Digging through logs is not observability. It's hope — wide events, structured errors, TypeScript-first, every runtime. The licence is MIT.

When your agent uses it

  • Tasks that involve Observability

Example prompts

  • “s happening in the CLI”
  • “/telemetry”

What it can do on your machine

Read from SKILL.md and the folder at commit 59a105f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Telemetry loads about 553 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 268 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~553

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from evloghq/evlog at commit 59a105f, republished under its MIT licence (© evloghq). 268 words, ~553 tokens.

Download SKILL.mdSave it as .claude/skills/telemetry/SKILL.md (or your agent's skills folder).
name
telemetry
description
Answer questions about how the evlog CLI is used in production and surface interesting findings from the telemetry dashboard's MCP. Load this when asked about CLI usage, telemetry, adoption, flags, or "what's happening in the CLI", and when the digest needs its CLI usage section.

Telemetry

Read-only production telemetry for the evlog CLI and anything else reporting through @evlog/telemetry, served by the telemetry app's MCP (telemetry__* tools). Ground every answer in the tools; never guess usage from memory.

The tools

  • telemetry-stats: aggregate for a range (24h/7d/30d) with the preceding equal window for comparison, breakdowns by environment, tool, source, Node major, tool version and OS, top commands, top error codes, duration percentiles, activity timeline.
  • telemetry-adoption: version rollout over time, new vs returning machines, weekday/hour punchcard, flag/custom-field breakdown.
  • telemetry-runs: the raw event list, filterable and sortable, with pagination.
  • telemetry-run: everything recorded for one run by id (flags, custom fields, environment).

What is interesting

  • Version adoption: are users moving to newer CLI versions? A release stalling in adoption is a signal that the upgrade path hurts.
  • Source mix: terminal vs CI vs agents vs automation. A shift here changes what the numbers mean.
  • Flags and custom fields: what people actually enable. A flag nobody uses may deserve deprecation; a custom field spreading suggests a workflow worth documenting.
  • Errors: top error codes and their trend. A code climbing week over week is an incident lead, not a footnote.
  • Period-over-period shifts: telemetry-stats returns the previous equal window; lean on it before calling anything a change.

Form

  • Prefer range: '7d' for stable signals, '30d' for adoption questions, '24h' only when asked about today.
  • Answer with numbers and a one-line interpretation. Cite the window. When the data is flat or empty, say so in one line instead of stretching it.
  • The dashboard serves generated sample data until real events land; treat unusually clean numbers as suspect on a fresh deployment.

© evloghq, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in apps/evi/agent/skills/telemetry of evloghq/evlog.

Open the folder on GitHubat commit 59a105f

Compare with similar skills

Telemetry next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Telemetry compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Telemetry this skillevloghq/evlog1.9k—~553Automated safety check: PassMIT
Kubernetes Network Root Cause Analysiskubeshark/kubeshark12k—~5.3kAutomated safety check: PassApache-2.0
UModel Root Cause Analysisalibaba/UnifiedModel412—~1.9kAutomated safety check: PassCustom licence
Observability Triageevery-app/open-seo23k—~1.7kAutomated safety check: PassMIT
Agentmeasureroy-tong/AgentMeasure218—~753Automated safety check: PassMIT
Logging Observabilitygetsentry/toolkit917—~2.6kAutomated safety check: PassCustom licence

Similar skills

  • Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.

    12k GitHub stars~5.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • UModel Root Cause Analysis

    alibaba/UnifiedModel

    Investigates a service incident to its root cause by querying a UModel object graph alongside metrics, logs, topology and recent deployments.

    412 GitHub stars~1.9k tokensUpdated 14 days ago
    DevOps & CloudAuto-check passed
  • Observability Triage

    every-app/open-seo

    Triage OpenSEO production errors in Cloudflare Workers Observability — verified query recipes, counting gotchas, and a known-noise filter list applied automatically.

    23k GitHub stars~1.7k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Agentmeasure

    roy-tong/AgentMeasure

    Check whether agent telemetry preserves measurement semantics.

    218 GitHub stars~753 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Logging Observability

    getsentry/toolkit

    Official

    Review code for correct logging and error handling patterns.

    917 GitHub stars~2.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • AWS Cost Operations

    zxkane/aws-skills

    AWS cost optimization, monitoring, and operational excellence expert.

    367 GitHub starsUsed in 1 repo~2.4k tokens
    DevOps & CloudAuto-check passed

More from evloghq/evlog

All 20 skills in this repo
  • Walks through adding a new built-in evlog drain adapter for an observability platform: source, build config, exports, tests, docs and PR scope.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Guides adding a new built-in enricher to the evlog package, covering the source, tests, docs, README, a related skill and a changeset.

    1.9k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Walks a contributor through adding a new HTTP framework integration to the evlog logging package: middleware source, build entry, exports, tests, example app and docs.

    1.9k GitHub stars~5k tokensUpdated yesterday
    Auto-check: notes
  • Walks through adding a new rule or framework adapter to `evlog map` in @evlog/cli, from the rule source and registry to types, tests, docs and the published skill.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Rules for writing and reviewing evlog docs, blog posts, READMEs, skills and AGENTS.md files, with separate review and rewrite roles, a house voice and a catalog of AI-sounding tells.

    1.9k GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Before After

    evloghq/evlog

    Produce a before/after visual comparison of an evlog surface (landing, docs, telemetry, playgrounds) and share it as public Blob URLs.

    1.9k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Telemetry

What does Telemetry do?

Answer questions about how the evlog CLI is used in production and surface interesting findings from the telemetry dashboard's MCP. Telemetry is an agent skill from evloghq/evlog. Answer questions about how the evlog CLI is used in production and surface interesting findings from the telemetry dashboard's MCP.

When should I use Telemetry?

Telemetry fits situations like: tasks that involve Observability.

How do I install Telemetry in Claude Code?

Run `npx skills add evloghq/evlog --skill telemetry -a claude-code`. Or copy the skill folder (apps/evi/agent/skills/telemetry in evloghq/evlog) into .claude/skills/telemetry in your project. Claude Code loads it when a task matches its description.

How do I install Telemetry in Codex?

Run `npx skills add evloghq/evlog --skill telemetry -a codex`. Or copy the skill folder (apps/evi/agent/skills/telemetry in evloghq/evlog) into .agents/skills/telemetry in your project. Codex loads it when a task matches its description.

Can I use Telemetry in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add evloghq/evlog --skill telemetry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/telemetry, .gemini/skills/telemetry, .github/skills/telemetry and .opencode/skills/telemetry in your project.

What does Telemetry need to run?

SKILL.md names no scripts, command-line tools or credentials: Telemetry is instructions for the agent only.

Does Telemetry access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Telemetry safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Telemetry use?

Telemetry is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Telemetry use?

About 553 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Telemetry?

Skills that share tags, products or a category with Telemetry: Kubernetes Network Root Cause Analysis (kubeshark/kubeshark, 12k stars), UModel Root Cause Analysis (alibaba/UnifiedModel, 412 stars), Observability Triage (every-app/open-seo, 23k stars) and Agentmeasure (roy-tong/AgentMeasure, 218 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Telemetry?

evloghq (a GitHub organization) maintains it in evloghq/evlog, which has 1,887 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 7, 2026.

Source: evloghq/evlog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.