[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF9547YYD37WDBB4810W29":3,"skill-same:01M6AF9547YYD37WDBB4810W29":86},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":67,"ownerHtmlUrl":68,"ownerBlogUrl":69,"ownerDescription":70,"updatedAt":71,"install":72,"resources":85},"01M6AF9547YYD37WDBB4810W29","railway-deployment",null,"Manage Railway deployments - view logs, redeploy, restart, or remove deployments. Use for deployment lifecycle (remove, stop, redeploy, restart), deployment visibility (list, status, history), and troubleshooting (logs, errors, failures, crashes). NOT for deleting services - use railway-environment skill with isDeleted for that.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33286,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fdeployment\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"deployment","Railway","railway deployment","list","for","errors","Redeploy","restart","manage","stop","remove","environment","view","cli","history","Bash","lifecycle","services","logs","infrastructure","debug","status","2026-11-10 10:12:30",false,"---\nname: railway-deployment\ndescription: Manage Railway deployments - view logs, redeploy, restart, or remove deployments. Use for deployment lifecycle (remove, stop, redeploy, restart), deployment visibility (list, status, history), and troubleshooting (logs, errors, failures, crashes). NOT for deleting services - use railway-environment skill with isDeleted for that.\nlicense: MIT\nallowed-tools: Bash(railway:*)\nmetadata:\n  version: 1.0.0\n  author: Railway\n  tags: [Railway, Deployment, Logs, Debug, Troubleshooting, Redeploy, Infrastructure]\n  dependencies: [railway-cli]\n---\n\n# Railway Deployment Management\n\nManage existing Railway deployments: list, view logs, redeploy, or remove.\n\n**Important:** \"Remove deployment\" (`railway down`) stops the current deployment but keeps the service. To delete a service entirely, use the railway-environment skill with `isDeleted: true`.\n\n## When to Use\n\n- User says \"remove deploy\", \"take down service\", \"stop deployment\", \"railway down\"\n- User wants to \"redeploy\", \"restart the service\", \"restart deployment\"\n- User asks to \"list deployments\", \"show deployment history\", \"deployment status\"\n- User asks to \"see logs\", \"show logs\", \"check errors\", \"debug issues\"\n\n## List Deployments\n\n```bash\nrailway deployment list --limit 10 --json\n```\n\nShows deployment IDs, statuses, and metadata. Use to find specific deployment IDs for logs or debugging.\n\n### Specify Service\n\n```bash\nrailway deployment list --service backend --limit 10 --json\n```\n\n## View Logs\n\n### Deploy Logs\n\n```bash\nrailway logs --lines 100 --json\n```\n\nIn non-interactive mode, streaming is auto-disabled and CLI fetches logs then exits.\n\n### Build Logs\n\n```bash\nrailway logs --build --lines 100 --json\n```\n\nFor debugging build failures or viewing build output.\n\n### Logs for Failed\u002FIn-Progress Deployments\n\nBy default `railway logs` shows the last successful deployment. Use `--latest` for current:\n\n```bash\nrailway logs --latest --lines 100 --json\n```\n\n### Filter Logs\n\n```bash\n# Errors only\nrailway logs --lines 50 --filter \"@level:error\" --json\n\n# Text search\nrailway logs --lines 50 --filter \"connection refused\" --json\n\n# Combined\nrailway logs --lines 50 --filter \"@level:error AND timeout\" --json\n```\n\n### Time-Based Filtering\n\n```bash\n# Logs from last hour\nrailway logs --since 1h --lines 100 --json\n\n# Logs between 30 and 10 minutes ago\nrailway logs --since 30m --until 10m --lines 100 --json\n\n# Logs from specific timestamp\nrailway logs --since 2024-01-15T10:00:00Z --lines 100 --json\n```\n\nFormats: relative (`30s`, `5m`, `2h`, `1d`, `1w`) or ISO 8601 timestamps.\n\n### Logs from Specific Deployment\n\nDeploy logs:\n```bash\nrailway logs \u003Cdeployment-id> --lines 100 --json\n```\n\nBuild logs:\n```bash\nrailway logs --build \u003Cdeployment-id> --lines 100 --json\n```\n\nGet deployment ID from `railway deployment list`.\n\n**Note:** The deployment ID is a positional argument, NOT `--deployment \u003Cid>`. The `--deployment` flag is a boolean that selects deploy logs (vs `--build` for build logs).\n\n## Redeploy\n\nRedeploy the most recent deployment:\n\n```bash\nrailway redeploy --service \u003Cname> -y\n```\n\nThe `-y` flag skips confirmation. Useful when:\n- Config changed via railway-environment skill\n- Need to restart without new code\n- Previous deploy succeeded but service misbehaving\n\n### Restart Container Only\n\nRestart without rebuilding (picks up external resource changes):\n\n```bash\nrailway restart --service \u003Cname> -y\n```\n\nUse when external resources (S3 files, config maps) changed but code didn't.\n\n## Remove Deployment\n\nTakes down the current deployment. The service remains but has no running deployment.\n\n```bash\n# Remove deployment for linked service\nrailway down -y\n\n# Remove deployment for specific service\nrailway down --service web -y\nrailway down --service api -y\n```\n\nThis is what users mean when they say \"remove deploy\", \"take down\", or \"stop the deployment\".\n\n**Note:** This does NOT delete the service. To delete a service entirely, use the railway-environment skill with `isDeleted: true`.\n\n## CLI Options\n\n### deployment list\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-e, --environment \u003CNAME>` | Environment name or ID |\n| `--limit \u003CN>` | Max deployments (default 20, max 1000) |\n| `--json` | JSON output |\n\n### logs\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-e, --environment \u003CNAME>` | Environment name or ID |\n| `-d, --deployment` | Show deploy logs (default, boolean flag) |\n| `-b, --build` | Show build logs (boolean flag) |\n| `-n, --lines \u003CN>` | Number of lines (required) |\n| `-f, --filter \u003CQUERY>` | Filter using query syntax |\n| `--since \u003CTIME>` | Start time (relative or ISO 8601) |\n| `--until \u003CTIME>` | End time (relative or ISO 8601) |\n| `--latest` | Most recent deployment (even if failed) |\n| `--json` | JSON output |\n| `[DEPLOYMENT_ID]` | Specific deployment (optional) |\n\n### redeploy\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-y, --yes` | Skip confirmation |\n\n### restart\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-y, --yes` | Skip confirmation |\n\n### down\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-e, --environment \u003CNAME>` | Environment name or ID |\n| `-y, --yes` | Skip confirmation |\n\n## Presenting Logs\n\nWhen showing logs:\n- Include timestamps\n- Highlight errors and warnings\n- For build failures: show error and suggest fixes\n- For runtime crashes: show stack trace context\n- Summarize patterns (e.g., \"15 timeout errors in last 100 logs\")\n\n## Composability\n\n- **Push new code**: Use railway-deploy skill\n- **Check service status**: Use railway-status skill\n- **Fix config issues**: Use railway-environment skill\n- **Create new service**: Use railway-new skill\n\n## Error Handling\n\n### No Service Linked\n```\nNo service linked. Run `railway service` to select one.\n```\n\n### No Deployments Found\n```\nNo deployments found. Deploy first with `railway up`.\n```\n\n### No Logs Found\nDeployment may be too old (log retention limits) or service hasn't produced output.\n","# Railway Deployment Management\n\nManage existing Railway deployments: list, view logs, redeploy, or remove.\n\n**Important:** \"Remove deployment\" (`railway down`) stops the current deployment but keeps the service. To delete a service entirely, use the railway-environment skill with `isDeleted: true`.\n\n## When to Use\n\n- User says \"remove deploy\", \"take down service\", \"stop deployment\", \"railway down\"\n- User wants to \"redeploy\", \"restart the service\", \"restart deployment\"\n- User asks to \"list deployments\", \"show deployment history\", \"deployment status\"\n- User asks to \"see logs\", \"show logs\", \"check errors\", \"debug issues\"\n\n## List Deployments\n\n```bash\nrailway deployment list --limit 10 --json\n```\n\nShows deployment IDs, statuses, and metadata. Use to find specific deployment IDs for logs or debugging.\n\n### Specify Service\n\n```bash\nrailway deployment list --service backend --limit 10 --json\n```\n\n## View Logs\n\n### Deploy Logs\n\n```bash\nrailway logs --lines 100 --json\n```\n\nIn non-interactive mode, streaming is auto-disabled and CLI fetches logs then exits.\n\n### Build Logs\n\n```bash\nrailway logs --build --lines 100 --json\n```\n\nFor debugging build failures or viewing build output.\n\n### Logs for Failed\u002FIn-Progress Deployments\n\nBy default `railway logs` shows the last successful deployment. Use `--latest` for current:\n\n```bash\nrailway logs --latest --lines 100 --json\n```\n\n### Filter Logs\n\n```bash\n# Errors only\nrailway logs --lines 50 --filter \"@level:error\" --json\n\n# Text search\nrailway logs --lines 50 --filter \"connection refused\" --json\n\n# Combined\nrailway logs --lines 50 --filter \"@level:error AND timeout\" --json\n```\n\n### Time-Based Filtering\n\n```bash\n# Logs from last hour\nrailway logs --since 1h --lines 100 --json\n\n# Logs between 30 and 10 minutes ago\nrailway logs --since 30m --until 10m --lines 100 --json\n\n# Logs from specific timestamp\nrailway logs --since 2024-01-15T10:00:00Z --lines 100 --json\n```\n\nFormats: relative (`30s`, `5m`, `2h`, `1d`, `1w`) or ISO 8601 timestamps.\n\n### Logs from Specific Deployment\n\nDeploy logs:\n```bash\nrailway logs \u003Cdeployment-id> --lines 100 --json\n```\n\nBuild logs:\n```bash\nrailway logs --build \u003Cdeployment-id> --lines 100 --json\n```\n\nGet deployment ID from `railway deployment list`.\n\n**Note:** The deployment ID is a positional argument, NOT `--deployment \u003Cid>`. The `--deployment` flag is a boolean that selects deploy logs (vs `--build` for build logs).\n\n## Redeploy\n\nRedeploy the most recent deployment:\n\n```bash\nrailway redeploy --service \u003Cname> -y\n```\n\nThe `-y` flag skips confirmation. Useful when:\n- Config changed via railway-environment skill\n- Need to restart without new code\n- Previous deploy succeeded but service misbehaving\n\n### Restart Container Only\n\nRestart without rebuilding (picks up external resource changes):\n\n```bash\nrailway restart --service \u003Cname> -y\n```\n\nUse when external resources (S3 files, config maps) changed but code didn't.\n\n## Remove Deployment\n\nTakes down the current deployment. The service remains but has no running deployment.\n\n```bash\n# Remove deployment for linked service\nrailway down -y\n\n# Remove deployment for specific service\nrailway down --service web -y\nrailway down --service api -y\n```\n\nThis is what users mean when they say \"remove deploy\", \"take down\", or \"stop the deployment\".\n\n**Note:** This does NOT delete the service. To delete a service entirely, use the railway-environment skill with `isDeleted: true`.\n\n## CLI Options\n\n### deployment list\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-e, --environment \u003CNAME>` | Environment name or ID |\n| `--limit \u003CN>` | Max deployments (default 20, max 1000) |\n| `--json` | JSON output |\n\n### logs\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-e, --environment \u003CNAME>` | Environment name or ID |\n| `-d, --deployment` | Show deploy logs (default, boolean flag) |\n| `-b, --build` | Show build logs (boolean flag) |\n| `-n, --lines \u003CN>` | Number of lines (required) |\n| `-f, --filter \u003CQUERY>` | Filter using query syntax |\n| `--since \u003CTIME>` | Start time (relative or ISO 8601) |\n| `--until \u003CTIME>` | End time (relative or ISO 8601) |\n| `--latest` | Most recent deployment (even if failed) |\n| `--json` | JSON output |\n| `[DEPLOYMENT_ID]` | Specific deployment (optional) |\n\n### redeploy\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-y, --yes` | Skip confirmation |\n\n### restart\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-y, --yes` | Skip confirmation |\n\n### down\n\n| Flag | Description |\n|------|-------------|\n| `-s, --service \u003CNAME>` | Service name or ID |\n| `-e, --environment \u003CNAME>` | Environment name or ID |\n| `-y, --yes` | Skip confirmation |\n\n## Presenting Logs\n\nWhen showing logs:\n- Include timestamps\n- Highlight errors and warnings\n- For build failures: show error and suggest fixes\n- For runtime crashes: show stack trace context\n- Summarize patterns (e.g., \"15 timeout errors in last 100 logs\")\n\n## Composability\n\n- **Push new code**: Use railway-deploy skill\n- **Check service status**: Use railway-status skill\n- **Fix config issues**: Use railway-environment skill\n- **Create new service**: Use railway-new skill\n\n## Error Handling\n\n### No Service Linked\n```\nNo service linked. Run `railway service` to select one.\n```\n\n### No Deployments Found\n```\nNo deployments found. Deploy first with `railway up`.\n```\n\n### No Logs Found\nDeployment may be too old (log retention limits) or service hasn't produced output.\n",{"name":5,"license":15,"metadata":51,"description":7,"allowed-tools":61},{"tags":52,"author":25,"version":58,"dependencies":59},[25,53,54,55,56,30,57],"Deployment","Logs","Debug","Troubleshooting","Infrastructure","1.0.0",[60],"railway-cli","Bash(railway:*)","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fdeployment",3909,"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-11 11:53:30",{"source":8,"skillName":5,"commands":73,"prompt":83,"zipAvailable":84},[74,77,80],{"tool":75,"command":76},"npx","npx skills add davila7\u002Fclaude-code-templates --skill railway-deployment",{"tool":78,"command":79},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill railway-deployment",{"tool":81,"command":82},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill railway-deployment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fdeployment\u002FSKILL.md",true,[],[87,114,141,174,209,232],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":94,"publishedAt":46},"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",[93],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[95,96,97,98,99,28,100,101,102,103,104,105,106,107,108,109,110,111,112,113],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":121,"publishedAt":46},"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",[120],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[122,123,124,125,126,127,128,129,130,131,132,103,133,134,135,136,137,138,139,140],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":156,"publishedAt":46},"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",[147,150,151],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":152,"categoryName":153,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[157,158,159,160,161,162,163,28,164,165,166,167,168,169,170,102,171,172,103,173],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"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":178,"licenseFileUrl":179,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":46},"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",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,28,208],"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":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":213,"sourceHtmlUrl":214,"categories":215,"keywords":220,"publishedAt":46},"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",[216,219],{"categoryNo":217,"categoryName":218,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},[221,222,223,224,225,187,226,196,197,227,228,42,229,28,230,105,231],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","screenshots","local","behavior",{"skillNo":233,"name":234,"nameZh":6,"description":235,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":178,"licenseFileUrl":236,"sourceHtmlUrl":237,"categories":238,"keywords":246,"publishedAt":46},"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",[239,242,243],{"categoryNo":240,"categoryName":241,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":244,"categoryName":245,"taxonomyType":154,"taxonomyTypeDesc":155},"01JBSEEDCAT000000000000036","内容创作者",[247,248,249,250,251,252,253,254,189,255,199,133,256,257,258,259,260,169,261,103,262,263,264,265,266,111,267],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]