[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72D67DF8JCRBDZXDABHMN0B":3,"skill-same:01M72D67DF8JCRBDZXDABHMN0B":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":13,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M72D67DF8JCRBDZXDABHMN0B","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.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Frailway-deployment\u002FSKILL.md",[],[],"2026-11-10 18:39:20",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.\nversion: 1.0.0\nauthor: Railway\nlicense: MIT\ntags: [Railway, Deployment, Logs, Debug, Troubleshooting, Redeploy, Infrastructure]\ndependencies: [railway-cli]\nallowed-tools: Bash(railway:*)\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,"tags":23,"author":24,"license":14,"version":31,"description":7,"dependencies":32,"allowed-tools":34},[24,25,26,27,28,29,30],"Railway","Deployment","Logs","Debug","Troubleshooting","Redeploy","Infrastructure","1.0.0",[33],"railway-cli","Bash(railway:*)","main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Frailway-deployment","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add Sansar35\u002Fclaude-agent --skill railway-deployment",{"tool":47,"command":48},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill railway-deployment",{"tool":50,"command":51},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill railway-deployment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Frailway-deployment\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},".skill-source.json","REFERENCE","参考文档",559,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Frailway-deployment\u002F.skill-source.json",[62,69,76,83,90,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]