Create, rename, and manage services; check deployment status and health.
Works with
Check service status, deployment history, and health via CLI commands returning JSON
Create services with Docker images or empty (GitHub repos configured via environment skill)
Rename services and update icons using GraphQL mutations; supports image URLs, animated GIFs, and Railway Devicons
Link or switch between services in the current directory with railway service link
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionserviceExecute the skills CLI command in your project's root directory to begin installation:
Fetches service from railwayapp/railway-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate service. Access via /service in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
225
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
225
stars
Check status, update properties, and advanced service creation.
Note: For creating services with local code (the common case), prefer the new skill which handles project setup, scaffolding, and service creation together.
For GitHub repo sources: Use new skill to create empty service, then environment skill to configure source.repo via staged changes API.
Create a new service via GraphQL API. There is no CLI command for this.
railway status --json
Extract:
project.id - for creating the serviceenvironment.id - for staging the instance configmutation serviceCreate($input: ServiceCreateInput!) {
serviceCreate(input: $input) {
id
name
}
}
| Field | Type | Description |
|---|---|---|
projectId |
String! | Project ID (required) |
name |
String | Service name (auto-generated if omitted) |
source.image |
String | Docker image (e.g., nginx:latest) |
source.repo |
String | GitHub repo (e.g., user/repo) |
branch |
String | Git branch for repo source |
environmentId |
String | If set and is a fork, only creates in that env |
bash <<'SCRIPT'
scripts/railway-api.sh \
'mutation createService($input: ServiceCreateInput!) {
serviceCreate(input: $input) { id name }
}' \
'{"input": {"projectId": "PROJECT_ID"}}'
SCRIPT
bash <<'SCRIPT'
scripts/railway-api.sh \
'mutation createService($input: ServiceCreateInput!) {
serviceCreate(input: $input) { id name }
}' \
'{"input": {"projectId": "PROJECT_ID", "name": "my-service", "source": {"image": "nginx:latest"}}}'
SCRIPT
Do NOT use serviceCreate with source.repo - use staged changes API instead.
Flow:
serviceCreate(input: {projectId: "...", name: "my-service"})environment skill to configure source via staged changes APIUse environment skill to configure the service instance:
{
"services": {
"<serviceId>": {
"isCreated": true,
"source": { "image": "nginx:latest" },
"variables": {
"PORT": { "value": "8080" }
}
}
}
}
Critical: Always include isCreated: true for new service instances.
Then use environment skill to apply and deploy.
For variable references, see reference/variables.md.
railway service status --json
Returns current deployment status for the linked service.
railway deployment list --json --limit 5
Show:
| Status | Meaning |
|---|---|
| SUCCESS | Deployed and running |
| FAILED | Build or deploy failed |
| DEPLOYING | Currently deploying |
| BUILDING | Build in progress |
| CRASHED | Runtime crash |
| REMOVED | Deployment removed |
Update service name or icon via GraphQL API.
railway status --json
Extract service.id from the response.
bash <<'SCRIPT'
scripts/railway-api.sh \
'mutation updateService($id: String!, $input: ServiceUpdateInput!) {
serviceUpdate(id: $id, input: $input) { id name }
}' \
'{"id": "SERVICE_ID", "input": {"name": "new-name"}}'
SCRIPT
Icons can be image URLs or animated GIFs.
| Type | Example |
|---|---|
| Image URL | "icon": "https://example.com/logo.png" |
| Animated GIF | "icon": "https://example.com/animated.gif" |
| Devicons | "icon": "https://devicons.railway.app/github" |
Railway Devicons: Query https://devicons.railway.app/{query} for common developer icons (e.g., github, postgres, redis, nodejs). Browse all at https://devicons.railway.app
bash <<'SCRIPT'
scripts/railway-api.sh \
'mutation updateService($id: String!, $input: ServiceUpdateInput!) {
serviceUpdate(id: $id, input: $input) { id icon }
}' \
'{"id": "SERVICE_ID", "input": {"icon": "https://devicons.railway.app/github"}}'
SCRIPT
| Field | Type | Description |
|---|---|---|
name |
String | Service name |
icon |
String | Emoji or image URL (including animated GIFs) |
Switch the linked service for the current directory:
railway service link
Or specify directly:
railway service link <service-name>
new skill (handles scaffolding + creation)environment skill (variables, commands, image, etc.)environment skill with isDeleted: trueenvironment skilldeployment skilldeploy skillNo service linked. Run `railway service link` to link a service.
Service exists but has no deployments yet. Deploy with `railway up`.
Service "foo" not found. Check available services with `railway status`.
User may not be in a linked project. Check railway status.
User needs at least DEVELOPER role to create services.
Docker image must be accessible (public or with registry credentials).
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in service — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
service reduced setup friction for our internal harness; good balance of opinion and flexibility.
service is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added service from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for service matched our evaluation — installs cleanly and behaves as described in the markdown.
service fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: service is the kind of skill you can hand to a new teammate without a long onboarding doc.
service is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
service has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 67