Support document answers in Lumen with exact quotations linked to their source paragraphs. Retrieve paragraph references, check quotation text and location, fix citation errors, and add verified links that open the supporting passages.
How Lumen cites a document - the citation object, how to get anchors, quote rules and `lumen cite check`. Load before writing any claim about a document.
Run score Not tested
See how to installThis skill helps provide document answers in Lumen with exact quotations tied to their source paragraphs. It uses a document ID, a paragraph anchor, and a verbatim quote, then checks that the quote matches the source with lumen cite check. A verified link can be added to an answer so readers can open the cited paragraph.
Use it when explaining a contract or showing the source behind a decision. It also provides steps for resolving citation errors, such as a missing quote, an incorrect paragraph location, an overly long quote, or a document ID that does not exist.
You need an environment with Lumen commands. Get anchors from lumen read or lumen search output. Copy a quote exactly from one paragraph and keep it within 300 characters. Do not use ellipses inside quotes or paraphrase them. lumen result write also checks citations and refuses to write the file until every citation passes.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 28, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Lumen shows every citation to a lawyer next to the source passage, and checks it against the source before the lawyer sees it. A citation that fails the check is shown as "Citation not found". Get it right the first time.
{ "doc_id": "<id from lumen docs>", "a": "p3.12", "quote": "verbatim text from that paragraph" }
a is the paragraph anchor: p<page>.<n>. Take it from lumen read or lumen search. Never compute it.quote is copied character for character from ONE paragraph: at most 300 characters, no "..." inside, no paraphrase, case kept.lumen search --matter <matter_dir> --query "limitation of liability capped" # hits: doc_id, a, snippet
lumen read --doc <doc_id> --anchor p3.12 --context 1 # the paragraph and its neighbours
lumen read --doc <doc_id> # the whole document
echo '{"citations": [{"doc_id": "...", "a": "p3.12", "quote": "..."}]}' | lumen cite check
| Code | Meaning | Fix |
|---|---|---|
not_found | The quote is not in the document | Copy the exact words from lumen read output |
wrong_anchor | The quote is in another paragraph (fixed_anchor) | Use fixed_anchor |
too_long | Over 300 characters | Quote fewer words |
unknown_doc | No such document | Use a doc_id from lumen docs |
lumen result write runs the same check on every citation in a result and refuses the file until each passes.
Write each citation as a Markdown link after the claim:
[1](/cite?d=<doc_id>&a=p3.12&q=<url-encoded quote>). lumen cite check prints this link as link for every citation that passes: paste it, do not encode a quote by hand. A bare [1] with no link is not a citation, and Lumen marks the answer as unchecked. Number them in order. Lumen shows each link as a numbered chip that opens the quoted paragraph. Outside the links, name a document by its filename, never by its doc_id.
Good:
{"doc_id": "k17", "a": "p2.9", "quote": "Neither party's liability under or in connection with this Agreement"} - exact words, one paragraph.{"doc_id": "k17", "a": "p1.4", "quote": "renews automatically for successive periods of one (1) year"}.{"doc_id": "k22", "a": "p1.6", "quote": "the Customer is entitled to service credits"}.Bad:
"quote": "liability is unlimited" - a paraphrase. The document says "shall be limited or capped in amount"."quote": "shall not exceed ... twelve (12) months" - an ellipsis inside a quote."a": "3.12" - not an anchor. Anchors look like p3.12.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.