record

Classifies and promotes durable records into ledger categories with contract validation.

10|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/nrdxp/predicate --skill record-nrdxp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record
Source: https://github.com/nrdxp/predicate/tree/main/skills/record
Command: npx skills add https://github.com/nrdxp/predicate --skill record-nrdxp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Long agent walks lose decisions, accepted limitations, and process lessons in ephemeral scratch notes; this Skill enforces categorized, machine-validated durable record-keeping so the trail stays reconstructable. ## Core Features & Use Cases - Category model: Routes each step's output into flight-log, tech-debt, or process-feedback records, each with a defined contract, .ledger home, and trigger. - Three-gate promotion: Promotes artifacts from scratch to ledger or repo/docs via structural readiness (Nickel contract validation), a zero-context sensibility read, and role-based authorization. - Use Case: When an agent accepts a known limitation instead of fixing it, it writes a tech-debt YAML entry with a falsifiable claim and signpost, validates it with nickel export --apply-contract, and commits it to .ledger/tech-debt/ instead of burying it in prose. ## Quick Start Ask the agent to record the limitation you just accepted as a validated tech-debt entry in the ledger.

Frequently Asked Questions about record

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

FAQPage Schema
How do I record tech debt from an AI agent workflow?

Write a YAML entry with id, claim, location, severity, why_deferred, and signpost fields, then validate it with nickel export using the tech_debt_apply.ncl contract. The validated file is committed to .ledger/tech-debt/ instead of being buried in prose logs.

What is the difference between flight-log, tech-debt, and process-feedback records?

Flight-log is a narrative zettelkasten of decisions and pivots with no formal contract. Tech-debt captures accepted limitations as machine-validated YAML, and process-feedback records friction, misses, improvements, and amendments, each with its own Nickel contract and .ledger home.

How does artifact promotion from scratch to ledger work?

Promotion passes three gates: structural readiness via Nickel contract export, a zero-context sensibility read that strips session-only references while keeping load-bearing rationale, and role-based authorization determining who may promote each artifact class.

Can an agent promote doctrine changes automatically?

No. Doctrine edits to files like rules.md or ambient.md are a reserved halt requiring human approval before merge. A worker can emit the draft but must stop for review before touching the destination.

What happens if a record fails Nickel contract validation?

A record that does not export cleanly against its contract fails Gate 1 structural readiness and must not proceed to the sensibility read. The project-local gate script in .ledger/gates/ also rejects invalid records at commit time.