[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DBPAS8QPYP149NT9FWRX5N":3,"skill-same:01M6DBPAS8QPYP149NT9FWRX5N":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":23,"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},"01M6DBPAS8QPYP149NT9FWRX5N","plankton-code-quality",null,"Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.","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\u002Fplankton-code-quality\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"code quality","code","plankton code quality","quality","plankton","file","write","edit","auto","hooks","enforcement","community","time","formatting","2026-11-10 10:12:30",false,"---\nname: plankton-code-quality\ndescription: \"Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks.\"\norigin: community\n---\n\n# Plankton Code Quality Skill\n\nIntegration reference for Plankton (credit: @alxfazio), a write-time code quality enforcement system for Claude Code. Plankton runs formatters and linters on every file edit via PostToolUse hooks, then spawns Claude subprocesses to fix violations the agent didn't catch.\n\n## When to Use\n\n- You want automatic formatting and linting on every file edit (not just at commit time)\n- You need defense against agents modifying linter configs to pass instead of fixing code\n- You want tiered model routing for fixes (Haiku for simple style, Sonnet for logic, Opus for types)\n- You work with multiple languages (Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile)\n\n## How It Works\n\n### Three-Phase Architecture\n\nEvery time Claude Code edits or writes a file, Plankton's `multi_linter.sh` PostToolUse hook runs:\n\n```\nPhase 1: Auto-Format (Silent)\n├─ Runs formatters (ruff format, biome, shfmt, taplo, markdownlint)\n├─ Fixes 40-50% of issues silently\n└─ No output to main agent\n\nPhase 2: Collect Violations (JSON)\n├─ Runs linters and collects unfixable violations\n├─ Returns structured JSON: {line, column, code, message, linter}\n└─ Still no output to main agent\n\nPhase 3: Delegate + Verify\n├─ Spawns claude -p subprocess with violations JSON\n├─ Routes to model tier based on violation complexity:\n│   ├─ Haiku: formatting, imports, style (E\u002FW\u002FF codes) — 120s timeout\n│   ├─ Sonnet: complexity, refactoring (C901, PLR codes) — 300s timeout\n│   └─ Opus: type system, deep reasoning (unresolved-attribute) — 600s timeout\n├─ Re-runs Phase 1+2 to verify fixes\n└─ Exit 0 if clean, Exit 2 if violations remain (reported to main agent)\n```\n\n### What the Main Agent Sees\n\n| Scenario | Agent sees | Hook exit |\n|----------|-----------|-----------|\n| No violations | Nothing | 0 |\n| All fixed by subprocess | Nothing | 0 |\n| Violations remain after subprocess | `[hook] N violation(s) remain` | 2 |\n| Advisory (duplicates, old tooling) | `[hook:advisory] ...` | 0 |\n\nThe main agent only sees issues the subprocess couldn't fix. Most quality problems are resolved transparently.\n\n### Config Protection (Defense Against Rule-Gaming)\n\nLLMs will modify `.ruff.toml` or `biome.json` to disable rules rather than fix code. Plankton blocks this with three layers:\n\n1. **PreToolUse hook** — `protect_linter_configs.sh` blocks edits to all linter configs before they happen\n2. **Stop hook** — `stop_config_guardian.sh` detects config changes via `git diff` at session end\n3. **Protected files list** — `.ruff.toml`, `biome.json`, `.shellcheckrc`, `.yamllint`, `.hadolint.yaml`, and more\n\n### Package Manager Enforcement\n\nA PreToolUse hook on Bash blocks legacy package managers:\n- `pip`, `pip3`, `poetry`, `pipenv` → Blocked (use `uv`)\n- `npm`, `yarn`, `pnpm` → Blocked (use `bun`)\n- Allowed exceptions: `npm audit`, `npm view`, `npm publish`\n\n## Setup\n\n### Quick Start\n\n```bash\n# Clone Plankton into your project (or a shared location)\n# Note: Plankton is by @alxfazio\ngit clone https:\u002F\u002Fgithub.com\u002Falexfazio\u002Fplankton.git\ncd plankton\n\n# Install core dependencies\nbrew install jaq ruff uv\n\n# Install Python linters\nuv sync --all-extras\n\n# Start Claude Code — hooks activate automatically\nclaude\n```\n\nNo install command, no plugin config. The hooks in `.claude\u002Fsettings.json` are picked up automatically when you run Claude Code in the Plankton directory.\n\n### Per-Project Integration\n\nTo use Plankton hooks in your own project:\n\n1. Copy `.claude\u002Fhooks\u002F` directory to your project\n2. Copy `.claude\u002Fsettings.json` hook configuration\n3. Copy linter config files (`.ruff.toml`, `biome.json`, etc.)\n4. Install the linters for your languages\n\n### Language-Specific Dependencies\n\n| Language | Required | Optional |\n|----------|----------|----------|\n| Python | `ruff`, `uv` | `ty` (types), `vulture` (dead code), `bandit` (security) |\n| TypeScript\u002FJS | `biome` | `oxlint`, `semgrep`, `knip` (dead exports) |\n| Shell | `shellcheck`, `shfmt` | — |\n| YAML | `yamllint` | — |\n| Markdown | `markdownlint-cli2` | — |\n| Dockerfile | `hadolint` (>= 2.12.0) | — |\n| TOML | `taplo` | — |\n| JSON | `jaq` | — |\n\n## Pairing with ECC\n\n### Complementary, Not Overlapping\n\n| Concern | ECC | Plankton |\n|---------|-----|----------|\n| Code quality enforcement | PostToolUse hooks (Prettier, tsc) | PostToolUse hooks (20+ linters + subprocess fixes) |\n| Security scanning | AgentShield, security-reviewer agent | Bandit (Python), Semgrep (TypeScript) |\n| Config protection | — | PreToolUse blocks + Stop hook detection |\n| Package manager | Detection + setup | Enforcement (blocks legacy PMs) |\n| CI integration | — | Pre-commit hooks for git |\n| Model routing | Manual (`\u002Fmodel opus`) | Automatic (violation complexity → tier) |\n\n### Recommended Combination\n\n1. Install ECC as your plugin (agents, skills, commands, rules)\n2. Add Plankton hooks for write-time quality enforcement\n3. Use AgentShield for security audits\n4. Use ECC's verification-loop as a final gate before PRs\n\n### Avoiding Hook Conflicts\n\nIf running both ECC and Plankton hooks:\n- ECC's Prettier hook and Plankton's biome formatter may conflict on JS\u002FTS files\n- Resolution: disable ECC's Prettier PostToolUse hook when using Plankton (Plankton's biome is more comprehensive)\n- Both can coexist on different file types (ECC handles what Plankton doesn't cover)\n\n## Configuration Reference\n\nPlankton's `.claude\u002Fhooks\u002Fconfig.json` controls all behavior:\n\n```json\n{\n  \"languages\": {\n    \"python\": true,\n    \"shell\": true,\n    \"yaml\": true,\n    \"json\": true,\n    \"toml\": true,\n    \"dockerfile\": true,\n    \"markdown\": true,\n    \"typescript\": {\n      \"enabled\": true,\n      \"js_runtime\": \"auto\",\n      \"biome_nursery\": \"warn\",\n      \"semgrep\": true\n    }\n  },\n  \"phases\": {\n    \"auto_format\": true,\n    \"subprocess_delegation\": true\n  },\n  \"subprocess\": {\n    \"tiers\": {\n      \"haiku\":  { \"timeout\": 120, \"max_turns\": 10 },\n      \"sonnet\": { \"timeout\": 300, \"max_turns\": 10 },\n      \"opus\":   { \"timeout\": 600, \"max_turns\": 15 }\n    },\n    \"volume_threshold\": 5\n  }\n}\n```\n\n**Key settings:**\n- Disable languages you don't use to speed up hooks\n- `volume_threshold` — violations > this count auto-escalate to a higher model tier\n- `subprocess_delegation: false` — skip Phase 3 entirely (just report violations)\n\n## Environment Overrides\n\n| Variable | Purpose |\n|----------|---------|\n| `HOOK_SKIP_SUBPROCESS=1` | Skip Phase 3, report violations directly |\n| `HOOK_SUBPROCESS_TIMEOUT=N` | Override tier timeout |\n| `HOOK_DEBUG_MODEL=1` | Log model selection decisions |\n| `HOOK_SKIP_PM=1` | Bypass package manager enforcement |\n\n## References\n\n- Plankton (credit: @alxfazio)\n- Plankton REFERENCE.md — Full architecture documentation (credit: @alxfazio)\n- Plankton SETUP.md — Detailed installation guide (credit: @alxfazio)\n\n## ECC v1.8 Additions\n\n### Copyable Hook Profile\n\nSet strict quality behavior:\n\n```bash\nexport ECC_HOOK_PROFILE=strict\nexport ECC_QUALITY_GATE_FIX=true\nexport ECC_QUALITY_GATE_STRICT=true\n```\n\n### Language Gate Table\n\n- TypeScript\u002FJavaScript: Biome preferred, Prettier fallback\n- Python: Ruff format\u002Fcheck\n- Go: gofmt\n\n### Config Tamper Guard\n\nDuring quality enforcement, flag changes to config files in same iteration:\n\n- `biome.json`, `.eslintrc*`, `prettier.config*`, `tsconfig.json`, `pyproject.toml`\n\nIf config is changed to suppress violations, require explicit review before merge.\n\n### CI Integration Pattern\n\nUse the same commands in CI as local hooks:\n\n1. run formatter checks\n2. run lint\u002Ftype checks\n3. fail fast on strict mode\n4. publish remediation summary\n\n### Health Metrics\n\nTrack:\n- edits flagged by gates\n- average remediation time\n- repeat violations by category\n- merge blocks due to gate failures\n","# Plankton Code Quality Skill\n\nIntegration reference for Plankton (credit: @alxfazio), a write-time code quality enforcement system for Claude Code. Plankton runs formatters and linters on every file edit via PostToolUse hooks, then spawns Claude subprocesses to fix violations the agent didn't catch.\n\n## When to Use\n\n- You want automatic formatting and linting on every file edit (not just at commit time)\n- You need defense against agents modifying linter configs to pass instead of fixing code\n- You want tiered model routing for fixes (Haiku for simple style, Sonnet for logic, Opus for types)\n- You work with multiple languages (Python, TypeScript, Shell, YAML, JSON, TOML, Markdown, Dockerfile)\n\n## How It Works\n\n### Three-Phase Architecture\n\nEvery time Claude Code edits or writes a file, Plankton's `multi_linter.sh` PostToolUse hook runs:\n\n```\nPhase 1: Auto-Format (Silent)\n├─ Runs formatters (ruff format, biome, shfmt, taplo, markdownlint)\n├─ Fixes 40-50% of issues silently\n└─ No output to main agent\n\nPhase 2: Collect Violations (JSON)\n├─ Runs linters and collects unfixable violations\n├─ Returns structured JSON: {line, column, code, message, linter}\n└─ Still no output to main agent\n\nPhase 3: Delegate + Verify\n├─ Spawns claude -p subprocess with violations JSON\n├─ Routes to model tier based on violation complexity:\n│   ├─ Haiku: formatting, imports, style (E\u002FW\u002FF codes) — 120s timeout\n│   ├─ Sonnet: complexity, refactoring (C901, PLR codes) — 300s timeout\n│   └─ Opus: type system, deep reasoning (unresolved-attribute) — 600s timeout\n├─ Re-runs Phase 1+2 to verify fixes\n└─ Exit 0 if clean, Exit 2 if violations remain (reported to main agent)\n```\n\n### What the Main Agent Sees\n\n| Scenario | Agent sees | Hook exit |\n|----------|-----------|-----------|\n| No violations | Nothing | 0 |\n| All fixed by subprocess | Nothing | 0 |\n| Violations remain after subprocess | `[hook] N violation(s) remain` | 2 |\n| Advisory (duplicates, old tooling) | `[hook:advisory] ...` | 0 |\n\nThe main agent only sees issues the subprocess couldn't fix. Most quality problems are resolved transparently.\n\n### Config Protection (Defense Against Rule-Gaming)\n\nLLMs will modify `.ruff.toml` or `biome.json` to disable rules rather than fix code. Plankton blocks this with three layers:\n\n1. **PreToolUse hook** — `protect_linter_configs.sh` blocks edits to all linter configs before they happen\n2. **Stop hook** — `stop_config_guardian.sh` detects config changes via `git diff` at session end\n3. **Protected files list** — `.ruff.toml`, `biome.json`, `.shellcheckrc`, `.yamllint`, `.hadolint.yaml`, and more\n\n### Package Manager Enforcement\n\nA PreToolUse hook on Bash blocks legacy package managers:\n- `pip`, `pip3`, `poetry`, `pipenv` → Blocked (use `uv`)\n- `npm`, `yarn`, `pnpm` → Blocked (use `bun`)\n- Allowed exceptions: `npm audit`, `npm view`, `npm publish`\n\n## Setup\n\n### Quick Start\n\n```bash\n# Clone Plankton into your project (or a shared location)\n# Note: Plankton is by @alxfazio\ngit clone https:\u002F\u002Fgithub.com\u002Falexfazio\u002Fplankton.git\ncd plankton\n\n# Install core dependencies\nbrew install jaq ruff uv\n\n# Install Python linters\nuv sync --all-extras\n\n# Start Claude Code — hooks activate automatically\nclaude\n```\n\nNo install command, no plugin config. The hooks in `.claude\u002Fsettings.json` are picked up automatically when you run Claude Code in the Plankton directory.\n\n### Per-Project Integration\n\nTo use Plankton hooks in your own project:\n\n1. Copy `.claude\u002Fhooks\u002F` directory to your project\n2. Copy `.claude\u002Fsettings.json` hook configuration\n3. Copy linter config files (`.ruff.toml`, `biome.json`, etc.)\n4. Install the linters for your languages\n\n### Language-Specific Dependencies\n\n| Language | Required | Optional |\n|----------|----------|----------|\n| Python | `ruff`, `uv` | `ty` (types), `vulture` (dead code), `bandit` (security) |\n| TypeScript\u002FJS | `biome` | `oxlint`, `semgrep`, `knip` (dead exports) |\n| Shell | `shellcheck`, `shfmt` | — |\n| YAML | `yamllint` | — |\n| Markdown | `markdownlint-cli2` | — |\n| Dockerfile | `hadolint` (>= 2.12.0) | — |\n| TOML | `taplo` | — |\n| JSON | `jaq` | — |\n\n## Pairing with ECC\n\n### Complementary, Not Overlapping\n\n| Concern | ECC | Plankton |\n|---------|-----|----------|\n| Code quality enforcement | PostToolUse hooks (Prettier, tsc) | PostToolUse hooks (20+ linters + subprocess fixes) |\n| Security scanning | AgentShield, security-reviewer agent | Bandit (Python), Semgrep (TypeScript) |\n| Config protection | — | PreToolUse blocks + Stop hook detection |\n| Package manager | Detection + setup | Enforcement (blocks legacy PMs) |\n| CI integration | — | Pre-commit hooks for git |\n| Model routing | Manual (`\u002Fmodel opus`) | Automatic (violation complexity → tier) |\n\n### Recommended Combination\n\n1. Install ECC as your plugin (agents, skills, commands, rules)\n2. Add Plankton hooks for write-time quality enforcement\n3. Use AgentShield for security audits\n4. Use ECC's verification-loop as a final gate before PRs\n\n### Avoiding Hook Conflicts\n\nIf running both ECC and Plankton hooks:\n- ECC's Prettier hook and Plankton's biome formatter may conflict on JS\u002FTS files\n- Resolution: disable ECC's Prettier PostToolUse hook when using Plankton (Plankton's biome is more comprehensive)\n- Both can coexist on different file types (ECC handles what Plankton doesn't cover)\n\n## Configuration Reference\n\nPlankton's `.claude\u002Fhooks\u002Fconfig.json` controls all behavior:\n\n```json\n{\n  \"languages\": {\n    \"python\": true,\n    \"shell\": true,\n    \"yaml\": true,\n    \"json\": true,\n    \"toml\": true,\n    \"dockerfile\": true,\n    \"markdown\": true,\n    \"typescript\": {\n      \"enabled\": true,\n      \"js_runtime\": \"auto\",\n      \"biome_nursery\": \"warn\",\n      \"semgrep\": true\n    }\n  },\n  \"phases\": {\n    \"auto_format\": true,\n    \"subprocess_delegation\": true\n  },\n  \"subprocess\": {\n    \"tiers\": {\n      \"haiku\":  { \"timeout\": 120, \"max_turns\": 10 },\n      \"sonnet\": { \"timeout\": 300, \"max_turns\": 10 },\n      \"opus\":   { \"timeout\": 600, \"max_turns\": 15 }\n    },\n    \"volume_threshold\": 5\n  }\n}\n```\n\n**Key settings:**\n- Disable languages you don't use to speed up hooks\n- `volume_threshold` — violations > this count auto-escalate to a higher model tier\n- `subprocess_delegation: false` — skip Phase 3 entirely (just report violations)\n\n## Environment Overrides\n\n| Variable | Purpose |\n|----------|---------|\n| `HOOK_SKIP_SUBPROCESS=1` | Skip Phase 3, report violations directly |\n| `HOOK_SUBPROCESS_TIMEOUT=N` | Override tier timeout |\n| `HOOK_DEBUG_MODEL=1` | Log model selection decisions |\n| `HOOK_SKIP_PM=1` | Bypass package manager enforcement |\n\n## References\n\n- Plankton (credit: @alxfazio)\n- Plankton REFERENCE.md — Full architecture documentation (credit: @alxfazio)\n- Plankton SETUP.md — Detailed installation guide (credit: @alxfazio)\n\n## ECC v1.8 Additions\n\n### Copyable Hook Profile\n\nSet strict quality behavior:\n\n```bash\nexport ECC_HOOK_PROFILE=strict\nexport ECC_QUALITY_GATE_FIX=true\nexport ECC_QUALITY_GATE_STRICT=true\n```\n\n### Language Gate Table\n\n- TypeScript\u002FJavaScript: Biome preferred, Prettier fallback\n- Python: Ruff format\u002Fcheck\n- Go: gofmt\n\n### Config Tamper Guard\n\nDuring quality enforcement, flag changes to config files in same iteration:\n\n- `biome.json`, `.eslintrc*`, `prettier.config*`, `tsconfig.json`, `pyproject.toml`\n\nIf config is changed to suppress violations, require explicit review before merge.\n\n### CI Integration Pattern\n\nUse the same commands in CI as local hooks:\n\n1. run formatter checks\n2. run lint\u002Ftype checks\n3. fail fast on strict mode\n4. publish remediation summary\n\n### Health Metrics\n\nTrack:\n- edits flagged by gates\n- average remediation time\n- repeat violations by category\n- merge blocks due to gate failures\n",{"name":5,"origin":35,"description":7},"main","a298c929b6cbd662e1fce54302ce520d5ceea1a5",".agents\u002Fskills\u002Fplankton-code-quality","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 plankton-code-quality",{"tool":55,"command":56},"bunx","bunx skills add Prekzursil\u002Fagent-skills-toolchain --skill plankton-code-quality",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Prekzursil\u002Fagent-skills-toolchain --skill plankton-code-quality","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FPrekzursil\u002Fagent-skills-toolchain\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fplankton-code-quality\u002FSKILL.md",true,[],[64,85,116,143,157,173],{"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,76,77,78,79,80,81,82,83,84,29],"clarify requirements","clarify","requirements","risk","options","task","prompts","goal","scanning","use","context","repo","injection","execution",{"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":96,"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",[91],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[97,98,99,100,101,102,103,104,105,106,107,108,109,110,80,111,112,113,114,115],"openmm md","how","decision","pick","linux","analyze","tool","stack","open","NVIDIA","gpu","license","workflow","windows","free","molecular dynamics","local","do","MCP",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"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",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":126,"categoryName":127,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000008","测试与质量",[129,130,131,132,133,134,135,136,137,138,98,139,140,141,142],"review","visual","visual review","pages","web","false","iteration","take","check","slides","ui","screenshot","playwright","screenshots",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"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",[],[145,150,151,152,153,154,155,156],"setup","report","project","installation","project setup","issues","state",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":164,"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",[163],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[159,165,76,166,167,168,80,169,170,171,172],"start issue","issue","ready","work on issue","user","work","work on","development",{"skillNo":174,"name":150,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"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",[],[150,152,113,179,154,180],"files","interactive"]