[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HPXK5MA2N0FQHEC97Y7157":3,"skill-same:01M6HPXK5MA2N0FQHEC97Y7157":102},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6HPXK5MA2N0FQHEC97Y7157","perspicacity",null,"Perspicacity scene perception DSL — structured 3D spatial awareness for AI. Reference for reading and reasoning about .picacia format output.","pedronaugusto\u002Fblender-weave","pedronaugusto","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16762743?v=4","01M6HPX2VRKA8WM7J6HB3AHXAE","Pedro Augusto","01M6HPX30EFSJ68B7XT70Z2E4K",8,"MIT","https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Fperspicacity\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31],"reasoning","awareness","3D","format","reference","Spatial","structured","perception","output","about","reading","for","dsl","2026-11-10 10:12:30",false,"---\nname: grounded-citations\ndescription: \"Ground answers and documents in cited, verifiable sources.\"\nversion: 1.2.0\nauthor: Hermes Agent + Teknium\nlicense: MIT\nplatforms: [linux, macos, windows]\nmetadata:\n  hermes:\n    tags: [Research, Citations, Grounding, Sources, Web, Reports]\n    category: research\n    related_skills: [arxiv, pdf, reddit-reading, rss-feeds, youtube-content]\n---\n\n# Grounded Citations\n\nEvery claim taken from an outside source gets an inline numbered citation and a\n`Sources:` list, Perplexity-style. A ledger script owns the `url → [n]` mapping\nso the numbers and URLs come from retrieval, never from memory — the model only\never emits small integers it was handed.\n\nFor high-stakes work the same ledger doubles as a fact-checking chain: verbatim\nquotes are attached to each source (rejected unless they literally appear in\nthe fetched page text), claims from model knowledge are flagged `[unverified]`,\nand `verify --evidence` fails any draft whose cited sources carry no evidence.\n\nThis skill covers answers in chat, written documents (markdown, PDF, docx,\nslides), and research reports. It does not cover academic BibTeX pipelines —\nfor conference papers use the `arxiv` skill, which this skill\nfeeds (see `references\u002Fcitation-formats.md`).\n\n## When to Use\n\nUse whenever an answer or artifact rests on information you fetched rather than\nknew:\n\n- Research, comparisons, news summaries, \"what is the current state of X\"\n- Any deliverable you write to disk that quotes, paraphrases, or reports\n  outside facts — reports, briefs, docs, decks, wiki pages\n- Fact-finding where the user will want to check your work\n- Multi-source synthesis where conflicting sources must be attributed\n\nSkip inline citations when the retrieval is incidental to another task — a\nquick syntax\u002Fversion lookup mid-coding, casual conversation, creative writing.\nMention a URL only if the user would plausibly want the link.\n\n## Prerequisites\n\nNone beyond the standard toolset. `scripts\u002Fsources.py` is stdlib-only Python 3.\nRetrieval comes from whatever is configured: `web_search`, `web_extract`,\n`browser_navigate`, or `terminal` (curl, CLIs).\n\nLedger location: `$HERMES_HOME\u002Fcache\u002Fcitations\u002Fledger.json` (profile-aware).\nOverride per task with `--ledger \u003Cpath>` or `HERMES_CITATION_LEDGER`.\n\n## How to Run\n\n```bash\nS=~\u002F.hermes\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002Fscripts\u002Fsources.py\n\npython \"$S\" reset                                  # start a clean ledger\npython \"$S\" add https:\u002F\u002Fexample.com\u002Fa --title \"A\"  # prints: [1]\npython \"$S\" add https:\u002F\u002Fexample.com\u002Fb --title \"B\"  # prints: [2]\npython \"$S\" list                                   # ledger table\npython \"$S\" render                                 # Sources: block\npython \"$S\" verify draft.md                        # catch bad citations\n```\n\n`add` is idempotent and URL-normalized: the same page always returns the same\nid within a ledger, so ids stay stable across many search\u002Fextract rounds.\n\n## Quick Reference\n\n| Action | Command |\n|---|---|\n| Fresh ledger for a new task | `sources.py reset` |\n| Register a source, get its id | `sources.py add \u003Curl> [--title T]` |\n| Register several at once | `sources.py add \u003Curl1> \u003Curl2> ...` |\n| Register from JSON tool output | `sources.py ingest results.json` |\n| Attach verbatim evidence to a source | `sources.py quote \u003Cid> --text \"exact wording\" --from page.txt` |\n| Show ledger | `sources.py list [--json]` |\n| Render the Sources block | `sources.py render [--style markdown\\|plain\\|footnotes\\|bibtex\\|evidence] [--only 1,3]` |\n| Render only what a draft cites | `sources.py render --cited-in draft.md` |\n| Rewrite a draft's Sources block in place | `sources.py render --replace-in draft.md` |\n| Check a draft's citations | `sources.py verify draft.md [--strict] [--min-coverage 0.6] [--evidence]` |\n\n## Procedure\n\n① **Reset the ledger** at the start of a task that will produce a grounded\nanswer or document. Skip the reset when continuing work whose ids are already\nin a draft — reusing the ledger keeps the numbering stable.\n\n② **Register every source at retrieval time.** After each `web_search` \u002F\n`web_extract` \u002F `browser_navigate` \u002F fetch, pass the URLs to `sources.py add`\n(or pipe the raw JSON through `sources.py ingest`). Do this *before* writing\nprose. Registering later, from memory, is the failure mode this skill exists to\nprevent.\n\n③ **Write cite-while-drafting.** Place the bracketed id(s) immediately after\neach sentence the source supports:\n\n```\nIce floats because it is less dense than liquid water.[1][2]\n```\n\n- No space before the bracket; each id in its own brackets.\n- Max 3 ids per sentence. Cite per sentence, not one dump at the end.\n- Only ids the ledger returned. Never invent an id or a URL.\n- Claims from your own knowledge get no citation.\n- Conflicting sources: present both readings, each with its own id.\n- Quote exact figures, dates, and names as the source states them; flag gaps\n  explicitly (\"no source found for X\") instead of smoothing them over.\n\n④ **Append the Sources block** with `sources.py render --cited-in \u003Cdraft>` so\nthe id → URL mapping is generated mechanically from the ledger, not retyped.\nFor non-markdown targets pick the matching `--style` and follow\n`references\u002Fcitation-formats.md` for placement (footnotes in docx, endnotes in\nPDF\u002FLaTeX, a Sources slide in decks, per-page source lists in wiki output).\n\n⑤ **Verify before delivering** — `sources.py verify \u003Cdraft>` exits non-zero on\nunknown ids, on a Sources block that disagrees with the ledger, or (with\n`--min-coverage`) on prose that is too thinly cited. Fix and re-run.\n\n⑥ **Chat answers** follow the same steps with the draft in your reply: register\nsources, cite inline, end with the rendered `Sources:` list. For a short answer\nyou may render the block from `sources.py render --only \u003Cids>` instead of\nwriting to a file.\n\n## Multi-Platform Sweeps\n\n\"What are people saying about X\" \u002F \"research X across the web\" is not one\n`web_search`. Fan out across source types, collect in parallel, then synthesise\nwith every claim attributed to the platform it came from:\n\n| Source type | Route | What it adds |\n|---|---|---|\n| Open web | `web_search` → `web_extract` | official docs, articles, announcements |\n| Community discussion | `reddit-reading` (`search`, `thread`) | real user experience, complaints, workarounds |\n| Blogs \u002F releases \u002F changelogs | `rss-feeds` (`read`, `discover`) | dated primary posts, version history |\n| Video | `youtube-content` | walkthroughs, demos, talks |\n| Code | `terminal` with `gh search repos` \u002F `gh search issues` | implementations, open bugs |\n| X\u002FTwitter | `xurl` (needs API access) | announcements, developer chatter |\n\nThe `reddit-reading` and `rss-feeds` skills are optional. If absent, install with\n`hermes skills install official\u002Fsocial-media\u002Freddit-reading` or\n`hermes skills install official\u002Fresearch\u002Frss-feeds` before using them.\n\nRegister every URL from every route in the ledger as it arrives (step ②). Keep\nopinion and measurement apart: a Reddit thread is evidence that users *report*\nsomething, not that it is true; pair it with a primary source or label it as\nsentiment. Report per-platform coverage gaps (\"Reddit search returned nothing\nnewer than March\") rather than silently narrowing to what worked.\n\n## Fact-Checking Mode\n\nFor work where the reader must be able to check the chain — medical, legal,\nfinancial, safety, disputed claims, or when the user asks for fact-checking —\nupgrade from citations to evidence:\n\n① **Attach a verbatim quote per source.** After extracting a page, save its\ntext to a file and attach the sentence(s) that carry each claim:\n\n```bash\npython \"$S\" quote 1 --text \"Ice is about 9% less dense than liquid water.\" --from page1.txt\n```\n\nThe quote is rejected unless it appears verbatim in the evidence text\n(insensitive to whitespace, case, and markdown markup — inline links like\n`_[ERAP1](https:\u002F\u002F…)_` in extracted text match the plain prose a reader sees),\nso a paraphrase or misremembered figure cannot masquerade as evidence.\nCopy-paste from the fetched text; never retype. Quote the sentence as the\nreader sees it — the matcher sees through the extractor's markup for you, so\nyou don't have to reproduce link syntax or escaped asterisks in your quote.\n\n② **Flag model-knowledge claims with `[unverified]`.** A load-bearing claim\nyou could not source gets an explicit marker instead of a citation:\n\n```\nThe refactor likely predates the 2.0 release.[unverified]\n```\n\n`verify --min-coverage` counts `[unverified]` sentences as covered — the goal\nis declared provenance for every claim, not a citation on every sentence.\nIf a key claim can be checked, check it; `[unverified]` is for what genuinely\ncannot be, and a fact-check deliverable dominated by `[unverified]` markers\nshould say so in its summary.\n\n③ **Cross-check disputed facts against a second independent source.** When two\nsources disagree, cite both readings with their own ids and quotes, and say\nwhich you weight and why. One source is reporting; two independent sources are\ncorroboration.\n\n④ **Verify with the evidence gate and render the evidence block:**\n\n```bash\npython \"$S\" verify report.md --evidence --min-coverage 0.5\npython \"$S\" render --style evidence --replace-in report.md\n```\n\n`--evidence` fails the draft if any cited source has no attached quote. The\n`evidence` render style prints each source's quotes beneath its URL, so the\ndeliverable shows claim → source → exact supporting text with nothing taken on\nfaith. Use `--replace-in \u003Cdraft>` to rewrite an existing Sources block in place\n(idempotent — safe to re-run after attaching more quotes); `--cited-in` prints\nto stdout instead. Both emit the heading `## Sources` (`--style plain` emits\n`Sources:`).\n\n**What `--min-coverage` counts.** Coverage is\n`sentences with declared provenance \u002F prose sentences`. A prose sentence is a\nnon-empty line fragment of 4+ words after the Sources block, headings (`#`),\ntable rows (`|`), and fenced code are dropped; blockquote markers are stripped.\nProvenance is declared by either a `[n]` citation or an `[unverified]` marker,\nso a sentence carrying both counts once. Run `verify` without a threshold first\nand read the `info: stats:` line to see the counts before picking a number.\n\n## Pitfalls\n\n- **Registering after writing.** The ledger must be populated from tool output,\n  not reconstructed from the draft — that reintroduces exactly the hallucinated\n  -URL risk the numbering removes.\n- **Renumbering mid-task.** Never hand-edit ids in a draft. Ids are ledger\n  identities; if a draft cites `[4]`, `[4]` must stay that source. Run `reset`\n  only between tasks.\n- **Retyping URLs into the Sources block.** Always `render`. A hand-typed URL\n  is an unverified claim.\n- **Citing a search snippet as if you read the page.** A `web_search`\n  description supports only what it literally says. Cite the extracted page\n  when the claim needs the body — `web_extract` it first.\n- **Over-citing.** Three ids on a sentence is the ceiling; a citation on every\n  clause makes text unreadable and hides which source carries the load.\n- **Citing the ledger in code\u002Fconfig artifacts.** Source comments belong in\n  prose deliverables and doc headers, not inside generated code.\n- **Parallel subagents.** Each subagent has its own working directory; point\n  them all at one ledger with `--ledger` (or `HERMES_CITATION_LEDGER`) if their\n  outputs get merged, otherwise their ids will collide.\n- **Quoting from a snippet instead of the page.** Evidence quotes must come\n  from the extracted page text, not a search-result description — `web_extract`\n  first, save the text, then `quote --from` that file.\n- **Paraphrasing into `quote --text`.** The verbatim check will reject it; the\n  fix is to find the actual sentence, not to reword until something matches.\n- **Using `[unverified]` as an escape hatch.** It marks the rare claim that\n  genuinely cannot be sourced; if most sentences carry it, the task needed more\n  retrieval, not more markers.\n- **Hand-editing the Sources block.** Use `render --replace-in \u003Cdraft>`; slicing\n  the file yourself risks a stale or duplicated block that `verify` then flags.\n\n## Verification\n\n```bash\npython \"$S\" verify report.md --strict --min-coverage 0.5\n```\n\nGreen means: every `[n]` in the draft exists in the ledger, the Sources block\nlists exactly the cited ids with the ledger's URLs, and the cited share of\nsource-bearing sentences meets the threshold. Read the warnings even when the\nexit code is 0 — uncited registered sources usually mean a claim lost its\nattribution during editing.\n","# Grounded Citations\n\nEvery claim taken from an outside source gets an inline numbered citation and a\n`Sources:` list, Perplexity-style. A ledger script owns the `url → [n]` mapping\nso the numbers and URLs come from retrieval, never from memory — the model only\never emits small integers it was handed.\n\nFor high-stakes work the same ledger doubles as a fact-checking chain: verbatim\nquotes are attached to each source (rejected unless they literally appear in\nthe fetched page text), claims from model knowledge are flagged `[unverified]`,\nand `verify --evidence` fails any draft whose cited sources carry no evidence.\n\nThis skill covers answers in chat, written documents (markdown, PDF, docx,\nslides), and research reports. It does not cover academic BibTeX pipelines —\nfor conference papers use the `arxiv` skill, which this skill\nfeeds (see `references\u002Fcitation-formats.md`).\n\n## When to Use\n\nUse whenever an answer or artifact rests on information you fetched rather than\nknew:\n\n- Research, comparisons, news summaries, \"what is the current state of X\"\n- Any deliverable you write to disk that quotes, paraphrases, or reports\n  outside facts — reports, briefs, docs, decks, wiki pages\n- Fact-finding where the user will want to check your work\n- Multi-source synthesis where conflicting sources must be attributed\n\nSkip inline citations when the retrieval is incidental to another task — a\nquick syntax\u002Fversion lookup mid-coding, casual conversation, creative writing.\nMention a URL only if the user would plausibly want the link.\n\n## Prerequisites\n\nNone beyond the standard toolset. `scripts\u002Fsources.py` is stdlib-only Python 3.\nRetrieval comes from whatever is configured: `web_search`, `web_extract`,\n`browser_navigate`, or `terminal` (curl, CLIs).\n\nLedger location: `$HERMES_HOME\u002Fcache\u002Fcitations\u002Fledger.json` (profile-aware).\nOverride per task with `--ledger \u003Cpath>` or `HERMES_CITATION_LEDGER`.\n\n## How to Run\n\n```bash\nS=~\u002F.hermes\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002Fscripts\u002Fsources.py\n\npython \"$S\" reset                                  # start a clean ledger\npython \"$S\" add https:\u002F\u002Fexample.com\u002Fa --title \"A\"  # prints: [1]\npython \"$S\" add https:\u002F\u002Fexample.com\u002Fb --title \"B\"  # prints: [2]\npython \"$S\" list                                   # ledger table\npython \"$S\" render                                 # Sources: block\npython \"$S\" verify draft.md                        # catch bad citations\n```\n\n`add` is idempotent and URL-normalized: the same page always returns the same\nid within a ledger, so ids stay stable across many search\u002Fextract rounds.\n\n## Quick Reference\n\n| Action | Command |\n|---|---|\n| Fresh ledger for a new task | `sources.py reset` |\n| Register a source, get its id | `sources.py add \u003Curl> [--title T]` |\n| Register several at once | `sources.py add \u003Curl1> \u003Curl2> ...` |\n| Register from JSON tool output | `sources.py ingest results.json` |\n| Attach verbatim evidence to a source | `sources.py quote \u003Cid> --text \"exact wording\" --from page.txt` |\n| Show ledger | `sources.py list [--json]` |\n| Render the Sources block | `sources.py render [--style markdown\\|plain\\|footnotes\\|bibtex\\|evidence] [--only 1,3]` |\n| Render only what a draft cites | `sources.py render --cited-in draft.md` |\n| Rewrite a draft's Sources block in place | `sources.py render --replace-in draft.md` |\n| Check a draft's citations | `sources.py verify draft.md [--strict] [--min-coverage 0.6] [--evidence]` |\n\n## Procedure\n\n① **Reset the ledger** at the start of a task that will produce a grounded\nanswer or document. Skip the reset when continuing work whose ids are already\nin a draft — reusing the ledger keeps the numbering stable.\n\n② **Register every source at retrieval time.** After each `web_search` \u002F\n`web_extract` \u002F `browser_navigate` \u002F fetch, pass the URLs to `sources.py add`\n(or pipe the raw JSON through `sources.py ingest`). Do this *before* writing\nprose. Registering later, from memory, is the failure mode this skill exists to\nprevent.\n\n③ **Write cite-while-drafting.** Place the bracketed id(s) immediately after\neach sentence the source supports:\n\n```\nIce floats because it is less dense than liquid water.[1][2]\n```\n\n- No space before the bracket; each id in its own brackets.\n- Max 3 ids per sentence. Cite per sentence, not one dump at the end.\n- Only ids the ledger returned. Never invent an id or a URL.\n- Claims from your own knowledge get no citation.\n- Conflicting sources: present both readings, each with its own id.\n- Quote exact figures, dates, and names as the source states them; flag gaps\n  explicitly (\"no source found for X\") instead of smoothing them over.\n\n④ **Append the Sources block** with `sources.py render --cited-in \u003Cdraft>` so\nthe id → URL mapping is generated mechanically from the ledger, not retyped.\nFor non-markdown targets pick the matching `--style` and follow\n`references\u002Fcitation-formats.md` for placement (footnotes in docx, endnotes in\nPDF\u002FLaTeX, a Sources slide in decks, per-page source lists in wiki output).\n\n⑤ **Verify before delivering** — `sources.py verify \u003Cdraft>` exits non-zero on\nunknown ids, on a Sources block that disagrees with the ledger, or (with\n`--min-coverage`) on prose that is too thinly cited. Fix and re-run.\n\n⑥ **Chat answers** follow the same steps with the draft in your reply: register\nsources, cite inline, end with the rendered `Sources:` list. For a short answer\nyou may render the block from `sources.py render --only \u003Cids>` instead of\nwriting to a file.\n\n## Multi-Platform Sweeps\n\n\"What are people saying about X\" \u002F \"research X across the web\" is not one\n`web_search`. Fan out across source types, collect in parallel, then synthesise\nwith every claim attributed to the platform it came from:\n\n| Source type | Route | What it adds |\n|---|---|---|\n| Open web | `web_search` → `web_extract` | official docs, articles, announcements |\n| Community discussion | `reddit-reading` (`search`, `thread`) | real user experience, complaints, workarounds |\n| Blogs \u002F releases \u002F changelogs | `rss-feeds` (`read`, `discover`) | dated primary posts, version history |\n| Video | `youtube-content` | walkthroughs, demos, talks |\n| Code | `terminal` with `gh search repos` \u002F `gh search issues` | implementations, open bugs |\n| X\u002FTwitter | `xurl` (needs API access) | announcements, developer chatter |\n\nThe `reddit-reading` and `rss-feeds` skills are optional. If absent, install with\n`hermes skills install official\u002Fsocial-media\u002Freddit-reading` or\n`hermes skills install official\u002Fresearch\u002Frss-feeds` before using them.\n\nRegister every URL from every route in the ledger as it arrives (step ②). Keep\nopinion and measurement apart: a Reddit thread is evidence that users *report*\nsomething, not that it is true; pair it with a primary source or label it as\nsentiment. Report per-platform coverage gaps (\"Reddit search returned nothing\nnewer than March\") rather than silently narrowing to what worked.\n\n## Fact-Checking Mode\n\nFor work where the reader must be able to check the chain — medical, legal,\nfinancial, safety, disputed claims, or when the user asks for fact-checking —\nupgrade from citations to evidence:\n\n① **Attach a verbatim quote per source.** After extracting a page, save its\ntext to a file and attach the sentence(s) that carry each claim:\n\n```bash\npython \"$S\" quote 1 --text \"Ice is about 9% less dense than liquid water.\" --from page1.txt\n```\n\nThe quote is rejected unless it appears verbatim in the evidence text\n(insensitive to whitespace, case, and markdown markup — inline links like\n`_[ERAP1](https:\u002F\u002F…)_` in extracted text match the plain prose a reader sees),\nso a paraphrase or misremembered figure cannot masquerade as evidence.\nCopy-paste from the fetched text; never retype. Quote the sentence as the\nreader sees it — the matcher sees through the extractor's markup for you, so\nyou don't have to reproduce link syntax or escaped asterisks in your quote.\n\n② **Flag model-knowledge claims with `[unverified]`.** A load-bearing claim\nyou could not source gets an explicit marker instead of a citation:\n\n```\nThe refactor likely predates the 2.0 release.[unverified]\n```\n\n`verify --min-coverage` counts `[unverified]` sentences as covered — the goal\nis declared provenance for every claim, not a citation on every sentence.\nIf a key claim can be checked, check it; `[unverified]` is for what genuinely\ncannot be, and a fact-check deliverable dominated by `[unverified]` markers\nshould say so in its summary.\n\n③ **Cross-check disputed facts against a second independent source.** When two\nsources disagree, cite both readings with their own ids and quotes, and say\nwhich you weight and why. One source is reporting; two independent sources are\ncorroboration.\n\n④ **Verify with the evidence gate and render the evidence block:**\n\n```bash\npython \"$S\" verify report.md --evidence --min-coverage 0.5\npython \"$S\" render --style evidence --replace-in report.md\n```\n\n`--evidence` fails the draft if any cited source has no attached quote. The\n`evidence` render style prints each source's quotes beneath its URL, so the\ndeliverable shows claim → source → exact supporting text with nothing taken on\nfaith. Use `--replace-in \u003Cdraft>` to rewrite an existing Sources block in place\n(idempotent — safe to re-run after attaching more quotes); `--cited-in` prints\nto stdout instead. Both emit the heading `## Sources` (`--style plain` emits\n`Sources:`).\n\n**What `--min-coverage` counts.** Coverage is\n`sentences with declared provenance \u002F prose sentences`. A prose sentence is a\nnon-empty line fragment of 4+ words after the Sources block, headings (`#`),\ntable rows (`|`), and fenced code are dropped; blockquote markers are stripped.\nProvenance is declared by either a `[n]` citation or an `[unverified]` marker,\nso a sentence carrying both counts once. Run `verify` without a threshold first\nand read the `info: stats:` line to see the counts before picking a number.\n\n## Pitfalls\n\n- **Registering after writing.** The ledger must be populated from tool output,\n  not reconstructed from the draft — that reintroduces exactly the hallucinated\n  -URL risk the numbering removes.\n- **Renumbering mid-task.** Never hand-edit ids in a draft. Ids are ledger\n  identities; if a draft cites `[4]`, `[4]` must stay that source. Run `reset`\n  only between tasks.\n- **Retyping URLs into the Sources block.** Always `render`. A hand-typed URL\n  is an unverified claim.\n- **Citing a search snippet as if you read the page.** A `web_search`\n  description supports only what it literally says. Cite the extracted page\n  when the claim needs the body — `web_extract` it first.\n- **Over-citing.** Three ids on a sentence is the ceiling; a citation on every\n  clause makes text unreadable and hides which source carries the load.\n- **Citing the ledger in code\u002Fconfig artifacts.** Source comments belong in\n  prose deliverables and doc headers, not inside generated code.\n- **Parallel subagents.** Each subagent has its own working directory; point\n  them all at one ledger with `--ledger` (or `HERMES_CITATION_LEDGER`) if their\n  outputs get merged, otherwise their ids will collide.\n- **Quoting from a snippet instead of the page.** Evidence quotes must come\n  from the extracted page text, not a search-result description — `web_extract`\n  first, save the text, then `quote --from` that file.\n- **Paraphrasing into `quote --text`.** The verbatim check will reject it; the\n  fix is to find the actual sentence, not to reword until something matches.\n- **Using `[unverified]` as an escape hatch.** It marks the rare claim that\n  genuinely cannot be sourced; if most sentences carry it, the task needed more\n  retrieval, not more markers.\n- **Hand-editing the Sources block.** Use `render --replace-in \u003Cdraft>`; slicing\n  the file yourself risks a stale or duplicated block that `verify` then flags.\n\n## Verification\n\n```bash\npython \"$S\" verify report.md --strict --min-coverage 0.5\n```\n\nGreen means: every `[n]` in the draft exists in the ledger, the Sources block\nlists exactly the cited ids with the ledger's URLs, and the cited share of\nsource-bearing sentences meets the threshold. Read the warnings even when the\nexit code is 0 — uncited registered sources usually mean a claim lost its\nattribution during editing.\n",{"name":37,"author":38,"license":15,"version":39,"metadata":40,"platforms":56,"description":60},"grounded-citations","Hermes Agent + Teknium","1.2.0",{"hermes":41},{"tags":42,"category":49,"related_skills":50},[43,44,45,46,47,48],"Research","Citations","Grounding","Sources","Web","Reports","research",[51,52,53,54,55],"arxiv","pdf","reddit-reading","rss-feeds","youtube-content",[57,58,59],"linux","macos","windows","Ground answers and documents in cited, verifiable sources.","main","64e2fc9afa7bb3da1138eb73399144d0e7e73e9d","claude-plugin\u002Fskills\u002Fperspicacity",3,"https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave","https:\u002F\u002Fgithub.com\u002Fpedronaugusto","2026-11-10 03:07:12",{"source":8,"skillName":37,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add pedronaugusto\u002Fblender-weave --skill grounded-citations",{"tool":74,"command":75},"bunx","bunx skills add pedronaugusto\u002Fblender-weave --skill grounded-citations",{"tool":77,"command":78},"pnpm","pnpm dlx skills add pedronaugusto\u002Fblender-weave --skill grounded-citations","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Fperspicacity\u002FSKILL.md",true,[82,88,92,98],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fcitation-formats.md","REFERENCE","参考文档",2418,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fwriting\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002Freferences\u002Fcitation-formats.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fgrounding-rationale.md",3127,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fwriting\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002Freferences\u002Fgrounding-rationale.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002F_hermes_home.py","SCRIPT","脚本",836,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fwriting\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002Fscripts\u002F_hermes_home.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fsources.py",25808,"https:\u002F\u002Fgithub.com\u002Fadnichols\u002Fai-configs\u002Fblob\u002Fmain\u002F_hermes\u002Fdefault\u002Fprofiles\u002Fwriting\u002Fskills\u002Fresearch\u002Fgrounded-citations\u002Fscripts\u002Fsources.py",[103,115,125,139,149,162],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":32},"01M6HPY0J2SFKBYX5694JDTCC3","walkthrough","Plan and render a camera walkthrough animation","https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Fwalkthrough\u002FSKILL.md",[],[105,110,111,112,113,114],"Animation","plan","camera","render","true",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":32},"01M6HPXY36AJ6S4M8A7VKEPQQY","fill","Analyze empty space and suggest items to fill the room","https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Fspace-fill\u002FSKILL.md",[],[117,114,122,123,124],"analyze","empty","space",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":32},"01M6HPXW8TVKQ6Y6EGKHGRTNY8","scene-check","Run Scene Doctor to diagnose and fix scene issues","https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Fscene-check\u002FSKILL.md",[],[132,133,134,135,136,137,138,114],"scene check","check","doctor","issues","run","diagnose","fix",{"skillNo":140,"name":113,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"publishedAt":32},"01M6HPXTKC3MG6CGG32C2BGBFT","Set up and execute a render of the current camera view","https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Frender-setup\u002FSKILL.md",[],[113,114,145,112,146,147,148],"up","SET","view","execute",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":32},"01M6HPXRYFPGMKBTPJFMKTXV6G","save","Quick save with snapshot and auto-generated filename","https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Fquick-save\u002FSKILL.md",[],[151,156,157,158,159,160,161,114],"snapshot","generated","auto","auto-generated","with","quick",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":32},"01M6HPXED8N91RBXMFZTCG2328","material-recipes","PBR material recipes for BlenderWeave — ready-to-use parameter sets for common materials like wood, metal, glass, concrete, fabric, and more.","https:\u002F\u002Fgithub.com\u002Fpedronaugusto\u002Fblender-weave\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Fskills\u002Fmaterial-recipes\u002FSKILL.md",[],[169,170,171,172,173,174,175,176,177,30,178,179],"material recipes","material","recipes","pbr","fabric","common","use","ready","more","materials","metal"]