# compile-basic

Adopt this skill: https://proskills.md/skills/other/sno-ai-mda-conformance-compile-46-basic-targets-expected

Page: https://proskills.md/skills/other/sno-ai-mda-conformance-compile-46-basic-targets-expected
This document is the public skill bundle for that page. It contains SKILL.md and every helper file the catalog carries. No login is required.

## File: conformance/compile/46-basic-targets/expected/SKILL.md
size: 351
sha: ffde8fd4664b1fac576f87ed2f734262ed5abe38
upstream: https://github.com/sno-ai/mda/blob/main/conformance/compile/46-basic-targets/expected/SKILL.md

```text
---
name: compile-basic
description: Basic compiler conformance fixture.
allowed-tools: Read Bash(echo:*)
metadata:
  snoai-llmix:
    module: search_summary
    preset: openai_fast
    common:
      provider: openai
      model: gpt-5-mini
  mda:
    requires:
      network: none
---

# Compile basic

Use this fixture to confirm target projection.
```

## File: conformance/compile/46-basic-targets/expected/AGENTS.md
size: 370
sha: 46b0002e9eecb3584fdc5a3e968e655d1e1e553d
upstream: https://github.com/sno-ai/mda/blob/main/conformance/compile/46-basic-targets/expected/AGENTS.md

```text
---
name: compile-basic
description: Basic compiler conformance fixture.
metadata:
  snoai-llmix:
    module: search_summary
    preset: openai_fast
    common:
      provider: openai
      model: gpt-5-mini
  claude-code:
    allowed-tools: Read Bash(echo:*)
  mda:
    requires:
      network: none
---

# Compile basic

Use this fixture to confirm target projection.
```

## File: conformance/compile/46-basic-targets/expected/mcp-server.json
size: 73
sha: 98b372b3639fda4e2b65e8bacfcde768bf2d1261
upstream: https://github.com/sno-ai/mda/blob/main/conformance/compile/46-basic-targets/expected/mcp-server.json

```text
{
	"name": "compile-basic",
	"version": "0.1.0",
	"transport": "stdio"
}
```

## File: conformance/compile/46-basic-targets/expected/MCP-SERVER.md
size: 370
sha: 46b0002e9eecb3584fdc5a3e968e655d1e1e553d
upstream: https://github.com/sno-ai/mda/blob/main/conformance/compile/46-basic-targets/expected/MCP-SERVER.md

```text
---
name: compile-basic
description: Basic compiler conformance fixture.
metadata:
  snoai-llmix:
    module: search_summary
    preset: openai_fast
    common:
      provider: openai
      model: gpt-5-mini
  claude-code:
    allowed-tools: Read Bash(echo:*)
  mda:
    requires:
      network: none
---

# Compile basic

Use this fixture to confirm target projection.
```

## File: README.md
upstream: https://github.com/sno-ai/mda/blob/main/README.md

````text
# 📝 MDA Open Spec — Markdown for Agent

> A Markdown superset for agent-facing documents. **One source, many targets** — compile into the `.md` files every major agent runtime already loads. **Tamper-evident at load** — every artifact carries a reproducible content digest, and signed artifacts carry Sigstore-anchored signatures, so neither the agent loading the doc nor the human reviewing it has to trust an unsigned blob.

