recorded-field-attribution SKILL.md skillA
recorded-field-attribution from confighub/cub-scout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add confighub/cub-scout/recorded-field-attribution@git:20260930.dffb108Pins git:20260930.dffb108 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- confighub/cub-scout
- Path
evals/recorded-mcp-probe/economy-skill/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260930.dffb108, committed Sep 30, 2026
- Size
- 1,550 bytes
- Repository stars
- 14
- License
- MIT
Use when asked which manager is recorded for a field on a known Kubernetes resource, especially when the resource and exact canonical field path are supplied. Route a known exact-path question directly to the recorded `explain` MCP tool instead of doing broad rediscovery first. This is a preference for compact evidence, not a requirement to call a tool.
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
# Recorded field attribution For a known resource and exact canonical field path, prefer one direct call to the available `explain` MCP tool with the resource and `field_path`. The returned field-attribution evidence is scoped to that path; it is not a substitute for the ordinary resource summary. Do not call inventory, health, lineage, or comparison tools first solely to rediscover manager evidence. Do not guess a canonical path. If the resource or path is not known, use only the recorded evidence already available to identify it, or ask for the missing detail. Raw recorded object evidence may still be read when it is needed to check a result or understand an unknown response; the compact tool result does not prohibit that drill-down. Treat missing, malformed, unrecognized, or ambiguous path evidence as unknown, without substituting resource-level manager summaries. Manager strings do not identify a person or prove the latest writer. Resource ownership classification and field-manager evidence are separate facts. This package is recorded-only: never fall back to a live cluster, kubectl, shell, or an unrelated source.
Read the whole file at its exact version.
How to install
mdr add confighub/cub-scout/recorded-field-attribution@sha256:9f77fb53bec0cf60The line at the top of this page pins the label git:20260930.dffb108, 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_zxtj6b6nwgnar66c)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 30, 2026.
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 (1550 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
confighub/cub-scout · 14 stars · license MIT · pushed 2026-10-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zxtj6b6nwgnar66c GET https://markdownregistry.com/api/v1/resolve?ref=confighub/cub-scout/recorded-field-attribution GET https://markdownregistry.com/api/v1/blob/9f77fb53bec0cf60e42df7b86e2300a081e2dfacaa8f848adf3150265007215d
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.