[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DDKVQNNESFZW17RD3SSVGZ":3,"skill-same:01M7DDKVQNNESFZW17RD3SSVGZ":67},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7DDKVQNNESFZW17RD3SSVGZ","production-ready",null,"Prepares, audits, and hardens projects for production deployment. Detects financial cost loopholes, unbounded queries, runaway API billing risks, missing timeouts, and uncapped loops. Generates dynamic, strictly validated environment variable configs (.env, .env.example), implements health probes, graceful shutdown protocols, error shielding, security headers, and rate limits. Use whenever the user asks to \"make this production ready\", \"audit for production\", \"check deployment readiness\", \"prevent billing runaways\", \"setup environment variables\", \"prepare for release\", or before shipping any code to cloud\u002Fstaging\u002Fproduction.","Marvellbrazil\u002Fmy-agentic-skills","Marvellbrazil","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184349613?v=4","01M7DCJPCRHP7SZS0T5H1GJZ8F","Marvello Faisal","01M7DCJPDCZDB94VG0QXGC6RC3",5,"MIT","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproduction-ready\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: production-ready\ndescription: Prepares, audits, and hardens projects for production deployment. Detects financial cost loopholes, unbounded queries, runaway API billing risks, missing timeouts, and uncapped loops. Generates dynamic, strictly validated environment variable configs (.env, .env.example), implements health probes, graceful shutdown protocols, error shielding, security headers, and rate limits. Use whenever the user asks to \"make this production ready\", \"audit for production\", \"check deployment readiness\", \"prevent billing runaways\", \"setup environment variables\", \"prepare for release\", or before shipping any code to cloud\u002Fstaging\u002Fproduction.\nallowed-tools: Bash Read Grep Glob Edit Write\n---\n\n# Production-Ready Setups Creator\n\nTransform prototype and development-grade code into resilient, cost-controlled, and observable production-ready software.\n\nDeploying unhardened software causes two major classes of failure:\n1. **Financial and Resource Disasters**: Uncapped loops, unbounded database queries, missing network timeouts, and unprotected third-party API calls (e.g. OpenAI, Stripe) that trigger massive cloud bills, exhaust connection pools, or cause self-inflicted denial-of-service.\n2. **Operational Fragility**: Hardcoded connection strings, missing environment validation, dropped in-flight requests during rolling deployments, unmasked stack traces leaking to users, and unstructured logs.\n\nThis skill audits a codebase across these failure modes, implements missing production safeguards, and generates verified configuration.\n\n---\n\n## The 5 Pillars of Production Readiness\n\n| Pillar | Focus | Reference Module |\n| --- | --- | --- |\n| **1. Cost & Resource Guards** | Query limits, pagination, network timeouts, backoff, LLM\u002FAPI spending caps | `references\u002Fcost-and-resource-guards.md` |\n| **2. Dynamic Environment & Config** | Zero hardcoded values, startup schema validation, complete `.env.example` | `references\u002Fenv-and-config.md` |\n| **3. Resilience & Lifecycle** | Graceful shutdown (`SIGTERM`\u002F`SIGINT`), health probes (`\u002Flivez`, `\u002Freadyz`) | `references\u002Fresilience-and-lifecycle.md` |\n| **4. Security & Error Shielding** | Security headers, CORS restriction, rate limiting, generic 500 responses | `references\u002Fsecurity-and-observability.md` |\n| **5. Observability & Logging** | Structured JSON logging, request correlation IDs, PII redaction | `references\u002Fsecurity-and-observability.md` |\n\n---\n\n## Workflow\n\n### Step 1 — Project Discovery & Surface Analysis\n\nInspect the project to identify runtime, framework, database, external dependencies, and ingress entry points.\n\n```bash\n# Identify manifests, runtimes, and lockfiles\nls -la\ncat package.json pyproject.toml go.mod Cargo.toml requirements.txt 2>\u002Fdev\u002Fnull | head -50\n\n# Scan existing environment setups\nfind . -maxdepth 2 -name \".env*\" -not -path \".\u002F.git\u002F*\"\n\n# Locate entry points and server definitions\ngrep -rnE \"(listen\\(|createServer|FastAPI\\(|express\\(|http\\.ListenAndServe)\" src\u002F app\u002F server\u002F 2>\u002Fdev\u002Fnull | head -20\n```\n\nRecord:\n- Primary language, framework, and runtime version.\n- Database clients \u002F ORMs (Prisma, Drizzle, TypeORM, SQLAlchemy, pg, Mongoose).\n- External paid APIs (OpenAI, Anthropic, Stripe, SendGrid, Twilio, AWS SDK).\n- Process entry point file (`server.ts`, `main.py`, `app.js`).\n\n---\n\n### Step 2 — Audit for Financial Loopholes & Cost Hazards\n\nSearch the codebase for code patterns that risk runaway cloud or API spend:\n\n```bash\n# 1. Unbounded Database Queries (missing limit\u002Ftake)\ngrep -rnE \"(findMany|findAll|\\.find\\(|SELECT \\*)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | grep -vE \"(take:|limit:|LIMIT)\" | head -30\n\n# 2. Network calls without explicit timeouts\ngrep -rnE \"fetch\\(|axios\\.(get|post)|requests\\.(get|post)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -30\n\n# 3. Uncapped concurrent paid API calls\ngrep -rnE \"Promise\\.all\\(\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -20\n\n# 4. Unbounded loops or queue processing\ngrep -rnE \"while\\s*\\(true\\)|while\\s*\\(1\\)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -20\n```\n\nRead `references\u002Fcost-and-resource-guards.md` for specific remediation patterns:\n- Clamp all client-supplied pagination limits: `Math.min(limit, 100)`.\n- Attach `AbortSignal.timeout(ms)` to every HTTP call.\n- Wrap concurrent batches in concurrency limiters (e.g. `p-limit`).\n- Add hard token ceilings (`max_tokens`) to LLM requests.\n\n---\n\n### Step 3 — Dynamic Environment Configuration & Schema Validation\n\nGuarantee zero hardcoding. The project must be fully configurable across environments by altering environment variables alone.\n\n1. **Audit for hardcoded values**:\n   ```bash\n   grep -rnE \"(http:\u002F\u002Flocalhost|0\\.0\\.0\\.0|postgres:\u002F\u002F|mongodb:\u002F\u002F|redis:\u002F\u002F)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -30\n   grep -rnE \"(sk-[a-zA-Z0-9]{20,}|bearer [a-zA-Z0-9_\\-\\.]{20,})\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -20\n   ```\n\n2. **Implement Fail-Fast Startup Validation**:\n   If the project lacks startup schema validation, implement an environment validator module (e.g. `src\u002Fconfig\u002Fenv.ts` using Zod\u002FJoi or `app\u002Fconfig.py` using Pydantic Settings).\n   - Require all critical connection strings (`DATABASE_URL`, `SECRET_KEY`, `PORT`).\n   - Coerce numeric and boolean strings to native primitives.\n   - Halt execution (`process.exit(1)`) on boot if any required key is missing, listing every missing key.\n\n3. **Generate or Sync `.env.example`**:\n   - Inventory every environment variable referenced in the code.\n   - Write `.env.example` with clear comments, type formats, and safe non-secret defaults.\n   - Ensure `.env` is listed in `.gitignore`.\n\nRead `references\u002Fenv-and-config.md` for full implementation details.\n\n---\n\n### Step 4 — Implement Resilience & Lifecycle Controls\n\nEnsure containers and instances can be stopped, restarted, and deployed without dropping user requests or corrupting transactions.\n\n1. **Add Graceful Shutdown**:\n   - Catch `SIGTERM` and `SIGINT`.\n   - Close HTTP listener to stop new connections.\n   - Set a 15–30s shutdown deadline.\n   - Drain active requests and close database pools cleanly (`db.$disconnect()` or `pool.end()`).\n\n2. **Add Liveness & Readiness Probes**:\n   - `\u002Flivez` (or `\u002Fhealthz`): Shallow check verifying the HTTP event loop is active (returns 200).\n   - `\u002Freadyz`: Deep check verifying database and critical backing services respond (returns 200 or 503).\n\n3. **Add Global Process Exception Traps**:\n   - Catch `uncaughtException` and `unhandledRejection`.\n   - Log the fatal diagnostic and exit cleanly with code 1 so the supervisor can spawn a fresh instance.\n\nRead `references\u002Fresilience-and-lifecycle.md` for code templates.\n\n---\n\n### Step 5 — Security & Observability Hardening\n\n1. **HTTP Security Headers & CORS**:\n   - Add security headers (`helmet` in Node.js, security middleware in Python).\n   - Restrict CORS origin to explicitly configured `CORS_ORIGIN` env vars. Never leave `*` with credentials in production.\n\n2. **Ingress Payload & Rate Limiting**:\n   - Restrict body-parser payloads (e.g. `express.json({ limit: '1mb' })`).\n   - Apply rate limiting to public and authentication endpoints.\n\n3. **Error Shielding**:\n   - Replace raw error responses with sanitized envelopes.\n   - Never send database errors, query strings, or stack traces to client HTTP responses.\n\n4. **Structured JSON Logging**:\n   - Replace ad-hoc `console.log` with structured JSON logger (e.g. Pino, Winston, Loguru).\n   - Redact sensitive keys (`password`, `token`, `authorization`, `creditCard`).\n\nRead `references\u002Fsecurity-and-observability.md` for implementation patterns.\n\n---\n\n### Step 6 — Verification & Delivery Report\n\nVerify all changes:\n1. Verify the project builds: run build command.\n2. Verify test suites pass: run test command.\n3. Validate `.env.example` matches code references.\n\nDeliver a structured **Production Readiness Report**:\n\n```markdown\n# Production Readiness Report — [Project Name]\n\n## Summary\n- **Status**: [Ready \u002F Ready with Warnings \u002F Action Required]\n- **Runtime**: [e.g. Node 20 \u002F TypeScript \u002F Express]\n- **Safeguards Applied**: [N] automated fixes implemented\n\n## 1. Loophole & Financial Hazard Audit\n- [x] Query limits: pagination clamped to max 100\n- [x] Network timeouts: AbortSignal attached to all external fetch calls\n- [x] Paid API limits: LLM generations constrained with max_tokens\n- [x] Rate limiting: Ingress endpoints protected\n\n## 2. Dynamic Environment & Configuration\n- [x] Fail-fast startup validator implemented in `src\u002Fconfig\u002Fenv.ts`\n- [x] Zero hardcoded URLs\u002Fsecrets remaining\n- [x] `.env.example` synchronized with all required variables\n- [x] `.env` confirmed in `.gitignore`\n\n## 3. Resilience & Lifecycle\n- [x] Graceful shutdown handling `SIGTERM`\u002F`SIGINT` with 15s drain\n- [x] `\u002Flivez` and `\u002Freadyz` health endpoints configured\n- [x] Top-level process crash handlers installed\n\n## 4. Security & Observability\n- [x] Security headers & CORS lockdown configured\n- [x] Client error shielding active (zero stack traces leaked)\n- [x] Structured JSON logger with automatic PII redaction\n\n## Next Steps for Operator\n1. Copy `.env.example` to `.env` and fill production secrets in target environment.\n2. Configure cloud orchestrator (Kubernetes \u002F ECS \u002F Cloud Run) to target `\u002Flivez` and `\u002Freadyz`.\n```\n","# Production-Ready Setups Creator\n\nTransform prototype and development-grade code into resilient, cost-controlled, and observable production-ready software.\n\nDeploying unhardened software causes two major classes of failure:\n1. **Financial and Resource Disasters**: Uncapped loops, unbounded database queries, missing network timeouts, and unprotected third-party API calls (e.g. OpenAI, Stripe) that trigger massive cloud bills, exhaust connection pools, or cause self-inflicted denial-of-service.\n2. **Operational Fragility**: Hardcoded connection strings, missing environment validation, dropped in-flight requests during rolling deployments, unmasked stack traces leaking to users, and unstructured logs.\n\nThis skill audits a codebase across these failure modes, implements missing production safeguards, and generates verified configuration.\n\n---\n\n## The 5 Pillars of Production Readiness\n\n| Pillar | Focus | Reference Module |\n| --- | --- | --- |\n| **1. Cost & Resource Guards** | Query limits, pagination, network timeouts, backoff, LLM\u002FAPI spending caps | `references\u002Fcost-and-resource-guards.md` |\n| **2. Dynamic Environment & Config** | Zero hardcoded values, startup schema validation, complete `.env.example` | `references\u002Fenv-and-config.md` |\n| **3. Resilience & Lifecycle** | Graceful shutdown (`SIGTERM`\u002F`SIGINT`), health probes (`\u002Flivez`, `\u002Freadyz`) | `references\u002Fresilience-and-lifecycle.md` |\n| **4. Security & Error Shielding** | Security headers, CORS restriction, rate limiting, generic 500 responses | `references\u002Fsecurity-and-observability.md` |\n| **5. Observability & Logging** | Structured JSON logging, request correlation IDs, PII redaction | `references\u002Fsecurity-and-observability.md` |\n\n---\n\n## Workflow\n\n### Step 1 — Project Discovery & Surface Analysis\n\nInspect the project to identify runtime, framework, database, external dependencies, and ingress entry points.\n\n```bash\n# Identify manifests, runtimes, and lockfiles\nls -la\ncat package.json pyproject.toml go.mod Cargo.toml requirements.txt 2>\u002Fdev\u002Fnull | head -50\n\n# Scan existing environment setups\nfind . -maxdepth 2 -name \".env*\" -not -path \".\u002F.git\u002F*\"\n\n# Locate entry points and server definitions\ngrep -rnE \"(listen\\(|createServer|FastAPI\\(|express\\(|http\\.ListenAndServe)\" src\u002F app\u002F server\u002F 2>\u002Fdev\u002Fnull | head -20\n```\n\nRecord:\n- Primary language, framework, and runtime version.\n- Database clients \u002F ORMs (Prisma, Drizzle, TypeORM, SQLAlchemy, pg, Mongoose).\n- External paid APIs (OpenAI, Anthropic, Stripe, SendGrid, Twilio, AWS SDK).\n- Process entry point file (`server.ts`, `main.py`, `app.js`).\n\n---\n\n### Step 2 — Audit for Financial Loopholes & Cost Hazards\n\nSearch the codebase for code patterns that risk runaway cloud or API spend:\n\n```bash\n# 1. Unbounded Database Queries (missing limit\u002Ftake)\ngrep -rnE \"(findMany|findAll|\\.find\\(|SELECT \\*)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | grep -vE \"(take:|limit:|LIMIT)\" | head -30\n\n# 2. Network calls without explicit timeouts\ngrep -rnE \"fetch\\(|axios\\.(get|post)|requests\\.(get|post)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -30\n\n# 3. Uncapped concurrent paid API calls\ngrep -rnE \"Promise\\.all\\(\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -20\n\n# 4. Unbounded loops or queue processing\ngrep -rnE \"while\\s*\\(true\\)|while\\s*\\(1\\)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -20\n```\n\nRead `references\u002Fcost-and-resource-guards.md` for specific remediation patterns:\n- Clamp all client-supplied pagination limits: `Math.min(limit, 100)`.\n- Attach `AbortSignal.timeout(ms)` to every HTTP call.\n- Wrap concurrent batches in concurrency limiters (e.g. `p-limit`).\n- Add hard token ceilings (`max_tokens`) to LLM requests.\n\n---\n\n### Step 3 — Dynamic Environment Configuration & Schema Validation\n\nGuarantee zero hardcoding. The project must be fully configurable across environments by altering environment variables alone.\n\n1. **Audit for hardcoded values**:\n   ```bash\n   grep -rnE \"(http:\u002F\u002Flocalhost|0\\.0\\.0\\.0|postgres:\u002F\u002F|mongodb:\u002F\u002F|redis:\u002F\u002F)\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -30\n   grep -rnE \"(sk-[a-zA-Z0-9]{20,}|bearer [a-zA-Z0-9_\\-\\.]{20,})\" src\u002F app\u002F 2>\u002Fdev\u002Fnull | head -20\n   ```\n\n2. **Implement Fail-Fast Startup Validation**:\n   If the project lacks startup schema validation, implement an environment validator module (e.g. `src\u002Fconfig\u002Fenv.ts` using Zod\u002FJoi or `app\u002Fconfig.py` using Pydantic Settings).\n   - Require all critical connection strings (`DATABASE_URL`, `SECRET_KEY`, `PORT`).\n   - Coerce numeric and boolean strings to native primitives.\n   - Halt execution (`process.exit(1)`) on boot if any required key is missing, listing every missing key.\n\n3. **Generate or Sync `.env.example`**:\n   - Inventory every environment variable referenced in the code.\n   - Write `.env.example` with clear comments, type formats, and safe non-secret defaults.\n   - Ensure `.env` is listed in `.gitignore`.\n\nRead `references\u002Fenv-and-config.md` for full implementation details.\n\n---\n\n### Step 4 — Implement Resilience & Lifecycle Controls\n\nEnsure containers and instances can be stopped, restarted, and deployed without dropping user requests or corrupting transactions.\n\n1. **Add Graceful Shutdown**:\n   - Catch `SIGTERM` and `SIGINT`.\n   - Close HTTP listener to stop new connections.\n   - Set a 15–30s shutdown deadline.\n   - Drain active requests and close database pools cleanly (`db.$disconnect()` or `pool.end()`).\n\n2. **Add Liveness & Readiness Probes**:\n   - `\u002Flivez` (or `\u002Fhealthz`): Shallow check verifying the HTTP event loop is active (returns 200).\n   - `\u002Freadyz`: Deep check verifying database and critical backing services respond (returns 200 or 503).\n\n3. **Add Global Process Exception Traps**:\n   - Catch `uncaughtException` and `unhandledRejection`.\n   - Log the fatal diagnostic and exit cleanly with code 1 so the supervisor can spawn a fresh instance.\n\nRead `references\u002Fresilience-and-lifecycle.md` for code templates.\n\n---\n\n### Step 5 — Security & Observability Hardening\n\n1. **HTTP Security Headers & CORS**:\n   - Add security headers (`helmet` in Node.js, security middleware in Python).\n   - Restrict CORS origin to explicitly configured `CORS_ORIGIN` env vars. Never leave `*` with credentials in production.\n\n2. **Ingress Payload & Rate Limiting**:\n   - Restrict body-parser payloads (e.g. `express.json({ limit: '1mb' })`).\n   - Apply rate limiting to public and authentication endpoints.\n\n3. **Error Shielding**:\n   - Replace raw error responses with sanitized envelopes.\n   - Never send database errors, query strings, or stack traces to client HTTP responses.\n\n4. **Structured JSON Logging**:\n   - Replace ad-hoc `console.log` with structured JSON logger (e.g. Pino, Winston, Loguru).\n   - Redact sensitive keys (`password`, `token`, `authorization`, `creditCard`).\n\nRead `references\u002Fsecurity-and-observability.md` for implementation patterns.\n\n---\n\n### Step 6 — Verification & Delivery Report\n\nVerify all changes:\n1. Verify the project builds: run build command.\n2. Verify test suites pass: run test command.\n3. Validate `.env.example` matches code references.\n\nDeliver a structured **Production Readiness Report**:\n\n```markdown\n# Production Readiness Report — [Project Name]\n\n## Summary\n- **Status**: [Ready \u002F Ready with Warnings \u002F Action Required]\n- **Runtime**: [e.g. Node 20 \u002F TypeScript \u002F Express]\n- **Safeguards Applied**: [N] automated fixes implemented\n\n## 1. Loophole & Financial Hazard Audit\n- [x] Query limits: pagination clamped to max 100\n- [x] Network timeouts: AbortSignal attached to all external fetch calls\n- [x] Paid API limits: LLM generations constrained with max_tokens\n- [x] Rate limiting: Ingress endpoints protected\n\n## 2. Dynamic Environment & Configuration\n- [x] Fail-fast startup validator implemented in `src\u002Fconfig\u002Fenv.ts`\n- [x] Zero hardcoded URLs\u002Fsecrets remaining\n- [x] `.env.example` synchronized with all required variables\n- [x] `.env` confirmed in `.gitignore`\n\n## 3. Resilience & Lifecycle\n- [x] Graceful shutdown handling `SIGTERM`\u002F`SIGINT` with 15s drain\n- [x] `\u002Flivez` and `\u002Freadyz` health endpoints configured\n- [x] Top-level process crash handlers installed\n\n## 4. Security & Observability\n- [x] Security headers & CORS lockdown configured\n- [x] Client error shielding active (zero stack traces leaked)\n- [x] Structured JSON logger with automatic PII redaction\n\n## Next Steps for Operator\n1. Copy `.env.example` to `.env` and fill production secrets in target environment.\n2. Configure cloud orchestrator (Kubernetes \u002F ECS \u002F Cloud Run) to target `\u002Flivez` and `\u002Freadyz`.\n```\n",{"name":5,"description":7,"allowed-tools":24},"Bash Read Grep Glob Edit Write","main","42203fde5eb692ba254e058168ee1af75855fcb4","skills\u002Fproduction-ready",0,"https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills","skills.marvellofaisal.me","https:\u002F\u002Fgithub.com\u002FMarvellbrazil","marvellofaisal.me","Software Engineering Student | Backend & API Developer | Tech Enthusiast | Homelabber","2026-10-23 22:23:52",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Marvellbrazil\u002Fmy-agentic-skills --skill production-ready",{"tool":41,"command":42},"bunx","bunx skills add Marvellbrazil\u002Fmy-agentic-skills --skill production-ready",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Marvellbrazil\u002Fmy-agentic-skills --skill production-ready","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproduction-ready\u002FSKILL.md",true,[49,55,59,63],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcost-and-resource-guards.md","REFERENCE","参考文档",6678,"https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproduction-ready\u002Freferences\u002Fcost-and-resource-guards.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fenv-and-config.md",5845,"https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproduction-ready\u002Freferences\u002Fenv-and-config.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fresilience-and-lifecycle.md",5342,"https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproduction-ready\u002Freferences\u002Fresilience-and-lifecycle.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fsecurity-and-observability.md",4885,"https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fproduction-ready\u002Freferences\u002Fsecurity-and-observability.md",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7DDQP2F4E42AMTGY0VCJ6G2","writing-guidelines","Review docs\u002Fprose for Writing Guidelines compliance. Use when asked to \"review my docs\", \"check writing style\", \"audit prose\", \"review docs voice and tone\", or \"check this page against the writing handbook\".","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-guidelines\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7DDQM00XGSGT8V797C89R2E","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7DDQEF1HP9CMH88HMN9MCBA","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7DDQA32ZAG7J4PMRXRSQ3NQ","workers-best-practices","Reviews and authors Cloudflare Workers code against production best practices. Load when writing new Workers, reviewing Worker code, configuring wrangler.jsonc, or checking for common Workers anti-patterns (streaming, floating promises, global state, secrets, bindings, observability). Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fworkers-best-practices\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7DDQ5482QSC0FC4NX107FVY","web-perf","Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7DDQ1GZ7Z2Y67460SJJEMC0","using-agent-skills","Discovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or workflow applies to the piece of work at hand. This is the meta-skill that governs how all other skills are discovered and invoked.","https:\u002F\u002Fgithub.com\u002FMarvellbrazil\u002Fmy-agentic-skills\u002Fblob\u002Fmain\u002Fskills\u002Fusing-agent-skills\u002FSKILL.md",[],[]]