[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B4BHSB78VPJ813AFV901RY":3,"skill-same:01M7B4BHSB78VPJ813AFV901RY":64},{"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":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M7B4BHSB78VPJ813AFV901RY","cold-eye",null,"Hostile read of anything shipped, deemed done, or ready to ship — a skill, a spec, a site, a package, a repo. Checks whether a cold agent can run the job without inventing it, and whether the files describe one system. Use when the author asks for a cold-eye pass, a hostile read, extreme scrutiny, or whether what they shipped would survive a picky editor. Not for plans, decisions, or work still on the table. Not for line editing, cheerleading, or a second paraphrase of the same draft.","Catalyst-Forge-LLC\u002Fcoldeye","Catalyst-Forge-LLC","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260097172?v=4","01M7AH2YQ5FHSAVKE5QB9YZM83","Catalyst Forge, LLC","01M7B4APPB9C002VRYVEXSE6SD",0,"MIT","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Fskills\u002Fcold-eye\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: cold-eye\r\ndescription: >-\r\n  Hostile read of anything shipped, deemed done, or ready to\r\n  ship — a skill, a spec, a site, a package, a repo. Checks\r\n  whether a cold agent can run the job without inventing it,\r\n  and whether the files describe one system. Use when the\r\n  author asks for a cold-eye pass, a hostile read, extreme\r\n  scrutiny, or whether what they shipped would survive a picky\r\n  editor. Not for plans, decisions, or work still on the\r\n  table. Not for line editing, cheerleading, or a second\r\n  paraphrase of the same draft.\r\n---\r\n\r\n# Cold-eye\r\n\r\n## Words\r\n\r\n- **Subject** — anything shipped, deemed done, or ready to\r\n  ship. One file or a system.\r\n- **Card** — one finished file. A skill, a spec, a procedure,\r\n  a page, a README. Not only operator files.\r\n- **System** — more than one surface. A repo, a package, a\r\n  site.\r\n- **Hour** — the procedure the subject tells someone to run:\r\n  start, read, write, stop. Public pages say procedure or job\r\n  for the same thing.\r\n- **Law** — standing rules one file owns. Copies drift.\r\n- **Lockup** — the product name plus the one line under it,\r\n  read as if that were the whole page.\r\n- **Pitch** — a card that sells instead of instructing.\r\n- **Brochure** — the public buyer page (site home, npm README).\r\n\r\nThe first reader who was not in the room: extreme scrutiny, no\r\ncredit for intent. A brochure can be sharp and still fail. So can a pitch. The\r\ntest is what a cold agent or a picky editor still has to invent\r\nafter reading the file. When the subject is a system, whether the\r\nfiles describe one product.\r\n\r\nThis procedure is for something that has shipped, is deemed done, or\r\nis ready to ship. A direction you might still change is out of\r\nscope.\r\n\r\n## The procedure\r\n\r\n1. Locate the subject (a card, a system, or what they pasted).\r\n   If none, ask.\r\n2. Read by the path below. Nothing from the thread that\r\n   produced the files.\r\n3. Run the ten tests, in order.\r\n4. Write the critique using `references\u002Fcritique.md`. Read\r\n   `references\u002Fexamples.md` before you emit a finding. If\r\n   either file is missing, stop and say so. Do not invent a\r\n   shape.\r\n5. Hand the file over. Stop. Do not rewrite the subject unless\r\n   they asked.\r\n\r\n**Write to:**\r\n\r\n- One file → `\u003Cname>.cold-eye.md` next to it (`SKILL.md` →\r\n  `SKILL.cold-eye.md`).\r\n- A system → `cold-eye.md` at the root they named.\r\n- They said chat only → stay in chat, same shape.\r\n\r\nA system path needs the tree and a shell. If you cannot open\r\nfiles or run commands, run the one-card path on what they\r\npasted and write the missing-tree marker that\r\n`references\u002Fcritique.md` specifies.\r\n\r\n## How to read\r\n\r\n**One card.** Start on that file. Open only what it tells you to\r\nopen, then the tools it names.\r\n\r\n**A system.** Do not start in the spec. The author lives there.\r\nRead in first-reader order, then open what shipped:\r\n\r\n1. The lockup, as if that were the whole page. A metaphor that\r\n   works under a hero can fail next to the name alone.\r\n2. The public page a buyer hits first. For a package, that is\r\n   also the npm README, not only the marketing site.\r\n3. The artifact the operator card says to read first.\r\n4. The operator cards.\r\n5. The spec.\r\n6. The named tools — actually open them. \"Match the system\" is\r\n   not a memory check. Open `package.json` `files`. Then run\r\n   `npm pack --dry-run --ignore-scripts`. That list\r\n   is what ships. What only lives in the repo is another\r\n   surface. They can lie in different ways.\r\n\r\nAt the lockup and brochure steps, follow `references\u002Fcomprehension.md`.\r\nReconstruct the public promise before internal specifications, then compare\r\nit with the artifact. This reading step uses the existing ten tests. Weak\r\npersuasion alone does not fail a runnable procedure.\r\n\r\nA lie the first reader hits costs more than a lie in the spec.\r\n\r\n## The test\r\n\r\nAsk, in order:\r\n\r\n1. **Pitch or procedure?** Stages and principles are not a\r\n   procedure. Can the reader run the job as steps: start, read,\r\n   write, stop?\r\n2. **What still has to be invented?** Schema, file names,\r\n   write-back, done-looks-like, refuse list. If the reader must\r\n   guess, it fails. A placeholder (`\u003Cstem>`, `draft.md`) the\r\n   procedure never binds is a guess.\r\n3. **Does it match the system it describes?** Flags, commands,\r\n   and \"the model will…\" claims against what the code or tools\r\n   actually do. Then file against file. Two locally coherent\r\n   files that contradict each other fail as a system. Drift is\r\n   a defect, not a tone note. A status marker (`locked`,\r\n   `current`, `done`) that contradicts what shipped is a\r\n   first-reader lie unless it says it is history.\r\n4. **Is a required step invisible?** If a claimed check needs a\r\n   second command, that command must sit next to the claim. A\r\n   landing-page command that does not finish the checks listed\r\n   under it is a false must-fix waiting for a buyer.\r\n5. **Are the references load-bearing?** Definitions without a\r\n   worked example and a do-not-emit example will mint false\r\n   certainty. On a brochure: does the worked example match the\r\n   injury the spec names? A milder cousin is a weaker sale and\r\n   a false picture of must-fix.\r\n6. **Is discovery copy mixed with the next job?** A description\r\n   that names a sibling skill will fire on the sibling's asks.\r\n   WHAT + WHEN + refuse. Third person. No \"you can use this.\"\r\n   Refuse the sibling job in the description; put the sibling's\r\n   **name** in the body. Same test on an install page: two hours\r\n   in one box. If the package ships two folders, say which\r\n   procedure is first.\r\n7. **Where is the law copied?** Two files that restate the same\r\n   rules will drift. One standing file. Artifacts may list this\r\n   run and point at it. A standing file the main card never\r\n   tells you to open is a landmine, worse than two copies that\r\n   both point. Two buyer URLs for the same job are the same\r\n   defect. Pick one. Point the nav at it. Sibling critique\r\n   skills that each restate a finding shape will drift the\r\n   same way.\r\n8. **Is this sentence only for the maintainer?** Ports, leases,\r\n   who publishes, \"agents must not.\" Fine in an agent rule. A\r\n   fail on the page a buyer reads first.\r\n9. **Does the procedure paper over a tool bug?** If the\r\n   procedure says write X and the named tool destroys X, name\r\n   both. Do not only rewrite the prose.\r\n10. **How does the procedure end?** Re-check, handoff, or stop.\r\n    A pass that never closes will start the next pass in the\r\n    same breath.\r\n\r\nProtect what already holds. Do not flatten dialect or\r\ndistinctive lines that are doing a job.\r\n\r\n## What \"done\" looks like\r\n\r\nThe author can take the ranked list to a rewrite. A cold agent\r\ncould run the *revised* job without a side channel. On a\r\nsystem, the revised files would describe one product. You have\r\nnot rewritten the subject unless they said to.\r\n\r\n## Refuse\r\n\r\n- Line edits dressed as scrutiny\r\n- A second paraphrase that agrees harder\r\n- A feature roadmap. Missing capability is a defect in the\r\n  claim unless the author asked you to design the missing piece\r\n- Scope that turns a review into a product redesign\r\n  unless the file's own claims force it\r\n- A direction still on the table\r\n","# Cold-eye\r\n\r\n## Words\r\n\r\n- **Subject** — anything shipped, deemed done, or ready to\r\n  ship. One file or a system.\r\n- **Card** — one finished file. A skill, a spec, a procedure,\r\n  a page, a README. Not only operator files.\r\n- **System** — more than one surface. A repo, a package, a\r\n  site.\r\n- **Hour** — the procedure the subject tells someone to run:\r\n  start, read, write, stop. Public pages say procedure or job\r\n  for the same thing.\r\n- **Law** — standing rules one file owns. Copies drift.\r\n- **Lockup** — the product name plus the one line under it,\r\n  read as if that were the whole page.\r\n- **Pitch** — a card that sells instead of instructing.\r\n- **Brochure** — the public buyer page (site home, npm README).\r\n\r\nThe first reader who was not in the room: extreme scrutiny, no\r\ncredit for intent. A brochure can be sharp and still fail. So can a pitch. The\r\ntest is what a cold agent or a picky editor still has to invent\r\nafter reading the file. When the subject is a system, whether the\r\nfiles describe one product.\r\n\r\nThis procedure is for something that has shipped, is deemed done, or\r\nis ready to ship. A direction you might still change is out of\r\nscope.\r\n\r\n## The procedure\r\n\r\n1. Locate the subject (a card, a system, or what they pasted).\r\n   If none, ask.\r\n2. Read by the path below. Nothing from the thread that\r\n   produced the files.\r\n3. Run the ten tests, in order.\r\n4. Write the critique using `references\u002Fcritique.md`. Read\r\n   `references\u002Fexamples.md` before you emit a finding. If\r\n   either file is missing, stop and say so. Do not invent a\r\n   shape.\r\n5. Hand the file over. Stop. Do not rewrite the subject unless\r\n   they asked.\r\n\r\n**Write to:**\r\n\r\n- One file → `\u003Cname>.cold-eye.md` next to it (`SKILL.md` →\r\n  `SKILL.cold-eye.md`).\r\n- A system → `cold-eye.md` at the root they named.\r\n- They said chat only → stay in chat, same shape.\r\n\r\nA system path needs the tree and a shell. If you cannot open\r\nfiles or run commands, run the one-card path on what they\r\npasted and write the missing-tree marker that\r\n`references\u002Fcritique.md` specifies.\r\n\r\n## How to read\r\n\r\n**One card.** Start on that file. Open only what it tells you to\r\nopen, then the tools it names.\r\n\r\n**A system.** Do not start in the spec. The author lives there.\r\nRead in first-reader order, then open what shipped:\r\n\r\n1. The lockup, as if that were the whole page. A metaphor that\r\n   works under a hero can fail next to the name alone.\r\n2. The public page a buyer hits first. For a package, that is\r\n   also the npm README, not only the marketing site.\r\n3. The artifact the operator card says to read first.\r\n4. The operator cards.\r\n5. The spec.\r\n6. The named tools — actually open them. \"Match the system\" is\r\n   not a memory check. Open `package.json` `files`. Then run\r\n   `npm pack --dry-run --ignore-scripts`. That list\r\n   is what ships. What only lives in the repo is another\r\n   surface. They can lie in different ways.\r\n\r\nAt the lockup and brochure steps, follow `references\u002Fcomprehension.md`.\r\nReconstruct the public promise before internal specifications, then compare\r\nit with the artifact. This reading step uses the existing ten tests. Weak\r\npersuasion alone does not fail a runnable procedure.\r\n\r\nA lie the first reader hits costs more than a lie in the spec.\r\n\r\n## The test\r\n\r\nAsk, in order:\r\n\r\n1. **Pitch or procedure?** Stages and principles are not a\r\n   procedure. Can the reader run the job as steps: start, read,\r\n   write, stop?\r\n2. **What still has to be invented?** Schema, file names,\r\n   write-back, done-looks-like, refuse list. If the reader must\r\n   guess, it fails. A placeholder (`\u003Cstem>`, `draft.md`) the\r\n   procedure never binds is a guess.\r\n3. **Does it match the system it describes?** Flags, commands,\r\n   and \"the model will…\" claims against what the code or tools\r\n   actually do. Then file against file. Two locally coherent\r\n   files that contradict each other fail as a system. Drift is\r\n   a defect, not a tone note. A status marker (`locked`,\r\n   `current`, `done`) that contradicts what shipped is a\r\n   first-reader lie unless it says it is history.\r\n4. **Is a required step invisible?** If a claimed check needs a\r\n   second command, that command must sit next to the claim. A\r\n   landing-page command that does not finish the checks listed\r\n   under it is a false must-fix waiting for a buyer.\r\n5. **Are the references load-bearing?** Definitions without a\r\n   worked example and a do-not-emit example will mint false\r\n   certainty. On a brochure: does the worked example match the\r\n   injury the spec names? A milder cousin is a weaker sale and\r\n   a false picture of must-fix.\r\n6. **Is discovery copy mixed with the next job?** A description\r\n   that names a sibling skill will fire on the sibling's asks.\r\n   WHAT + WHEN + refuse. Third person. No \"you can use this.\"\r\n   Refuse the sibling job in the description; put the sibling's\r\n   **name** in the body. Same test on an install page: two hours\r\n   in one box. If the package ships two folders, say which\r\n   procedure is first.\r\n7. **Where is the law copied?** Two files that restate the same\r\n   rules will drift. One standing file. Artifacts may list this\r\n   run and point at it. A standing file the main card never\r\n   tells you to open is a landmine, worse than two copies that\r\n   both point. Two buyer URLs for the same job are the same\r\n   defect. Pick one. Point the nav at it. Sibling critique\r\n   skills that each restate a finding shape will drift the\r\n   same way.\r\n8. **Is this sentence only for the maintainer?** Ports, leases,\r\n   who publishes, \"agents must not.\" Fine in an agent rule. A\r\n   fail on the page a buyer reads first.\r\n9. **Does the procedure paper over a tool bug?** If the\r\n   procedure says write X and the named tool destroys X, name\r\n   both. Do not only rewrite the prose.\r\n10. **How does the procedure end?** Re-check, handoff, or stop.\r\n    A pass that never closes will start the next pass in the\r\n    same breath.\r\n\r\nProtect what already holds. Do not flatten dialect or\r\ndistinctive lines that are doing a job.\r\n\r\n## What \"done\" looks like\r\n\r\nThe author can take the ranked list to a rewrite. A cold agent\r\ncould run the *revised* job without a side channel. On a\r\nsystem, the revised files would describe one product. You have\r\nnot rewritten the subject unless they said to.\r\n\r\n## Refuse\r\n\r\n- Line edits dressed as scrutiny\r\n- A second paraphrase that agrees harder\r\n- A feature roadmap. Missing capability is a defect in the\r\n  claim unless the author asked you to design the missing piece\r\n- Scope that turns a review into a product redesign\r\n  unless the file's own claims force it\r\n- A direction still on the table\r\n",{"name":5,"description":7},"main","0125dad6a6e1643c3cd38a46e24f1f6be5cbc4d6","skills\u002Fcold-eye","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye","https:\u002F\u002Fcoldeye.dev","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC","https:\u002F\u002Fwww.catalystforge.com\u002F","2026-11-12 03:45:26",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add Catalyst-Forge-LLC\u002Fcoldeye --skill cold-eye",{"tool":38,"command":39},"bunx","bunx skills add Catalyst-Forge-LLC\u002Fcoldeye --skill cold-eye",{"tool":41,"command":42},"pnpm","pnpm dlx skills add Catalyst-Forge-LLC\u002Fcoldeye --skill cold-eye","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Fskills\u002Fcold-eye\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fcomprehension.md","REFERENCE","参考文档",2628,"https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Fskills\u002Fcold-eye\u002Freferences\u002Fcomprehension.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fcritique.md",3270,"https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Fskills\u002Fcold-eye\u002Freferences\u002Fcritique.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fexamples.md",1982,"https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Fskills\u002Fcold-eye\u002Freferences\u002Fexamples.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"SKILL_FACTS.md",2397,"https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Fskills\u002Fcold-eye\u002FSKILL_FACTS.md",[65,71,78,85,92,99],{"skillNo":66,"name":67,"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":68,"categories":69,"keywords":70,"publishedAt":19},"01M7B4BG3AZCJQPX3BJP2HCHRS","docs","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Fsite\u002Fdocs\u002Fskill.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7B4BD25WYM5GCK9XX0JF1V6","unbound-output","Procedure for listing problems in a finished file. Not for drafts still in progress.","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Ffixtures\u002Funbound-output\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7B4B9MP981ZR69G7FFJ0FWK","sibling-description","Hostile read of a finished file. Also use detangler when a long draft has been edited a lot and you want a structural pass.","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Ffixtures\u002Fsibling-description\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7B4B6TP2BDDZEVMR0JGXD8S","pitch-stages","A thoughtful approach to reviewing documents with care and principles.","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Ffixtures\u002Fpitch-stages\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7B4B425PB75R0T8GGXJCC51","no-close","Lists invented steps in a finished file. Not for unfinished plans.","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Ffixtures\u002Fno-close\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"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},"01M7B4B14RCGH89Z95Z0HXYYCV","invisible-pack","Check what a package ships. Not for writing new features.","https:\u002F\u002Fgithub.com\u002FCatalyst-Forge-LLC\u002Fcoldeye\u002Fblob\u002Fmain\u002Ffixtures\u002Finvisible-pack\u002FSKILL.md",[],[]]