oc-telemetry-ops
Telemetry operations harness — opt-in, local-first usage metering that records which skills and phases actually run, to a local .checkpoints/usage.sqlite store, then produces anonymized local aggregate exports. Use for /oc-telemetry, "usage metering", "opchain usage telemetry", "opt-in analytics", "which skills do people use", "usage stats", "dashboard data", "anonymized usage". Default stance is OFF — nothing is recorded until you explicitly enable it, and no prompt content or PII ever leaves the machine. Pairs with oc-cost-ops (cost per run) for the cost-per-feature dashboard stats. NOT application or production observability (oc-monitoring-ops).
Target: Databases. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Telemetry Ops
- /oc-telemetry — Command Reference
- How This Skill Fits the Build Pipeline
- Installed runtime
- The telemetryhandle checkpoint field (wire 1.1)
- Principle 1: Local-first metering, content-free by schema
- Principle 2: Opt-in — tracked state is not consent
- Principle 3: Aggregate-only export
On first invocation, read references/orchestrator.md and follow its welcome protocol. Answer "is anyone actually using this, and which parts?" — without betraying opchain's local-first, no-backend stance. Telemetry Ops meters skill/phase usage into a local SQLite store (.checkpoints/usage.sqlite), strictly opt-in, and produces an anonymized local aggregate export (pipelines run, most-used skill, model-tier mix, cost-per-shipped-feature). The public /dashboard currently uses sample data; export ingestion is not implemented. The CLI does not publish the raw store or the aggregate. This is not a hosted analytics product and not PostHog (that's the site's consent-gated client analytics). Telemetry Ops is about the skills pipeline's own usage, recorded where the work happens — locally, in git-adjacent state — so the numbers are real (they come from actual runs) and private (they stay put unless you export an aggregate). Default OFF. Tracked state is not consent. Metering does nothing until /oc-telemetry enable records opt-in in the gitignored local SQLite store. A telemetryhandle checkpoint field, including a cloned legacy enabled: true, is never consent. See references/privacy-consent.
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- asfbay-bit/opchain-skills
- Source file
- plugins/opchain/skills/oc-telemetry-ops/SKILL.md
- Fixed revision
- 1c7c7bd69a7d875a5dffb419911c24752ca6c285
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: asfbay-bit/opchain-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-10T17:01:27.050Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
Apache-2.0. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.