meta-theory SKILL.md skillA

meta-theory from kimyx0207/meta_kim is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add kimyx0207/meta_kim/meta-theory@v3.0.0

Pins v3.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
kimyx0207/meta_kim
Path
canonical/skills/meta-theory/SKILL.md
Versions recorded
5
Latest version
v3.0.0, committed Nov 15, 2026
First version recorded
Nov 14, 2026
Size
120,426 bytes
Repository stars
290
License
Apache-2.0

Meta_Kim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.

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

# Meta-Theory Dispatcher
## Purpose
Run Meta_Kim as an executable governance system, not a theory essay. The main thread locks intent, gathers evidence, chooses route, delegates bounded work, reviews, verifies, and synthesizes. It must not become a generic implementation worker for non-trivial work. Machine contract: `config/contracts/core-loop-contract.json` is the compact default-path contract for this skill. It binds ordinary durable work and explicit meta-theory shortcuts to `npm run meta:theory:run`, requires the eight-stage spine, and defines which gates block, warn, or stay progressive.
The default governed runner remains planned-only. When the maintainer explicitly supplies `--execute-stage-dag`, the P-117 bridge executes the existing `coreLoop.stageDagPacket` in read-only shadow mode through either `--stage-runner-runtime codex` or `--stage-runner-runtime claude`, with the P-118 kernel retaining durable node commits; `--resume-stage-dag` continues only the exact bound unfinished run. The ready-set executor defaults to native concurrency. `--stage-runner-orchestrator langgraph` may dynamically load an explicitly installed, currently tested `@langchain/langgraph@1.4.8` and…
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_m3tvirs32vstjpsu/3ae4f215527881aa39e62f9b56b32fc7c30986373d3a807339609757256a3d82.json

Then /plugin install meta-theory@markdownregistry-m3tvirs32vstjpsu in Claude Code. It installs v3.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add kimyx0207/meta_kim/meta-theory@sha256:3ae4f215527881aa

The line at the top of this page pins the label v3.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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_m3tvirs32vstjpsu.svg)](https://markdownregistry.com/a/art_m3tvirs32vstjpsu)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in kimyx0207/meta_kim/meta-theory since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of meta-theory from somewhere else? Ask it: where did my meta-theory come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 5 versions of this file, between Nov 14, 2026 and Nov 15, 2026, more than one a day.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
v3.0.0 latest2026-11-15 d84b547 120,426 BA view · diff
v3.0.02026-11-15 e22833b 119,125 BA view · diff
v3.0.02026-11-15 0728d2e 118,698 BA view · diff
v3.0.02026-11-15 5431daf 118,198 BA view · diff
v3.0.02026-11-14 2008ea9 118,120 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (120426 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

GitHub

kimyx0207/meta_kim · 290 stars · license Apache-2.0 · pushed 2026-11-18 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_m3tvirs32vstjpsu
GET https://markdownregistry.com/api/v1/resolve?ref=kimyx0207/meta_kim/meta-theory
GET https://markdownregistry.com/api/v1/blob/3ae4f215527881aa39e62f9b56b32fc7c30986373d3a807339609757256a3d82

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.

More from kimyx0207/meta_kim

AGENTS.md AGENTS.md file
kimyx0207/meta_kim · AGENTS.md
git:20261115.5431daf · audit A · 290 stars
CLAUDE.md CLAUDE.md file
kimyx0207/meta_kim · CLAUDE.md
git:20261115.5431daf · audit A · 290 stars
save-progress SKILL.md skill
kimyx0207/meta_kim · canonical/runtime-assets/claude/commands/save-progress/SKILL.md · Save current project task progress to local task state file for cross-session continuity. Use when the user asks to…
git:20260612.208934c · audit B · 290 stars
same-set-reusable-flow-for-project-file-inventor SKILL.md skill
kimyx0207/meta_kim · canonical/skills/same-set-reusable-flow-for-project-file-inventor/SKILL.md · Reusable Meta_Kim file inventory classification flow. It helps separate durable sources, generated evidence, runtime…
v0.1.0 · audit A · 290 stars
llms.txt llms.txt file
kimyx0207/meta_kim · llms.txt
git:20261003.02b13ba · audit A · 290 stars

Every file in kimyx0207/meta_kim

Browse by kind, by grade A, or by owner.