knowledge-capture skillA
knowledge-capture is agent-read markdown (skill) from eltmon/overdeck: AI self-monitoring skill. Triggers proactively when AI detects confusion or makes corrected mistakes (wrong DB schema, incorrect assumptions, user corrections on key insights). Prompts to capture learnings as project-specific skills. NOT user-invoked - AI should reference this when confused..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Knowledge Capture This skill helps AI assistants recognize their own confusion and systematically capture project-specific knowledge to prevent repeated mistakes. ## When to Trigger (Self-Assessment) **IMPORTANT:** This skill is NOT user-invoked. As the AI, you should proactively invoke this when you detect ANY of these situations: ### High-Confidence Triggers (Always Invoke) 1. **Database Schema Mistakes** [category: `database`] - Queried a column that doesn't exist - Used wrong column name (e.g., `user_id` vs `userId` vs `owner_id`) - Assumed an index exists that doesn't - Got foreign key relationships wrong - Example: "SELECT created_at FROM users" → Error: column "created_at" doesn't exist (it's "createdAt") 2. **User Corrections on Architecture** [category: `architecture`] - User corrects you on how a system component works - User explains a non-obvious design pattern in use - User clarifies that "we don't do it that way here" - Example: "Actually, we use event sourcing here, not direct DB updates" 3. **API/Interface Misunderstandings** [category: `api`] - Called an API endpoint that doesn't exist …
Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/knowledge-capture@git:20260908.0c0074fmdr add eltmon/overdeck/knowledge-capture@sha256:9b034fa3249a0b7ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_juz3mrpyjmr6qz4g)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260908.0c0074f latest | 2026-09-08 | 0c0074f | 14,579 B | A | view · diff |
| git:20260618.e501626 | 2026-06-18 | e501626 | 14,449 B | A | view · diff |
| git:20260522.817c2c7 | 2026-05-22 | 817c2c7 | 14,459 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 (14579 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
eltmon/overdeck · 28 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_juz3mrpyjmr6qz4g GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/knowledge-capture GET https://markdownregistry.com/api/v1/blob/9b034fa3249a0b7e53dee12861f15c94984195c681020c97c473dc0b7e64e626
Your agent 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.