service_skill
- Shell
- Official
79
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill railwayapp/railway-skills --skill service- SKILL.md6.4 KB
Overview
This skill manages Railway services: check service status, rename or update icons, link services, and create services using Docker images. It focuses on service-level operations and integrates with the GraphQL API for create and update mutations. For local-code service creation or GitHub sources, it defers to the appropriate skills for a complete flow.
How this skill works
It inspects project and environment context from railway status output to identify projectId, environmentId, and service IDs. It uses GraphQL mutations (serviceCreate and serviceUpdate) to create services or update properties and relies on the environment skill to configure and apply instance-level settings. For Docker-image services, provide source.image during creation; for GitHub repos, create an empty service then configure source via staged environment changes.
When to use it
- To check a service's current deployment status, health, or recent deployments
- To rename a service or change its icon (image URL, GIF, or devicons)
- To switch or link the service for the current directory with railway service link
- To create a new service that runs a Docker image (advanced scenarios)
- To prepare an empty service before configuring a GitHub repo source via environment changes
Best practices
- Use railway status --json to extract project.id, environment.id, and service.id before API calls
- Prefer the new skill for creating services from local code; this skill is for service-level operations
- Never create a GitHub-backed service directly with serviceCreate.source.repo; create empty service then configure via environment
- Always include isCreated: true when adding a new service instance in environment staged changes
- Check permission level (DEVELOPER or higher) before creating services and validate Docker image accessibility
Example use cases
- Create an empty service in a project by calling the serviceCreate mutation with projectId
- Create a service that runs nginx by providing source.image: nginx:latest in the create mutation
- Rename an existing service by running serviceUpdate with the service ID and new name
- Update a service icon to a devicon URL (https://devicons.railway.app/github) using serviceUpdate
- Link the current directory to a service using railway service link or specify the service name directly
FAQ
No. Create an empty service with serviceCreate, then configure the repo source using the environment skill and staged changes API.
How do I deploy a Docker image as a service?
Provide source.image in the ServiceCreateInput when calling the serviceCreate mutation, then configure instance variables and apply changes with the environment skill.