[![Latest release](https://img.shields.io/badge/release-v1.0.0--rc.3-blue)](https://github.com/sno-ai/mda/releases/tag/v1.0.0-rc.3)
[![License](https://img.shields.io/github/license/sno-ai/mda)](https://github.com/sno-ai/mda/blob/main/LICENSE)
[![Docs](https://img.shields.io/badge/docs-mda.sno.dev-3b82f6)](https://mda.sno.dev)
[![GitHub stars](https://img.shields.io/github/stars/sno-ai/mda?style=flat&color=yellow)](https://github.com/sno-ai/mda/stargazers)

**Read in other languages:** **English** · [中文](docs/readme/README.zh-CN.md) · [Deutsch](docs/readme/README.de.md) · [Español](docs/readme/README.es.md) · [Français](docs/readme/README.fr.md) · [Русский](docs/readme/README.ru.md) · [한국어](docs/readme/README.ko.md) · [日本語](docs/readme/README.ja.md) · [हिन्दी](docs/readme/README.hi.md)

## What MDA is

Until now, you shipped the same skill four times. Once as `SKILL.md` for the agentskills.io runtimes. Once as `AGENTS.md` for the AAIF ecosystem. Once as `MCP-SERVER.md` with a sidecar JSON. Once as `CLAUDE.md`. Same content, four frontmatter shapes. Update one, forget the others, and a month in, the four files have quietly drifted into four slightly different instruction files.

You write one `.mda`. The compiler emits the rest.

![One .mda source compiled through a deterministic pipeline into SKILL.md, AGENTS.md, MCP-SERVER.md, and CLAUDE.md](images/hero-compile-pipeline.png)

```
                ┌─────────────────────────┐
                │   <name>.mda  (source)  │   ← MDA superset
                └────────────┬────────────┘
                             │  mda compile
                             ▼
   ┌─────────────────────────────────────────────────────────┐
   │ <name>/SKILL.md     (+ scripts/, references/, assets/)  │
   │ AGENTS.md                                               │
   │ <name>/MCP-SERVER.md  (+ mcp-server.json sidecar)       │
   │ CLAUDE.md                                               │
   └─────────────────────────────────────────────────────────┘
                       drop-in compatible
```

## Compatibility

**Write your skill once. It drops into every major agent runtime — unchanged.**

<a href="compat/claude-code/"><img src="images/compat/claude-code.svg" width="220" alt="Claude Code — drop-in compatible"></a>
<a href="compat/codex-cli/"><img src="images/compat/codex-cli.svg" width="220" alt="Codex CLI — drop-in compatible"></a>
<a href="compat/opencode/"><img src="images/compat/opencode.svg" width="220" alt="OpenCode — drop-in compatible"></a>
<a href="compat/hermes/"><img src="images/compat/hermes.svg" width="220" alt="Hermes Agent — drop-in compatible"></a>
<a href="compat/openclaw/"><img src="images/compat/openclaw.svg" width="220" alt="OpenClaw — drop-in compatible"></a>

Five SKILL.md runtimes verified end-to-end with reproducible install kits in [`compat/`](compat/). Compiled `AGENTS.md` artifacts also drop into the AAIF ecosystem (Codex, Copilot, Cursor, Windsurf, Amp, Devin, Gemini CLI, VS Code, Jules, Factory), and at the documentation level into skills.sh and other 2026 SKILL.md consumers.

And those four files can't say who signed them. The agent loading `SKILL.md` has no way to verify the content matches what you wrote, and the curator reviewing `AGENTS.md` has no way to know whose hands have been on it between merge and load. The standard frontmatter shapes have nowhere to put a content digest or a signature, so the trust decision quietly falls back to "we trust the repo, somehow."

MDA carries a JCS-canonicalized `integrity.digest` and DSSE-enveloped, Sigstore-anchored `signatures[]` in the frontmatter itself. Both sides — the agent at load time and the human at review time — can make a real trust decision against the artifact in hand, not against a feeling about the repo. Tamper-evidence and signer verification ship in the contract, not as a later bolt-on.

![Three MDA additions on top of standard Markdown: rich frontmatter, typed footnote relationships, signed identity](images/three-additions.png)

`.mda` adds three things on top of standard Markdown. All of them optional.

1. **Rich YAML frontmatter.** Beyond the open-standard `name` and `description` baseline, MDA carries `doc-id`, `version`, `requires`, `depends-on`, `relationships`, and `tags`. Agent-aware tools use these for routing, dependency resolution, and graph traversal. See [`spec/v1.0/02-frontmatter.md`](spec/v1.0/02-frontmatter.md) and [`spec/v1.0/10-capabilities.md`](spec/v1.0/10-capabilities.md).
2. **Typed footnote relationships.** Standard Markdown footnotes whose payload is a JSON object: `parent`, `child`, `related`, `cites`, `supports`, `contradicts`, `extends`. Mirrored to `metadata.mda.relationships` in body order on compile. See [`spec/v1.0/03-relationships.md`](spec/v1.0/03-relationships.md).
3. **Cryptographic identity.** A JCS-canonicalized `integrity` digest plus DSSE-enveloped, Sigstore-anchored `signatures[]`. The compiled `.md` carries reproducible tamper detection without bolting it on later. See [`spec/v1.0/08-integrity.md`](spec/v1.0/08-integrity.md) and [`spec/v1.0/09-signatures.md`](spec/v1.0/09-signatures.md).

A `.mda` source with only the open-standard frontmatter compiles unchanged into a `.md`. Use as much or as little of MDA as your project needs.

## Why this exists

The honest version. I kept shipping the same skill four times. Same content, four wrappers. Each runtime had its own opinions about what frontmatter belonged at the top and what counted as vendor-specific. The third or fourth time I copy-pasted a paragraph between `SKILL.md` and `AGENTS.md` and then watched them drift, I started writing this.

The thing is, the duplication isn't the worst part. The worst part is what you can't say in any of those formats. You can't say "this skill depends on that one, version `^1.2.0`, with this content digest." You can't say "this file was signed by this identity at this Rekor index." You can't say "the relationship between this document and that one is `supports`, not `cites`." There's nowhere to put that information, so it sits in prose, where neither agents nor humans can act on it reliably.

MDA puts those things in the frontmatter and footnotes, in shapes a JSON Schema can validate. The Markdown body still renders. The standard fields still load. Everything new is optional. That's the whole pitch.

For the long version, two documents go deeper. Both trace every claim back to a section of the spec, and both call out current ecosystem gaps inline. Read them if you're deciding whether to adopt.

- [**`docs/v1.0/ai-agent-core-value.md`**](docs/v1.0/ai-agent-core-value.md) — five points framed for runtimes, harnesses, validators, and dispatchers. What MDA gives an agent at load time: structured `requires` for typed dispatch, verifiable trust at load, machine-readable graph edges, filename-based one-lookup target dispatch, and the same validation contract for agent-authored and compiler-emitted output.
- [**`docs/v1.0/human-curator-user-core-value.md`**](docs/v1.0/human-curator-user-core-value.md) — six points framed for the people who write and curate agent-facing instruction libraries. What MDA gives an author at ship time: one source into multiple ecosystems, tamper-evidence and publisher attribution, machine-readable dependency graph and version pinning, LLM-mediated authoring without learning every runtime's frontmatter, smaller (not zero) vendor lock-in, and strict validation that catches almost-conformant artifacts before they ship.

## Three authoring modes

MDA artifacts may be produced 
````
