[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AF99E64BBC903DRY4KNS9W":3,"skill-same:01M6AF99E64BBC903DRY4KNS9W":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":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":68,"repositoryHtmlUrl":69,"repositoryHomepageUrl":70,"ownerHtmlUrl":71,"ownerBlogUrl":72,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M6AF99E64BBC903DRY4KNS9W","railway-environment",null,"Query, stage, and apply configuration changes for Railway environments. Use for ANY variable or env var operations, service configuration (source, build settings, deploy settings), lifecycle (delete service), and applying changes. Prefer over railway-status skill for any configuration or variable queries.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fenvironment\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"railway environment","environment","Railway","queries","apply","changes","source","for","environments","Variables","env","stage","query","cli","use","Bash","lifecycle","delete","infrastructure","deploy","status","2026-11-10 10:12:30",false,"---\nname: railway-environment\ndescription: Query, stage, and apply configuration changes for Railway environments. Use for ANY variable or env var operations, service configuration (source, build settings, deploy settings), lifecycle (delete service), and applying changes. Prefer over railway-status skill for any configuration or variable queries.\nlicense: MIT\nallowed-tools: Bash(railway:*)\nmetadata:\n  version: 1.0.0\n  author: Railway\n  tags: [Railway, Environment, Configuration, Variables, Build, Deploy, Infrastructure, Settings]\n  dependencies: [railway-cli]\n---\n\n# Environment Configuration\n\nQuery, stage, and apply configuration changes for Railway environments.\n\n## Shell Escaping\n\n**CRITICAL:** When running GraphQL queries via bash, you MUST wrap in heredoc to prevent shell escaping issues:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh 'query ...' '{\"var\": \"value\"}'\nSCRIPT\n```\n\nWithout the heredoc wrapper, multi-line commands break and exclamation marks in GraphQL non-null types get escaped, causing query failures.\n\n## When to Use\n\n- User wants to create a new environment\n- User wants to duplicate an environment (e.g., \"copy production to staging\")\n- User wants to switch to a different environment\n- User asks about current build\u002Fdeploy settings, variables, replicas, health checks, domains\n- User asks to change service source (Docker image, branch, commit, root directory)\n- User wants to connect a service to a GitHub repo\n- User wants to deploy from a GitHub repo (create empty service first via railway-new skill, then use this)\n- User asks to change build or start command\n- User wants to add\u002Fupdate\u002Fdelete environment variables\n- User wants to change replica count or configure health checks\n- User asks to delete a service, volume, or bucket\n- User says \"apply changes\", \"commit changes\", \"deploy changes\"\n- Auto-fixing build errors detected in logs\n\n## Create Environment\n\nCreate a new environment in the linked project:\n\n```bash\nrailway environment new \u003Cname>\n```\n\nDuplicate an existing environment:\n\n```bash\nrailway environment new staging --duplicate production\n```\n\nWith service-specific variables:\n\n```bash\nrailway environment new staging --duplicate production --service-variable api PORT=3001\n```\n\n## Switch Environment\n\nLink a different environment to the current directory:\n\n```bash\nrailway environment \u003Cname>\n```\n\nOr by ID:\n\n```bash\nrailway environment \u003Cenvironment-id>\n```\n\n## Get Context\n\n```bash\nrailway status --json\n```\n\nExtract:\n\n- `project.id` - for service lookup\n- `environment.id` - for the mutations\n- `service.id` - default service if user doesn't specify one\n\n### Resolve Service ID\n\nIf user specifies a service by name, query project services:\n\n```graphql\nquery projectServices($projectId: String!) {\n  project(id: $projectId) {\n    services {\n      edges {\n        node {\n          id\n          name\n        }\n      }\n    }\n  }\n}\n```\n\nMatch the service name (case-insensitive) to get the service ID.\n\n## Query Configuration\n\nFetch current environment configuration and staged changes.\n\n```graphql\nquery environmentConfig($environmentId: String!) {\n  environment(id: $environmentId) {\n    id\n    config(decryptVariables: false)\n    serviceInstances {\n      edges {\n        node {\n          id\n          serviceId\n        }\n      }\n    }\n  }\n  environmentStagedChanges(environmentId: $environmentId) {\n    id\n    patch(decryptVariables: false)\n  }\n}\n```\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'query envConfig($envId: String!) {\n    environment(id: $envId) { id config(decryptVariables: false) }\n    environmentStagedChanges(environmentId: $envId) { id patch(decryptVariables: false) }\n  }' \\\n  '{\"envId\": \"ENV_ID\"}'\nSCRIPT\n```\n\n### Response Structure\n\nThe `config` field contains current configuration:\n\n```json\n{\n  \"services\": {\n    \"\u003CserviceId>\": {\n      \"source\": { \"repo\": \"...\", \"branch\": \"main\" },\n      \"build\": { \"buildCommand\": \"npm run build\", \"builder\": \"NIXPACKS\" },\n      \"deploy\": {\n        \"startCommand\": \"npm start\",\n        \"multiRegionConfig\": { \"us-west2\": { \"numReplicas\": 1 } }\n      },\n      \"variables\": { \"NODE_ENV\": { \"value\": \"production\" } },\n      \"networking\": { \"serviceDomains\": {}, \"customDomains\": {} }\n    }\n  },\n  \"sharedVariables\": { \"DATABASE_URL\": { \"value\": \"...\" } }\n}\n```\n\nThe `patch` field in `environmentStagedChanges` contains pending changes. The effective configuration is the base `config` merged with the staged `patch`.\n\nFor complete field reference, see [reference\u002Fenvironment-config.md](..\u002Freference\u002Fenvironment-config.md).\n\nFor variable syntax and service wiring patterns, see [reference\u002Fvariables.md](..\u002Freference\u002Fvariables.md).\n\n## Get Rendered Variables\n\nThe GraphQL queries above return **unrendered** variables - template syntax like `${{shared.DOMAIN}}` is preserved. This is correct for management\u002Fediting.\n\nTo see **rendered** (resolved) values as they appear at runtime:\n\n```bash\n# Current linked service\nrailway variables --json\n\n# Specific service\nrailway variables --service \u003Cservice-name> --json\n```\n\n**When to use:**\n- Debugging connection issues (see actual URLs\u002Fports)\n- Verifying variable resolution is correct\n- Viewing Railway-injected values (RAILWAY_*)\n\n## Stage Changes\n\nStage configuration changes via the `environmentStageChanges` mutation. Use `merge: true` to automatically merge with existing staged changes.\n\n```graphql\nmutation stageEnvironmentChanges(\n  $environmentId: String!\n  $input: EnvironmentConfig!\n  $merge: Boolean\n) {\n  environmentStageChanges(\n    environmentId: $environmentId\n    input: $input\n    merge: $merge\n  ) {\n    id\n  }\n}\n```\n\n**Important:** Always use variables (not inline input) because service IDs are UUIDs which can't be used as unquoted GraphQL object keys.\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation stageChanges($environmentId: String!, $input: EnvironmentConfig!, $merge: Boolean) {\n    environmentStageChanges(environmentId: $environmentId, input: $input, merge: $merge) { id }\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"input\": {\"services\": {\"SERVICE_ID\": {\"build\": {\"buildCommand\": \"npm run build\"}}}}, \"merge\": true}'\nSCRIPT\n```\n\n### Delete Service\n\nUse `isDeleted: true`:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation stageChanges($environmentId: String!, $input: EnvironmentConfig!, $merge: Boolean) {\n    environmentStageChanges(environmentId: $environmentId, input: $input, merge: $merge) { id }\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"input\": {\"services\": {\"SERVICE_ID\": {\"isDeleted\": true}}}, \"merge\": true}'\nSCRIPT\n```\n\n## Stage and Apply Immediately\n\nFor single changes that should deploy right away, use `environmentPatchCommit` to stage and apply in one call.\n\n```graphql\nmutation environmentPatchCommit(\n  $environmentId: String!\n  $patch: EnvironmentConfig\n  $commitMessage: String\n) {\n  environmentPatchCommit(\n    environmentId: $environmentId\n    patch: $patch\n    commitMessage: $commitMessage\n  )\n}\n```\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation patchCommit($environmentId: String!, $patch: EnvironmentConfig, $commitMessage: String) {\n    environmentPatchCommit(environmentId: $environmentId, patch: $patch, commitMessage: $commitMessage)\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"patch\": {\"services\": {\"SERVICE_ID\": {\"variables\": {\"API_KEY\": {\"value\": \"secret\"}}}}}, \"commitMessage\": \"add API_KEY\"}'\nSCRIPT\n```\n\n**When to use:** Single change, no need to batch, user wants immediate deployment.\n\n**When NOT to use:** Multiple related changes to batch, or user says \"stage only\" \u002F \"don't deploy yet\".\n\n## Apply Staged Changes\n\nCommit staged changes and trigger deployments.\n\n**Note:** There is no `railway apply` CLI command. Use the mutation below or direct users to the web UI.\n\n### Apply Mutation\n\n**Mutation name: `environmentPatchCommitStaged`**\n\n```graphql\nmutation environmentPatchCommitStaged(\n  $environmentId: String!\n  $message: String\n  $skipDeploys: Boolean\n) {\n  environmentPatchCommitStaged(\n    environmentId: $environmentId\n    commitMessage: $message\n    skipDeploys: $skipDeploys\n  )\n}\n```\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation commitStaged($environmentId: String!, $message: String) {\n    environmentPatchCommitStaged(environmentId: $environmentId, commitMessage: $message)\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"message\": \"add API_KEY variable\"}'\nSCRIPT\n```\n\n### Parameters\n\n| Field           | Type    | Default | Description                                 |\n| --------------- | ------- | ------- | ------------------------------------------- |\n| `environmentId` | String! | -       | Environment ID from status                  |\n| `message`       | String  | null    | Short description of changes                |\n| `skipDeploys`   | Boolean | false   | Skip deploys (only if user explicitly asks) |\n\n### Commit Message\n\nKeep very short - one sentence max. Examples:\n\n- \"set build command to fix npm error\"\n- \"add API_KEY variable\"\n- \"increase replicas to 3\"\n\nLeave empty if no meaningful description.\n\n### Default Behavior\n\n**Always deploy** unless user explicitly asks to skip. Only set `skipDeploys: true` if user says \"apply without deploying\", \"commit but don't deploy\", or \"skip deploys\".\n\nReturns a workflow ID (string) on success.\n\n## Auto-Apply Behavior\n\nBy default, **apply changes immediately**.\n\n### Flow\n\n**Single change:** Use `environmentPatchCommit` to stage and apply in one call.\n\n**Multiple changes or batching:** Use `environmentStageChanges` with `merge: true` for each change, then `environmentPatchCommitStaged` to apply.\n\n### When NOT to Auto-Apply\n\n- User explicitly says \"stage only\", \"don't deploy yet\", or similar\n- User is making multiple related changes that should deploy together\n\n**When you don't auto-apply, tell the user:**\n\n> Changes staged. Apply them at: https:\u002F\u002Frailway.com\u002Fproject\u002F{projectId}\n> Or ask me to apply them.\n\nGet `projectId` from `railway status --json` → `project.id`\n\n## Error Handling\n\n### Service Not Found\n\n```\nService \"foo\" not found in project. Available services: api, web, worker\n```\n\n### No Staged Changes\n\n```\nNo patch to apply\n```\n\nThere are no staged changes to commit. Stage changes first.\n\n### Invalid Configuration\n\nCommon issues:\n\n- `buildCommand` and `startCommand` cannot be identical\n- `buildCommand` only valid with NIXPACKS builder\n- `dockerfilePath` only valid with DOCKERFILE builder\n\n### No Permission\n\n```\nYou don't have permission to modify this environment. Check your Railway role.\n```\n\n### No Linked Project\n\n```\nNo project linked. Run `railway link` to link a project.\n```\n\n## Composability\n\n- **Create service**: Use railway-service skill\n- **View logs**: Use railway-deployment skill\n- **Add domains**: Use railway-domain skill\n- **Deploy local code**: Use railway-deploy skill\n","# Environment Configuration\n\nQuery, stage, and apply configuration changes for Railway environments.\n\n## Shell Escaping\n\n**CRITICAL:** When running GraphQL queries via bash, you MUST wrap in heredoc to prevent shell escaping issues:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh 'query ...' '{\"var\": \"value\"}'\nSCRIPT\n```\n\nWithout the heredoc wrapper, multi-line commands break and exclamation marks in GraphQL non-null types get escaped, causing query failures.\n\n## When to Use\n\n- User wants to create a new environment\n- User wants to duplicate an environment (e.g., \"copy production to staging\")\n- User wants to switch to a different environment\n- User asks about current build\u002Fdeploy settings, variables, replicas, health checks, domains\n- User asks to change service source (Docker image, branch, commit, root directory)\n- User wants to connect a service to a GitHub repo\n- User wants to deploy from a GitHub repo (create empty service first via railway-new skill, then use this)\n- User asks to change build or start command\n- User wants to add\u002Fupdate\u002Fdelete environment variables\n- User wants to change replica count or configure health checks\n- User asks to delete a service, volume, or bucket\n- User says \"apply changes\", \"commit changes\", \"deploy changes\"\n- Auto-fixing build errors detected in logs\n\n## Create Environment\n\nCreate a new environment in the linked project:\n\n```bash\nrailway environment new \u003Cname>\n```\n\nDuplicate an existing environment:\n\n```bash\nrailway environment new staging --duplicate production\n```\n\nWith service-specific variables:\n\n```bash\nrailway environment new staging --duplicate production --service-variable api PORT=3001\n```\n\n## Switch Environment\n\nLink a different environment to the current directory:\n\n```bash\nrailway environment \u003Cname>\n```\n\nOr by ID:\n\n```bash\nrailway environment \u003Cenvironment-id>\n```\n\n## Get Context\n\n```bash\nrailway status --json\n```\n\nExtract:\n\n- `project.id` - for service lookup\n- `environment.id` - for the mutations\n- `service.id` - default service if user doesn't specify one\n\n### Resolve Service ID\n\nIf user specifies a service by name, query project services:\n\n```graphql\nquery projectServices($projectId: String!) {\n  project(id: $projectId) {\n    services {\n      edges {\n        node {\n          id\n          name\n        }\n      }\n    }\n  }\n}\n```\n\nMatch the service name (case-insensitive) to get the service ID.\n\n## Query Configuration\n\nFetch current environment configuration and staged changes.\n\n```graphql\nquery environmentConfig($environmentId: String!) {\n  environment(id: $environmentId) {\n    id\n    config(decryptVariables: false)\n    serviceInstances {\n      edges {\n        node {\n          id\n          serviceId\n        }\n      }\n    }\n  }\n  environmentStagedChanges(environmentId: $environmentId) {\n    id\n    patch(decryptVariables: false)\n  }\n}\n```\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'query envConfig($envId: String!) {\n    environment(id: $envId) { id config(decryptVariables: false) }\n    environmentStagedChanges(environmentId: $envId) { id patch(decryptVariables: false) }\n  }' \\\n  '{\"envId\": \"ENV_ID\"}'\nSCRIPT\n```\n\n### Response Structure\n\nThe `config` field contains current configuration:\n\n```json\n{\n  \"services\": {\n    \"\u003CserviceId>\": {\n      \"source\": { \"repo\": \"...\", \"branch\": \"main\" },\n      \"build\": { \"buildCommand\": \"npm run build\", \"builder\": \"NIXPACKS\" },\n      \"deploy\": {\n        \"startCommand\": \"npm start\",\n        \"multiRegionConfig\": { \"us-west2\": { \"numReplicas\": 1 } }\n      },\n      \"variables\": { \"NODE_ENV\": { \"value\": \"production\" } },\n      \"networking\": { \"serviceDomains\": {}, \"customDomains\": {} }\n    }\n  },\n  \"sharedVariables\": { \"DATABASE_URL\": { \"value\": \"...\" } }\n}\n```\n\nThe `patch` field in `environmentStagedChanges` contains pending changes. The effective configuration is the base `config` merged with the staged `patch`.\n\nFor complete field reference, see [reference\u002Fenvironment-config.md](..\u002Freference\u002Fenvironment-config.md).\n\nFor variable syntax and service wiring patterns, see [reference\u002Fvariables.md](..\u002Freference\u002Fvariables.md).\n\n## Get Rendered Variables\n\nThe GraphQL queries above return **unrendered** variables - template syntax like `${{shared.DOMAIN}}` is preserved. This is correct for management\u002Fediting.\n\nTo see **rendered** (resolved) values as they appear at runtime:\n\n```bash\n# Current linked service\nrailway variables --json\n\n# Specific service\nrailway variables --service \u003Cservice-name> --json\n```\n\n**When to use:**\n- Debugging connection issues (see actual URLs\u002Fports)\n- Verifying variable resolution is correct\n- Viewing Railway-injected values (RAILWAY_*)\n\n## Stage Changes\n\nStage configuration changes via the `environmentStageChanges` mutation. Use `merge: true` to automatically merge with existing staged changes.\n\n```graphql\nmutation stageEnvironmentChanges(\n  $environmentId: String!\n  $input: EnvironmentConfig!\n  $merge: Boolean\n) {\n  environmentStageChanges(\n    environmentId: $environmentId\n    input: $input\n    merge: $merge\n  ) {\n    id\n  }\n}\n```\n\n**Important:** Always use variables (not inline input) because service IDs are UUIDs which can't be used as unquoted GraphQL object keys.\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation stageChanges($environmentId: String!, $input: EnvironmentConfig!, $merge: Boolean) {\n    environmentStageChanges(environmentId: $environmentId, input: $input, merge: $merge) { id }\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"input\": {\"services\": {\"SERVICE_ID\": {\"build\": {\"buildCommand\": \"npm run build\"}}}}, \"merge\": true}'\nSCRIPT\n```\n\n### Delete Service\n\nUse `isDeleted: true`:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation stageChanges($environmentId: String!, $input: EnvironmentConfig!, $merge: Boolean) {\n    environmentStageChanges(environmentId: $environmentId, input: $input, merge: $merge) { id }\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"input\": {\"services\": {\"SERVICE_ID\": {\"isDeleted\": true}}}, \"merge\": true}'\nSCRIPT\n```\n\n## Stage and Apply Immediately\n\nFor single changes that should deploy right away, use `environmentPatchCommit` to stage and apply in one call.\n\n```graphql\nmutation environmentPatchCommit(\n  $environmentId: String!\n  $patch: EnvironmentConfig\n  $commitMessage: String\n) {\n  environmentPatchCommit(\n    environmentId: $environmentId\n    patch: $patch\n    commitMessage: $commitMessage\n  )\n}\n```\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation patchCommit($environmentId: String!, $patch: EnvironmentConfig, $commitMessage: String) {\n    environmentPatchCommit(environmentId: $environmentId, patch: $patch, commitMessage: $commitMessage)\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"patch\": {\"services\": {\"SERVICE_ID\": {\"variables\": {\"API_KEY\": {\"value\": \"secret\"}}}}}, \"commitMessage\": \"add API_KEY\"}'\nSCRIPT\n```\n\n**When to use:** Single change, no need to batch, user wants immediate deployment.\n\n**When NOT to use:** Multiple related changes to batch, or user says \"stage only\" \u002F \"don't deploy yet\".\n\n## Apply Staged Changes\n\nCommit staged changes and trigger deployments.\n\n**Note:** There is no `railway apply` CLI command. Use the mutation below or direct users to the web UI.\n\n### Apply Mutation\n\n**Mutation name: `environmentPatchCommitStaged`**\n\n```graphql\nmutation environmentPatchCommitStaged(\n  $environmentId: String!\n  $message: String\n  $skipDeploys: Boolean\n) {\n  environmentPatchCommitStaged(\n    environmentId: $environmentId\n    commitMessage: $message\n    skipDeploys: $skipDeploys\n  )\n}\n```\n\nExample:\n\n```bash\nbash \u003C\u003C'SCRIPT'\n${CLAUDE_PLUGIN_ROOT}\u002Fskills\u002Flib\u002Frailway-api.sh \\\n  'mutation commitStaged($environmentId: String!, $message: String) {\n    environmentPatchCommitStaged(environmentId: $environmentId, commitMessage: $message)\n  }' \\\n  '{\"environmentId\": \"ENV_ID\", \"message\": \"add API_KEY variable\"}'\nSCRIPT\n```\n\n### Parameters\n\n| Field           | Type    | Default | Description                                 |\n| --------------- | ------- | ------- | ------------------------------------------- |\n| `environmentId` | String! | -       | Environment ID from status                  |\n| `message`       | String  | null    | Short description of changes                |\n| `skipDeploys`   | Boolean | false   | Skip deploys (only if user explicitly asks) |\n\n### Commit Message\n\nKeep very short - one sentence max. Examples:\n\n- \"set build command to fix npm error\"\n- \"add API_KEY variable\"\n- \"increase replicas to 3\"\n\nLeave empty if no meaningful description.\n\n### Default Behavior\n\n**Always deploy** unless user explicitly asks to skip. Only set `skipDeploys: true` if user says \"apply without deploying\", \"commit but don't deploy\", or \"skip deploys\".\n\nReturns a workflow ID (string) on success.\n\n## Auto-Apply Behavior\n\nBy default, **apply changes immediately**.\n\n### Flow\n\n**Single change:** Use `environmentPatchCommit` to stage and apply in one call.\n\n**Multiple changes or batching:** Use `environmentStageChanges` with `merge: true` for each change, then `environmentPatchCommitStaged` to apply.\n\n### When NOT to Auto-Apply\n\n- User explicitly says \"stage only\", \"don't deploy yet\", or similar\n- User is making multiple related changes that should deploy together\n\n**When you don't auto-apply, tell the user:**\n\n> Changes staged. Apply them at: https:\u002F\u002Frailway.com\u002Fproject\u002F{projectId}\n> Or ask me to apply them.\n\nGet `projectId` from `railway status --json` → `project.id`\n\n## Error Handling\n\n### Service Not Found\n\n```\nService \"foo\" not found in project. Available services: api, web, worker\n```\n\n### No Staged Changes\n\n```\nNo patch to apply\n```\n\nThere are no staged changes to commit. Stage changes first.\n\n### Invalid Configuration\n\nCommon issues:\n\n- `buildCommand` and `startCommand` cannot be identical\n- `buildCommand` only valid with NIXPACKS builder\n- `dockerfilePath` only valid with DOCKERFILE builder\n\n### No Permission\n\n```\nYou don't have permission to modify this environment. Check your Railway role.\n```\n\n### No Linked Project\n\n```\nNo project linked. Run `railway link` to link a project.\n```\n\n## Composability\n\n- **Create service**: Use railway-service skill\n- **View logs**: Use railway-deployment skill\n- **Add domains**: Use railway-domain skill\n- **Deploy local code**: Use railway-deploy skill\n",{"name":5,"license":15,"metadata":53,"description":7,"allowed-tools":64},{"tags":54,"author":29,"version":61,"dependencies":62},[29,55,56,36,57,58,59,60],"Environment","Configuration","Build","Deploy","Infrastructure","Settings","1.0.0",[63],"railway-cli","Bash(railway:*)","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fenvironment",3911,"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 21:38:31",{"source":8,"skillName":5,"commands":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add davila7\u002Fclaude-code-templates --skill railway-environment",{"tool":81,"command":82},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill railway-environment",{"tool":84,"command":85},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill railway-environment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Frailway\u002Fenvironment\u002FSKILL.md",true,[],[90,116,143,175,210,234],{"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":6,"sourceHtmlUrl":94,"categories":95,"keywords":97,"publishedAt":48},"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",[96],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[98,99,100,101,102,34,103,104,41,105,106,107,108,109,110,111,112,113,114,115],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":123,"publishedAt":48},"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",[122],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[124,125,126,127,128,129,130,131,132,133,134,105,135,136,137,138,139,140,141,142],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":158,"publishedAt":48},"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",[149,152,153],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[159,160,161,162,163,164,165,34,166,167,168,169,170,171,172,41,173,174,105,39],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":179,"licenseFileUrl":180,"sourceHtmlUrl":181,"categories":182,"keywords":186,"publishedAt":48},"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",[183],{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,208,34,209],"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":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":179,"licenseFileUrl":214,"sourceHtmlUrl":215,"categories":216,"keywords":221,"publishedAt":48},"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",[217,220],{"categoryNo":218,"categoryName":219,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":184,"categoryName":185,"taxonomyType":21,"taxonomyTypeDesc":22},[222,223,224,225,226,188,227,197,198,228,229,230,231,34,232,107,233],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":179,"licenseFileUrl":238,"sourceHtmlUrl":239,"categories":240,"keywords":248,"publishedAt":48},"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",[241,244,245],{"categoryNo":242,"categoryName":243,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":246,"categoryName":247,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000036","内容创作者",[249,250,251,252,253,254,255,256,190,257,200,135,258,259,260,261,262,171,263,105,264,265,266,267,268,113,269],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]