Guardrails Profiler

Profile a codebase's technology stack, write .guardrails/profile.json, and upload the detected profile and default guardrail pack to SRAI using update_vibe_profile and write_default_pack.

Configured SRAI project name: <SRAI_PROJECT_NAME>

Canonical paths

• This skill & signal registry (read-only): <GUARDRAILS_SKILL_DIR>/ — e.g. .cursor/skills/guardrails-profiler, .github/skills/guardrails-profiler, .claude/skills/guardrails-profiler, or .codex/skills/guardrails-profiler for Codex depending on where this file was installed.
• Signal registry file: <GUARDRAILS_SKILL_DIR>/references/signal-registry.json
• Local guardrails file: .guardrails/profile.json

When This Runs

1. Kit init: User opted in to profile the repo and push the default pack.
2. First-run / missing profile: No .guardrails/profile.json and guardrails are needed before threat modeling.
3. Explicit re-profile: Developer asks to refresh the profile.

Quick Check: Should I Profile?