apple-runtime-telemetry-workflow
/apple-runtime-telemetry-workflow
Add and verify privacy-aware Apple unified logging and signposts in macOS, iOS, and related Apple apps. Use when designing Logger categories, diagnosing intermittent runtime behavior, collecting focused evidence, or measuring an operation with OSSignposter.
- Author
- gaelic-ghost ↗
- Repository
- socket ↗
- Licence
- Apache-2.0
- Last repository change
- 26.08.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Add and verify privacy-aware Apple unified logging and signposts in macOS, iOS, and related Apple apps. Use when designing Logger categories, diagnosing intermittent runtime behavior, collecting focused evidence, or measuring an operation with OSSignposter.
Original author description
Add and verify privacy-aware Apple unified logging and signposts in macOS, iOS, and related Apple apps. Use when designing Logger categories, diagnosing intermittent runtime behavior, collecting focused evidence, or measuring an operation with OSSignposter.
How it works
- Purpose
- Workflow
- Guards
- References
SKILL.md preview
--- name: apple-runtime-telemetry-workflow description: Add and verify privacy-aware Apple unified logging and signposts in macOS, iOS, and related Apple apps. Use when designing Logger categories, diagnosing intermittent runtime behavior, collecting focused evidence, or measuring an operation with OSSignposter. --- # Apple Runtime Telemetry Workflow ## Purpose Add the smallest useful unified-log and signpost evidence to diagnose a concrete runtime question. This workflow owns `Logger`, subsystem/category design, privacy, evidence capture, and `OSSignposter` boundaries. It does not own generic server observability, analytics, crash reporting services, or broad event collection. ## Workflow 1. State the question to answer: lifecycle, command, window/scene transition, failure classification, or duration. Do not add telemetry without a specific observation need. 2. Choose a stable subsystem and a narrow category named for the owning feature. Keep a local logger close to that feature instead of creating an application-wide logging manager. 3. Emit a small lifecycle record at the transition and a precise error or fault record at a classified failure. Include non-sensitive identifiers only when they make the event actionable. 4. Leave interpolated values private by default. Mark a value `.public` only after confirming that it has no user, account, file-path, content, credential, or other sensitive-data meaning. 5. Use `OSSignposter` only when duration or event timing is the question. Begin and end the same measured operation, retain the interval state correctly, and inspect the result in Instruments rather than treating an ordinary log line as a timing measurement. 6. Reproduce the relevant flow and inspect the evidence in Xcode's debug console, Console, or the `log` tool. Filter by the documented subsystem/category and preserve only the minimal output needed to support the diagnosis. 7. Remove temporary high-volume records after the investigation, or keep a small durable lifecycle/error set with a clear operational value. ## Guards - Do not create a logging manager, repository, analytics pipeline, telemetry daemon, or remote collector for ordinary app diagnostics. - Do not put secrets, personal data, file contents, raw request bodies, authorization material, or full unreviewed object descriptions in logs. - Do not use `OSLogStore.local()` as a default app feature; Apple documents that local-store access needs an admin account and the `com.apple.logging.local-store` entitlement. - Do not claim a signpost proves a performance improvement until an Instruments capture measures the same scenario. - Hand ETTrace, memgraphs, leaks, and trace comparison to `ios-runtime-forensics-workflow`; hand build/run mechanics to `xcode-build-run-workflow`. ## References - `references/logger-privacy-and-evidence.md` - `references/signposts-and-runtime-capture.md`
Files in this package (4)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/logger-privacy-and-evidence.md 1 KB
- references/signposts-and-runtime-capture.md 1 KB
Versions
The database has no other skills named apple-runtime-telemetry-workflow.
Database snapshot: 13.11.2026 · package version 6fe9f2dbcbe5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100macos-telemetry
Add and verify lightweight macOS runtime telemetry. Use when wiring Logger events or inspecting logs for windows, sidebars, menus, and actions. - 100local-telemetry-c457cd7c
Add and verify lightweight macOS runtime telemetry. Use when wiring Logger events or inspecting logs for windows, sidebars, menus, and actions. - 100observability
Use when adding logging, instrumenting performance, wiring MetricKit, diagnosing production crashes or hangs, exporting logs for support, or choosing between print, Logger, signposts, and analytics SDKs. Writes and reviews Swift observability code on Apple platforms - unified logging (Logger… - 100oslog-logger-defaults
Set up logging for an Apple-platform Swift app with `os.Logger` and decide its `subsystem` / `category` naming and `privacy:` interpolation. Use when choosing a logging library (`os.Logger` vs swift-log `import Logging` vs CocoaLumberjack); when writing the first… - 100oslog
Read, stream, and analyze Apple unified logs (OSLog) for iOS/macOS apps. Auto-detects subsystem from Logger usage or bundle identifier. Supports live log show, real-time streaming, and .logarchive analysis with full predicate reference. Use when the user asks to check app logs,… - 90native
Native app development strategies including iOS/macOS (Apple platforms), Tauri desktop apps. Use when developing native mobile or desktop applications.