[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DGSC3SPPSYQNPR9G7NYYV4":3,"skill-same:01M7DGSC3SPPSYQNPR9G7NYYV4":44},{"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},"01M7DGSC3SPPSYQNPR9G7NYYV4","cli-software",null,"Use for any task whose prompt is a multi-part specification for a CLI tool or program (numbered requirements, commands, options, output formats, error handling, examples), especially when built incrementally across several checkpoints and graded by hidden tests. Load before reading the spec in detail.","jemdiggity\u002Fkojo","jemdiggity","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1940552?v=4","01M7DGK797SRB0B74KVSKQ44GZ","Jeremy Hale","01M7DGK7ABQPV6AA6CPDC2NNP7",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dbm\u002Fround1\u002Fs1b-union-echo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cli-software\ndescription: Use for any task whose prompt is a multi-part specification for a CLI tool or program (numbered requirements, commands, options, output formats, error handling, examples), especially when built incrementally across several checkpoints and graded by hidden tests. Load before reading the spec in detail.\n---\n\n# CLI software: accept the union, emit the superset\n\nRead the spec, keep short notes in `NOTES.md`, and verify by running real commands.\nBeyond that base, two rules decide most of the hidden-test outcome.\n\n## Rule 1: When the spec is silent or ambiguous, implement the union\n\nHidden tests were written by someone with one reading in mind, and you cannot ask which.\nA documented guess loses whenever it is the other reading. So never pick one:\nmake every plausible reading work.\n\nConcretely, whenever you notice yourself deciding, do all of the following that apply:\n\n- **Value semantics:** a field could be an expression or a literal? Try the richer\n  interpretation first, fall back to the literal on failure. A sibling field with the same\n  role tells you the intended semantics; match it.\n- **Option placement:** accept options before, between, and after positional arguments.\n- **Container shapes:** accept a bare list *and* an object wrapper around it; accept a\n  string *and* a structured object where either could encode the same thing; accept\n  missing optional keys with sensible defaults.\n- **Locations:** accept a file inside the expected directory *and* a path outside it;\n  relative and absolute paths; with and without extension where sensible.\n- **Case and spelling:** accept case-insensitive keywords and common aliases when the spec\n  does not forbid it.\n- **Pre-existing state:** read state you did not write (other tools, earlier versions,\n  hand-authored files). Parse liberally; tolerate extra keys and alternative encodings.\n\nDo not confuse \"accept the union\" with \"do anything\". Where the spec explicitly says an\ninput is an error, it is an error. Where the spec says nothing, be generous on input.\n\nWrite each union decision as one line in `NOTES.md` under `## Ambiguities` so later\ncheckpoints preserve it.\n\n## Rule 2: Output events echo every identifying field\n\nAny structured output (a JSON event, a log line, a status record, a dry-run plan) must\ncarry **every** field that identifies what happened, not just the fields shown in the\nspec's example:\n\n- operation type \u002F action name\n- the target object (table, file, resource, key), including its parent\u002Fcontainer\n- the subject inside the target (column, field, index, entry) when one exists\n- before\u002Fafter or from\u002Fto values for renames, moves, type changes, data rewrites\n- the name of anything created or removed as a side effect\n\nThe spec's example output is a **floor**, not a ceiling. Tests check for fields being\npresent and correct; an extra key costs nothing, a missing key fails the test. When you\nbuild the reverse\u002Fundo\u002Frollback record for an operation, it must identify its target as\ncompletely as the forward record did.\n\nBefore finishing each checkpoint, print one real event of each type your tool can emit\nand inspect it: for each, ask \"could a reader reconstruct exactly what happened, on what,\nfrom this line alone?\" If not, add fields.\n\n## Verify by running\n\n- Run every example command in the spec verbatim, then once more with a perturbation\n  (option order, path location, empty\u002Fnull value, quoted vs bare value).\n- Trigger every error bullet on purpose and check message, stream, and exit code.\n- Hand-craft an input that a *different* reasonable implementer might produce, and make\n  sure it is accepted.\n\n## Do not\n\n- Do not stop to ask about an ambiguity; the run is non-interactive. Implement both.\n- Do not reject inputs the spec does not explicitly forbid.\n- Do not wrap the command entry point in a broad exception handler that turns runtime\n  failures into usage messages. Usage errors come from the argument parser only; all other\n  failures print `Error: \u003Creason>` to stderr and exit non-zero, without a traceback.\n- Do not silently drop a guaranteed property because a fast path cannot preserve it; use\n  the thorough path or fail loudly.\n","# CLI software: accept the union, emit the superset\n\nRead the spec, keep short notes in `NOTES.md`, and verify by running real commands.\nBeyond that base, two rules decide most of the hidden-test outcome.\n\n## Rule 1: When the spec is silent or ambiguous, implement the union\n\nHidden tests were written by someone with one reading in mind, and you cannot ask which.\nA documented guess loses whenever it is the other reading. So never pick one:\nmake every plausible reading work.\n\nConcretely, whenever you notice yourself deciding, do all of the following that apply:\n\n- **Value semantics:** a field could be an expression or a literal? Try the richer\n  interpretation first, fall back to the literal on failure. A sibling field with the same\n  role tells you the intended semantics; match it.\n- **Option placement:** accept options before, between, and after positional arguments.\n- **Container shapes:** accept a bare list *and* an object wrapper around it; accept a\n  string *and* a structured object where either could encode the same thing; accept\n  missing optional keys with sensible defaults.\n- **Locations:** accept a file inside the expected directory *and* a path outside it;\n  relative and absolute paths; with and without extension where sensible.\n- **Case and spelling:** accept case-insensitive keywords and common aliases when the spec\n  does not forbid it.\n- **Pre-existing state:** read state you did not write (other tools, earlier versions,\n  hand-authored files). Parse liberally; tolerate extra keys and alternative encodings.\n\nDo not confuse \"accept the union\" with \"do anything\". Where the spec explicitly says an\ninput is an error, it is an error. Where the spec says nothing, be generous on input.\n\nWrite each union decision as one line in `NOTES.md` under `## Ambiguities` so later\ncheckpoints preserve it.\n\n## Rule 2: Output events echo every identifying field\n\nAny structured output (a JSON event, a log line, a status record, a dry-run plan) must\ncarry **every** field that identifies what happened, not just the fields shown in the\nspec's example:\n\n- operation type \u002F action name\n- the target object (table, file, resource, key), including its parent\u002Fcontainer\n- the subject inside the target (column, field, index, entry) when one exists\n- before\u002Fafter or from\u002Fto values for renames, moves, type changes, data rewrites\n- the name of anything created or removed as a side effect\n\nThe spec's example output is a **floor**, not a ceiling. Tests check for fields being\npresent and correct; an extra key costs nothing, a missing key fails the test. When you\nbuild the reverse\u002Fundo\u002Frollback record for an operation, it must identify its target as\ncompletely as the forward record did.\n\nBefore finishing each checkpoint, print one real event of each type your tool can emit\nand inspect it: for each, ask \"could a reader reconstruct exactly what happened, on what,\nfrom this line alone?\" If not, add fields.\n\n## Verify by running\n\n- Run every example command in the spec verbatim, then once more with a perturbation\n  (option order, path location, empty\u002Fnull value, quoted vs bare value).\n- Trigger every error bullet on purpose and check message, stream, and exit code.\n- Hand-craft an input that a *different* reasonable implementer might produce, and make\n  sure it is accepted.\n\n## Do not\n\n- Do not stop to ask about an ambiguity; the run is non-interactive. Implement both.\n- Do not reject inputs the spec does not explicitly forbid.\n- Do not wrap the command entry point in a broad exception handler that turns runtime\n  failures into usage messages. Usage errors come from the argument parser only; all other\n  failures print `Error: \u003Creason>` to stderr and exit non-zero, without a traceback.\n- Do not silently drop a guaranteed property because a fast path cannot preserve it; use\n  the thorough path or fail loudly.\n",{"name":5,"description":7},"main","90c4e234b13d749b2f69ddcb1c759e5f667f6413","skills\u002Fsonnet-dbm\u002Fround1\u002Fs1b-union-echo","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo","https:\u002F\u002Fgithub.com\u002Fjemdiggity","2026-11-01 06:04:44",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add jemdiggity\u002Fkojo --skill cli-software",{"tool":36,"command":37},"bunx","bunx skills add jemdiggity\u002Fkojo --skill cli-software",{"tool":39,"command":40},"pnpm","pnpm dlx skills add jemdiggity\u002Fkojo --skill cli-software","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dbm\u002Fround1\u002Fs1b-union-echo\u002FSKILL.md",true,[],[45,52,57,62,67,72],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":19},"01M7DGWAMS2Z08G9S6KYEBM4YG","service-spec","Invoke before reading any code, for any task whose prompt is a multi-part spec for a service, API or CLI built up over successive parts (part 1, part 2, ... each adding or changing behavior). Apply its rules while reading the spec literally and while choosing behavior where the spec is silent.","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dcs\u002Fround3\u002Fd3e-accept\u002FSKILL.md",[],[],{"skillNo":53,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7DGW5T9M4EXVHNTNW1NY6MR","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dcs\u002Fround3\u002Fd3d-exact-words\u002FSKILL.md",[],[],{"skillNo":58,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7DGW1S560QM0M72BSYP42XB","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dcs\u002Fround3\u002Fd3c-omit\u002FSKILL.md",[],[],{"skillNo":63,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7DGVXQS07PEJQBS7VJC9B7R","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dcs\u002Fround3\u002Fd3b-inherit\u002FSKILL.md",[],[],{"skillNo":68,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DGVSEXFX35NZPSPBN9833Q","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dcs\u002Fround3\u002Fd3a-gate-lean\u002FSKILL.md",[],[],{"skillNo":73,"name":47,"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},"01M7DGVNNTDB3EGQHJXTNM986H","Use for any task whose prompt is a multi-part spec for a service, API, or CLI built up over successive parts (part 1, part 2, ... each adding or changing behavior). Guides literal reading of the spec and the choices to make where it is silent.","https:\u002F\u002Fgithub.com\u002Fjemdiggity\u002Fkojo\u002Fblob\u002Fmain\u002Fskills\u002Fsonnet-dcs\u002Fround2\u002Fd2e-lean\u002FSKILL.md",[],[]]