[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPRKWEP46AFXY0RREH1PM2":3,"skill-same:01M7EPRKWEP46AFXY0RREH1PM2":99},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M7EPRKWEP46AFXY0RREH1PM2","two-columns",null,"Track where a fact was learned and when it was last used, with two extra columns on any note — first-seen and last-cited. Use when notes outgrow one file, when a claim needs its origin, when deciding what to compact or archive, or when handing notes to another agent. Triggers - \"where did we learn this\", \"when did we last use this\", \"what should I compact\", \"split my notes\", \"doubly linked\", \"first seen\", \"last cited\", \"citation pressure\", \"what can I archive\", \"hand my notes to another AI\".","inputloop\u002Fgarden","inputloop","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F339507215?v=4","01M7ENYT15EMVBAV30YXPQDYE2","Inputloop","01M7ENYT1SM9WM5PSMQDC9PE2G",0,"GPL-3.0","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: two-columns\ndescription: Track where a fact was learned and when it was last used, with two extra columns on any note — first-seen and last-cited. Use when notes outgrow one file, when a claim needs its origin, when deciding what to compact or archive, or when handing notes to another agent. Triggers - \"where did we learn this\", \"when did we last use this\", \"what should I compact\", \"split my notes\", \"doubly linked\", \"first seen\", \"last cited\", \"citation pressure\", \"what can I archive\", \"hand my notes to another AI\".\n---\n\n# Two Columns\n\nNotes usually carry what a thing *is*. Two more columns make them usable by\nsomebody who was not there:\n\n| column | what it holds | when it is written |\n|---|---|---|\n| **first-seen** | where this was learned — the earliest record of it you can open | once, when the note is born, and never again |\n| **last-cited** | the most recent time it was used, and where | every time it is used |\n\nEverything else in this skill follows from those two, including what to\narchive and what to keep.\n\n## Why two, and why these two\n\nNotes rot in two directions and the columns catch one each.\n\n**Backward.** A claim with no origin becomes a fact by sitting still. Nobody\ndemoted it; it just outlived the memory of who said it. `first-seen` is the\nreceipt, and it is a *pointer*, not a date — a date tells you a fact is old,\na pointer lets you go and check it.\n\n**Forward.** A note nobody has used in a year and a note used twelve times\nlast week look identical on disk. `last-cited` separates them, and the gap\nbetween the two columns is the number that makes the rest of this skill\nmechanical:\n\n```\npressure = citations since this note was last revised\n```\n\nHigh pressure means the note is load-bearing and stale — you are leaning on\nsomething you have not re-checked. Zero pressure means nothing needed it.\nThat is the compaction queue, and it is a count rather than a judgement.\n\n**Buoyancy.** Pressure is how far a note floats. High pressure stays at the\nsurface, where a reader meets it first. Zero pressure sinks toward the floor.\n*Sinking is not deletion* — the floor is still the store. A note at the floor\nis one you can still open; it is just not in the way.\n\n## The note shape\n\nStart from the [[pocket-mentat]] one-liner — it already carries the origin\nand the falsifier, and it needs no translation:\n\n```\nSEAM — PIN (triggers: …) — From: … — Would-change: …\n```\n\n- **SEAM** — the handle you will grab it by.\n- **PIN** — what it means in plain words, plus the trigger words that should\n  make it come back.\n- **From:** — `you` · `them` · `a source (named)` · `a guess`.\n- **Would-change:** — the one thing that would make this note wrong.\n\nThen add the two columns, plus the palace's links when they are obviously\nuseful:\n\n```\nfirst-seen:  \u003Cpointer to the earliest record>\nlast-cited:  \u003Cwhen, and where>\ncame-from:   \u003Cthe note this grew out of>\nleads-to:    \u003Cwhere it points next>\n```\n\n`came-from` \u002F `leads-to` are the [[fortress-palace]] spine. `first-seen` \u002F\n`last-cited` are the two columns. Beads on a string, walkable both ways.\n\n## The rule that makes it survive more than one file\n\n**When a note moves, changes, or is superseded, do not edit it. Write a new\none beside it and point back.**\n\n```\nfirst-seen: \u003Cunchanged — it still names the earliest record>\nprev:       \u003Cthe note this replaces>\n```\n\nThe old note stays. `first-seen` is *carried*, never recomputed — that is the\nwhole trick, and it is why the chain still works after a hundred revisions:\ngeneration 40 and generation 1 name the same origin, so no reader has to walk\nbackward to find out where a fact came from. They only walk backward if they\nwant to see how it got here.\n\nThree consequences worth having on purpose:\n\n1. **Nothing is lost to an edit**, so \"we simplified that note last month\" is\n   never the reason an answer is gone.\n2. **Editing somebody else's note becomes impossible rather than forbidden.**\n   A second person can only add. You do not need a rule about it.\n3. **Citing costs nothing.** A citation appends one line somewhere else; it\n   never rewrites the note. If you put `last-cited` *inside* the note you\n   would have to rewrite the note every time you used it, and the history\n   would fill with revisions that changed one timestamp.\n\nThat third one is why the two columns live in two different places, and it is\nthe most common thing to get wrong.\n\n## Paths, when notes point at files\n\nA path with no scheme is right on one machine and unresolvable everywhere\nelse, and the note does not say which machine. Give every path a prefix:\n\n```\nnotes:\u002Fseams\u002Ffoo.md          somewhere inside this notes area\nproject:\u002Fdocs\u002Fdesign.md      relative to the project root\nlaptop:\u002FUsers\u002Fme\u002Fx.md        pinned to a named machine, on purpose\n\u002FUsers\u002Fme\u002Fx.md               ← don't. Which machine? The note cannot say.\n```\n\nThe prefix is not bureaucracy. It is the difference between a note you can\nhand to somebody and a note that only works where it was written.\n\n## Doing it by hand, with no tools at all\n\nThis is the whole method, and it works in a plain text file:\n\n1. Write the note in the one-line shape above. Fill `From:` and\n   `Would-change:` even when they feel obvious — the obvious ones are the\n   ones that later turn out to be guesses.\n2. Set `first-seen` to the oldest thing you can actually open.\n3. Every time you use the note somewhere, add a line to a running list:\n   `\u003Cwhen> — \u003Cwhere you used it>`. That list is `last-cited`.\n4. To revise: **copy the note, change the copy, add `prev:`, keep\n   `first-seen` as it was.** Leave the original alone.\n5. To decide what to compact: count citations since each note's last\n   revision. Work top-down.\n\nNo tooling is required for any of that. The tool below only counts.\n\n## Checking it\n\n```\nsh scripts\u002Fdl1nk NOTES.md          per-note verdict, and the pressure column\nsh scripts\u002Fdl1nk --format          print the format reminder\nsh tests.sh                        fixtures vs expected verdicts\nsh tests.sh --prove-red            prove the harness can fail\n```\n\nVerdicts, in [[pocket-mentat]]'s own words plus the two this skill adds:\n\n| verdict | meaning |\n|---|---|\n| `OK` | seam, meaning, triggers, source, falsifier and both columns present |\n| `GUESS` | correctly labelled a guess — valid, and the label is the point |\n| `UNSOURCED` | no `From:` — a guess wearing a fact's clothes |\n| `UNFALSIFIABLE` | no `Would-change:` — an opinion filed as a note |\n| `NO-FIRST-SEEN` | cannot say where it was learned |\n| `NO-LAST-CITED` | never used since it was written, or nobody recorded it |\n| `BARE-PATH` | a path with no scheme |\n\n`UNSOURCED` and `UNFALSIFIABLE` are the two that matter most; the rest is\nhygiene. `NO-LAST-CITED` is *not* a defect on a new note — it is the normal\nstate of something written and not yet used.\n\n## What this is not for\n\nDo not put the columns on things that have no origin and no uses: a\npreference, a draft sentence, a shopping list. There the columns are cost\nwith no gauge. The test is whether you would ever want to ask \"where did this\ncome from\" or \"is anyone still using this\" — if not, skip it.\n\n**Off-switch.** Say \"no columns here — this is a draft\" and it stops applying.\n\n## Handing this to somebody else\n\n`assets\u002FTWO-COLUMNS.md` is the paste-in version: the same method with no\nhouse vocabulary, no links to other skills, and nothing that assumes a\nparticular tree. Hand it over **verbatim**. Translating it into local\nvocabulary destroys the only property that matters, which is that it works in\na stranger's assistant with no context at all.\n\n## Interlocks\n\n- [[pocket-mentat]] — the note shape this extends; the `came-from`\u002F`leads-to`\n  links are already there, and this adds the two columns.\n- [[fortress-palace]] — its tables are these notes at scale.\n- [[seams]] — `first-seen` is what makes a single source *visibly* single; a\n  claim with one source carries the dagger `†` until a second one is on disk.\n- [[countable-gauge]] — pressure is a gauge, so it prints a number and not a\n  verdict. What the number means is your judgement, not the tool's.\n- [[import-memory]] — the other direction, when notes are arriving.\n\n## Provenance\n\nThe two columns are Corwin's, stated 2026-09-14: *\"we must always implement in\nterms of keeping close track of where we learned something and the most\n[recent] citation of each fact we write\u002Fcite.\"* The note shape and the\n`came-from`\u002F`leads-to` links are [[pocket-mentat]]'s, unchanged. The\nbuoyancy reading is his own index card beside the 2026-09-14 drawing —\nSURFACE \u002F \"buoyancy\" over DEPTH \u002F FLOOR, periscope up, DIVE down.\n\nThe archive-only mechanics are implemented in `polygram\u002Fmcp\u002Fstore.py` and\nserved over MCP by `mentcached`; this skill is the version that works with\nnone of that installed. **Mint status: unblessed**, nothing installed.\n\n\u003C!-- footer: minted by bin\u002Fft1mt from conventions\u002Fhouse.env and conventions\u002FFOOTERS.org; edit those, not this -->\n*Version 1.1.0: edition revised from 1.0.1 on 2026-10-10; spine: 2026-09-14.*\n\nCopyright 2026 Corwin Brust \u003Ccorwin@bru.st> and Contributors; CC-BY-SA4: https:\u002F\u002Fcreativecommons.org\u002Flicenses\u002Fby-sa\u002F4.0\u002F (scripts GPL-3.0-or-later); Mentat (for Corwin; claude-opus-5-5)\n\u003C!-- \u002Ffooter -->\n","# Two Columns\n\nNotes usually carry what a thing *is*. Two more columns make them usable by\nsomebody who was not there:\n\n| column | what it holds | when it is written |\n|---|---|---|\n| **first-seen** | where this was learned — the earliest record of it you can open | once, when the note is born, and never again |\n| **last-cited** | the most recent time it was used, and where | every time it is used |\n\nEverything else in this skill follows from those two, including what to\narchive and what to keep.\n\n## Why two, and why these two\n\nNotes rot in two directions and the columns catch one each.\n\n**Backward.** A claim with no origin becomes a fact by sitting still. Nobody\ndemoted it; it just outlived the memory of who said it. `first-seen` is the\nreceipt, and it is a *pointer*, not a date — a date tells you a fact is old,\na pointer lets you go and check it.\n\n**Forward.** A note nobody has used in a year and a note used twelve times\nlast week look identical on disk. `last-cited` separates them, and the gap\nbetween the two columns is the number that makes the rest of this skill\nmechanical:\n\n```\npressure = citations since this note was last revised\n```\n\nHigh pressure means the note is load-bearing and stale — you are leaning on\nsomething you have not re-checked. Zero pressure means nothing needed it.\nThat is the compaction queue, and it is a count rather than a judgement.\n\n**Buoyancy.** Pressure is how far a note floats. High pressure stays at the\nsurface, where a reader meets it first. Zero pressure sinks toward the floor.\n*Sinking is not deletion* — the floor is still the store. A note at the floor\nis one you can still open; it is just not in the way.\n\n## The note shape\n\nStart from the [[pocket-mentat]] one-liner — it already carries the origin\nand the falsifier, and it needs no translation:\n\n```\nSEAM — PIN (triggers: …) — From: … — Would-change: …\n```\n\n- **SEAM** — the handle you will grab it by.\n- **PIN** — what it means in plain words, plus the trigger words that should\n  make it come back.\n- **From:** — `you` · `them` · `a source (named)` · `a guess`.\n- **Would-change:** — the one thing that would make this note wrong.\n\nThen add the two columns, plus the palace's links when they are obviously\nuseful:\n\n```\nfirst-seen:  \u003Cpointer to the earliest record>\nlast-cited:  \u003Cwhen, and where>\ncame-from:   \u003Cthe note this grew out of>\nleads-to:    \u003Cwhere it points next>\n```\n\n`came-from` \u002F `leads-to` are the [[fortress-palace]] spine. `first-seen` \u002F\n`last-cited` are the two columns. Beads on a string, walkable both ways.\n\n## The rule that makes it survive more than one file\n\n**When a note moves, changes, or is superseded, do not edit it. Write a new\none beside it and point back.**\n\n```\nfirst-seen: \u003Cunchanged — it still names the earliest record>\nprev:       \u003Cthe note this replaces>\n```\n\nThe old note stays. `first-seen` is *carried*, never recomputed — that is the\nwhole trick, and it is why the chain still works after a hundred revisions:\ngeneration 40 and generation 1 name the same origin, so no reader has to walk\nbackward to find out where a fact came from. They only walk backward if they\nwant to see how it got here.\n\nThree consequences worth having on purpose:\n\n1. **Nothing is lost to an edit**, so \"we simplified that note last month\" is\n   never the reason an answer is gone.\n2. **Editing somebody else's note becomes impossible rather than forbidden.**\n   A second person can only add. You do not need a rule about it.\n3. **Citing costs nothing.** A citation appends one line somewhere else; it\n   never rewrites the note. If you put `last-cited` *inside* the note you\n   would have to rewrite the note every time you used it, and the history\n   would fill with revisions that changed one timestamp.\n\nThat third one is why the two columns live in two different places, and it is\nthe most common thing to get wrong.\n\n## Paths, when notes point at files\n\nA path with no scheme is right on one machine and unresolvable everywhere\nelse, and the note does not say which machine. Give every path a prefix:\n\n```\nnotes:\u002Fseams\u002Ffoo.md          somewhere inside this notes area\nproject:\u002Fdocs\u002Fdesign.md      relative to the project root\nlaptop:\u002FUsers\u002Fme\u002Fx.md        pinned to a named machine, on purpose\n\u002FUsers\u002Fme\u002Fx.md               ← don't. Which machine? The note cannot say.\n```\n\nThe prefix is not bureaucracy. It is the difference between a note you can\nhand to somebody and a note that only works where it was written.\n\n## Doing it by hand, with no tools at all\n\nThis is the whole method, and it works in a plain text file:\n\n1. Write the note in the one-line shape above. Fill `From:` and\n   `Would-change:` even when they feel obvious — the obvious ones are the\n   ones that later turn out to be guesses.\n2. Set `first-seen` to the oldest thing you can actually open.\n3. Every time you use the note somewhere, add a line to a running list:\n   `\u003Cwhen> — \u003Cwhere you used it>`. That list is `last-cited`.\n4. To revise: **copy the note, change the copy, add `prev:`, keep\n   `first-seen` as it was.** Leave the original alone.\n5. To decide what to compact: count citations since each note's last\n   revision. Work top-down.\n\nNo tooling is required for any of that. The tool below only counts.\n\n## Checking it\n\n```\nsh scripts\u002Fdl1nk NOTES.md          per-note verdict, and the pressure column\nsh scripts\u002Fdl1nk --format          print the format reminder\nsh tests.sh                        fixtures vs expected verdicts\nsh tests.sh --prove-red            prove the harness can fail\n```\n\nVerdicts, in [[pocket-mentat]]'s own words plus the two this skill adds:\n\n| verdict | meaning |\n|---|---|\n| `OK` | seam, meaning, triggers, source, falsifier and both columns present |\n| `GUESS` | correctly labelled a guess — valid, and the label is the point |\n| `UNSOURCED` | no `From:` — a guess wearing a fact's clothes |\n| `UNFALSIFIABLE` | no `Would-change:` — an opinion filed as a note |\n| `NO-FIRST-SEEN` | cannot say where it was learned |\n| `NO-LAST-CITED` | never used since it was written, or nobody recorded it |\n| `BARE-PATH` | a path with no scheme |\n\n`UNSOURCED` and `UNFALSIFIABLE` are the two that matter most; the rest is\nhygiene. `NO-LAST-CITED` is *not* a defect on a new note — it is the normal\nstate of something written and not yet used.\n\n## What this is not for\n\nDo not put the columns on things that have no origin and no uses: a\npreference, a draft sentence, a shopping list. There the columns are cost\nwith no gauge. The test is whether you would ever want to ask \"where did this\ncome from\" or \"is anyone still using this\" — if not, skip it.\n\n**Off-switch.** Say \"no columns here — this is a draft\" and it stops applying.\n\n## Handing this to somebody else\n\n`assets\u002FTWO-COLUMNS.md` is the paste-in version: the same method with no\nhouse vocabulary, no links to other skills, and nothing that assumes a\nparticular tree. Hand it over **verbatim**. Translating it into local\nvocabulary destroys the only property that matters, which is that it works in\na stranger's assistant with no context at all.\n\n## Interlocks\n\n- [[pocket-mentat]] — the note shape this extends; the `came-from`\u002F`leads-to`\n  links are already there, and this adds the two columns.\n- [[fortress-palace]] — its tables are these notes at scale.\n- [[seams]] — `first-seen` is what makes a single source *visibly* single; a\n  claim with one source carries the dagger `†` until a second one is on disk.\n- [[countable-gauge]] — pressure is a gauge, so it prints a number and not a\n  verdict. What the number means is your judgement, not the tool's.\n- [[import-memory]] — the other direction, when notes are arriving.\n\n## Provenance\n\nThe two columns are Corwin's, stated 2026-09-14: *\"we must always implement in\nterms of keeping close track of where we learned something and the most\n[recent] citation of each fact we write\u002Fcite.\"* The note shape and the\n`came-from`\u002F`leads-to` links are [[pocket-mentat]]'s, unchanged. The\nbuoyancy reading is his own index card beside the 2026-09-14 drawing —\nSURFACE \u002F \"buoyancy\" over DEPTH \u002F FLOOR, periscope up, DIVE down.\n\nThe archive-only mechanics are implemented in `polygram\u002Fmcp\u002Fstore.py` and\nserved over MCP by `mentcached`; this skill is the version that works with\nnone of that installed. **Mint status: unblessed**, nothing installed.\n\n\u003C!-- footer: minted by bin\u002Fft1mt from conventions\u002Fhouse.env and conventions\u002FFOOTERS.org; edit those, not this -->\n*Version 1.1.0: edition revised from 1.0.1 on 2026-10-10; spine: 2026-09-14.*\n\nCopyright 2026 Corwin Brust \u003Ccorwin@bru.st> and Contributors; CC-BY-SA4: https:\u002F\u002Fcreativecommons.org\u002Flicenses\u002Fby-sa\u002F4.0\u002F (scripts GPL-3.0-or-later); Mentat (for Corwin; claude-opus-5-5)\n\u003C!-- \u002Ffooter -->\n",{"name":5,"description":7},"main","0b0a0f665f67605c3bc1d43500eea26ef3079a97","skills\u002Ftwo-columns","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden","https:\u002F\u002Fgithub.com\u002Finputloop","2026-10-14 18:29:39",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add inputloop\u002Fgarden --skill two-columns",{"tool":36,"command":37},"bunx","bunx skills add inputloop\u002Fgarden --skill two-columns",{"tool":39,"command":40},"pnpm","pnpm dlx skills add inputloop\u002Fgarden --skill two-columns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002FSKILL.md",true,[44,50,53,56,60,64,67,73,76,79,82,85,91,95],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},".arc\u002F2026-09\u002Fsignature-2026-09-23_pre-header-pass.asc","OTHER","其他",659,"https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-09\u002Fsignature-2026-09-23_pre-header-pass.asc",{"path":51,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":52},".arc\u002F2026-09\u002Fsignature-2026-09-24_162129Z_pre-manifest.asc","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-09\u002Fsignature-2026-09-24_162129Z_pre-manifest.asc",{"path":54,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":55},".arc\u002F2026-09\u002Fsignature-2026-09-27_203836Z_pre-manifest.asc","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-09\u002Fsignature-2026-09-27_203836Z_pre-manifest.asc",{"path":57,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":58,"sourceHtmlUrl":59},".arc\u002F2026-09\u002Fskill-manifest-2026-09-23_pre-header-pass",326,"https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-09\u002Fskill-manifest-2026-09-23_pre-header-pass",{"path":61,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":62,"sourceHtmlUrl":63},".arc\u002F2026-09\u002Fskill-manifest-2026-09-24_162129Z_pre-manifest",571,"https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-09\u002Fskill-manifest-2026-09-24_162129Z_pre-manifest",{"path":65,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":58,"sourceHtmlUrl":66},".arc\u002F2026-09\u002Fskill-manifest-2026-09-27_203836Z_pre-manifest","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-09\u002Fskill-manifest-2026-09-27_203836Z_pre-manifest",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},".arc\u002F2026-09\u002Ftests-2026-09-27_pre-hardening.sh","SCRIPT","脚本",7701,"https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-09\u002Ftests-2026-09-27_pre-hardening.sh",{"path":74,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":75},".arc\u002F2026-10\u002Fsignature-2026-10-10_104828Z_pre-manifest.asc","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-10\u002Fsignature-2026-10-10_104828Z_pre-manifest.asc",{"path":77,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":58,"sourceHtmlUrl":78},".arc\u002F2026-10\u002Fskill-manifest-2026-10-10_104828Z_pre-manifest","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.arc\u002F2026-10\u002Fskill-manifest-2026-10-10_104828Z_pre-manifest",{"path":80,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":81},".signature.asc","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.signature.asc",{"path":83,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":58,"sourceHtmlUrl":84},".skill-manifest","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002F.skill-manifest",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"assets\u002FTWO-COLUMNS.md","ASSET","资产文件",5281,"https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002Fassets\u002FTWO-COLUMNS.md",{"path":92,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fdl1nk",8889,"https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002Fscripts\u002Fdl1nk",{"path":96,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":97,"sourceHtmlUrl":98},"tests.sh",7700,"https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Ftwo-columns\u002Ftests.sh",[100,106,112,119,126,133],{"skillNo":101,"name":102,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7EPTX6X52ZPGVQZHKVJ7FAZ","alpha","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flane-d\u002Fbr1in\u002Fours\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7EPTWCTS80QHFQ2ND3A1CW1","gamma","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flane-d\u002Fbr1in\u002Fours\u002FSOFT-SKILLS\u002Fgamma\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":19},"01M7EPTV3K3SCTRP0DR6BMMKR0","quiet","A fixture skill that declares no preferences, so skill.quiet.* has no reader.","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flane-a\u002Fdeclared\u002Fsoft\u002Fquiet\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":19},"01M7EPTSG0VE67F6PFAC0XJDQ4","demo","A fixture skill for tests\u002Fprefs-declared-spec.rb; it declares two preferences inline.","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Flane-a\u002Fdeclared\u002Fsoft\u002Fdemo\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":19},"01M7EPTP0PM5WPTFBHPXBCFM5C","concise","Synthesized by polygram from memory tag 'concise'. explicitly flagged. Review and tighten this description before relying on it for triggering.","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fconcise\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":19},"01M7EPTAETQ62DJA8ZFEEBBZF0","writing-forms","Which writing form a dated deliverable takes in the shop, and the five techniques every form shares. Use whenever someone is about to write a dated deliverable — \"which form is this?\", \"write it up\", \"land a note \u002F card \u002F model \u002F lens\", \"what shape does a … take\", \"is there a form for this\", or when a new PREFIX-date-slug filename is about to be minted. Carries the rule that a deliverable picks ONE form and says so in its filename, points at the register c\u002Fwf (columns d\u002Fc\u002Fwf) as the source of truth, names the most-used forms, the five cross-cutting techniques (two piles · cite at the act · a falsifier on every concern · the pair rule · his words), how a new form is born, and the fence on notes other sessions wrote. Not rolls (report kinds and their guards), not reformat-prompt (the REFORMAT pair), not run-card (the RUNCARD), not skill-creator (skills). Owns the FORM, not the content.","https:\u002F\u002Fgithub.com\u002Finputloop\u002Fgarden\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-forms\u002FSKILL.md",[],[]]