[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EGNH19PRWK8VZYYPXVDJX2":3,"skill-same:01M6EGNH19PRWK8VZYYPXVDJX2":62},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M6EGNH19PRWK8VZYYPXVDJX2","ln-774-healthcheck-setup",null,"Configures health check endpoints for Kubernetes readiness\u002Fliveness\u002Fstartup","levalencia\u002Fagent-god-mode","levalencia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6962857?v=4","01M6EB0FZZ4BPQPC4HET4QY6NM","Luis Valencia ","01M6EB0G4HWHPWW0H9X7QKSAHP",3,"MIT","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-774-healthcheck-setup\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"healthcheck","setup","ln 774 healthcheck setup","kubernetes","startup","health","check","health check","endpoints","readiness","2026-11-10 10:12:30",false,"---\nname: ln-774-healthcheck-setup\ndescription: Configures health check endpoints for Kubernetes readiness\u002Fliveness\u002Fstartup\nlicense: MIT\n---\n\n# ln-774-healthcheck-setup\n\n**Type:** L3 Worker\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-770-crosscutting-setup\n\nConfigures health check endpoints for Kubernetes probes and monitoring.\n\n---\n\n## Overview\n\n| Aspect | Details |\n|--------|---------|\n| **Input** | Context Store from ln-770 |\n| **Output** | Health check endpoints and Kubernetes probe configuration |\n| **Stacks** | .NET (AspNetCore.Diagnostics.HealthChecks), Python (FastAPI routes) |\n\n---\n\n## Phase 1: Receive Context + Identify Dependencies\n\nAccept Context Store and scan for dependencies to monitor.\n\n**Required Context:**\n- `STACK`: .NET or Python\n- `PROJECT_ROOT`: Project directory path\n\n**Idempotency Check:**\n- .NET: Grep for `AddHealthChecks` or `MapHealthChecks`\n- Python: Grep for `\u002Fhealth` route\n- If found: Return `{ \"status\": \"skipped\" }`\n\n**Dependency Detection:**\n\n| Dependency | .NET Detection | Python Detection |\n|------------|----------------|------------------|\n| PostgreSQL | `Npgsql` in csproj | `psycopg2` or `asyncpg` in requirements |\n| MySQL | `MySql.Data` in csproj | `mysql-connector-python` in requirements |\n| Redis | `StackExchange.Redis` in csproj | `redis` in requirements |\n| RabbitMQ | `RabbitMQ.Client` in csproj | `pika` or `aio-pika` in requirements |\n| MongoDB | `MongoDB.Driver` in csproj | `pymongo` in requirements |\n\n---\n\n## Phase 2: Design Health Check Strategy\n\nDefine three types of health endpoints per Kubernetes best practices.\n\n### Endpoint Types\n\n| Endpoint | Probe Type | Purpose | Checks |\n|----------|------------|---------|--------|\n| `\u002Fhealth\u002Flive` | Liveness | Is app alive? | App responds (no dependency checks) |\n| `\u002Fhealth\u002Fready` | Readiness | Can app serve traffic? | All dependencies healthy |\n| `\u002Fhealth\u002Fstartup` | Startup (K8s 1.16+) | Is app initialized? | Initial warmup complete |\n\n### When Each Probe Fails\n\n| Probe | Failure Action | Kubernetes Behavior |\n|-------|----------------|---------------------|\n| Liveness | Container restart | kubelet restarts container |\n| Readiness | Remove from service | Traffic stopped, no restart |\n| Startup | Delay other probes | Liveness\u002FReadiness paused |\n\n---\n\n## Phase 3: Research Health Check Patterns\n\nUse MCP tools for current documentation.\n\n**For .NET:**\n```\nMCP ref: \"ASP.NET Core health checks Kubernetes probes\"\nContext7: \u002Fdotnet\u002Faspnetcore\n```\n\n**For Python:**\n```\nMCP ref: \"FastAPI health check endpoint Kubernetes\"\nContext7: \u002Ftiangolo\u002Ffastapi\n```\n\n**Key Patterns to Research:**\n1. Database health checks (connection pool)\n2. Redis connectivity check\n3. Custom health check implementation\n4. Health check response writer customization\n\n---\n\n## Phase 4: Configure Kubernetes Probes\n\nDetermine probe timing based on application characteristics.\n\n### Probe Configuration\n\n| Parameter | Liveness | Readiness | Startup |\n|-----------|----------|-----------|---------|\n| `initialDelaySeconds` | 10 | 5 | 0 |\n| `periodSeconds` | 10 | 5 | 5 |\n| `timeoutSeconds` | 5 | 3 | 3 |\n| `failureThreshold` | 3 | 3 | 30 |\n| `successThreshold` | 1 | 1 | 1 |\n\n**Startup Probe Calculation:**\n```\nMax startup time = initialDelaySeconds + (periodSeconds × failureThreshold)\nDefault: 0 + (5 × 30) = 150 seconds\n```\n\n---\n\n## Phase 5: Generate Implementation\n\n### .NET Output Files\n\n| File | Purpose |\n|------|---------|\n| `Extensions\u002FHealthCheckExtensions.cs` | Health check registration |\n| `HealthChecks\u002FStartupHealthCheck.cs` | Custom startup check |\n\n**Generation Process:**\n1. Use MCP ref for current ASP.NET Core health checks API\n2. Generate HealthCheckExtensions with:\n   - AddHealthChecks registration\n   - Database health check (if detected)\n   - Redis health check (if detected)\n   - Custom StartupHealthCheck\n3. Configure three endpoints with proper tags\n\n**Packages to Add:**\n- `AspNetCore.HealthChecks.NpgSql` (if PostgreSQL)\n- `AspNetCore.HealthChecks.Redis` (if Redis)\n- `AspNetCore.HealthChecks.MySql` (if MySQL)\n\n**Registration Code:**\n```csharp\nbuilder.Services.AddHealthCheckServices(builder.Configuration);\n\u002F\u002F ...\napp.MapHealthCheckEndpoints();\n```\n\n### Python Output Files\n\n| File | Purpose |\n|------|---------|\n| `routes\u002Fhealth.py` | Health check router |\n| `services\u002Fhealth_checker.py` | Dependency health checks |\n\n**Generation Process:**\n1. Use MCP ref for FastAPI health patterns\n2. Generate health router with:\n   - \u002Fhealth\u002Flive endpoint (simple)\n   - \u002Fhealth\u002Fready endpoint (with dependency checks)\n   - \u002Fhealth\u002Fstartup endpoint\n3. Generate health_checker service for dependency verification\n\n**Registration Code:**\n```python\nfrom routes.health import health_router\napp.include_router(health_router)\n```\n\n### Kubernetes Manifest Snippet\n\nGenerate for inclusion in deployment.yaml:\n\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Flive\n    port: 5000\n  initialDelaySeconds: 10\n  periodSeconds: 10\n  timeoutSeconds: 5\n  failureThreshold: 3\n\nreadinessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Fready\n    port: 5000\n  initialDelaySeconds: 5\n  periodSeconds: 5\n  timeoutSeconds: 3\n  failureThreshold: 3\n\nstartupProbe:\n  httpGet:\n    path: \u002Fhealth\u002Fstartup\n    port: 5000\n  periodSeconds: 5\n  failureThreshold: 30\n```\n\n---\n\n## Phase 6: Validate\n\n**Validation Steps:**\n\n1. **Syntax check:**\n   - .NET: `dotnet build --no-restore`\n   - Python: `python -m py_compile routes\u002Fhealth.py`\n\n2. **Endpoint test:**\n   ```bash\n   curl http:\u002F\u002Flocalhost:5000\u002Fhealth\u002Flive\n   curl http:\u002F\u002Flocalhost:5000\u002Fhealth\u002Fready\n   curl http:\u002F\u002Flocalhost:5000\u002Fhealth\u002Fstartup\n   ```\n\n3. **Verify response format:**\n   ```json\n   {\n     \"status\": \"Healthy\",\n     \"checks\": {\n       \"database\": { \"status\": \"Healthy\", \"duration\": \"00:00:00.0234\" },\n       \"redis\": { \"status\": \"Healthy\", \"duration\": \"00:00:00.0012\" }\n     },\n     \"totalDuration\": \"00:00:00.0250\"\n   }\n   ```\n\n4. **Dependency failure test:**\n   - Stop database\n   - Verify `\u002Fhealth\u002Fready` returns 503\n   - Verify `\u002Fhealth\u002Flive` still returns 200\n\n---\n\n## Return to Coordinator\n\n```json\n{\n  \"status\": \"success\",\n  \"files_created\": [\n    \"Extensions\u002FHealthCheckExtensions.cs\",\n    \"HealthChecks\u002FStartupHealthCheck.cs\"\n  ],\n  \"packages_added\": [\n    \"AspNetCore.HealthChecks.NpgSql\"\n  ],\n  \"registration_code\": \"builder.Services.AddHealthCheckServices(configuration);\",\n  \"message\": \"Configured health checks with liveness, readiness, and startup probes\"\n}\n```\n\n---\n\n## Reference Links\n\n- [ASP.NET Core Health Checks](https:\u002F\u002Flearn.microsoft.com\u002Faspnet\u002Fcore\u002Fhost-and-deploy\u002Fhealth-checks)\n- [Kubernetes Probes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fconfigure-pod-container\u002Fconfigure-liveness-readiness-startup-probes\u002F)\n- [AWS EKS Health Check Best Practices](https:\u002F\u002Fdocs.aws.amazon.com\u002Feks\u002Flatest\u002Fbest-practices\u002Fapplication.html)\n\n---\n\n## Critical Rules\n\n- **Three separate endpoints** — `\u002Fhealth\u002Flive`, `\u002Fhealth\u002Fready`, `\u002Fhealth\u002Fstartup` per Kubernetes best practices\n- **Liveness must not check dependencies** — only confirms app is alive (avoids cascade restarts)\n- **Readiness checks all dependencies** — DB, Redis, RabbitMQ connectivity verified\n- **Auto-detect dependencies from project files** — scan csproj\u002Frequirements for known packages\n- **Idempotent** — if `AddHealthChecks`\u002F`MapHealthChecks` or `\u002Fhealth` route exists, return `status: \"skipped\"`\n\n## Definition of Done\n\n- Context Store received (stack, project root)\n- Dependencies detected (PostgreSQL, MySQL, Redis, RabbitMQ, MongoDB)\n- Health check endpoints generated (live, ready, startup) for detected stack\n- Kubernetes probe manifest snippet generated with proper timing parameters\n- Syntax validated (`dotnet build` or `py_compile`)\n- Structured JSON response returned to ln-770 coordinator\n\n---\n\n**Version:** 2.0.0\n**Last Updated:** 2026-01-10\n","# ln-774-healthcheck-setup\n\n**Type:** L3 Worker\n**Category:** 7XX Project Bootstrap\n**Parent:** ln-770-crosscutting-setup\n\nConfigures health check endpoints for Kubernetes probes and monitoring.\n\n---\n\n## Overview\n\n| Aspect | Details |\n|--------|---------|\n| **Input** | Context Store from ln-770 |\n| **Output** | Health check endpoints and Kubernetes probe configuration |\n| **Stacks** | .NET (AspNetCore.Diagnostics.HealthChecks), Python (FastAPI routes) |\n\n---\n\n## Phase 1: Receive Context + Identify Dependencies\n\nAccept Context Store and scan for dependencies to monitor.\n\n**Required Context:**\n- `STACK`: .NET or Python\n- `PROJECT_ROOT`: Project directory path\n\n**Idempotency Check:**\n- .NET: Grep for `AddHealthChecks` or `MapHealthChecks`\n- Python: Grep for `\u002Fhealth` route\n- If found: Return `{ \"status\": \"skipped\" }`\n\n**Dependency Detection:**\n\n| Dependency | .NET Detection | Python Detection |\n|------------|----------------|------------------|\n| PostgreSQL | `Npgsql` in csproj | `psycopg2` or `asyncpg` in requirements |\n| MySQL | `MySql.Data` in csproj | `mysql-connector-python` in requirements |\n| Redis | `StackExchange.Redis` in csproj | `redis` in requirements |\n| RabbitMQ | `RabbitMQ.Client` in csproj | `pika` or `aio-pika` in requirements |\n| MongoDB | `MongoDB.Driver` in csproj | `pymongo` in requirements |\n\n---\n\n## Phase 2: Design Health Check Strategy\n\nDefine three types of health endpoints per Kubernetes best practices.\n\n### Endpoint Types\n\n| Endpoint | Probe Type | Purpose | Checks |\n|----------|------------|---------|--------|\n| `\u002Fhealth\u002Flive` | Liveness | Is app alive? | App responds (no dependency checks) |\n| `\u002Fhealth\u002Fready` | Readiness | Can app serve traffic? | All dependencies healthy |\n| `\u002Fhealth\u002Fstartup` | Startup (K8s 1.16+) | Is app initialized? | Initial warmup complete |\n\n### When Each Probe Fails\n\n| Probe | Failure Action | Kubernetes Behavior |\n|-------|----------------|---------------------|\n| Liveness | Container restart | kubelet restarts container |\n| Readiness | Remove from service | Traffic stopped, no restart |\n| Startup | Delay other probes | Liveness\u002FReadiness paused |\n\n---\n\n## Phase 3: Research Health Check Patterns\n\nUse MCP tools for current documentation.\n\n**For .NET:**\n```\nMCP ref: \"ASP.NET Core health checks Kubernetes probes\"\nContext7: \u002Fdotnet\u002Faspnetcore\n```\n\n**For Python:**\n```\nMCP ref: \"FastAPI health check endpoint Kubernetes\"\nContext7: \u002Ftiangolo\u002Ffastapi\n```\n\n**Key Patterns to Research:**\n1. Database health checks (connection pool)\n2. Redis connectivity check\n3. Custom health check implementation\n4. Health check response writer customization\n\n---\n\n## Phase 4: Configure Kubernetes Probes\n\nDetermine probe timing based on application characteristics.\n\n### Probe Configuration\n\n| Parameter | Liveness | Readiness | Startup |\n|-----------|----------|-----------|---------|\n| `initialDelaySeconds` | 10 | 5 | 0 |\n| `periodSeconds` | 10 | 5 | 5 |\n| `timeoutSeconds` | 5 | 3 | 3 |\n| `failureThreshold` | 3 | 3 | 30 |\n| `successThreshold` | 1 | 1 | 1 |\n\n**Startup Probe Calculation:**\n```\nMax startup time = initialDelaySeconds + (periodSeconds × failureThreshold)\nDefault: 0 + (5 × 30) = 150 seconds\n```\n\n---\n\n## Phase 5: Generate Implementation\n\n### .NET Output Files\n\n| File | Purpose |\n|------|---------|\n| `Extensions\u002FHealthCheckExtensions.cs` | Health check registration |\n| `HealthChecks\u002FStartupHealthCheck.cs` | Custom startup check |\n\n**Generation Process:**\n1. Use MCP ref for current ASP.NET Core health checks API\n2. Generate HealthCheckExtensions with:\n   - AddHealthChecks registration\n   - Database health check (if detected)\n   - Redis health check (if detected)\n   - Custom StartupHealthCheck\n3. Configure three endpoints with proper tags\n\n**Packages to Add:**\n- `AspNetCore.HealthChecks.NpgSql` (if PostgreSQL)\n- `AspNetCore.HealthChecks.Redis` (if Redis)\n- `AspNetCore.HealthChecks.MySql` (if MySQL)\n\n**Registration Code:**\n```csharp\nbuilder.Services.AddHealthCheckServices(builder.Configuration);\n\u002F\u002F ...\napp.MapHealthCheckEndpoints();\n```\n\n### Python Output Files\n\n| File | Purpose |\n|------|---------|\n| `routes\u002Fhealth.py` | Health check router |\n| `services\u002Fhealth_checker.py` | Dependency health checks |\n\n**Generation Process:**\n1. Use MCP ref for FastAPI health patterns\n2. Generate health router with:\n   - \u002Fhealth\u002Flive endpoint (simple)\n   - \u002Fhealth\u002Fready endpoint (with dependency checks)\n   - \u002Fhealth\u002Fstartup endpoint\n3. Generate health_checker service for dependency verification\n\n**Registration Code:**\n```python\nfrom routes.health import health_router\napp.include_router(health_router)\n```\n\n### Kubernetes Manifest Snippet\n\nGenerate for inclusion in deployment.yaml:\n\n```yaml\nlivenessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Flive\n    port: 5000\n  initialDelaySeconds: 10\n  periodSeconds: 10\n  timeoutSeconds: 5\n  failureThreshold: 3\n\nreadinessProbe:\n  httpGet:\n    path: \u002Fhealth\u002Fready\n    port: 5000\n  initialDelaySeconds: 5\n  periodSeconds: 5\n  timeoutSeconds: 3\n  failureThreshold: 3\n\nstartupProbe:\n  httpGet:\n    path: \u002Fhealth\u002Fstartup\n    port: 5000\n  periodSeconds: 5\n  failureThreshold: 30\n```\n\n---\n\n## Phase 6: Validate\n\n**Validation Steps:**\n\n1. **Syntax check:**\n   - .NET: `dotnet build --no-restore`\n   - Python: `python -m py_compile routes\u002Fhealth.py`\n\n2. **Endpoint test:**\n   ```bash\n   curl http:\u002F\u002Flocalhost:5000\u002Fhealth\u002Flive\n   curl http:\u002F\u002Flocalhost:5000\u002Fhealth\u002Fready\n   curl http:\u002F\u002Flocalhost:5000\u002Fhealth\u002Fstartup\n   ```\n\n3. **Verify response format:**\n   ```json\n   {\n     \"status\": \"Healthy\",\n     \"checks\": {\n       \"database\": { \"status\": \"Healthy\", \"duration\": \"00:00:00.0234\" },\n       \"redis\": { \"status\": \"Healthy\", \"duration\": \"00:00:00.0012\" }\n     },\n     \"totalDuration\": \"00:00:00.0250\"\n   }\n   ```\n\n4. **Dependency failure test:**\n   - Stop database\n   - Verify `\u002Fhealth\u002Fready` returns 503\n   - Verify `\u002Fhealth\u002Flive` still returns 200\n\n---\n\n## Return to Coordinator\n\n```json\n{\n  \"status\": \"success\",\n  \"files_created\": [\n    \"Extensions\u002FHealthCheckExtensions.cs\",\n    \"HealthChecks\u002FStartupHealthCheck.cs\"\n  ],\n  \"packages_added\": [\n    \"AspNetCore.HealthChecks.NpgSql\"\n  ],\n  \"registration_code\": \"builder.Services.AddHealthCheckServices(configuration);\",\n  \"message\": \"Configured health checks with liveness, readiness, and startup probes\"\n}\n```\n\n---\n\n## Reference Links\n\n- [ASP.NET Core Health Checks](https:\u002F\u002Flearn.microsoft.com\u002Faspnet\u002Fcore\u002Fhost-and-deploy\u002Fhealth-checks)\n- [Kubernetes Probes](https:\u002F\u002Fkubernetes.io\u002Fdocs\u002Ftasks\u002Fconfigure-pod-container\u002Fconfigure-liveness-readiness-startup-probes\u002F)\n- [AWS EKS Health Check Best Practices](https:\u002F\u002Fdocs.aws.amazon.com\u002Feks\u002Flatest\u002Fbest-practices\u002Fapplication.html)\n\n---\n\n## Critical Rules\n\n- **Three separate endpoints** — `\u002Fhealth\u002Flive`, `\u002Fhealth\u002Fready`, `\u002Fhealth\u002Fstartup` per Kubernetes best practices\n- **Liveness must not check dependencies** — only confirms app is alive (avoids cascade restarts)\n- **Readiness checks all dependencies** — DB, Redis, RabbitMQ connectivity verified\n- **Auto-detect dependencies from project files** — scan csproj\u002Frequirements for known packages\n- **Idempotent** — if `AddHealthChecks`\u002F`MapHealthChecks` or `\u002Fhealth` route exists, return `status: \"skipped\"`\n\n## Definition of Done\n\n- Context Store received (stack, project root)\n- Dependencies detected (PostgreSQL, MySQL, Redis, RabbitMQ, MongoDB)\n- Health check endpoints generated (live, ready, startup) for detected stack\n- Kubernetes probe manifest snippet generated with proper timing parameters\n- Syntax validated (`dotnet build` or `py_compile`)\n- Structured JSON response returned to ln-770 coordinator\n\n---\n\n**Version:** 2.0.0\n**Last Updated:** 2026-01-10\n",{"name":5,"license":15,"description":7},"main","fa638b97a18ff6d9f26cf0eaf3dfa123531bcc87","organized-skills\u002Fln-774-healthcheck-setup",1,"https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode","https:\u002F\u002Fgithub.com\u002Flevalencia","https:\u002F\u002Fmedium.com\u002F@luisevalencia","Microsoft MVP - Artificial Intelligence\r\nMachine Learning Enthusiast\r\n","2026-05-02 06:55:36",{"source":8,"skillName":5,"commands":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add levalencia\u002Fagent-god-mode --skill ln-774-healthcheck-setup",{"tool":54,"command":55},"bunx","bunx skills add levalencia\u002Fagent-god-mode --skill ln-774-healthcheck-setup",{"tool":57,"command":58},"pnpm","pnpm dlx skills add levalencia\u002Fagent-god-mode --skill ln-774-healthcheck-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fln-774-healthcheck-setup\u002FSKILL.md",true,[],[63,85,121,148,174,202],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":34},"01M6EM8ES5M9J4S8N78NJST0YC","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzarr-python\u002FSKILL.md",[],[70,71,72,73,74,75,76,77,78,79,80,81,82,83,84],"python","zarr python","storage","integration","s3","gcs","cloud","dask","parallel","pipelines","arrays","numpy","scientific computing","scale","scientific",{"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":102,"publishedAt":34},"01M6EM8AR6ZFKZ9YVW8TTG850Z","zabbix","Zabbix monitoring system automation via API and Python. Use when: (1) Managing hosts, templates, items, triggers, or host groups, (2) Automating monitoring configuration, (3) Sending data via Zabbix trapper\u002Fsender, (4) Querying historical data or events, (5) Bulk operations on Zabbix objects, (6) Maintenance window management, (7) User\u002Fpermission management","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fzabbix-api-skill\u002FSKILL.md",[91,94,97],{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,70,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120],"automation","window management","monitoring","data","templates","api","system","operations","use","maintenance","objects","permission","bulk operations","triggers","host","events","via","bulk",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":34},"01M6EM6Q9JG846ECQY9A210A26","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fx-twitter-growth\u002FSKILL.md",[],[128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147],"twitter","x twitter growth","growth","competitive intelligence","search","analyzing","plan","marketing","web search","competitors","analyze","write","optimize","social","intelligence","viral","growth engine","mechanics","grow","competitive",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":34},"01M6EM3FQNPYNKPC4CV9TCVNGD","what-if-oracle","Run structured What-If scenario analysis with multi-branch possibility exploration. Use this skill when the user asks speculative questions like \"what if...\", \"what would happen if...\", \"what are the possibilities\", \"explore scenarios\", \"scenario analysis\", \"possibility space\", \"what could go wrong\", \"best case \u002F worst case\", \"risk analysis\", \"contingency planning\", \"strategic options\", or any question about uncertain futures. Also trigger when the user faces a fork-in-the-road decision, wants to stress-test an idea, or needs to think through consequences before committing.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fwhat-if-oracle\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,163,164,165,166,111,167,168,169,170,171,172,173],"oracle","what if oracle","test","planning","ux","futures","risk","analysis","explore","decision","branch","question","exploration","options","stress-test","strategies","trigger","case","multi",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":183,"publishedAt":34},"01M6EM08C06RGDYCJ86HAPK0FF","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvercel-react-best-practices\u002FSKILL.md",[180],{"categoryNo":181,"categoryName":182,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[184,185,186,187,188,189,190,191,192,193,194,195,196,106,197,198,199,200,201,116],"react","vercel react best practices","best practices","react best practices","vercel","writing","performance","components","react components","guidelines","tasks","code","Optimization","Next.js","refactoring","performance optimization","next","pages",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":218,"publishedAt":34},"01M6EM00S13326QM08DTM94J6Z","venue-templates","Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.","https:\u002F\u002Fgithub.com\u002Flevalencia\u002Fagent-god-mode\u002Fblob\u002Fmain\u002Forganized-skills\u002Fvenue-templates\u002FSKILL.md",[208,211,214,215],{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":212,"categoryName":213,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":95,"categoryName":96,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":216,"categoryName":217,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000036","内容创作者",[107,219,220,193,221,222,223,224,225,226,227,139,228,229,230,231,232,233,84,234],"venue templates","research","NeurIPS","ICML","LaTeX","science","Bash","access","read","edit","proposals","Academic","requirements","formatting","journal","chi"]