[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75B0RK20FGTGXMFFPJB79SY":3,"skill-same:01M75B0RK20FGTGXMFFPJB79SY":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75B0RK20FGTGXMFFPJB79SY","citation-verification",null,"The rules for grounding every claim about a matter document in a verified citation — anchoring quotes with the cite tool, handling failed verification, and sourcing case law only from the case-law tool. Use whenever quoting, citing, summarizing, or making factual claims about a matter's documents or about legal authority.","sure-scale\u002Fdoc-haus","sure-scale","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F282511471?v=4","01M75B01D5K1FE0HVC061PM46S","01M75B01E8V6PACDS15PW1JQK0",82,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fdochaus\u002Fskill\u002Fcitation-verification\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: citation-verification\ndescription: The rules for grounding every claim about a matter document in a verified citation — anchoring quotes with the cite tool, handling failed verification, and sourcing case law only from the case-law tool. Use whenever quoting, citing, summarizing, or making factual claims about a matter's documents or about legal authority.\n---\n\nA lawyer must never be handed a quote whose text does not exist in the\ndocument, or a case that does not exist in the reporter. Every factual claim\nabout a matter document is anchored before it is presented; every case-law\nclaim comes from a live lookup. Memory is not a source.\n\n\u003Cquote-first>\nWork in the order quote → assert → retract, never assert → find a quote to fit.\n\n- **Extract the supporting span before the claim.** For any sourced statement,\n  first locate the verbatim span in the matter document (search-document \u002F\n  read-document) that supports it. If no retrieved span supports a point, the\n  point has \"No relevant quotes found\" — do not make it.\n- **Assert only from extracted quotes.** Every claim must trace to a span you\n  actually pulled. Do not back-fill a quote to justify a conclusion you already\n  wrote; the quote comes first and the claim follows from it.\n- **Retract the unsupported.** Before presenting an answer, drop any claim that no\n  extracted span supports rather than leaving it standing as if grounded.\n- **Abstention is allowed and correct.** \"I can't find this in the matter's\n  approved sources\" is a valid answer. Prefer it over an answer assembled from\n  general legal knowledge — the matter's documents (and, for authority, the\n  case-law tool) are the only source of truth; your training never substitutes\n  for them or fills a gap they leave open.\n\u003C\u002Fquote-first>\n\n\u003Canti-sycophancy>\n- **Do not adopt the user's premise.** A request can carry a false legal or\n  jurisdiction premise (\"since this is governed by New York law ...\", \"the cap\n  is $5M, so ...\"). Verify the premise against the documents before relying on\n  it, and answer the corrected question.\n- **Surface and correct false premises** rather than quietly answering on top of\n  them. Reporting that the documents contradict the premise is more useful than\n  agreement.\n- **Refuse to manufacture authority.** Never invent or recall a clause, section\n  number, case, reporter citation, or governing-law fact to support an\n  unsupported position or to agree with the user. An unbacked position stays\n  unbacked and is reported as such.\n\u003C\u002Fanti-sycophancy>\n\n\u003Canchoring>\n- **Anchor every quotation.** Before any passage from a matter document goes\n  into an answer, call `cite` with it. All four required args matter:\n  `docPath` (the absolute path exactly as search-document or read-document\n  returned it — never a guessed or reconstructed path), `documentName` (the\n  human-readable name), `quote`, and `reason` (why the passage supports the\n  claim), plus an honest integer `confidence` 1-5.\n- **Quotes are verbatim, 10-600 characters.** Copy the text exactly as the\n  document returned it: no paraphrase, no added or removed ellipses, no\n  normalized punctuation or \"cleaned up\" spacing. Under 10 characters the tool\n  rejects the call — extend the quote with its surrounding sentence. Over 600,\n  split it into consecutive quotes or quote the operative sentence and put the\n  surroundings in the optional `context` arg.\n- **Claims without a quote are claims without support.** A statement like \"the\n  agreement has no cap on liability\" must rest on cited text (the clause that\n  governs liability, quoted) or be presented as unverified. Do not present a\n  conclusion about a document's contents with no anchored passage behind it.\n\u003C\u002Fanchoring>\n\n\u003Cverification-ladder>\nEvery citation any tool returns — search-document hits and cite anchors alike —\nis re-checked against the live file before you see it, on a three-step ladder:\n\n1. **exact** — the stored span still reproduces the excerpt verbatim: verified.\n2. **re-anchor** — the excerpt moved (the document was edited after indexing)\n   but still appears; the span is repaired and marked re-anchored: verified,\n   but the search index is stale.\n3. **reject** — the excerpt is nowhere in the live document: the citation is\n   dropped.\n\nWhen a result reports re-anchored or rejected citations, relay the\nrecommendation to re-upload (re-ingest) the named document — search stays\ninaccurate until then. Never quote or rely on a rejected passage.\n\u003C\u002Fverification-ladder>\n\n\u003Cfailed-verification>\nWhen `cite` cannot verify a quote, the quote is wrong — the tool re-extracted\nthe live document and the text is not in it.\n\n- **Re-read, then re-quote.** Go back to `read-document` or `search-document`,\n  find the passage, and copy the verified text verbatim into a new `cite` call.\n- **Never paraphrase-and-retry.** Reworking the failed quote from memory —\n  shuffling words, trimming clauses, \"fixing\" it until something passes — is\n  manufacturing a fabricated quotation. The only acceptable retry is text\n  freshly copied from a tool result.\n- **If the passage genuinely is not in the document**, say so. \"I could not\n  verify this in [document]\" is a correct answer; an unanchored quotation\n  never is.\n\u003C\u002Ffailed-verification>\n\n\u003Ccase-law>\n- Case names, reporter citations, holdings, and quotations from opinions come\n  ONLY from the `case-law` tool's results (or a connected CourtListener\n  source), never from memory — a remembered case is presumptively fabricated.\n  Cite only cases the tool returned, with the citation and URL it returned.\n- The corpus is U.S. opinions only. On a non-U.S. matter, do not present its\n  results as binding authority — flag them as U.S. precedent and route\n  jurisdiction-specific authority questions to the supervising lawyer.\n- When the tool returns nothing or is unreachable, report that. Never fill the\n  gap with an invented or recalled citation.\n- Auditing the citations in a finished brief or memo is its own procedure: the\n  cite-check skill.\n\u003C\u002Fcase-law>\n","A lawyer must never be handed a quote whose text does not exist in the\ndocument, or a case that does not exist in the reporter. Every factual claim\nabout a matter document is anchored before it is presented; every case-law\nclaim comes from a live lookup. Memory is not a source.\n\n\u003Cquote-first>\nWork in the order quote → assert → retract, never assert → find a quote to fit.\n\n- **Extract the supporting span before the claim.** For any sourced statement,\n  first locate the verbatim span in the matter document (search-document \u002F\n  read-document) that supports it. If no retrieved span supports a point, the\n  point has \"No relevant quotes found\" — do not make it.\n- **Assert only from extracted quotes.** Every claim must trace to a span you\n  actually pulled. Do not back-fill a quote to justify a conclusion you already\n  wrote; the quote comes first and the claim follows from it.\n- **Retract the unsupported.** Before presenting an answer, drop any claim that no\n  extracted span supports rather than leaving it standing as if grounded.\n- **Abstention is allowed and correct.** \"I can't find this in the matter's\n  approved sources\" is a valid answer. Prefer it over an answer assembled from\n  general legal knowledge — the matter's documents (and, for authority, the\n  case-law tool) are the only source of truth; your training never substitutes\n  for them or fills a gap they leave open.\n\u003C\u002Fquote-first>\n\n\u003Canti-sycophancy>\n- **Do not adopt the user's premise.** A request can carry a false legal or\n  jurisdiction premise (\"since this is governed by New York law ...\", \"the cap\n  is $5M, so ...\"). Verify the premise against the documents before relying on\n  it, and answer the corrected question.\n- **Surface and correct false premises** rather than quietly answering on top of\n  them. Reporting that the documents contradict the premise is more useful than\n  agreement.\n- **Refuse to manufacture authority.** Never invent or recall a clause, section\n  number, case, reporter citation, or governing-law fact to support an\n  unsupported position or to agree with the user. An unbacked position stays\n  unbacked and is reported as such.\n\u003C\u002Fanti-sycophancy>\n\n\u003Canchoring>\n- **Anchor every quotation.** Before any passage from a matter document goes\n  into an answer, call `cite` with it. All four required args matter:\n  `docPath` (the absolute path exactly as search-document or read-document\n  returned it — never a guessed or reconstructed path), `documentName` (the\n  human-readable name), `quote`, and `reason` (why the passage supports the\n  claim), plus an honest integer `confidence` 1-5.\n- **Quotes are verbatim, 10-600 characters.** Copy the text exactly as the\n  document returned it: no paraphrase, no added or removed ellipses, no\n  normalized punctuation or \"cleaned up\" spacing. Under 10 characters the tool\n  rejects the call — extend the quote with its surrounding sentence. Over 600,\n  split it into consecutive quotes or quote the operative sentence and put the\n  surroundings in the optional `context` arg.\n- **Claims without a quote are claims without support.** A statement like \"the\n  agreement has no cap on liability\" must rest on cited text (the clause that\n  governs liability, quoted) or be presented as unverified. Do not present a\n  conclusion about a document's contents with no anchored passage behind it.\n\u003C\u002Fanchoring>\n\n\u003Cverification-ladder>\nEvery citation any tool returns — search-document hits and cite anchors alike —\nis re-checked against the live file before you see it, on a three-step ladder:\n\n1. **exact** — the stored span still reproduces the excerpt verbatim: verified.\n2. **re-anchor** — the excerpt moved (the document was edited after indexing)\n   but still appears; the span is repaired and marked re-anchored: verified,\n   but the search index is stale.\n3. **reject** — the excerpt is nowhere in the live document: the citation is\n   dropped.\n\nWhen a result reports re-anchored or rejected citations, relay the\nrecommendation to re-upload (re-ingest) the named document — search stays\ninaccurate until then. Never quote or rely on a rejected passage.\n\u003C\u002Fverification-ladder>\n\n\u003Cfailed-verification>\nWhen `cite` cannot verify a quote, the quote is wrong — the tool re-extracted\nthe live document and the text is not in it.\n\n- **Re-read, then re-quote.** Go back to `read-document` or `search-document`,\n  find the passage, and copy the verified text verbatim into a new `cite` call.\n- **Never paraphrase-and-retry.** Reworking the failed quote from memory —\n  shuffling words, trimming clauses, \"fixing\" it until something passes — is\n  manufacturing a fabricated quotation. The only acceptable retry is text\n  freshly copied from a tool result.\n- **If the passage genuinely is not in the document**, say so. \"I could not\n  verify this in [document]\" is a correct answer; an unanchored quotation\n  never is.\n\u003C\u002Ffailed-verification>\n\n\u003Ccase-law>\n- Case names, reporter citations, holdings, and quotations from opinions come\n  ONLY from the `case-law` tool's results (or a connected CourtListener\n  source), never from memory — a remembered case is presumptively fabricated.\n  Cite only cases the tool returned, with the citation and URL it returned.\n- The corpus is U.S. opinions only. On a non-U.S. matter, do not present its\n  results as binding authority — flag them as U.S. precedent and route\n  jurisdiction-specific authority questions to the supervising lawyer.\n- When the tool returns nothing or is unreachable, report that. Never fill the\n  gap with an invented or recalled citation.\n- Auditing the citations in a finished brief or memo is its own procedure: the\n  cite-check skill.\n\u003C\u002Fcase-law>\n",{"name":5,"description":7},"dochaus","4fa71c1afaa510e46a51760c035a6be7350a4bfe","dochaus\u002Fskill\u002Fcitation-verification",23,"https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus","https:\u002F\u002Fdoc.haus","https:\u002F\u002Fgithub.com\u002Fsure-scale","2026-11-14 21:10:36",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sure-scale\u002Fdoc-haus --skill citation-verification",{"tool":37,"command":38},"bunx","bunx skills add sure-scale\u002Fdoc-haus --skill citation-verification",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sure-scale\u002Fdoc-haus --skill citation-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fdochaus\u002Fskill\u002Fcitation-verification\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M75B44S57BSW28BPNSY32KM3","figma-use","**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create\u002Fedit\u002Fdelete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75B41F6YZ7GGZR11247RWP4","figma-use-slides","This skill helps agents use Figma's use_figma MCP tool in the Slides context. Can be used alongside figma-use which has foundational context for using the use_figma tool.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-slides\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75B3XJZ4RQEVMRB8KJEZCXW","figma-use-motion","Motion \u002F animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-motion\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M75B3TSPBY2M1V5RJGDYMP60","figma-use-figjam","This skill helps agents use Figma's use_figma MCP tool in the FigJam context. Can be used alongside figma-use which has foundational context for using the use_figma tool.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-use-figjam\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M75B3NXNVRF8RRK5771619D6","figma-swiftui","SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views \u002F screens \u002F tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files \u002F an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-swiftui\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M75B3K427PFQTYE8TKXW6NST","figma-shaders","**MANDATORY prerequisite** — load this skill before calling `create_shader` or `update_shader`. Use when the user asks to create, author, change, fix, or iterate on a shader effect, shader fill, custom effect, custom fill, or procedural shader in Figma.","https:\u002F\u002Fgithub.com\u002Fsure-scale\u002Fdoc-haus\u002Fblob\u002Fdochaus\u002Fpackages\u002Fplugins\u002Ffigma\u002Fskills\u002Ffigma-shaders\u002FSKILL.md",[],[]]