telemetry

Add OSLog-based telemetry and debugging instrumentation to macOS applications.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/oliverames/ames-claude --skill telemetry-oliverames
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telemetry
Source: https://github.com/oliverames/ames-claude/tree/main/plugins/build-macos-apps-codex/skills/telemetry
Command: npx skills add https://github.com/oliverames/ames-claude --skill telemetry-oliverames

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Use OSLog for structured, category-based logging (Windowing, Sidebar, Commands, MenuBar, Sync, Import) to observe UI events and lifecycle transitions.
  • Keep logs concise and privacy-conscious, avoid secrets, and use signposts for timing when measuring performance.
  • Verify instrumentation by inspecting Console.app or streaming logs after a local run.

Quick Start

Instrument your macOS app with lightweight telemetry using OSLog and verify events after a build/run.

Frequently Asked Questions about telemetry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add telemetry to a macOS app using OSLog?

Add telemetry to a macOS app by wiring OSLog with category-based subsystems to observe UI events and lifecycle transitions. Use the Logger or os.Logger API to instrument window opens, sidebar interactions, and menu bar actions.

What is the best way to verify macOS app telemetry after a build and run?

Verify macOS app telemetry by inspecting Console.app or streaming logs after a local run. This confirms that your OSLog instrumentation correctly captures events across windowing, sidebar, and menu bar workflows.

How do I keep OSLog instrumentation concise and avoid logging secrets?

Keep OSLog instrumentation concise and privacy-conscious by enforcing safe logging practices and avoiding secrets. Use category-based subsystems to structure logs and apply signposts when measuring performance timing.

Can I measure performance timing in a macOS app using signposts?

Measure performance timing in a macOS app by using OSLog signposts. This allows you to capture timing intervals alongside category-based logging for windowing, sidebar, commands, menubar, sync, and import events.

Does OSLog support structured logging for specific UI events like sidebar interactions?

OSLog supports structured logging for specific UI events like sidebar interactions through category-based subsystems. This enables you to observe lifecycle transitions and user interactions across various macOS app workflows.

Why should I use category-based subsystems for macOS app debugging?

Use category-based subsystems for macOS app debugging to organize telemetry into distinct groups like Windowing, Sync, and Import. This structure keeps logs concise, avoids secrets, and simplifies verification via Console.