orc-export

Export ORC project context into portable AGENTS.md files and import foreign agent context.

6|1|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/azure-id/orc --skill orc-export-azure-id
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orc-export
Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-export
Command: npx skills add https://github.com/azure-id/orc --skill orc-export-azure-id

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams worry about vendor lock-in when adopting ORC, and agents like Cursor or Codex cannot read ORC's internal wiki, pact ledger, and boundary cards. This Skill compiles that context into a portable, derived AGENTS.md and can also import an existing AGENTS.md or .cursorrules from a repo that never ran ORC. ## Core Features & Use Cases - Derived export: Compiles the orientation doc, PACT.md, boundary cards, code patterns, and wiki pages into a fingerprinted AGENTS.md carrying a source_commit, verifiable with orc export --check in CI. - Secret-safe output: Never exports env files, credentials, run folders, or logs, and never re-summarizes evidence-anchored sources. - Guided import: Reads AGENTS.md, CLAUDE.md, .cursorrules, or copilot instructions, flags claims that are already wrong (dead paths, missing commands), and proposes pact entries and wiki seeds that the user confirms before anything is written. - Use Case: A team adopting ORC asks "are we locked in?" — run the export to produce a committed AGENTS.md that Cursor and Codex consume directly, then add orc export --check to CI so the file can never silently go stale. ## Quick Start Ask the assistant to export our ORC context to a portable AGENTS.md so other coding agents can read it.

Frequently Asked Questions about orc-export

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export ORC context to AGENTS.md?▼

Run `orc export` with an optional target of agents-md, skill, or both. The CLI compiles the orientation doc, PACT.md, boundary cards, code patterns, and wiki pages into a single derived file with a fingerprinted header.

How do I import an existing AGENTS.md or .cursorrules into ORC?▼

Run `orc export import` in the repo. It reads AGENTS.md, CLAUDE.md, .cursorrules, and copilot instructions, reports claims that are already wrong, and proposes pact entries and wiki seeds that you confirm before anything is written.

Does the AGENTS.md export stay up to date automatically?▼

The export carries a source_commit and a fingerprint of every source. Running `orc export --check` in CI exits 1 when a source changed or left the payload, naming why per source, so staleness is detected rather than silent.

Can exported AGENTS.md files leak secrets or credentials?▼

No. The export never includes .env files, anything whose path looks like a secret or credential, run folders, or logs. Sources are copied through unchanged with only their ORC frontmatter stripped.

Will imported context from .cursorrules change how ORC behaves?▼

No. Foreign context is treated as evidence, never instruction. It cannot change a phase, set a verdict, or authorize a write; the import only proposes changes and the user confirms each one.