library-record-writing

Write durable library records with machine-readable frontmatter and sorted index appends.

8|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/arthur0n/xenodot-forge --skill library-record-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: library-record-writing
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/library-record-writing
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill library-record-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how researcher agents write durable library records so verdicts are queryable, indexed, and reusable in future sessions instead of being rediscovered.

Core Features & Use Cases

  • Machine-face frontmatter: Keeps the record's metadata concise and machine-readable for sidebar and index consumption.
  • Index maintenance: Appends each new record to the correct kind index in filename order so the library stays searchable.
  • Post-adoption lesson capture: Adds a compact Lesson section after something is installed or built, preserving only the generalizable takeaway.
  • Use case: A research agent evaluates an addon, decides whether to adopt or reject it, then writes a one-page record that future agents can trust without repeating the research.

Quick Start

Ask the assistant to write a library record for the addon or tool you just evaluated and append it to the correct index.

Frequently Asked Questions about library-record-writing

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

FAQPage Schema
How do I write reusable research records that stay queryable across sessions?

To write reusable research records, you need machine-readable frontmatter and sorted index appends so verdicts remain queryable and durable for future sessions instead of being rediscovered.

What is the best way to maintain a per-kind library index for addon research verdicts?

Maintaining a per-kind library index requires appending each new research record in filename order, ensuring the library stays searchable and organized by tool or addon category.

How do I document adopt or reject decisions for external capabilities?

You document adopt or reject decisions by writing a one-page library record with machine-readable frontmatter that preserves the evaluation verdict for future agents to trust without repeating the research.

When do I need to add a Lesson section to a library record?

You add a compact four-field Lesson section to a library record after an addon or tool is adopted or built, preserving only the generalizable takeaway from the outcome.

Can I use this library record format for tools I decide to reject?

Yes, the library record format applies to researcher workflows that evaluate external capabilities and decide both adopt or reject outcomes, ensuring all verdicts are indexed and reusable.

What are the limitations of relying on frontmatter for library record indexing?

The frontmatter must be strictly machine-readable for sidebar and index consumption; records are constrained to a one-page format, and the optional Lesson section is only applicable post-adoption or build.