todero-files-with-the-work

Organizes agent briefs and documents, and appends source citations to every delivered output.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill todero-files-with-the-work-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todero-files-with-the-work
Source: https://github.com/nabitllc/todero/tree/main/skills/todero-files-with-the-work
Command: npx skills add https://github.com/nabitllc/todero --skill todero-files-with-the-work-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents often hand over work with no record of what they based it on, making outputs impossible to verify or audit. This Skill enforces a standard agent folder structure and requires every delivered piece of work to cite the files and conversation lines it drew on. ## Core Features & Use Cases - Standardized Agent Folder Structure: Defines a three-part layout under the agent directory: a brief.md file, a skills/ folder, and a documents folder for specs, data, and past decisions. - Structured Brief Template: The brief.md file contains four fixed sections — Identity, Constraints, Read first, and Inputs/Outputs — so each agent's role, limits, and expectations are explicit. - Mandatory Citation of Sources: Every output ends with a short "Used:" list naming the files and conversation lines it relied on, with anything uncheckable marked as unverified. - Use Case: A drafting agent produces a report from documents/spec.md and prior conversation; the delivered report ends with a three-line citation block so the reviewer can verify each claim against its source. ## Quick Start Set up my agent's folder with a brief.md following the four-section structure and make sure every output it hands in ends with a Used citation list.

Frequently Asked Questions about todero-files-with-the-work

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

FAQPage Schema
How do I structure an AI agent's files and brief?

Create a folder for the agent containing three parts: a brief.md file, a skills/ folder, and a documents folder. The brief.md has four sections — Identity, Constraints, Read first, and Inputs/Outputs — each kept to one sentence or a short list.

How do I make an AI agent cite its sources in outputs?

Require every handed-in output to end with a short "Used:" list naming the files and conversation lines it drew on, formatted in three lines or fewer. Anything the agent could not verify against a source is explicitly marked as unverified.

What goes in an agent brief's Constraints section?

The Constraints section states what the agent refuses to do, whether it may change anything or only propose changes, what it must cite, and the conditions under which it cannot hand over the work.

When should an agent mark output as unverified?

An output is marked unverified when a claim cannot be checked against any available file or conversation line, such as when a referenced schema does not yet define the field. If every input is verified, the unverified line is omitted entirely.

Does this agent folder structure include state or evaluation files?

No. The structure drops state.json and evals/ folders found in the upstream specification, because the local agent has no evals and its state lives in the task thread rather than a separate file.