[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF9BPAK4DK5QRT5Q8RVZ74":3,"skill-same:01M6AF9BPAK4DK5QRT5Q8RVZ74":81},{"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":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6AF9BPAK4DK5QRT5Q8RVZ74","railway-metrics",null,"Query resource usage metrics for Railway services. Use when user asks about resource usage, CPU, memory, network, disk, or service performance like \"how much memory is my service using\" or \"is my service slow\".","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fmetrics\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"metrics","Railway","railway metrics","how","when","for","usage","about","CPU","resources","query","use","Bash","cli","disk","network","services","monitoring","analytics","performance","memory","2026-11-10 10:12:30",false,"---\nname: railway-metrics\ndescription: Query resource usage metrics for Railway services. Use when user asks about resource usage, CPU, memory, network, disk, or service performance like \"how much memory is my service using\" or \"is my service slow\".\nlicense: MIT\nallowed-tools: Bash(railway:*)\nmetadata:\n  version: 1.0.0\n  author: Railway\n  tags: [Railway, Metrics, Monitoring, Performance, CPU, Memory, Resources, Analytics]\n  dependencies: [railway-cli]\n---\n\n# Railway Service Metrics\n\nQuery resource usage metrics for Railway services.\n\n## When to Use\n\n- User asks \"how much memory is my service using?\"\n- User asks about CPU usage, network traffic, disk usage\n- User wants to debug performance issues\n- User asks \"is my service healthy?\" (combine with railway-service skill)\n\n## Prerequisites\n\nGet environmentId and serviceId from linked project:\n\n```bash\nrailway status --json\n```\n\nExtract:\n- `environment.id` → environmentId\n- `service.id` → serviceId (optional - omit to get all services)\n\n## MetricMeasurement Values\n\n| Measurement | Description |\n|-------------|-------------|\n| CPU_USAGE | CPU usage (cores) |\n| CPU_LIMIT | CPU limit (cores) |\n| MEMORY_USAGE_GB | Memory usage in GB |\n| MEMORY_LIMIT_GB | Memory limit in GB |\n| NETWORK_RX_GB | Network received in GB |\n| NETWORK_TX_GB | Network transmitted in GB |\n| DISK_USAGE_GB | Disk usage in GB |\n| EPHEMERAL_DISK_USAGE_GB | Ephemeral disk usage in GB |\n| BACKUP_USAGE_GB | Backup usage in GB |\n\n## MetricTag Values (for groupBy)\n\n| Tag | Description |\n|-----|-------------|\n| DEPLOYMENT_ID | Group by deployment |\n| DEPLOYMENT_INSTANCE_ID | Group by instance |\n| REGION | Group by region |\n| SERVICE_ID | Group by service |\n\n## Query\n\n```graphql\nquery metrics(\n  $environmentId: String!\n  $serviceId: String\n  $startDate: DateTime!\n  $endDate: DateTime\n  $sampleRateSeconds: Int\n  $averagingWindowSeconds: Int\n  $groupBy: [MetricTag!]\n  $measurements: [MetricMeasurement!]!\n) {\n  metrics(\n    environmentId: $environmentId\n    serviceId: $serviceId\n    startDate: $startDate\n    endDate: $endDate\n    sampleRateSeconds: $sampleRateSeconds\n    averagingWindowSeconds: $averagingWindowSeconds\n    groupBy: $groupBy\n    measurements: $measurements\n  ) {\n    measurement\n    tags {\n      deploymentInstanceId\n      deploymentId\n      serviceId\n      region\n    }\n    values {\n      ts\n      value\n    }\n  }\n}\n```\n\n## Example: Last Hour CPU and Memory\n\nUse heredoc to avoid shell escaping issues:\n\n```bash\nbash \u003C\u003C'SCRIPT'\nSTART_DATE=$(date -u -v-1H +\"%Y-%m-%dT%H:%M:%SZ\" 2>\u002Fdev\u002Fnull || date -u -d \"1 hour ago\" +\"%Y-%m-%dT%H:%M:%SZ\")\nENV_ID=\"your-environment-id\"\nSERVICE_ID=\"your-service-id\"\n\nVARS=$(jq -n \\\n  --arg env \"$ENV_ID\" \\\n  --arg svc \"$SERVICE_ID\" \\\n  --arg start \"$START_DATE\" \\\n  '{environmentId: $env, serviceId: $svc, startDate: $start, measurements: [\"CPU_USAGE\", \"MEMORY_USAGE_GB\"]}')\n\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'query metrics($environmentId: String!, $serviceId: String, $startDate: DateTime!, $measurements: [MetricMeasurement!]!) {\n    metrics(environmentId: $environmentId, serviceId: $serviceId, startDate: $startDate, measurements: $measurements) {\n      measurement\n      tags { deploymentId region serviceId }\n      values { ts value }\n    }\n  }' \\\n  \"$VARS\"\nSCRIPT\n```\n\n## Example: All Services in Environment\n\nOmit serviceId and use groupBy to get metrics for all services:\n\n```bash\nbash \u003C\u003C'SCRIPT'\nSTART_DATE=$(date -u -v-1H +\"%Y-%m-%dT%H:%M:%SZ\" 2>\u002Fdev\u002Fnull || date -u -d \"1 hour ago\" +\"%Y-%m-%dT%H:%M:%SZ\")\nENV_ID=\"your-environment-id\"\n\nVARS=$(jq -n \\\n  --arg env \"$ENV_ID\" \\\n  --arg start \"$START_DATE\" \\\n  '{environmentId: $env, startDate: $start, measurements: [\"CPU_USAGE\", \"MEMORY_USAGE_GB\"], groupBy: [\"SERVICE_ID\"]}')\n\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'query metrics($environmentId: String!, $startDate: DateTime!, $measurements: [MetricMeasurement!]!, $groupBy: [MetricTag!]) {\n    metrics(environmentId: $environmentId, startDate: $startDate, measurements: $measurements, groupBy: $groupBy) {\n      measurement\n      tags { serviceId region }\n      values { ts value }\n    }\n  }' \\\n  \"$VARS\"\nSCRIPT\n```\n\n## Time Parameters\n\n| Parameter | Description |\n|-----------|-------------|\n| startDate | Required. ISO 8601 format (e.g., `2024-01-01T00:00:00Z`) |\n| endDate | Optional. Defaults to now |\n| sampleRateSeconds | Sample interval (e.g., 60 for 1-minute samples) |\n| averagingWindowSeconds | Averaging window for smoothing |\n\n**Tip:** For last hour, calculate startDate as `now - 1 hour` in ISO format.\n\n## Output Interpretation\n\n```json\n{\n  \"data\": {\n    \"metrics\": [\n      {\n        \"measurement\": \"CPU_USAGE\",\n        \"tags\": { \"deploymentId\": \"...\", \"serviceId\": \"...\", \"region\": \"us-west1\" },\n        \"values\": [\n          { \"ts\": \"2024-01-01T00:00:00Z\", \"value\": 0.25 },\n          { \"ts\": \"2024-01-01T00:01:00Z\", \"value\": 0.30 }\n        ]\n      }\n    ]\n  }\n}\n```\n\n- `ts` - timestamp in ISO format\n- `value` - metric value (cores for CPU, GB for memory\u002Fdisk\u002Fnetwork)\n\n## Composability\n\n- **Get IDs**: Use railway-status skill or `railway status --json`\n- **Check service health**: Use railway-service skill for deployment status\n- **View logs**: Use railway-deployment skill if metrics show issues\n- **Scale service**: Use railway-environment skill to adjust resources\n\n## Error Handling\n\n### Empty\u002FNull Metrics\n\nServices without active deployments return empty metrics arrays. When processing with jq, handle nulls:\n\n```bash\n# Safe iteration - skip nulls\njq -r '.data.metrics[]? | select(.values != null and (.values | length) > 0) | ...'\n\n# Check if metrics exist before processing\njq -e '.data.metrics | length > 0' response.json && echo \"has metrics\"\n```\n\n### No Metrics Data\n\nService may be new or have no traffic. Check:\n- Service has active deployment (stopped services have no metrics)\n- Time range includes deployment period\n\n### Invalid Service\u002FEnvironment ID\n\nVerify IDs with `railway status --json`.\n\n### Permission Denied\n\nUser needs access to the project to query metrics.\n","# Railway Service Metrics\n\nQuery resource usage metrics for Railway services.\n\n## When to Use\n\n- User asks \"how much memory is my service using?\"\n- User asks about CPU usage, network traffic, disk usage\n- User wants to debug performance issues\n- User asks \"is my service healthy?\" (combine with railway-service skill)\n\n## Prerequisites\n\nGet environmentId and serviceId from linked project:\n\n```bash\nrailway status --json\n```\n\nExtract:\n- `environment.id` → environmentId\n- `service.id` → serviceId (optional - omit to get all services)\n\n## MetricMeasurement Values\n\n| Measurement | Description |\n|-------------|-------------|\n| CPU_USAGE | CPU usage (cores) |\n| CPU_LIMIT | CPU limit (cores) |\n| MEMORY_USAGE_GB | Memory usage in GB |\n| MEMORY_LIMIT_GB | Memory limit in GB |\n| NETWORK_RX_GB | Network received in GB |\n| NETWORK_TX_GB | Network transmitted in GB |\n| DISK_USAGE_GB | Disk usage in GB |\n| EPHEMERAL_DISK_USAGE_GB | Ephemeral disk usage in GB |\n| BACKUP_USAGE_GB | Backup usage in GB |\n\n## MetricTag Values (for groupBy)\n\n| Tag | Description |\n|-----|-------------|\n| DEPLOYMENT_ID | Group by deployment |\n| DEPLOYMENT_INSTANCE_ID | Group by instance |\n| REGION | Group by region |\n| SERVICE_ID | Group by service |\n\n## Query\n\n```graphql\nquery metrics(\n  $environmentId: String!\n  $serviceId: String\n  $startDate: DateTime!\n  $endDate: DateTime\n  $sampleRateSeconds: Int\n  $averagingWindowSeconds: Int\n  $groupBy: [MetricTag!]\n  $measurements: [MetricMeasurement!]!\n) {\n  metrics(\n    environmentId: $environmentId\n    serviceId: $serviceId\n    startDate: $startDate\n    endDate: $endDate\n    sampleRateSeconds: $sampleRateSeconds\n    averagingWindowSeconds: $averagingWindowSeconds\n    groupBy: $groupBy\n    measurements: $measurements\n  ) {\n    measurement\n    tags {\n      deploymentInstanceId\n      deploymentId\n      serviceId\n      region\n    }\n    values {\n      ts\n      value\n    }\n  }\n}\n```\n\n## Example: Last Hour CPU and Memory\n\nUse heredoc to avoid shell escaping issues:\n\n```bash\nbash \u003C\u003C'SCRIPT'\nSTART_DATE=$(date -u -v-1H +\"%Y-%m-%dT%H:%M:%SZ\" 2>\u002Fdev\u002Fnull || date -u -d \"1 hour ago\" +\"%Y-%m-%dT%H:%M:%SZ\")\nENV_ID=\"your-environment-id\"\nSERVICE_ID=\"your-service-id\"\n\nVARS=$(jq -n \\\n  --arg env \"$ENV_ID\" \\\n  --arg svc \"$SERVICE_ID\" \\\n  --arg start \"$START_DATE\" \\\n  '{environmentId: $env, serviceId: $svc, startDate: $start, measurements: [\"CPU_USAGE\", \"MEMORY_USAGE_GB\"]}')\n\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'query metrics($environmentId: String!, $serviceId: String, $startDate: DateTime!, $measurements: [MetricMeasurement!]!) {\n    metrics(environmentId: $environmentId, serviceId: $serviceId, startDate: $startDate, measurements: $measurements) {\n      measurement\n      tags { deploymentId region serviceId }\n      values { ts value }\n    }\n  }' \\\n  \"$VARS\"\nSCRIPT\n```\n\n## Example: All Services in Environment\n\nOmit serviceId and use groupBy to get metrics for all services:\n\n```bash\nbash \u003C\u003C'SCRIPT'\nSTART_DATE=$(date -u -v-1H +\"%Y-%m-%dT%H:%M:%SZ\" 2>\u002Fdev\u002Fnull || date -u -d \"1 hour ago\" +\"%Y-%m-%dT%H:%M:%SZ\")\nENV_ID=\"your-environment-id\"\n\nVARS=$(jq -n \\\n  --arg env \"$ENV_ID\" \\\n  --arg start \"$START_DATE\" \\\n  '{environmentId: $env, startDate: $start, measurements: [\"CPU_USAGE\", \"MEMORY_USAGE_GB\"], groupBy: [\"SERVICE_ID\"]}')\n\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'query metrics($environmentId: String!, $startDate: DateTime!, $measurements: [MetricMeasurement!]!, $groupBy: [MetricTag!]) {\n    metrics(environmentId: $environmentId, startDate: $startDate, measurements: $measurements, groupBy: $groupBy) {\n      measurement\n      tags { serviceId region }\n      values { ts value }\n    }\n  }' \\\n  \"$VARS\"\nSCRIPT\n```\n\n## Time Parameters\n\n| Parameter | Description |\n|-----------|-------------|\n| startDate | Required. ISO 8601 format (e.g., `2024-01-01T00:00:00Z`) |\n| endDate | Optional. Defaults to now |\n| sampleRateSeconds | Sample interval (e.g., 60 for 1-minute samples) |\n| averagingWindowSeconds | Averaging window for smoothing |\n\n**Tip:** For last hour, calculate startDate as `now - 1 hour` in ISO format.\n\n## Output Interpretation\n\n```json\n{\n  \"data\": {\n    \"metrics\": [\n      {\n        \"measurement\": \"CPU_USAGE\",\n        \"tags\": { \"deploymentId\": \"...\", \"serviceId\": \"...\", \"region\": \"us-west1\" },\n        \"values\": [\n          { \"ts\": \"2024-01-01T00:00:00Z\", \"value\": 0.25 },\n          { \"ts\": \"2024-01-01T00:01:00Z\", \"value\": 0.30 }\n        ]\n      }\n    ]\n  }\n}\n```\n\n- `ts` - timestamp in ISO format\n- `value` - metric value (cores for CPU, GB for memory\u002Fdisk\u002Fnetwork)\n\n## Composability\n\n- **Get IDs**: Use railway-status skill or `railway status --json`\n- **Check service health**: Use railway-service skill for deployment status\n- **View logs**: Use railway-deployment skill if metrics show issues\n- **Scale service**: Use railway-environment skill to adjust resources\n\n## Error Handling\n\n### Empty\u002FNull Metrics\n\nServices without active deployments return empty metrics arrays. When processing with jq, handle nulls:\n\n```bash\n# Safe iteration - skip nulls\njq -r '.data.metrics[]? | select(.values != null and (.values | length) > 0) | ...'\n\n# Check if metrics exist before processing\njq -e '.data.metrics | length > 0' response.json && echo \"has metrics\"\n```\n\n### No Metrics Data\n\nService may be new or have no traffic. Check:\n- Service has active deployment (stopped services have no metrics)\n- Time range includes deployment period\n\n### Invalid Service\u002FEnvironment ID\n\nVerify IDs with `railway status --json`.\n\n### Permission Denied\n\nUser needs access to the project to query metrics.\n",{"name":5,"license":15,"metadata":45,"description":7,"allowed-tools":56},{"tags":46,"author":20,"version":53,"dependencies":54},[20,47,48,49,27,50,51,52],"Metrics","Monitoring","Performance","Memory","Resources","Analytics","1.0.0",[55],"railway-cli","Bash(railway:*)","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fmetrics",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add davila7\u002Fclaude-code-templates --skill railway-metrics",{"tool":73,"command":74},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill railway-metrics",{"tool":76,"command":77},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill railway-metrics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fmetrics\u002FSKILL.md",true,[],[82,110,137,169,204,228],{"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":93,"publishedAt":40},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[88],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[94,95,96,97,98,24,99,100,30,23,101,102,103,104,105,106,107,22,108,109],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","public","look",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":117,"publishedAt":40},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[116],{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},[118,119,120,121,122,123,124,125,126,127,128,23,129,130,131,132,133,134,135,136],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":152,"publishedAt":40},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[143,146,147],{"categoryNo":144,"categoryName":145,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":148,"categoryName":149,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[153,154,155,156,157,158,159,24,160,161,162,163,164,165,166,30,167,168,23,29],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":173,"licenseFileUrl":174,"sourceHtmlUrl":175,"categories":176,"keywords":180,"publishedAt":40},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[177],{"categoryNo":178,"categoryName":179,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000009","前端开发",[181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,24,203],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":173,"licenseFileUrl":208,"sourceHtmlUrl":209,"categories":210,"keywords":215,"publishedAt":40},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[211,214],{"categoryNo":212,"categoryName":213,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":178,"categoryName":179,"taxonomyType":91,"taxonomyTypeDesc":92},[216,217,218,219,220,182,221,191,192,222,223,224,225,24,226,102,227],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":229,"name":230,"nameZh":6,"description":231,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":173,"licenseFileUrl":232,"sourceHtmlUrl":233,"categories":234,"keywords":242,"publishedAt":40},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[235,238,239],{"categoryNo":236,"categoryName":237,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":240,"categoryName":241,"taxonomyType":150,"taxonomyTypeDesc":151},"01JBSEEDCAT000000000000036","内容创作者",[243,244,245,246,247,248,249,250,184,251,194,129,252,253,254,255,256,165,257,23,258,259,260,261,262,22,263],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]