New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Telemetry

by robinebers in robinebers/openusage

Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running.

MITAuto-check passedDevOps & Cloud

Install Telemetry

skills CLI
$ npx skills add robinebers/openusage --skill telemetry -a claude-code

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

GitHub CLI
$ gh skill install robinebers/openusage 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/robinebers/openusage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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
4.3k
Token cost
~977 tokens
SKILL.md length
449 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running.

  • Works in 5 steps: Identify the behavior that needs… → Add the smallest useful instrumentation. → Build and run the app. → …
  • Wiring Logger / os.Logger
  • SKILL.md covers Quick Start, Core Guidelines, Minimal Logger Pattern and Workflow, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Telemetry is an agent skill from robinebers/openusage. Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running. Use when wiring Logger / os.Logger, adding log points for window/sidebar/menu-bar actions, reading runtime logs from Console or log stream, or confirming that expected events fire after a local run.

Its SKILL.md is about 980 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 macOS. The repository describes itself as: Burning through your subscriptions too fast? Paying for stuff you never use? Stop guessing. OpenUsage is free and open source. The licence is MIT.

When your agent uses it

  • Wiring Logger / os.Logger
  • Adding log points for window/sidebar/menu-bar actions
  • Reading runtime logs from Console
  • Confirming that expected events fire after a local run

Example prompts

  • “/telemetry”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify the behavior that needs observability.
  2. Add the smallest useful instrumentation.
  3. Build and run the app.
  4. Read runtime logs and verify the event fired.
  5. Tighten or remove instrumentation.

What it can do on your machine

Read from SKILL.md and the folder at commit cb21465. 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 (its code samples are swift).

    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 977 tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 449 words of instructions outside code blocks.

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

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 robinebers/openusage at commit cb21465, republished under its MIT licence (© robinebers). 449 words, ~977 tokens.

