[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DB538KC4BHWTXX2YA8G3DJ":3,"skill-same:01M6DB538KC4BHWTXX2YA8G3DJ":72},{"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":28,"publishedAt":47,"linkOnly":48,"markdownContent":49,"markdownBody":50,"frontMatter":51,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6DB538KC4BHWTXX2YA8G3DJ","cli-anything",null,"Use when you want to make a command-line tool reliably callable and parseable by an AI agent — introspect its --help, define a structured-output (--json) contract and a stable error contract, then generate a SKILL.md wrapper with verified examples. Triggers on \"wrap this CLI\", \"make X agent-usable\", \"generate a skill for this command\", \"turn a tool into an agent skill\".","Prekzursil\u002Fagent-skills-toolchain","Prekzursil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F54636077?v=4","01M6DACZ1PCQHD99SCR1YXG28B","Andrei Mihai Visalon","01M6DACZ670WZF535V3WYYSS4Z",0,"MIT","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcli-anything\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46],"CLI Anything","cli","Wrapper","triggers","define","contract","agent skill","structured","structured-output","wrap","use","command","json","tool","examples","help","generate","ai agent","2026-11-10 10:12:30",false,"---\nname: cli-anything\ndescription: Use when you want to make a command-line tool reliably callable and parseable by an AI agent — introspect its --help, define a structured-output (--json) contract and a stable error contract, then generate a SKILL.md wrapper with verified examples. Triggers on \"wrap this CLI\", \"make X agent-usable\", \"generate a skill for this command\", \"turn a tool into an agent skill\".\n---\n\n\u003C!-- Source: cherry-picked from https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco (skills\u002Fcli-anything) on 27.08.2026 per grill decision G-11\u002F11B. Adapted to house format. -->\n\n# cli-anything: wrap any CLI into an agent skill\n\nTurn any command-line tool into something an AI agent can call reliably and parse. The output is a thin, well-documented wrapper contract — never a reimplementation of the tool. Use the real tool; document how to drive it.\n\n## When to use\n\nYou have a CLI (your own, or a third-party binary) and you want an agent to invoke it predictably, read structured results, and recover from errors. This skill produces a `SKILL.md` wrapper that encodes that contract. New wrappers go in the vault (`C:\\Users\\Prekzursil\\.agents\\skills\\\u003Ctool-name>\\SKILL.md`), followed by `sync_shared_state.ps1`.\n\n## Step 1 — Introspect the CLI (do not guess)\n\nEnumerate the real surface before writing anything:\n\n- Run `\u003Ctool> --help` and `\u003Ctool> \u003Csubcommand> --help` for each subcommand.\n- Capture: subcommands, flags (required vs optional), positional args, exit codes, and the output format (human text vs structured).\n- If `--help` is thin, read the source or man page. Every claim in the wrapper must trace to observed behavior.\n\n## Step 2 — Define the output contract\n\n- Prefer a `--json` machine-readable mode for every command an agent will call. Document the exact JSON keys the agent should read (one shape per command).\n- If the tool has no JSON mode, say so honestly and document what to parse from stdout (and which token carries the answer). Do not pretend output is structured when it is not.\n- Human output stays the default; structured output is the agent path.\n\n## Step 3 — Define the error contract\n\n- Map exit codes to meaning (0 = success; document each non-zero class).\n- On failure, surface a parseable signal (`{\"error\": \"...\", \"code\": N}` if the tool supports it, otherwise the captured stderr) — never a bare stack trace.\n- Fail loud and parseable. Never half-succeed silently.\n\n## Step 4 — Write the SKILL.md wrapper\n\nStandard structure so an agent can discover and drive the tool:\n\n- Frontmatter: `name`, `description` (house format: starts with \"Use when ...\" and includes natural trigger phrases).\n- `Commands` — each command: purpose, exact invocation, args, and the result shape it returns.\n- `Examples` — 2-4 real invocations with expected output.\n- `Errors` — the exit-code\u002Ferror contract from Step 3.\n- `Notes` — auth, side effects, idempotency, network egress, prerequisites.\n\n## Step 5 — Verify against reality\n\n- Run each documented command once; confirm the real output matches what the wrapper claims.\n- Confirm any `--json` shape parses.\n- A wrapper that drifts from reality is worse than none — re-introspect and fix.\n\n## Principles\n\n- Use the real tool; never reimplement its logic in the wrapper.\n- Deterministic and structured beats clever.\n- The wrapper is a contract: introspect, structure, document, verify.\n","\u003C!-- Source: cherry-picked from https:\u002F\u002Fgithub.com\u002Fcoco-research\u002Fcoco (skills\u002Fcli-anything) on 27.08.2026 per grill decision G-11\u002F11B. Adapted to house format. -->\n\n# cli-anything: wrap any CLI into an agent skill\n\nTurn any command-line tool into something an AI agent can call reliably and parse. The output is a thin, well-documented wrapper contract — never a reimplementation of the tool. Use the real tool; document how to drive it.\n\n## When to use\n\nYou have a CLI (your own, or a third-party binary) and you want an agent to invoke it predictably, read structured results, and recover from errors. This skill produces a `SKILL.md` wrapper that encodes that contract. New wrappers go in the vault (`C:\\Users\\Prekzursil\\.agents\\skills\\\u003Ctool-name>\\SKILL.md`), followed by `sync_shared_state.ps1`.\n\n## Step 1 — Introspect the CLI (do not guess)\n\nEnumerate the real surface before writing anything:\n\n- Run `\u003Ctool> --help` and `\u003Ctool> \u003Csubcommand> --help` for each subcommand.\n- Capture: subcommands, flags (required vs optional), positional args, exit codes, and the output format (human text vs structured).\n- If `--help` is thin, read the source or man page. Every claim in the wrapper must trace to observed behavior.\n\n## Step 2 — Define the output contract\n\n- Prefer a `--json` machine-readable mode for every command an agent will call. Document the exact JSON keys the agent should read (one shape per command).\n- If the tool has no JSON mode, say so honestly and document what to parse from stdout (and which token carries the answer). Do not pretend output is structured when it is not.\n- Human output stays the default; structured output is the agent path.\n\n## Step 3 — Define the error contract\n\n- Map exit codes to meaning (0 = success; document each non-zero class).\n- On failure, surface a parseable signal (`{\"error\": \"...\", \"code\": N}` if the tool supports it, otherwise the captured stderr) — never a bare stack trace.\n- Fail loud and parseable. Never half-succeed silently.\n\n## Step 4 — Write the SKILL.md wrapper\n\nStandard structure so an agent can discover and drive the tool:\n\n- Frontmatter: `name`, `description` (house format: starts with \"Use when ...\" and includes natural trigger phrases).\n- `Commands` — each command: purpose, exact invocation, args, and the result shape it returns.\n- `Examples` — 2-4 real invocations with expected output.\n- `Errors` — the exit-code\u002Ferror contract from Step 3.\n- `Notes` — auth, side effects, idempotency, network egress, prerequisites.\n\n## Step 5 — Verify against reality\n\n- Run each documented command once; confirm the real output matches what the wrapper claims.\n- Confirm any `--json` shape parses.\n- A wrapper that drifts from reality is worse than none — re-introspect and fix.\n\n## Principles\n\n- Use the real tool; never reimplement its logic in the wrapper.\n- Deterministic and structured beats clever.\n- The wrapper is a contract: introspect, structure, document, verify.\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fcli-anything","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill cli-anything",{"tool":64,"command":65},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill cli-anything",{"tool":67,"command":68},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill cli-anything","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fcli-anything\u002FSKILL.md",true,[],[73,94,120,147,161,177],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":47},"01M6DF7D7478R55P46REYH4QAC","clarify-requirements","Resolve genuine pre-execution ambiguity by scanning repo context, generating 1-6 grounded options, and asking 1-3 focused questions via AskUserQuestion. NOT for mid-task use (injection risk); NOT when the goal is already unambiguous; use to disambiguate vague prompts before any file edits.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fworkspace-hooks\u002Fskills\u002Fclarify-requirements\u002FSKILL.md",[],[80,81,82,83,84,85,86,87,88,39,89,90,91,92,93],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":101,"publishedAt":47},"01M6DF79CA4BHJS66J8EZDBPWJ","openmm-md","Run FREE, open-source, Windows-native GPU molecular dynamics via the openmm-md MCP (OpenMM + CUDA on the local NVIDIA GPU). Use for protein \u002F protein-ligand MD when you want a free stack or are on Windows without a Schrodinger license. Covers the full workflow (prepare, solvate, minimize, equilibrate, production, analyze, mmgbsa) AND an honest decision guide vs Schrodinger Desmond, including how to run Desmond legitimately on Linux or a cloud GPU with a real license. This is a deliberately LESSER free alternative and does NOT replace the schrodinger MCP tools. Do NOT use it to pick a free tool when a validated FEP+, WaterMap, IFD-MD, or Prime MM-GBSA result is actually required.","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Fmcp\u002Fopenmm-md-mcp\u002Fskill\u002Fopenmm-md\u002FSKILL.md",[100],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[102,103,104,105,106,107,42,108,109,110,111,112,113,114,39,115,116,117,118,119],"openmm md","how","decision","pick","linux","analyze","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":132,"publishedAt":47},"01M6DF76C1MG85VEWP8VZCBNMN","visual-review","Take screenshots of web pages and UI using Playwright for visual review and iteration","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fvisual-review\u002FSKILL.md",[126,129],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":130,"categoryName":131,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[133,134,135,136,137,138,139,140,141,142,103,143,144,145,146],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":47},"01M6DF73AQVCBZKEN0YXEX9FXP","status","Diagnostic status report — shows metaswarm installation state, project setup, and potential issues","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstatus\u002FSKILL.md",[],[149,154,155,156,157,158,159,160],"setup","report","project","installation","project setup","issues","state",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":168,"publishedAt":47},"01M6DF6X6C2XB0P6GX76P7TTYV","start","Use when starting work on any task, when the user mentions metaswarm, or when the user wants to begin tracked development work","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fstart\u002FSKILL.md",[167],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[163,169,85,170,171,172,39,173,174,175,176],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":178,"name":154,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":47},"01M6DF6QMJ9AJKFKHHKRT005PQ","Interactive project setup — detects your project, configures metaswarm, writes project-local files","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Ftools\u002Feditor\u002Fmetaswarm\u002Fskills\u002Fsetup\u002FSKILL.md",[],[154,156,117,183,158,184],"files","interactive"]