Individual skill
railway-exposure-audit
Audit a Railway deployment's public domains, TCP proxies, private networking, service bindings, trust boundaries, and repository configuration for accidental exposure without dumping variables, logs, credentials, or provider configuration.
skills/railway-exposure-audit/SKILL.md
Source commit e17f9081b1b1746a837bb188f6ef3245d720fc4b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 13
- Repository last updated
- Nov 1, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- accessibility Repository topic
- claude-code Repository topic
- code-review Repository topic
- core-web-vitals Repository topic
- playwright Repository topic
- privacy Repository topic
- qa Repository topic
- quality-assurance Repository topic
- security Repository topic
- seo Repository topic
- devops Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,393 bytes
Read excerpt
# Railway Exposure Audit
Map what a Railway deployment exposes and whether each boundary is intentional and protected. Public reachability, weak protection, vulnerability, and compromise are separate conclusions.
## Prerequisites
- A local repository and, when available, a user-supplied Railway project or deployment view.
- Current access to Railway's official networking documentation for platform semantics.
- Optional read-only provider access. The repository-only path must still produce useful results and explicit verification gaps.
## Trigger
- "Audit our Railway exposure"
- "Is our Railway database or Redis public?"