Download SKILL.mdSave it as .claude/skills/telemetry/SKILL.md (or your agent's skills folder).
name
telemetry
description
Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running. Use when wiring `Logger` / `os.Logger`, adding log points for window/sidebar/menu-bar actions, reading runtime logs from Console or `log stream`, or confirming that expected events fire after a local run.

Telemetry

Quick Start

Use this skill to add lightweight app instrumentation that helps debug behavior without turning the codebase into a logging landfill. Prefer Apple's unified logging APIs and verify the events after a build/run loop.

Core Guidelines

  • Prefer Logger from the OSLog framework for structured app logs.
  • Give each feature a clear subsystem/category pair so runtime filtering stays easy.
  • Log meaningful user and app lifecycle events: window opening, sidebar selection changes, menu commands, menu bar extra actions, sync/load milestones, and unexpected fallback paths.
  • Keep info logs concise and stable. Use debug logs for noisy state details.
  • Do not log secrets, auth tokens, personal data, or raw document contents.
  • Add signposts only when measuring timing or performance spans; do not overinstrument by default.

Minimal Logger Pattern

swift
import OSLog

private let logger = Logger(
  subsystem: Bundle.main.bundleIdentifier ?? "SampleApp",
  category: "Sidebar"
)

@MainActor
func selectItem(_ item: SidebarItem) {
  logger.info("Selected sidebar item: \(item.id, privacy: .public)")
  selection = item.id
}

Use feature-specific categories like Windowing, Commands, MenuBar, Sidebar, Sync, or Import so logs can be filtered quickly.

Workflow

  1. Identify the behavior that needs observability.

    • Window open/close
    • Sidebar or inspector selection changes
    • Menu or keyboard command actions
    • Menu bar extra actions
    • Background load/sync/import events
    • Error and recovery paths

  2. Add the smallest useful instrumentation.

    • Create one Logger per feature area or type.
    • Log action boundaries and key state transitions.
    • Prefer one high-signal line per user action over noisy value dumps.

  3. Build and run the app.

    • Use build-run-debug for the build/run loop.
    • If script/build_and_run.sh exists, prefer ./script/build_and_run.sh --telemetry for live telemetry checks or ./script/build_and_run.sh --logs for broader process logs.
    • Exercise the UI or command path that should emit telemetry.

  4. Read runtime logs and verify the event fired.

    • Use Console.app with a process/subsystem filter when that is the fastest manual check.
    • Use log stream --style compact --predicate 'process == "AppName"' for live terminal verification.
    • Prefer tighter predicates when you know the subsystem/category: log stream --style compact --predicate 'subsystem == "com.example.app" && category == "Sidebar"'

  5. Tighten or remove instrumentation.

    • If the event fires, keep only the logs that remain useful for future debugging.
    • If it does not fire, move the log closer to the suspected control path and rerun.
Show full SKILL.md (118 more words)Show less

Verification Checklist

  • The app builds after telemetry changes.
  • The relevant action emits exactly one clear log line or a small bounded sequence.
  • The log can be filtered by process, subsystem, or category.
  • No sensitive payloads are written to unified logs.
  • Noisy temporary debug logs are removed or demoted before finishing.

Guardrails

  • Do not use print as the primary app telemetry mechanism for macOS app code.
  • Do not leave a dense trail of permanent debug logs around every state mutation.
  • Do not claim an event is wired correctly until you have a concrete verification path through Console, log stream, or captured process output.
  • If the debugging task is mostly about crash/backtrace analysis rather than action telemetry, switch to build-run-debug.

© robinebers, 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 .agents/skills/telemetry of robinebers/openusage.

Open the folder on GitHubat commit cb21465

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 skillrobinebers/openusage4.3k—~977Automated safety check: PassMIT
Deploy Observabilityaliyun/alibabacloud-observability-mcp-server166—~2.6kAutomated safety check: NotesNone
Sls Dashboard Builderalibaba/loongsuite-pilot200—~1.8kAutomated safety check: PassApache-2.0
Loongsuite Pilot Insightalibaba/loongsuite-pilot200—~944Automated safety check: PassApache-2.0
Vercel Optimize Auditvercel-labs/agent-skills32k8 repos~4.3kAutomated safety check: PassNone
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT

Similar skills

  • Deploy Observability

    aliyun/alibabacloud-observability-mcp-server

    Deploy, start, and update the Alibaba Cloud Observability MCP Server (阿里云可观测 MCP Server).

    166 GitHub stars~2.6k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check: notes

  • Sls Dashboard Builder

    alibaba/loongsuite-pilot

    当任务需要创建、修改、扩展或重组阿里云 SLS 的 dashboard JSON 或可导入的大盘配置时使用；尤其适用于线上大盘、强对比的分析看板、已校验的查询包，或需要专业中文标签与指标定义的运维向大盘。

    200 GitHub stars~1.8k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Loongsuite Pilot Insight

    alibaba/loongsuite-pilot

    基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。

    200 GitHub stars~944 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Vercel Optimize Audit

    vercel-labs/agent-skills

    Official

    Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.

    32k GitHub starsUsed in 8 repos~4.3k tokens
    DevOps & CloudAuto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Kubeshark Installer

    kubeshark/kubeshark

    Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.

    12k GitHub stars~3.6k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes

More from robinebers/openusage

All 25 skills in this repo

  • Swiftui Patterns

    robinebers/openusage

    Best practices and example-driven guidance for building native macOS SwiftUI scenes and components, including windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and…

    4.3k GitHub stars~3.4k tokensUpdated 2 days ago
    Auto-check passed

  • macOS Telemetry

    robinebers/openusage

    Add and verify lightweight macOS runtime telemetry. An agent skill from robinebers/openusage.

    4.3k GitHub stars~934 tokensUpdated 2 days ago
    Auto-check passed

  • Release Swift

    robinebers/openusage

    Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes.

    4.3k GitHub stars~1.6k tokensUpdated 2 days ago
    Auto-check passed

  • Window Management

    robinebers/openusage

    Customize macOS 15+ SwiftUI windows and scene behavior using Window, WindowGroup, and macOS window modifiers.

    4.3k GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed

  • Appkit Interop

    robinebers/openusage

    Decide when and how to bridge a macOS app from SwiftUI into AppKit.

    4.3k GitHub stars~741 tokensUpdated 2 days ago
    Auto-check passed

  • Build Run Debug

    robinebers/openusage

    Build, run, and debug local macOS apps and desktop executables using shell-first Xcode and Swift workflows.

    4.3k GitHub stars~1.8k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Telemetry

What does Telemetry do?

Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running. Telemetry is an agent skill from robinebers/openusage. Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running.

When should I use Telemetry?

Telemetry fits situations like: wiring Logger / os.Logger; adding log points for window/sidebar/menu-bar actions; reading runtime logs from Console; confirming that expected events fire after a local run.

How do I install Telemetry in Claude Code?

Run `npx skills add robinebers/openusage --skill telemetry -a claude-code`. Or copy the skill folder (.agents/skills/telemetry in robinebers/openusage) 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 robinebers/openusage --skill telemetry -a codex`. Or copy the skill folder (.agents/skills/telemetry in robinebers/openusage) 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 robinebers/openusage --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 977 tokens (SKILL.md is roughly 3.9k 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: Deploy Observability (aliyun/alibabacloud-observability-mcp-server, 166 stars), Sls Dashboard Builder (alibaba/loongsuite-pilot, 200 stars), Loongsuite Pilot Insight (alibaba/loongsuite-pilot, 200 stars) and Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Telemetry?

robinebers (a GitHub user) maintains it in robinebers/openusage, which has 4,335 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 6, 2026.

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