source-ledger
- Trigger
- When a task needs facts from more than one page
- Output
- A table of claim, source, access date, quote and confidence
- Guardrail
- A source the agent did not open is marked 'not opened', never cited.
noindex and takes no payment; the public site is the production build.
Four skills for source-checked research: a source ledger, a claim checker, a comparison matrix and a freshness scan.
Create one folder per skill under `skills/` in the project the agent works in: `source-ledger/`, `claim-checker/`, `comparison-builder/`, `freshness-scan/`.
Add a `SKILL.md` to each folder with a specific `description`. The description is the trigger; write it as a situation, not a topic.
Put long source notes in `references/` and keep the main file short enough to read in one pass.
Run the three tests below with a prompt that should trigger each skill. If the agent never loads it, the description is too vague.
skills/my-pack/
|-- SKILL.md
|-- references/
|-- scripts/
`-- assets/
Pass condition: The agent creates a two-row table with an access date and marks missing cells 'not published'; it does not rank the routes.
Pass condition: Each number is labelled fact, opinion or unknown; at least one unsupported claim is removed rather than reworded.
Pass condition: The agent lists the sources that changed and does not update the reviewed date on its own.
Research is where an agent's confidence is most expensive. A wrong date in a client update is embarrassing; a wrong eligibility rule in a move plan is costly. This pack makes the evidence visible before the prose gets smooth.
The four skills cover one loop: collect a source, check a claim, compare options, and notice when the source changed. They are deliberately small. A research skill that tries to do all four in one file becomes a prompt with a folder around it.
Every factual sentence has a source a reader can open, or it is removed. That rule is easy to state and hard to follow, because a model can produce a plausible sentence faster than a person can check it. The skills put the check in the path instead of relying on willpower.
jurisdiction field to the source ledger and make it required./skills/research-desk.md.
Send the scenario, the prompt that failed, or the harness change that broke your setup. The help desk takes questions and corrections from humans and agents, and every accepted fix updates the page date.