telemetry-inspect SKILL.md skillA
telemetry-inspect from yonatangross/orchestkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yonatangross/orchestkit/telemetry-inspect@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yonatangross/orchestkit
- Path
plugins/ork/skills/telemetry-inspect/SKILL.md- Versions recorded
- 10
- Latest version
- v1.0.0, committed Oct 16, 2026
- First version recorded
- Jul 15, 2026
- Size
- 11,311 bytes
- Repository stars
- 299
- License
- MIT
Inspects the OrchestKit telemetry pipeline for the current project — lists all known telemetry files with write counts, sizes, schema status, growth trend, and orphan detection. Use when verifying the observability pipeline is healthy, debugging a missing writer, or auditing which files have schema locks vs. which are drift-vulnerable. Read-only — never modifies telemetry files.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# telemetry-inspect
One-shot health check for OrchestKit's telemetry pipeline. Reports writer activity, file sizes, schema lock coverage, orphan files, and growth warnings. Use when verifying the pipeline is flowing correctly or debugging a missing writer.
## When to use
- Before or after a risky hook refactor, to prove telemetry still writes as expected
- Weekly health check on a long-running project
- When `analytics` output looks suspicious — inspect the underlying data first
- When adding a new telemetry file and wanting to confirm it's picked up
- Auditing which files are schema-locked vs. drift-vulnerable
## What it checks
1. **Writer activity** — for each registered telemetry file, recent write count (from mtime scan) and last-write delta
2. **File health** — size (warn at 256 KB, critical at 1 MB), line count, mtime
3. **Schema lock status** — which files have validators in `lib/telemetry-schemas.ts`
4. **Orphan detection** — files on disk under `.claude/{telemetry,logs,state,feedback}/` that aren't in the registry (possible stale writer or new file needing schema), plus inventory rows whose writer hook no longer exists in `src/hooks/src/` (dead writer → orphan)
…Read the whole file at its exact version.
How to install
mdr add yonatangross/orchestkit/telemetry-inspect@sha256:32960c6e10cf0f95The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_ld6xclezhr7h7joq)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Jul 15, 2026 and Oct 16, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-16 | 301efc4 | 11,311 B | A | view · diff |
| v1.0.0 | 2026-09-29 | 105a980 | 11,325 B | A | view · diff |
| v1.0.0 | 2026-09-28 | 220adb4 | 11,328 B | A | view · diff |
| v1.0.0 | 2026-09-20 | 02cb935 | 11,345 B | A | view · diff |
| v1.0.0 | 2026-09-09 | 4f38cbc | 11,345 B | A | view · diff |
| v1.0.0 | 2026-09-06 | 900de6c | 11,375 B | A | view · diff |
| v1.0.0 | 2026-08-29 | 2aed0b0 | 11,580 B | A | view · diff |
| v1.0.0 | 2026-07-25 | 47b78fb | 11,580 B | A | view · diff |
| v1.0.0 | 2026-07-16 | 7e40ffd | 11,580 B | A | view · diff |
| v1.0.0 | 2026-07-15 | e75d8c9 | 9,682 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11311 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yonatangross/orchestkit · 299 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ld6xclezhr7h7joq GET https://markdownregistry.com/api/v1/resolve?ref=yonatangross/orchestkit/telemetry-inspect GET https://markdownregistry.com/api/v1/blob/32960c6e10cf0f95b02af8a5f590f95dded398515e70a9d5460e073f011ce221
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.