[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DEG2EF8MVTCD5HWR92HN6B":3,"skill-same:01M6DEG2EF8MVTCD5HWR92HN6B":63},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6DEG2EF8MVTCD5HWR92HN6B","mise",null,"Use when managing dev tool and language runtime versions with mise (mise-en-place) — the asdf\u002Fnvm\u002Fpyenv\u002Frbenv replacement: pinning global vs per-project versions via mise.toml or .tool-versions, per-directory environment variables, the task runner, installing non-language CLIs (npm\u002Fcargo\u002Fpipx\u002Fubi\u002Faqua\u002Fgo backends), or setting up mise on Windows PowerShell (shims vs activate, mise trust).","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\u002Fskills\u002Fmise\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"en","cargo","aqua","toml","runtime","project","runner","task","activate","trust","directory","up","use","environment","tool","asdf","powershell","dev","windows","2026-11-10 10:12:30",false,"---\nname: mise\ndescription: \"Use when managing dev tool and language runtime versions with mise (mise-en-place) — the asdf\u002Fnvm\u002Fpyenv\u002Frbenv replacement: pinning global vs per-project versions via mise.toml or .tool-versions, per-directory environment variables, the task runner, installing non-language CLIs (npm\u002Fcargo\u002Fpipx\u002Fubi\u002Faqua\u002Fgo backends), or setting up mise on Windows PowerShell (shims vs activate, mise trust).\"\n---\n\n# mise (mise-en-place)\n\n## Overview\n\nmise is **three tools in one**: a polyglot **version manager** (asdf\u002Fnvm\u002Fpyenv\u002Frbenv replacement), a per-directory **environment-variable** manager (direnv replacement), and a **task runner** (make\u002Fjust replacement). Core mental model: **mise owns the tools you hand it and ignores the rest** — it installs its own managed copies under its data dir and prepends them to `PATH`; tools you don't declare keep resolving from the normal `PATH`.\n\n## When to Use\n\n- Pin or switch runtime\u002FCLI versions per project or globally (`node`, `python`, `go`, `rust`, `terraform`, `jq`, `ripgrep`, …).\n- Replace a pile of `nvm`\u002F`pyenv`\u002F`asdf`\u002F`scoop`-pinned tools with one config.\n- Load per-directory env vars or `.env` files automatically.\n- Run repeatable project tasks (`mise run build`).\n- Install release-only binaries from GitHub\u002Fregistries (`ubi:`, `aqua:`, `cargo:`, `npm:`, `pipx:`, `go:`).\n\n**Not for:** Python app dependency isolation (use a real venv \u002F `uv` \u002F `poetry`; mise manages the *python interpreter version*, not your project packages). System OS packages (use the OS package manager).\n\n## Quick Reference\n\n| Goal | Command |\n|---|---|\n| Install + pin in **current dir** | `mise use node@22` (writes nearest `mise.toml`) |\n| Install + pin **globally** | `mise use -g node@22` (writes `~\u002F.config\u002Fmise\u002Fconfig.toml`) |\n| Remove a pin | `mise unuse node` \u002F `mise unuse -g node` |\n| Install everything from config | `mise install` |\n| List installed \u002F active | `mise ls` |\n| List installable versions | `mise ls-remote node` |\n| Where is the active binary | `mise which node` \u002F `mise where node` |\n| One-off with a version | `mise exec node@20 -- node script.js` |\n| Session-only version | `mise shell node@20` |\n| Show \u002F upgrade outdated | `mise outdated` \u002F `mise upgrade` |\n| Run a task | `mise run \u003Ctask>` (alias `mise r`) |\n| Rebuild shims after install | `mise reshim` |\n| Update mise itself | `mise self-update` |\n\nRun `mise \u003Ccmd> --help` for flags rather than memorizing them.\n\n## Tool Versions: Global vs Local (the precedence rule)\n\nTwo \"global\" senses, two answers:\n\n1. **Global default versions — fully supported.** `mise use -g \u003Ctool>@\u003Cver>` writes `~\u002F.config\u002Fmise\u002Fconfig.toml`, which applies in *every* directory. Per-directory config (`mise.toml` \u002F `.mise.toml` \u002F `.tool-versions`) **overrides** global when present (nearest config wins; a parent dir's config can also apply — `mise use` may write a parent file, so check the path it reports).\n\n2. **Adopting tools already installed elsewhere (scoop, system Python) — partial, by design.** mise does **not** scan and absorb existing installs; it shadows them with its own managed copies. To make mise *defer to* an existing binary:\n   - **Don't declare it** — anything not in mise config keeps resolving from your normal `PATH` (scoop, system installer) untouched. This is the simplest \"leave my global tools alone.\"\n   - **`path:` runtime (reliable, all backends):** point mise at a specific binary, e.g. in `.tool-versions`: `shfmt path:.\u002Fbin\u002Fshfmt` or an absolute path.\n   - **`tool@system` (use with care):** e.g. `python@system` means \"use whatever's on `PATH`.\" This is **not a documented mise version scope** — only some legacy asdf-style plugins honor it. Prefer `path:` for reliable, cross-backend behavior.\n\nGlobal config (`~\u002F.config\u002Fmise\u002Fconfig.toml`) example:\n\n```toml\n[tools]\nnode = 'lts'\npython = ['3.11', '3.12']   # multiple versions; first is default\n\n[settings]\nidiomatic_version_file_enable_tools = ['node']   # read .nvmrc etc.\n```\n\n## Config File: mise.toml (env + tasks)\n\n```toml\n[tools]\nnode = '22'\n\n[env]\nDATABASE_URL = 'postgres:\u002F\u002Flocalhost\u002Fdev'\n_.file = '.env'             # also load a dotenv file\n\n[tasks.build]\nrun = 'npm run build'\n\n[tasks.test]\ndepends = ['build']\nrun = 'npm test'\n```\n\n`mise.toml` (committed) vs `mise.local.toml` (gitignored, machine overrides). `.tool-versions` (asdf format) is also read for tool versions only. Run tasks with `mise run test` (auto-runs its `build` dependency first); list them with `mise tasks`. **mise won't load `[env]` or `[tasks]` until you `mise trust` the directory** (see below).\n\n## Backends (install from beyond languages)\n\n| Prefix | Source | Example |\n|---|---|---|\n| (core) | built-in languages | `mise use node@22` |\n| `ubi:` | any GitHub release binary | `mise use ubi:BurntSushi\u002Fripgrep` |\n| `aqua:` | aqua registry | `mise use aqua:cli\u002Fcli` |\n| `cargo:` | crates.io (builds) | `mise use cargo:ripgrep` |\n| `npm:` | npm | `mise use npm:prettier@3` |\n| `pipx:` | PyPI apps | `mise use pipx:black` |\n| `go:` | Go modules | `mise use go:github.com\u002F...` |\n\n## Activation: shims vs activate\n\n- **Shims (default, works everywhere incl. non-interactive shells & editors):** mise's shims dir is on `PATH`; shim exes resolve the right version on call. No shell hook needed. Check with `mise doctor` → `shims_on_path: yes`.\n- **`activate` (faster, enables `[env]`\u002Fauto-switching on `cd`):** add a shell hook. If `mise doctor` shows `shell: (unknown)`, activate is **not** set up — you're shims-only.\n\nPowerShell setup (add to `$PROFILE`):\n\n```powershell\n# one-time: create the profile if missing, then append the dynamic activation hook\nif (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force }\nAdd-Content $PROFILE 'mise activate pwsh | Out-String | Invoke-Expression'\n. $PROFILE   # reload current session\n```\n\nThe `mise activate pwsh | Out-String | Invoke-Expression` form re-runs on every shell start, so it always reflects the installed mise (verified working on pwsh 7). `Out-String | Invoke-Expression` is the PowerShell equivalent of bash's `eval \"$(...)\"`.\n\nbash\u002Fzsh: `echo 'eval \"$(mise activate bash)\"' >> ~\u002F.bashrc` (or `zsh`). After installs that add new binaries, run `mise reshim` if a new bin isn't found.\n\n## mise trust (security)\n\nmise will **not** load `[env]`\u002F`[tasks]` from a directory's config until you trust it (prevents a cloned repo from running arbitrary env\u002Ftasks). `mise trust` marks the current config trusted; `mise untrust` reverses it; `trusted_config_paths` in global settings pre-trusts a directory tree.\n\n## CI\n\n```yaml\n- uses: jdx\u002Fmise-action@v4   # installs tools from mise.toml\u002F.tool-versions, with caching\n- run: node -v\n```\n\n## Common Mistakes\n\n- **Expecting mise to manage app packages.** It manages the *interpreter\u002Ftool version*, not your project's pip\u002Fnpm deps.\n- **Editing the wrong config.** `mise use` writes the *nearest* `mise.toml`, which may be a parent dir. Use `-g` for global or `--path` for an explicit file; confirm the path it prints.\n- **Assuming `@system` always works.** It doesn't across all backends — use `path:` when you must reuse an existing binary.\n- **`[env]`\u002Ftasks \"not loading.\"** The dir isn't trusted yet → `mise trust`.\n- **New binary not found after install** → `mise reshim` (shims mode) or reopen the shell (activate mode).\n\n## References\n\n- Docs: https:\u002F\u002Fmise.jdx.dev (`\u002Fjdx\u002Fmise` on Context7) — configuration, dev-tools, env, tasks.\n- `mise doctor` for a full diagnostic of config files, backends, and activation state.\n","# mise (mise-en-place)\n\n## Overview\n\nmise is **three tools in one**: a polyglot **version manager** (asdf\u002Fnvm\u002Fpyenv\u002Frbenv replacement), a per-directory **environment-variable** manager (direnv replacement), and a **task runner** (make\u002Fjust replacement). Core mental model: **mise owns the tools you hand it and ignores the rest** — it installs its own managed copies under its data dir and prepends them to `PATH`; tools you don't declare keep resolving from the normal `PATH`.\n\n## When to Use\n\n- Pin or switch runtime\u002FCLI versions per project or globally (`node`, `python`, `go`, `rust`, `terraform`, `jq`, `ripgrep`, …).\n- Replace a pile of `nvm`\u002F`pyenv`\u002F`asdf`\u002F`scoop`-pinned tools with one config.\n- Load per-directory env vars or `.env` files automatically.\n- Run repeatable project tasks (`mise run build`).\n- Install release-only binaries from GitHub\u002Fregistries (`ubi:`, `aqua:`, `cargo:`, `npm:`, `pipx:`, `go:`).\n\n**Not for:** Python app dependency isolation (use a real venv \u002F `uv` \u002F `poetry`; mise manages the *python interpreter version*, not your project packages). System OS packages (use the OS package manager).\n\n## Quick Reference\n\n| Goal | Command |\n|---|---|\n| Install + pin in **current dir** | `mise use node@22` (writes nearest `mise.toml`) |\n| Install + pin **globally** | `mise use -g node@22` (writes `~\u002F.config\u002Fmise\u002Fconfig.toml`) |\n| Remove a pin | `mise unuse node` \u002F `mise unuse -g node` |\n| Install everything from config | `mise install` |\n| List installed \u002F active | `mise ls` |\n| List installable versions | `mise ls-remote node` |\n| Where is the active binary | `mise which node` \u002F `mise where node` |\n| One-off with a version | `mise exec node@20 -- node script.js` |\n| Session-only version | `mise shell node@20` |\n| Show \u002F upgrade outdated | `mise outdated` \u002F `mise upgrade` |\n| Run a task | `mise run \u003Ctask>` (alias `mise r`) |\n| Rebuild shims after install | `mise reshim` |\n| Update mise itself | `mise self-update` |\n\nRun `mise \u003Ccmd> --help` for flags rather than memorizing them.\n\n## Tool Versions: Global vs Local (the precedence rule)\n\nTwo \"global\" senses, two answers:\n\n1. **Global default versions — fully supported.** `mise use -g \u003Ctool>@\u003Cver>` writes `~\u002F.config\u002Fmise\u002Fconfig.toml`, which applies in *every* directory. Per-directory config (`mise.toml` \u002F `.mise.toml` \u002F `.tool-versions`) **overrides** global when present (nearest config wins; a parent dir's config can also apply — `mise use` may write a parent file, so check the path it reports).\n\n2. **Adopting tools already installed elsewhere (scoop, system Python) — partial, by design.** mise does **not** scan and absorb existing installs; it shadows them with its own managed copies. To make mise *defer to* an existing binary:\n   - **Don't declare it** — anything not in mise config keeps resolving from your normal `PATH` (scoop, system installer) untouched. This is the simplest \"leave my global tools alone.\"\n   - **`path:` runtime (reliable, all backends):** point mise at a specific binary, e.g. in `.tool-versions`: `shfmt path:.\u002Fbin\u002Fshfmt` or an absolute path.\n   - **`tool@system` (use with care):** e.g. `python@system` means \"use whatever's on `PATH`.\" This is **not a documented mise version scope** — only some legacy asdf-style plugins honor it. Prefer `path:` for reliable, cross-backend behavior.\n\nGlobal config (`~\u002F.config\u002Fmise\u002Fconfig.toml`) example:\n\n```toml\n[tools]\nnode = 'lts'\npython = ['3.11', '3.12']   # multiple versions; first is default\n\n[settings]\nidiomatic_version_file_enable_tools = ['node']   # read .nvmrc etc.\n```\n\n## Config File: mise.toml (env + tasks)\n\n```toml\n[tools]\nnode = '22'\n\n[env]\nDATABASE_URL = 'postgres:\u002F\u002Flocalhost\u002Fdev'\n_.file = '.env'             # also load a dotenv file\n\n[tasks.build]\nrun = 'npm run build'\n\n[tasks.test]\ndepends = ['build']\nrun = 'npm test'\n```\n\n`mise.toml` (committed) vs `mise.local.toml` (gitignored, machine overrides). `.tool-versions` (asdf format) is also read for tool versions only. Run tasks with `mise run test` (auto-runs its `build` dependency first); list them with `mise tasks`. **mise won't load `[env]` or `[tasks]` until you `mise trust` the directory** (see below).\n\n## Backends (install from beyond languages)\n\n| Prefix | Source | Example |\n|---|---|---|\n| (core) | built-in languages | `mise use node@22` |\n| `ubi:` | any GitHub release binary | `mise use ubi:BurntSushi\u002Fripgrep` |\n| `aqua:` | aqua registry | `mise use aqua:cli\u002Fcli` |\n| `cargo:` | crates.io (builds) | `mise use cargo:ripgrep` |\n| `npm:` | npm | `mise use npm:prettier@3` |\n| `pipx:` | PyPI apps | `mise use pipx:black` |\n| `go:` | Go modules | `mise use go:github.com\u002F...` |\n\n## Activation: shims vs activate\n\n- **Shims (default, works everywhere incl. non-interactive shells & editors):** mise's shims dir is on `PATH`; shim exes resolve the right version on call. No shell hook needed. Check with `mise doctor` → `shims_on_path: yes`.\n- **`activate` (faster, enables `[env]`\u002Fauto-switching on `cd`):** add a shell hook. If `mise doctor` shows `shell: (unknown)`, activate is **not** set up — you're shims-only.\n\nPowerShell setup (add to `$PROFILE`):\n\n```powershell\n# one-time: create the profile if missing, then append the dynamic activation hook\nif (-not (Test-Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force }\nAdd-Content $PROFILE 'mise activate pwsh | Out-String | Invoke-Expression'\n. $PROFILE   # reload current session\n```\n\nThe `mise activate pwsh | Out-String | Invoke-Expression` form re-runs on every shell start, so it always reflects the installed mise (verified working on pwsh 7). `Out-String | Invoke-Expression` is the PowerShell equivalent of bash's `eval \"$(...)\"`.\n\nbash\u002Fzsh: `echo 'eval \"$(mise activate bash)\"' >> ~\u002F.bashrc` (or `zsh`). After installs that add new binaries, run `mise reshim` if a new bin isn't found.\n\n## mise trust (security)\n\nmise will **not** load `[env]`\u002F`[tasks]` from a directory's config until you trust it (prevents a cloned repo from running arbitrary env\u002Ftasks). `mise trust` marks the current config trusted; `mise untrust` reverses it; `trusted_config_paths` in global settings pre-trusts a directory tree.\n\n## CI\n\n```yaml\n- uses: jdx\u002Fmise-action@v4   # installs tools from mise.toml\u002F.tool-versions, with caching\n- run: node -v\n```\n\n## Common Mistakes\n\n- **Expecting mise to manage app packages.** It manages the *interpreter\u002Ftool version*, not your project's pip\u002Fnpm deps.\n- **Editing the wrong config.** `mise use` writes the *nearest* `mise.toml`, which may be a parent dir. Use `-g` for global or `--path` for an explicit file; confirm the path it prints.\n- **Assuming `@system` always works.** It doesn't across all backends — use `path:` when you must reuse an existing binary.\n- **`[env]`\u002Ftasks \"not loading.\"** The dir isn't trusted yet → `mise trust`.\n- **New binary not found after install** → `mise reshim` (shims mode) or reopen the shell (activate mode).\n\n## References\n\n- Docs: https:\u002F\u002Fmise.jdx.dev (`\u002Fjdx\u002Fmise` on Context7) — configuration, dev-tools, env, tasks.\n- `mise doctor` for a full diagnostic of config files, backends, and activation state.\n",{"name":5,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5","skills\u002Fmise","https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain","https:\u002F\u002Fgithub.com\u002FPrekzursil","2026-11-02 14:30:57",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Prekzursil\u002Fagent-skills-toolchain --skill mise",{"tool":55,"command":56},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill mise",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill mise","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002Fskills\u002Fmise\u002FSKILL.md",true,[],[64,84,113,140,153,169],{"skillNo":65,"name":66,"nameZh":6,"description":67,"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":38},"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",[],[71,72,73,74,75,26,76,77,78,31,79,80,81,82,83],"clarify requirements","clarify","requirements","risk","options","prompts","goal","scanning","context","repo","injection","execution","file",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":95,"publishedAt":38},"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",[90],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[96,97,98,99,100,101,33,102,103,104,105,106,107,37,31,108,109,110,111,112],"openmm md","how","decision","pick","linux","analyze","stack","open","NVIDIA","gpu","license","workflow","free","molecular dynamics","local","do","MCP",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":125,"publishedAt":38},"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",[119,122],{"categoryNo":120,"categoryName":121,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":123,"categoryName":124,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000008","测试与质量",[126,127,128,129,130,131,132,133,134,135,97,136,137,138,139],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":38},"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",[],[142,147,148,24,149,150,151,152],"setup","report","installation","project setup","issues","state",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":38},"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",[159],{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[155,161,26,162,163,164,31,165,166,167,168],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":170,"name":147,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":38},"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",[],[147,24,110,175,150,176],"files","interactive"]