[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77NQFA8PXVB63CC70AA2RX8":3,"skill-same:01M77NQFA8PXVB63CC70AA2RX8":47},{"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":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77NQFA8PXVB63CC70AA2RX8","multi-env-isolator",null,"Generate isolated dev\u002Ftest\u002Fprod environments for uvicorn\u002FFastAPI Python web projects with frontend (Vue\u002FReact) support. Creates separate config files, startup scripts (backend + frontend), data directories, Playwright test integration, and documentation with one command. Use when:\n(1) Setting up a new FastAPI\u002Fuvicorn + Vue\u002FReact project that needs dev\u002Ftest\u002Fprod separation\n(2) An existing project has only one environment and needs isolation for parallel work\n(3) A multi-agent team needs developers (Valina) and testers (Choco) working simultaneously without conflicts\n(4) Someone asks \"how to separate development and production\" or \"set up environment isolation\"\n(5) A project suffers from dev changes breaking production, or testers interfering with developers\n(6) You need Playwright E2E test integration with isolated test environment\nNOT for: Node.js-only, Go, Docker-based, or non-Python projects (backend startup scripts are uvicorn-specific).","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fm\u002Fmulti-env-isolator\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: multi-env-isolator\ndescription: |\n  Generate isolated dev\u002Ftest\u002Fprod environments for uvicorn\u002FFastAPI Python web projects with frontend (Vue\u002FReact) support. Creates separate config files, startup scripts (backend + frontend), data directories, Playwright test integration, and documentation with one command. Use when:\n  (1) Setting up a new FastAPI\u002Fuvicorn + Vue\u002FReact project that needs dev\u002Ftest\u002Fprod separation\n  (2) An existing project has only one environment and needs isolation for parallel work\n  (3) A multi-agent team needs developers (Valina) and testers (Choco) working simultaneously without conflicts\n  (4) Someone asks \"how to separate development and production\" or \"set up environment isolation\"\n  (5) A project suffers from dev changes breaking production, or testers interfering with developers\n  (6) You need Playwright E2E test integration with isolated test environment\n  NOT for: Node.js-only, Go, Docker-based, or non-Python projects (backend startup scripts are uvicorn-specific).\n---\n\n# Multi-Environment Isolator\n\nGenerate isolated dev\u002Ftest\u002Fprod environments for uvicorn\u002FFastAPI projects with frontend support (Vue\u002FReact) with one command.\n\n## What This Skill Does\n\nThis skill solves a common problem in multi-agent AI teams: **developers, testers, and production users stepping on each other's toes.** It generates a complete environment isolation setup so that:\n\n- **Valina (Developer)** can freely break things on ports 8000\u002F3000 without affecting anyone\n- **Choco (Tester)** can validate releases on ports 8001\u002F3001 with isolated test data and Playwright tests\n- **Production** stays stable on ports 8002\u002F4173, untouched by dev\u002Ftest activity\n\nEach environment gets its own config file, startup scripts (backend + frontend), database, media storage, and Playwright test configuration — completely isolated from the others.\n\n## What Gets Generated\n\nRunning the setup script creates this structure inside the target project:\n\n```\nyour-project\u002F\n├── .env.dev              # Dev config: DEBUG=True, hot reload, no rate limit\n├── .env.test             # Test config: rate limiting enabled, QA settings\n├── .env.prod             # Prod config: DEBUG=False, secure CORS, multi-worker\n├── scripts\u002F\n│   # Backend scripts\n│   ├── start-backend-dev.sh    # Starts dev server on port 8000 with --reload\n│   ├── start-backend-test.sh   # Starts test server on port 8001\n│   └── start-backend-prod.sh   # Starts prod server on port 8002 with auto workers\n│   # Frontend scripts (Vue\u002FReact)\n│   ├── start-frontend-dev.sh   # Starts dev frontend on port 3000\n│   ├── start-frontend-test.sh  # Starts test frontend on port 3001\n│   └── start-frontend-prod.sh  # Starts prod frontend on port 4173 (preview)\n│   # Test scripts\n│   └── run-playwright-tests.sh # Runs Playwright E2E tests on test environment\n├── data\u002F\n│   ├── dev\u002F              # Dev database + media uploads (safe to delete)\n│   │   └── media\u002F\n│   ├── test\u002F             # Test database + media uploads\n│   │   └── media\u002F\n│   └── prod\u002F             # Prod database + media uploads (back this up!)\n│       └── media\u002F\n├── docs\u002F\n│   └── MULTI_ENV_SETUP.md  # Auto-generated setup guide for the team\n├── cloud_docs\u002Ffrontend\u002F\n│   └── playwright.config.ts  # Playwright test config (if frontend exists)\n└── .gitignore            # Updated to exclude .env.* and data\u002F\n```\n\n## How to Use\n\n### Step 1: Run the setup script\n\n```bash\npython3 scripts\u002Fsetup_envs.py \u002Fpath\u002Fto\u002Fyour-project \\\n  --name \"Your Project Name\" \\\n  --dev-backend-port 8000 \\\n  --dev-frontend-port 3000 \\\n  --test-backend-port 8001 \\\n  --test-frontend-port 3001 \\\n  --prod-backend-port 8002 \\\n  --prod-frontend-port 4173 \\\n  --dev-user \"Valina\" \\\n  --test-user \"Choco\" \\\n  --app-module \"server.main:app\" \\\n  --frontend-dir \"cloud_docs\u002Ffrontend\"\n```\n\nAll flags except `--name` are optional and have sensible defaults.\n\n### Step 2: Start environments\n\n```bash\n# For Valina (Development)\n.\u002Fscripts\u002Fstart-dev.sh        # Starts both backend (8000) and frontend (3000)\n\n# For Choco (Testing)\n.\u002Fscripts\u002Fstart-test.sh       # Starts both backend (8001) and frontend (3001)\n.\u002Fscripts\u002Frun-playwright-tests.sh  # Runs E2E tests\n\n# For Production\n.\u002Fscripts\u002Fstart-prod.sh       # Starts both backend (8002) and frontend (4173)\n```\n\n### Step 2: Customize configs\n\nEdit the generated `.env.dev`, `.env.test`, `.env.prod` files to add project-specific settings like API keys, external service URLs, etc.\n\n### Step 3: Start an environment\n\n```bash\n# For development (hot reload enabled)\n.\u002Fscripts\u002Fstart-dev.sh\n\n# For testing\n.\u002Fscripts\u002Fstart-test.sh\n\n# For production\n.\u002Fscripts\u002Fstart-prod.sh\n```\n\nEach script loads its own `.env.*` file, uses its own port, and writes to its own `data\u002F` subdirectory.\n\n## Command Reference\n\n```\npython3 scripts\u002Fsetup_envs.py \u003Cproject_dir> --name \u003Cname> [options]\n```\n\n| Flag | Default | Description |\n|------|---------|-------------|\n| `project_dir` | (required) | Path to the target project |\n| `--name` | (required) | Project name, used in configs and docs |\n| `--dev-port` | 8020 | Development server port |\n| `--test-port` | 8010 | Testing server port |\n| `--prod-port` | 8000 | Production server port |\n| `--dev-user` | (none) | Developer name, shown in dev startup message |\n| `--test-user` | (none) | Tester name, shown in test startup message |\n| `--db-type` | sqlite | `sqlite` or `postgres` |\n| `--app-module` | server.main:app | Uvicorn application module path |\n| `--dev-db` | (auto) | Override dev database URL |\n| `--test-db` | (auto) | Override test database URL |\n| `--prod-db` | (auto) | Override prod database URL |\n\n## Environment Differences at a Glance\n\n| Setting | Dev (Valina) | Test (Choco) | Prod |\n|---------|--------------|--------------|------|\n| Backend Port | 8000 | 8001 | 8002 |\n| Frontend Port | 3000 | 3001 | 4173 |\n| `DEBUG` | True | True | **False** |\n| Hot Reload | **Yes** | No | No |\n| CORS | Allow All | Allow All | **Restricted** |\n| Rate Limiting | **Off** | On | On |\n| Workers | 1 (reload) | 1 | **Auto (CPU cores)** |\n| Log Level | DEBUG | INFO | **WARNING** |\n| Database | `data\u002Fdev\u002F` | `data\u002Ftest\u002F` | `data\u002Fprod\u002F` |\n| Media | `data\u002Fdev\u002Fmedia\u002F` | `data\u002Ftest\u002Fmedia\u002F` | `data\u002Fprod\u002Fmedia\u002F` |\n| Playwright Tests | ❌ Not recommended | **✅ Recommended** | ❌ Never |\n\n## Recommended Git Branch Strategy\n\nFor teams using this setup:\n\n```\nmain ──────────── Production (start-prod.sh) - Ports 8002\u002F4173\n  ├── release\u002F* ── Testing (start-test.sh + run-playwright-tests.sh) - Ports 8001\u002F3001\n  └── feature\u002F* ── Development (start-dev.sh) - Ports 8000\u002F3000\n```\n\n1. **Valina (Developer)** works on `feature\u002F*`, deploys to dev environment (8000\u002F3000)\n2. Merge to `release\u002F*`, **Choco (Tester)** validates on test environment (8001\u002F3001)\n3. Choco runs Playwright tests: `.\u002Fscripts\u002Frun-playwright-tests.sh`\n4. Tester approves, merge to `main`, deploy to production (8002\u002F4173)\n\n### Parallel Development and Testing\n\n**Key benefit**: Valina and Choco can work simultaneously without conflicts!\n\n```\nTime  | Valina (Dev)              | Choco (Test)\n------|---------------------------|---------------------------\n14:00 | start-dev.sh (8000\u002F3000)  | -\n14:05 | Continue coding...        | start-test.sh (8001\u002F3001)\n14:10 | Continue coding...        | run-playwright-tests.sh\n14:20 | Continue coding...        | Tests pass! Report results\n14:25 | Continue coding...        | stop-test.sh\n```\n\n**No port conflicts! No data interference!** ✅\n\n## Important Notes\n\n- **Existing files are not overwritten.** If `.env.dev` already exists, the script skips it and prints a warning. Safe to re-run.\n- **Backend startup scripts are uvicorn-specific.** The generated `start-backend-*.sh` scripts use `uvicorn` commands. For other frameworks, modify the scripts after generation.\n- **Frontend scripts support Vue\u002FReact.** The generated `start-frontend-*.sh` scripts use `npm run dev` and `npm run preview`. For Vite projects, they work out of the box.\n- **Production JWT secret must be changed.** The generated `.env.prod` has a placeholder `JWT_SECRET`. Replace it with a strong random value before going live.\n- **Back up production data.** The `data\u002Fprod\u002F` directory contains the production database. Set up regular backups.\n- **Playwright tests require Node.js.** The test script requires Playwright to be installed: `npm install -D @playwright\u002Ftest`\n- **Test data cleanup.** After running Playwright tests, consider cleaning up test data to keep the test environment clean.\n\n## Detailed Config Reference\n\nFor all environment variables and troubleshooting: read `references\u002Fconfig-options.md`\n","# Multi-Environment Isolator\n\nGenerate isolated dev\u002Ftest\u002Fprod environments for uvicorn\u002FFastAPI projects with frontend support (Vue\u002FReact) with one command.\n\n## What This Skill Does\n\nThis skill solves a common problem in multi-agent AI teams: **developers, testers, and production users stepping on each other's toes.** It generates a complete environment isolation setup so that:\n\n- **Valina (Developer)** can freely break things on ports 8000\u002F3000 without affecting anyone\n- **Choco (Tester)** can validate releases on ports 8001\u002F3001 with isolated test data and Playwright tests\n- **Production** stays stable on ports 8002\u002F4173, untouched by dev\u002Ftest activity\n\nEach environment gets its own config file, startup scripts (backend + frontend), database, media storage, and Playwright test configuration — completely isolated from the others.\n\n## What Gets Generated\n\nRunning the setup script creates this structure inside the target project:\n\n```\nyour-project\u002F\n├── .env.dev              # Dev config: DEBUG=True, hot reload, no rate limit\n├── .env.test             # Test config: rate limiting enabled, QA settings\n├── .env.prod             # Prod config: DEBUG=False, secure CORS, multi-worker\n├── scripts\u002F\n│   # Backend scripts\n│   ├── start-backend-dev.sh    # Starts dev server on port 8000 with --reload\n│   ├── start-backend-test.sh   # Starts test server on port 8001\n│   └── start-backend-prod.sh   # Starts prod server on port 8002 with auto workers\n│   # Frontend scripts (Vue\u002FReact)\n│   ├── start-frontend-dev.sh   # Starts dev frontend on port 3000\n│   ├── start-frontend-test.sh  # Starts test frontend on port 3001\n│   └── start-frontend-prod.sh  # Starts prod frontend on port 4173 (preview)\n│   # Test scripts\n│   └── run-playwright-tests.sh # Runs Playwright E2E tests on test environment\n├── data\u002F\n│   ├── dev\u002F              # Dev database + media uploads (safe to delete)\n│   │   └── media\u002F\n│   ├── test\u002F             # Test database + media uploads\n│   │   └── media\u002F\n│   └── prod\u002F             # Prod database + media uploads (back this up!)\n│       └── media\u002F\n├── docs\u002F\n│   └── MULTI_ENV_SETUP.md  # Auto-generated setup guide for the team\n├── cloud_docs\u002Ffrontend\u002F\n│   └── playwright.config.ts  # Playwright test config (if frontend exists)\n└── .gitignore            # Updated to exclude .env.* and data\u002F\n```\n\n## How to Use\n\n### Step 1: Run the setup script\n\n```bash\npython3 scripts\u002Fsetup_envs.py \u002Fpath\u002Fto\u002Fyour-project \\\n  --name \"Your Project Name\" \\\n  --dev-backend-port 8000 \\\n  --dev-frontend-port 3000 \\\n  --test-backend-port 8001 \\\n  --test-frontend-port 3001 \\\n  --prod-backend-port 8002 \\\n  --prod-frontend-port 4173 \\\n  --dev-user \"Valina\" \\\n  --test-user \"Choco\" \\\n  --app-module \"server.main:app\" \\\n  --frontend-dir \"cloud_docs\u002Ffrontend\"\n```\n\nAll flags except `--name` are optional and have sensible defaults.\n\n### Step 2: Start environments\n\n```bash\n# For Valina (Development)\n.\u002Fscripts\u002Fstart-dev.sh        # Starts both backend (8000) and frontend (3000)\n\n# For Choco (Testing)\n.\u002Fscripts\u002Fstart-test.sh       # Starts both backend (8001) and frontend (3001)\n.\u002Fscripts\u002Frun-playwright-tests.sh  # Runs E2E tests\n\n# For Production\n.\u002Fscripts\u002Fstart-prod.sh       # Starts both backend (8002) and frontend (4173)\n```\n\n### Step 2: Customize configs\n\nEdit the generated `.env.dev`, `.env.test`, `.env.prod` files to add project-specific settings like API keys, external service URLs, etc.\n\n### Step 3: Start an environment\n\n```bash\n# For development (hot reload enabled)\n.\u002Fscripts\u002Fstart-dev.sh\n\n# For testing\n.\u002Fscripts\u002Fstart-test.sh\n\n# For production\n.\u002Fscripts\u002Fstart-prod.sh\n```\n\nEach script loads its own `.env.*` file, uses its own port, and writes to its own `data\u002F` subdirectory.\n\n## Command Reference\n\n```\npython3 scripts\u002Fsetup_envs.py \u003Cproject_dir> --name \u003Cname> [options]\n```\n\n| Flag | Default | Description |\n|------|---------|-------------|\n| `project_dir` | (required) | Path to the target project |\n| `--name` | (required) | Project name, used in configs and docs |\n| `--dev-port` | 8020 | Development server port |\n| `--test-port` | 8010 | Testing server port |\n| `--prod-port` | 8000 | Production server port |\n| `--dev-user` | (none) | Developer name, shown in dev startup message |\n| `--test-user` | (none) | Tester name, shown in test startup message |\n| `--db-type` | sqlite | `sqlite` or `postgres` |\n| `--app-module` | server.main:app | Uvicorn application module path |\n| `--dev-db` | (auto) | Override dev database URL |\n| `--test-db` | (auto) | Override test database URL |\n| `--prod-db` | (auto) | Override prod database URL |\n\n## Environment Differences at a Glance\n\n| Setting | Dev (Valina) | Test (Choco) | Prod |\n|---------|--------------|--------------|------|\n| Backend Port | 8000 | 8001 | 8002 |\n| Frontend Port | 3000 | 3001 | 4173 |\n| `DEBUG` | True | True | **False** |\n| Hot Reload | **Yes** | No | No |\n| CORS | Allow All | Allow All | **Restricted** |\n| Rate Limiting | **Off** | On | On |\n| Workers | 1 (reload) | 1 | **Auto (CPU cores)** |\n| Log Level | DEBUG | INFO | **WARNING** |\n| Database | `data\u002Fdev\u002F` | `data\u002Ftest\u002F` | `data\u002Fprod\u002F` |\n| Media | `data\u002Fdev\u002Fmedia\u002F` | `data\u002Ftest\u002Fmedia\u002F` | `data\u002Fprod\u002Fmedia\u002F` |\n| Playwright Tests | ❌ Not recommended | **✅ Recommended** | ❌ Never |\n\n## Recommended Git Branch Strategy\n\nFor teams using this setup:\n\n```\nmain ──────────── Production (start-prod.sh) - Ports 8002\u002F4173\n  ├── release\u002F* ── Testing (start-test.sh + run-playwright-tests.sh) - Ports 8001\u002F3001\n  └── feature\u002F* ── Development (start-dev.sh) - Ports 8000\u002F3000\n```\n\n1. **Valina (Developer)** works on `feature\u002F*`, deploys to dev environment (8000\u002F3000)\n2. Merge to `release\u002F*`, **Choco (Tester)** validates on test environment (8001\u002F3001)\n3. Choco runs Playwright tests: `.\u002Fscripts\u002Frun-playwright-tests.sh`\n4. Tester approves, merge to `main`, deploy to production (8002\u002F4173)\n\n### Parallel Development and Testing\n\n**Key benefit**: Valina and Choco can work simultaneously without conflicts!\n\n```\nTime  | Valina (Dev)              | Choco (Test)\n------|---------------------------|---------------------------\n14:00 | start-dev.sh (8000\u002F3000)  | -\n14:05 | Continue coding...        | start-test.sh (8001\u002F3001)\n14:10 | Continue coding...        | run-playwright-tests.sh\n14:20 | Continue coding...        | Tests pass! Report results\n14:25 | Continue coding...        | stop-test.sh\n```\n\n**No port conflicts! No data interference!** ✅\n\n## Important Notes\n\n- **Existing files are not overwritten.** If `.env.dev` already exists, the script skips it and prints a warning. Safe to re-run.\n- **Backend startup scripts are uvicorn-specific.** The generated `start-backend-*.sh` scripts use `uvicorn` commands. For other frameworks, modify the scripts after generation.\n- **Frontend scripts support Vue\u002FReact.** The generated `start-frontend-*.sh` scripts use `npm run dev` and `npm run preview`. For Vite projects, they work out of the box.\n- **Production JWT secret must be changed.** The generated `.env.prod` has a placeholder `JWT_SECRET`. Replace it with a strong random value before going live.\n- **Back up production data.** The `data\u002Fprod\u002F` directory contains the production database. Set up regular backups.\n- **Playwright tests require Node.js.** The test script requires Playwright to be installed: `npm install -D @playwright\u002Ftest`\n- **Test data cleanup.** After running Playwright tests, consider cleaning up test data to keep the test environment clean.\n\n## Detailed Config Reference\n\nFor all environment variables and troubleshooting: read `references\u002Fconfig-options.md`\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fm\u002Fmulti-env-isolator",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill multi-env-isolator",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill multi-env-isolator",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill multi-env-isolator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fm\u002Fmulti-env-isolator\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"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},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]