[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6GWZXY072GRAVC5KK8DM003":3,"skill-same:01M6GWZXY072GRAVC5KK8DM003":89},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M6GWZXY072GRAVC5KK8DM003","traffic-surge-runbook",null,"Emergency runbook for handling sudden traffic surges (viral events, market crashes, exchange collapses). Provides step-by-step actions to keep the platform stable under 10-100x normal load. Use during or before anticipated high-traffic events.","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fnirholas-traffic-surge-runbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fnirholas-traffic-surge-runbook\u002FSKILL.md",[],[20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"runbook","traffic surge runbook","traffic","surge","platform","normal","for","load","advanced","keep","events","free","performance","scaling","exchange","viral","news","incident","crypto","Market","use","actions","2026-11-10 10:12:30",false,"---\nname: traffic-surge-runbook\ndescription: Emergency runbook for handling sudden traffic surges (viral events, market crashes, exchange collapses). Provides step-by-step actions to keep the platform stable under 10-100x normal load. Use during or before anticipated high-traffic events.\nlicense: MIT\nmetadata:\n  category: operations\n  difficulty: advanced\n  author: free-crypto-news\n  tags: [runbook, traffic, surge, incident, scaling, emergency, performance]\n---\n\n# Traffic Surge Runbook\n\n## When to use this skill\n\nUse when:\n- Traffic spikes 5x+ above normal (viral post, market crash, hack)\n- Anticipating a major event (ETF decision, halving, exchange listing)\n- API response times degrading (p99 > 1s)\n- WebSocket connections approaching limit\n- Redis\u002Fcache memory approaching capacity\n- Upstream providers being rate-limited\n\n## Severity Levels\n\n| Level | Trigger | Response Time |\n|-------|---------|---------------|\n| **S1 Critical** | Site down, all APIs 500 | Immediate |\n| **S2 Major** | p99 > 2s, 10%+ error rate | 15 min |\n| **S3 Minor** | p99 > 1s, 5%+ error rate | 1 hour |\n| **S4 Warning** | Traffic 3x normal, cache hit \u003C 80% | 4 hours |\n\n## Immediate Actions (first 5 minutes)\n\n### 1. Increase Cache TTLs\n\nThe single most impactful action. Every cache hit saves an upstream request.\n\n```bash\n# Emergency cache TTL overrides (set via environment)\nCACHE_TTL_NEWS=300       # 2min → 5min\nCACHE_TTL_PRICES=60      # 30s → 60s\nCACHE_TTL_AI=600         # 5min → 10min\nCACHE_TTL_STATIC=7200    # 1hr → 2hr\n```\n\nOr if no env-based override, update the stale-while-revalidate window to serve stale for longer.\n\n### 2. Enable Aggressive Rate Limiting\n\nTemporarily lower rate limits to protect the system:\n\n```\nanonymous:    30 req\u002Fmin  (was 60)\nfree:        100 req\u002Fmin  (was 200)\npro:         500 req\u002Fmin  (was 1,000)\n```\n\n### 3. Scale Horizontally\n\n```bash\n# Docker: add replicas\ndocker compose -f docker-compose.scale.yml up -d --scale app=8\n\n# Vercel: scales automatically (but check function limits)\n# Railway: increase instance count via dashboard\n```\n\n### 4. Disable Non-Essential Endpoints\n\nTemporarily return 503 for expensive endpoints:\n\n```\n\u002Fapi\u002Fai\u002F*          → 503 (AI analysis is expensive)\n\u002Fapi\u002Fpodcast\u002F*     → 503 (TTS generation)\n\u002Fapi\u002Fcommentary\u002F*  → 503 (streaming AI)\n\u002Fapi\u002Ftranslate\u002F*   → 503 (Gemini API calls)\n\u002Fapi\u002Fvector-search → 503 (embedding computation)\n```\n\nKeep running:\n```\n\u002Fapi\u002Fnews          → Essential (core product)\n\u002Fapi\u002Fprices        → Essential (most popular)\n\u002Fapi\u002Frss           → Essential (feed readers, low cost)\n\u002Fapi\u002Fbreaking      → Essential (core product)\n\u002Fapi\u002Fhealth        → Essential (monitoring)\n```\n\n### 5. Check Provider Health\n\n```typescript\n\u002F\u002F Via API: GET \u002Fapi\u002Fhealth\n\u002F\u002F Or in code:\nimport { registry } from '@\u002Flib\u002Fproviders\u002Fregistry';\nconsole.log(registry.report());\n```\n\nIf providers are failing:\n- Check if upstream APIs are also experiencing high load\n- If CoinGecko is down → system falls back to CoinCap → Binance\n- If all market price providers fail → serve stale cache\n\n## Medium-Term Actions (30 min – 2 hours)\n\n### 6. Enable CDN Edge Caching\n\nAdd cache headers to responses if not already present:\n\n```typescript\n\u002F\u002F In API route:\nreturn new Response(json, {\n  headers: {\n    'Cache-Control': 'public, s-maxage=120, stale-while-revalidate=300',\n    'CDN-Cache-Control': 'max-age=120',\n    'Vercel-CDN-Cache-Control': 'max-age=120',\n  },\n});\n```\n\n### 7. WebSocket Shedding\n\nIf WebSocket connections are maxed:\n- Increase heartbeat interval: 30s → 60s\n- Reduce broadcast frequency: every 5s → every 15s\n- Disconnect idle connections (no subscription, no recent messages)\n- Reject new connections with 503 + Retry-After header\n\n### 8. Database Connection Pool\n\n```bash\n# If using Neon PostgreSQL:\n# Increase connection pool via dashboard\n# Enable connection pooler (PgBouncer)\n\n# If Redis is under pressure:\n# Increase maxmemory\n# Switch eviction to allkeys-lru\n# Increase maxclients\n```\n\n### 9. RSS Polling Throttle\n\nReduce RSS polling frequency during surges:\n- Tier 1 sources (CoinDesk, Decrypt): keep 1min polling\n- Tier 2 sources: reduce to 5min polling\n- Tier 3 sources: reduce to 15min polling\n- Disabled sources: skip entirely\n\n## Recovery Actions (post-surge)\n\n### 10. Restore Normal Configuration\n\nAfter traffic returns to normal (\u003C 2x baseline):\n\n1. Restore original cache TTLs\n2. Restore original rate limits\n3. Re-enable disabled endpoints\n4. Restore RSS polling frequency\n5. Verify all provider chains are healthy\n6. Check for any data gaps during the surge\n\n### 11. Post-Incident Review\n\nCollect:\n- Peak request rate (req\u002Fs)\n- Peak concurrent WebSocket connections\n- Max error rate\n- Cache hit rate during surge\n- Which providers failed\n- Which endpoints were slowest\n- Total duration of degraded service\n\nThen:\n- File an incident report\n- Identify permanent fixes\n- Update capacity planning targets\n- Add monitoring for any blind spots discovered\n\n## Monitoring Dashboards\n\n| Metric | Tool | Alert Threshold |\n|--------|------|-----------------|\n| Request rate | Vercel Analytics | > 3x normal |\n| Error rate | Sentry | > 1% |\n| p99 latency | Vercel Speed Insights | > 500ms |\n| Cache hit rate | Redis metrics | \u003C 80% |\n| WS connections | Custom metric | > 80% capacity |\n| RSS polling success | Pino logs | \u003C 90% |\n| Provider health | registry.report() | Any \"critical\" |\n\n## Notes for Agent Use\n\n- This runbook should be run proactively before known events\n- The most impactful single action is increasing cache TTLs\n- Horizontal scaling is fast with docker-compose.scale.yml\n- AI endpoints are the most expensive — disable first\n- RSS and news endpoints are cheap — keep running\n- Always verify recovery with a health check sweep\n","# Traffic Surge Runbook\n\n## When to use this skill\n\nUse when:\n- Traffic spikes 5x+ above normal (viral post, market crash, hack)\n- Anticipating a major event (ETF decision, halving, exchange listing)\n- API response times degrading (p99 > 1s)\n- WebSocket connections approaching limit\n- Redis\u002Fcache memory approaching capacity\n- Upstream providers being rate-limited\n\n## Severity Levels\n\n| Level | Trigger | Response Time |\n|-------|---------|---------------|\n| **S1 Critical** | Site down, all APIs 500 | Immediate |\n| **S2 Major** | p99 > 2s, 10%+ error rate | 15 min |\n| **S3 Minor** | p99 > 1s, 5%+ error rate | 1 hour |\n| **S4 Warning** | Traffic 3x normal, cache hit \u003C 80% | 4 hours |\n\n## Immediate Actions (first 5 minutes)\n\n### 1. Increase Cache TTLs\n\nThe single most impactful action. Every cache hit saves an upstream request.\n\n```bash\n# Emergency cache TTL overrides (set via environment)\nCACHE_TTL_NEWS=300       # 2min → 5min\nCACHE_TTL_PRICES=60      # 30s → 60s\nCACHE_TTL_AI=600         # 5min → 10min\nCACHE_TTL_STATIC=7200    # 1hr → 2hr\n```\n\nOr if no env-based override, update the stale-while-revalidate window to serve stale for longer.\n\n### 2. Enable Aggressive Rate Limiting\n\nTemporarily lower rate limits to protect the system:\n\n```\nanonymous:    30 req\u002Fmin  (was 60)\nfree:        100 req\u002Fmin  (was 200)\npro:         500 req\u002Fmin  (was 1,000)\n```\n\n### 3. Scale Horizontally\n\n```bash\n# Docker: add replicas\ndocker compose -f docker-compose.scale.yml up -d --scale app=8\n\n# Vercel: scales automatically (but check function limits)\n# Railway: increase instance count via dashboard\n```\n\n### 4. Disable Non-Essential Endpoints\n\nTemporarily return 503 for expensive endpoints:\n\n```\n\u002Fapi\u002Fai\u002F*          → 503 (AI analysis is expensive)\n\u002Fapi\u002Fpodcast\u002F*     → 503 (TTS generation)\n\u002Fapi\u002Fcommentary\u002F*  → 503 (streaming AI)\n\u002Fapi\u002Ftranslate\u002F*   → 503 (Gemini API calls)\n\u002Fapi\u002Fvector-search → 503 (embedding computation)\n```\n\nKeep running:\n```\n\u002Fapi\u002Fnews          → Essential (core product)\n\u002Fapi\u002Fprices        → Essential (most popular)\n\u002Fapi\u002Frss           → Essential (feed readers, low cost)\n\u002Fapi\u002Fbreaking      → Essential (core product)\n\u002Fapi\u002Fhealth        → Essential (monitoring)\n```\n\n### 5. Check Provider Health\n\n```typescript\n\u002F\u002F Via API: GET \u002Fapi\u002Fhealth\n\u002F\u002F Or in code:\nimport { registry } from '@\u002Flib\u002Fproviders\u002Fregistry';\nconsole.log(registry.report());\n```\n\nIf providers are failing:\n- Check if upstream APIs are also experiencing high load\n- If CoinGecko is down → system falls back to CoinCap → Binance\n- If all market price providers fail → serve stale cache\n\n## Medium-Term Actions (30 min – 2 hours)\n\n### 6. Enable CDN Edge Caching\n\nAdd cache headers to responses if not already present:\n\n```typescript\n\u002F\u002F In API route:\nreturn new Response(json, {\n  headers: {\n    'Cache-Control': 'public, s-maxage=120, stale-while-revalidate=300',\n    'CDN-Cache-Control': 'max-age=120',\n    'Vercel-CDN-Cache-Control': 'max-age=120',\n  },\n});\n```\n\n### 7. WebSocket Shedding\n\nIf WebSocket connections are maxed:\n- Increase heartbeat interval: 30s → 60s\n- Reduce broadcast frequency: every 5s → every 15s\n- Disconnect idle connections (no subscription, no recent messages)\n- Reject new connections with 503 + Retry-After header\n\n### 8. Database Connection Pool\n\n```bash\n# If using Neon PostgreSQL:\n# Increase connection pool via dashboard\n# Enable connection pooler (PgBouncer)\n\n# If Redis is under pressure:\n# Increase maxmemory\n# Switch eviction to allkeys-lru\n# Increase maxclients\n```\n\n### 9. RSS Polling Throttle\n\nReduce RSS polling frequency during surges:\n- Tier 1 sources (CoinDesk, Decrypt): keep 1min polling\n- Tier 2 sources: reduce to 5min polling\n- Tier 3 sources: reduce to 15min polling\n- Disabled sources: skip entirely\n\n## Recovery Actions (post-surge)\n\n### 10. Restore Normal Configuration\n\nAfter traffic returns to normal (\u003C 2x baseline):\n\n1. Restore original cache TTLs\n2. Restore original rate limits\n3. Re-enable disabled endpoints\n4. Restore RSS polling frequency\n5. Verify all provider chains are healthy\n6. Check for any data gaps during the surge\n\n### 11. Post-Incident Review\n\nCollect:\n- Peak request rate (req\u002Fs)\n- Peak concurrent WebSocket connections\n- Max error rate\n- Cache hit rate during surge\n- Which providers failed\n- Which endpoints were slowest\n- Total duration of degraded service\n\nThen:\n- File an incident report\n- Identify permanent fixes\n- Update capacity planning targets\n- Add monitoring for any blind spots discovered\n\n## Monitoring Dashboards\n\n| Metric | Tool | Alert Threshold |\n|--------|------|-----------------|\n| Request rate | Vercel Analytics | > 3x normal |\n| Error rate | Sentry | > 1% |\n| p99 latency | Vercel Speed Insights | > 500ms |\n| Cache hit rate | Redis metrics | \u003C 80% |\n| WS connections | Custom metric | > 80% capacity |\n| RSS polling success | Pino logs | \u003C 90% |\n| Provider health | registry.report() | Any \"critical\" |\n\n## Notes for Agent Use\n\n- This runbook should be run proactively before known events\n- The most impactful single action is increasing cache TTLs\n- Horizontal scaling is fast with docker-compose.scale.yml\n- AI endpoints are the most expensive — disable first\n- RSS and news endpoints are cheap — keep running\n- Always verify recovery with a health check sweep\n",{"name":5,"license":15,"metadata":47,"description":7},{"tags":48,"author":50,"category":51,"difficulty":28},[20,22,23,37,33,49,32],"emergency","free-crypto-news","operations","main","3df1d0d67b30ff15236561f8c0f9f06d33f42dfd","skills\u002Fmcp-servers\u002Fnirholas-traffic-surge-runbook",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-13 02:31:19",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill traffic-surge-runbook",{"tool":67,"command":68},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill traffic-surge-runbook",{"tool":70,"command":71},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill traffic-surge-runbook","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fnirholas-traffic-surge-runbook\u002FSKILL.md",true,[75,79,85],{"path":76,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":16},"LICENSE","许可证",860,{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"SOURCE.md","REFERENCE","参考文档",361,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fnirholas-traffic-surge-runbook\u002FSOURCE.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"TRUST.auto.yaml",2197,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fnirholas-traffic-surge-runbook\u002FTRUST.auto.yaml",[90,117,139,156,169,179],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":42},"01M712C436EQYE43342Q4E7GG1","recipe-performance","Diagnose a specific MetaMask user flow's real-app performance and Sentry critical-user-flow telemetry with deterministic mm-harness recipes. Use for CUF boundaries, cold\u002Fwarm\u002Fbackground-resume behavior, latency regressions, lifecycle tags, duplicate or blocking network requests, long tasks, layout\u002Fpaint cost, screen redraws, React rerenders, or browser trace analysis where tests alone cannot prove the real app.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fwallets\u002Fmetamask-official-recipe-performance\u002FSKILL.md",[],[32,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116],"recipe performance","recipe","mm","sentry","harness","app","deterministic","recipes","flow","cold","critical","analysis","tasks","react","browser","layout","screen","network","metamask",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":121,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":42},"01M70XT2F8A5CQZ81JBP98KSW3","mexc-spot-websocket","MEXC Spot WebSocket workflows for public streams, protobuf handling, depth maintenance, listen keys, and private streams without exposing API keys.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-websocket\u002FSKILL.md",[],[126,127,128,129,130,131,132,133,134,135,26,136,137,138],"mexc spot websocket","spot","websocket","api","workflows","public","listen","streams","depth","keys","api keys","maintenance","protobuf",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":121,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":42},"01M70XT0MBXN3WZY1BKN0CPNKR","mexc-spot-rest","MEXC Spot REST workflows for public data, signed account requests, orders, wallet\u002Fadmin actions, and secure signing without exposing API keys.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-spot-rest\u002FSKILL.md",[],[147,127,148,149,150,151,152,136,26,135,41,153,154,131,155,130,129],"mexc spot rest","REST","admin","signing","Wallet","requests","secure","data","orders",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":121,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":163,"publishedAt":42},"01M70XSYSVZ2N0N91XCAR2CAK0","mexc-futures-websocket","MEXC Futures WebSocket workflows for public streams, private account\u002Forder\u002Fposition streams, ping\u002Fpong, subscriptions, and depth maintenance.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fmncrftfrcnm-mexc-futures-websocket\u002FSKILL.md",[],[164,165,128,166,167,137,26,168,134,133,131,130],"mexc futures websocket","futures","position","ping","subscriptions",{"skillNo":170,"name":171,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":172,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":42},"01M6H0ZWHVE5W04WG2DKQE2SQC","0xklen-version-and-refresh-sanctions-lists","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-version-and-refresh-sanctions-lists\u002FSKILL.md",[],[176,177,178],"refresh","0xklen version and refresh sanctions lists","version",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":183,"sourceHtmlUrl":184,"categories":185,"keywords":186,"publishedAt":42},"01M6H0Z28Q3R8J0S799GJQWXM3","verify-tests-cover-changed-lines","Use when a PR adds code that the existing suite may not exercise. Measures patch coverage — the share of newly changed lines hit by tests — before approving.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fpayments\u002F0xklen-verify-tests-cover-changed-lines\u002FSKILL.md",[],[187,188,189,190,191,192,193,40,194,195,196],"tests","cover","verify tests cover changed lines","verify","coverage","pr","exercise","patch","code","share"]