Rekor — Data Layer for AI Agents

You have access to the rekor CLI — the builder interface for Rekor. Use it to set up schemas, configure record_types, test in preview environments, and promote to production. Production agents use MCP tools to read/write records; external systems integrate via REST API. The CLI is your tool for designing and managing the data model.

This file is self-contained on concepts: The Rekor Object Model defines every primitive, the Task → Feature Map routes any request to the section that implements it, and Where to Find More Detail says when to open the bundled references/ files for full option grammar.

Agent Guidelines

• Drive Rekor through the rekor CLI when you have shell access. If you also have mcp__rekor__* tools in your toolset, prefer the CLI for setup and configuration; reserve MCP tools for production read/write operations.
• Only provide information from this skill, tool descriptions, or reference documentation. Do not invent URLs, paths, commands, or flags.
• Read the matching references/*.md file before configuring its feature. This file deliberately carries the concepts and common command shapes only; the full option grammar for querying/search tuning, external sources, MCP Factory Actions/toolsets, executors, and provider adapters lives in the bundled reference files (index in Where to Find More Detail).
• Schema work (record_types, inbound webhooks, triggers, MCP Factory toolsets) only happens in preview bases. Always create or use a preview before changing schemas.
• Identifiers are permanent. The id of a base, record_type, relationship type, Action, and MCP Factory toolset is its identity and is immutable — chosen once at creation and never renamed. Display names and descriptions stay editable, but never the id (a relationship type has no separate name — its id is also its label). There is no rename: to "rename" one of these you create a new entity and migrate its data (the old one is left untouched). So choose clear, stable, lowercase-slug ids up front (e.g. patients, treated_by).
• Promotion is human-only. When schema is ready, surface the exact rekor bases promote command and wait for the user to run it.
• Tokens are shown only once on creation. Always tell the user to copy and store it before doing anything else.
• Never auto-commit. Show the user git diff (when working with schema files) and wait for approval.