Add, view, or remove domains for Railway services.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrailway-domainExecute the skills CLI command in your project's root directory to begin installation:
Fetches railway-domain from davila7/claude-code-templates 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 railway-domain. Access via /railway-domain 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
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
24.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
24.2K
stars
Add, view, or remove domains for Railway services.
Generate a railway-provided domain (max 1 per service):
railway domain --json
For a specific service:
railway domain --json --service backend
Returns the generated domain URL. Service must have a deployment.
railway domain example.com --json
Returns required DNS records:
{
"domain": "example.com",
"dnsRecords": [
{ "type": "CNAME", "host": "@", "value": "..." }
]
}
Tell user to add these records to their DNS provider.
Use railway-environment skill to see configured domains, or query directly:
query domains($envId: String!) {
environment(id: $envId) {
config(decryptVariables: false)
}
}
Domains are in config.services.<serviceId>.networking:
serviceDomains - Railway-provided domainscustomDomains - User-provided domainsUse railway-environment skill to remove domains:
{
"services": {
"<serviceId>": {
"networking": {
"customDomains": { "<domainId>": null }
}
}
}
}
{
"services": {
"<serviceId>": {
"networking": {
"serviceDomains": { "<domainId>": null }
}
}
}
}
Then use railway-environment skill to apply and commit the change.
| Flag | Description |
|---|---|
[DOMAIN] |
Custom domain to add (omit for railway domain) |
-p, --port <PORT> |
Port to connect |
-s, --service <NAME> |
Target service (defaults to linked) |
--json |
JSON output |
No service linked. Use --service flag or run `railway service` to select one.
Service already has a railway-provided domain. Maximum 1 per service.
Service has no deployment. Deploy first with `railway up`.
Invalid domain format. Use a valid domain like "example.com" or "api.example.com".
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
davila7/claude-code-templates
railway-domain fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for railway-domain matched our evaluation — installs cleanly and behaves as described in the markdown.
railway-domain is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
railway-domain has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: railway-domain is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: railway-domain is focused, and the summary matches what you get after install.
railway-domain has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in railway-domain — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend railway-domain for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
railway-domain reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 53