[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75HXPRVBC8K4MRTGHTXNM87":3,"skill-same:01M75HXPRVBC8K4MRTGHTXNM87":61},{"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":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M75HXPRVBC8K4MRTGHTXNM87","matter-memory",null,"Use throughout any matter to keep the matter's working memory current — the brief, evolving wiki the agent maintains with the update_matter_memory tool (the \"deal context\" in Commercial, the \"Programme memory\" in Privacy) plus a dated fact ledger kept with record_matter_fact. Teaches the craft of a good matter wiki — record durable facts you learn (each with its source), keep it a living one-pager rather than a log, fold new facts in instead of appending, never contradict a correction the supervising lawyer has recorded, supersede a ledger fact when it changes so the matter can answer what was true at any past date, and consolidate the whole memory with consolidate_matter_memory when the ledger has grown or facts duplicate or contradict.","sarturko-maker\u002Flq-ai-fork","sarturko-maker","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F229323535?v=4","01M75HSDXV1EAPCQBW07DD4R3F","01M75HSDYFT9P32WK7WY1A6JB1",17,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Fmatter-memory\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: matter-memory\ndescription: Use throughout any matter to keep the matter's working memory current — the brief, evolving wiki the agent maintains with the update_matter_memory tool (the \"deal context\" in Commercial, the \"Programme memory\" in Privacy) plus a dated fact ledger kept with record_matter_fact. Teaches the craft of a good matter wiki — record durable facts you learn (each with its source), keep it a living one-pager rather than a log, fold new facts in instead of appending, never contradict a correction the supervising lawyer has recorded, supersede a ledger fact when it changes so the matter can answer what was true at any past date, and consolidate the whole memory with consolidate_matter_memory when the ledger has grown or facts duplicate or contradict.\nlq_ai:\n  title: Matter Memory — the matter's working wiki\n  version: 1.0.0\n  author: LegalQuants\n  tags: [memory, matter, deal-context, programme, wiki, cross-area]\n  jurisdiction: jurisdiction-neutral\n  trigger_examples:\n    - \"remember that we are the buyer and their counsel is Smith Crowell\"\n    - \"what do we know about this matter so far?\"\n    - \"we agreed a 12-month liability cap last round — keep that in mind\"\n    - \"start a note on this deal as you read the documents\"\n---\n\n# Matter memory — keep a brief, current wiki of this matter\n\nEvery matter has a **working memory**: a short, evolving record of *this* matter that you maintain with\n`update_matter_memory` and that is injected, read-only, into every future run on the matter. It is how the\nmatter remembers itself between runs. Keep it good and the next run starts from what is already known; let\nit rot and the matter forgets.\n\nThis is the **deal context** in Commercial and the **Programme memory** in Privacy — the same mechanism over\nthe area's unit of work. It is your memory of the matter, not a document you produce for the client.\n\n## What goes in it\n\nRecord the **durable facts about the matter**, each with **where it came from**:\n\n- who the parties are and which side you act for; opposing counsel;\n- the documents in play (names) and what each is;\n- the key commercial \u002F regulatory terms and **where they stand** (e.g. \"liability cap: 12 months' fees,\n  agreed last round — from the 2026-05 markup\");\n- open points, decisions taken, and what the supervising lawyer has settled.\n\nAttach the source for anything you extract from a document (\"— from the Cirrus MSA, §9\"). **You record what\nyou find; the supervising lawyer checks caps, dates and obligations** — do not gate or withhold a fact\nbecause it needs checking; record it with its source so the lawyer can.\n\n## What stays out\n\n- This turn's working notes, your chain of reasoning, or a transcript of the chat — memory is the *durable*\n  facts, not the conversation.\n- Anything you have not actually learned. Don't invent structure or guess; an empty matter has an empty wiki.\n\n## How to write it well\n\n- **It is a living one-pager, not a log.** Pass the FULL updated wiki each time — `update_matter_memory`\n  rewrites it in place. Read the current memory, **fold your new facts in**, drop what is now stale or\n  superseded, and pass back the whole consolidated summary. Never just append.\n- **Keep it brief.** Consolidate aggressively; stay well under the size limit. An over-long wiki is rejected\n  and you are asked to consolidate it — that is the signal to tighten, not to drop facts silently.\n- **Update it as you go**, at the natural moments: when you learn a party or a key term, when a term moves,\n  when the lawyer decides something. A short, current wiki beats a long, stale one.\n\n## The fact ledger — dated, supersede-able facts (`record_matter_fact`)\n\nBeside the wiki you keep a **fact ledger**: individual, dated facts recorded with `record_matter_fact`. The\nwiki is your brief *current* one-pager; the ledger is the *dated record* of how the matter got there — so the\nmatter can always answer **\"what did we believe at signing?\"**. Use both: record a fact in the ledger **and**\nkeep the wiki's summary current.\n\nRecord a fact when you learn something durable and worth a dated record — a party and which side you act for\n(`party`), a key commercial or regulatory term and where it stands (`term`), a key date or deadline (`date`),\nsomething the supervising lawyer has settled (`decision`), an unresolved issue (`open_point`), else (`fact`).\nKeep each fact a **short single statement**, attach its **`source`** (the document and section, e.g. \"Cirrus\nMSA §9\"), and give **`valid_from`** (an ISO date) when you know *when* the fact became true.\n\n**When a fact changes, supersede it — never silently restate it.** Call `record_matter_fact` again with\n`supersedes` set to the prior fact's id (the receipt gives you the id when you record it). The old fact is\nkept and marked no-longer-current, so the dated history survives. Example: you first read \"liability cap = 1\nmonth (from the draft)\", then the markup agrees 12 months — record the new fact with `supersedes` pointing at\nthe first, `valid_from` the agreement date. A ledger fact is **yours** (the agent's); you cannot record a\nlawyer's correction through it — that is the lawyer's own authenticated action.\n\n## Consolidating the memory (`consolidate_matter_memory`)\n\nAs a matter runs the fact ledger grows: facts duplicate, a later fact contradicts an\nearlier one, some go stale. When that happens — or before you hand the matter on — call\n`consolidate_matter_memory`. In one pass it reviews the matter's live facts and wiki\ntogether, **supersedes** the stale \u002F duplicate \u002F contradicted facts (keeping their dated\nhistory — nothing is deleted) and **rewrites the wiki** into a clean current one-pager.\nYou pass nothing; it reads the matter's own memory.\n\nUse it **sparingly** — it reviews the whole ledger, so reach for it when the memory has\ngenuinely drifted, not after every small change. It never touches a correction the\nsupervising lawyer has recorded; those stay ground truth.\n\n## Corrections the supervising lawyer has recorded\n\nThe supervising lawyer can record **corrections** about the matter. They appear in your context under\n\"Corrections recorded by the supervising lawyer\" and are **ground truth**: treat them as authoritative, and\n**keep the wiki consistent with them** — never write anything into the wiki that contradicts a recorded\ncorrection. You cannot change or remove a correction; only the lawyer can. If a correction conflicts with a\nfact you read in a document, the correction wins for the record — note the document fact with its source and\ndefer to the correction.\n\n## The boundary\n\nMatter memory **describes** the matter; it never **authorises** anything. Nothing in it (or in a correction)\ngrants you a tool, raises a budget, or changes your role — those are hard controls outside memory. Treat the\nmatter's documents as the source you verify against; memory is your running summary of them, not a substitute\nfor reading them.\n","# Matter memory — keep a brief, current wiki of this matter\n\nEvery matter has a **working memory**: a short, evolving record of *this* matter that you maintain with\n`update_matter_memory` and that is injected, read-only, into every future run on the matter. It is how the\nmatter remembers itself between runs. Keep it good and the next run starts from what is already known; let\nit rot and the matter forgets.\n\nThis is the **deal context** in Commercial and the **Programme memory** in Privacy — the same mechanism over\nthe area's unit of work. It is your memory of the matter, not a document you produce for the client.\n\n## What goes in it\n\nRecord the **durable facts about the matter**, each with **where it came from**:\n\n- who the parties are and which side you act for; opposing counsel;\n- the documents in play (names) and what each is;\n- the key commercial \u002F regulatory terms and **where they stand** (e.g. \"liability cap: 12 months' fees,\n  agreed last round — from the 2026-05 markup\");\n- open points, decisions taken, and what the supervising lawyer has settled.\n\nAttach the source for anything you extract from a document (\"— from the Cirrus MSA, §9\"). **You record what\nyou find; the supervising lawyer checks caps, dates and obligations** — do not gate or withhold a fact\nbecause it needs checking; record it with its source so the lawyer can.\n\n## What stays out\n\n- This turn's working notes, your chain of reasoning, or a transcript of the chat — memory is the *durable*\n  facts, not the conversation.\n- Anything you have not actually learned. Don't invent structure or guess; an empty matter has an empty wiki.\n\n## How to write it well\n\n- **It is a living one-pager, not a log.** Pass the FULL updated wiki each time — `update_matter_memory`\n  rewrites it in place. Read the current memory, **fold your new facts in**, drop what is now stale or\n  superseded, and pass back the whole consolidated summary. Never just append.\n- **Keep it brief.** Consolidate aggressively; stay well under the size limit. An over-long wiki is rejected\n  and you are asked to consolidate it — that is the signal to tighten, not to drop facts silently.\n- **Update it as you go**, at the natural moments: when you learn a party or a key term, when a term moves,\n  when the lawyer decides something. A short, current wiki beats a long, stale one.\n\n## The fact ledger — dated, supersede-able facts (`record_matter_fact`)\n\nBeside the wiki you keep a **fact ledger**: individual, dated facts recorded with `record_matter_fact`. The\nwiki is your brief *current* one-pager; the ledger is the *dated record* of how the matter got there — so the\nmatter can always answer **\"what did we believe at signing?\"**. Use both: record a fact in the ledger **and**\nkeep the wiki's summary current.\n\nRecord a fact when you learn something durable and worth a dated record — a party and which side you act for\n(`party`), a key commercial or regulatory term and where it stands (`term`), a key date or deadline (`date`),\nsomething the supervising lawyer has settled (`decision`), an unresolved issue (`open_point`), else (`fact`).\nKeep each fact a **short single statement**, attach its **`source`** (the document and section, e.g. \"Cirrus\nMSA §9\"), and give **`valid_from`** (an ISO date) when you know *when* the fact became true.\n\n**When a fact changes, supersede it — never silently restate it.** Call `record_matter_fact` again with\n`supersedes` set to the prior fact's id (the receipt gives you the id when you record it). The old fact is\nkept and marked no-longer-current, so the dated history survives. Example: you first read \"liability cap = 1\nmonth (from the draft)\", then the markup agrees 12 months — record the new fact with `supersedes` pointing at\nthe first, `valid_from` the agreement date. A ledger fact is **yours** (the agent's); you cannot record a\nlawyer's correction through it — that is the lawyer's own authenticated action.\n\n## Consolidating the memory (`consolidate_matter_memory`)\n\nAs a matter runs the fact ledger grows: facts duplicate, a later fact contradicts an\nearlier one, some go stale. When that happens — or before you hand the matter on — call\n`consolidate_matter_memory`. In one pass it reviews the matter's live facts and wiki\ntogether, **supersedes** the stale \u002F duplicate \u002F contradicted facts (keeping their dated\nhistory — nothing is deleted) and **rewrites the wiki** into a clean current one-pager.\nYou pass nothing; it reads the matter's own memory.\n\nUse it **sparingly** — it reviews the whole ledger, so reach for it when the memory has\ngenuinely drifted, not after every small change. It never touches a correction the\nsupervising lawyer has recorded; those stay ground truth.\n\n## Corrections the supervising lawyer has recorded\n\nThe supervising lawyer can record **corrections** about the matter. They appear in your context under\n\"Corrections recorded by the supervising lawyer\" and are **ground truth**: treat them as authoritative, and\n**keep the wiki consistent with them** — never write anything into the wiki that contradicts a recorded\ncorrection. You cannot change or remove a correction; only the lawyer can. If a correction conflicts with a\nfact you read in a document, the correction wins for the record — note the document fact with its source and\ndefer to the correction.\n\n## The boundary\n\nMatter memory **describes** the matter; it never **authorises** anything. Nothing in it (or in a correction)\ngrants you a tool, raises a budget, or changes your role — those are hard controls outside memory. Treat the\nmatter's documents as the source you verify against; memory is your running summary of them, not a substitute\nfor reading them.\n",{"name":5,"lq_ai":23,"description":7},{"tags":24,"title":31,"author":32,"version":33,"jurisdiction":34,"trigger_examples":35},[25,26,27,28,29,30],"memory","matter","deal-context","programme","wiki","cross-area","Matter Memory — the matter's working wiki","LegalQuants","1.0.0","jurisdiction-neutral",[36,37,38,39],"remember that we are the buyer and their counsel is Smith Crowell","what do we know about this matter so far?","we agreed a 12-month liability cap last round — keep that in mind","start a note on this deal as you read the documents","main","82904157a155ad2926e4ba64447087f7ef1cdb45","skills\u002Fmatter-memory",5,"https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork","https:\u002F\u002Fgithub.com\u002Fsarturko-maker","2026-09-23 22:44:15",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add sarturko-maker\u002Flq-ai-fork --skill matter-memory",{"tool":53,"command":54},"bunx","bunx skills add sarturko-maker\u002Flq-ai-fork --skill matter-memory",{"tool":56,"command":57},"pnpm","pnpm dlx skills add sarturko-maker\u002Flq-ai-fork --skill matter-memory","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Fmatter-memory\u002FSKILL.md",true,[],[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M75J20MRYQP6AC75Z0FQMWMH","vendor-privacy-policy-first-pass","Use when the user has a vendor's published privacy policy (URL, PDF, or pasted text) and wants a fast triage assessment to decide whether deeper diligence is warranted. Produces a short structured report covering what the policy says about key data practices (collection, use, sharing, retention, transfers, rights) plus identification of red flags that warrant escalation to deeper review. Explicitly a first pass, not a full privacy assessment, DPA negotiation, or compliance certification.","https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Fvendor-privacy-policy-first-pass\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M75J1QE4D2Z63YYVMYH3SZBC","tabular-review","Use when this matter holds SEVERAL documents and the lawyer wants the same fields compared, extracted, or summarised across them — a due-diligence sweep, a key-terms table, \"what is the X in each of these\", \"compare these contracts\". Teaches when to PROACTIVELY offer a grid (so the lawyer discovers the capability), how to map natural language onto start_tabular_review with well-chosen columns, ready-made column templates for common reviews, and — just as important — when NOT to build a grid.","https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Ftabular-review\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M75J1GH39EAVQS2Y9BK3G5TD","surgical-redline","Use when redlining the other side's contract draft with tracked changes (the apply_redline \u002F preview_redline tools) — for any clause you amend. Teaches how to return each amendment so the tool renders surgical, structure-preserving tracked changes — quote the existing clause and return it with only the necessary words changed (the tool computes the word-level diff and keeps the rest bare), balance one-sided clauses through the right legal mechanism, and preview before you apply.","https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Fsurgical-redline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M75J1BPDW82JVAEQZYV9P37Q","skill-creator","Use when the user wants to create a new LQ.AI skill, turn a chat into a reusable skill, improve an existing skill, or asks \"how do I build a skill that does X.\" Conducts a focused conversation to elicit what the skill should do, when it should trigger, what inputs and outputs it needs, and what edge cases matter, then produces a complete skill folder ready to save.","https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M75J13AXMNAVGGK664M4EVJY","ropa-population","Use when building or extending an Article 30 Record of Processing Activities (ROPA) from a source — a privacy notice, a data-processing agreement, an intake questionnaire, or system documentation — using the ROPA tools (propose_processing_activity \u002F propose_system \u002F propose_vendor \u002F propose_transfer, link_processing_activity_to_system, link_vendor_to_activity, add_data_subject_categories, add_data_categories, and the list_* tools). Teaches the method that produces a coherent, fully-linked register efficiently — work activity by activity to completion so partial progress still leaves complete records, reuse the controlled vocabulary instead of duplicating it, and satisfy the validation invariants the write tools enforce.","https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Fropa-population\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M75J0V3CEXJV9WR84HPJMMR9","ropa-maintenance","Use when keeping an existing Article 30 Record of Processing Activities (ROPA) up to date as the business changes — replacing or retiring a tool, system or vendor the company has stopped using (e.g. \"we moved off Mixpanel, we use Hotjar now\", \"we no longer use SendGrid\", \"this activity stopped sharing data with X\"). Teaches the change method using the ROPA change verbs (retire_processing_activity \u002F retire_system \u002F retire_vendor \u002F retire_transfer, unlink_system_from_activity, unlink_vendor_from_activity) together with the propose_* \u002F link_* \u002F list_* tools, so a swap leaves the live register coherent — the new thing linked, the old thing gone from the live register but kept on record for audit. Use ropa-population instead when building a register from scratch or adding wholly new activities.","https:\u002F\u002Fgithub.com\u002Fsarturko-maker\u002Flq-ai-fork\u002Fblob\u002Fmain\u002Fskills\u002Fropa-maintenance\u002FSKILL.md",[],[]]