rudder-profiles-debuglisted
Install: claude install-skill rudderlabs/rudder-agent-skills
# RudderStack Profiles Debugging
Debug Profiles errors with a structured loop: classify, fix, validate, and stop before thrashing.
## Workflow
1. **Classify the error** — Match the error output against the classification table below.
2. **Apply the smallest plausible fix** — One change, then re-validate.
3. **Re-run `pb compile`** (for compile errors) or the precise recovery command (for run failures).
4. **Escalate progressively** — If the first fix doesn't work:
- 2nd attempt: consult `search_profiles_docs()` for relevant documentation.
- 3rd attempt: read documentation examples and reference files.
- 4th attempt: **STOP** — present all findings to the user and ask for guidance.
5. Never attempt more than 4 fix cycles without user input.
## Error Classification
| Error Pattern | Category | First Action |
|---------------|----------|-------------|
| `unmarshal`, `field not found`, parser line/col | YAML Structure | Check `references/common-yaml-mistakes.md`; inspect the referenced YAML section |
| `id type X not found` | Cross-File Reference | Verify id_type names match between `pb_project.yaml` and `models/` files |
| `model X not found` | Model Dependency | Run `pb show models`; check `from:` paths and model names |
| `invalid identifier`, `column not found` | SQL/Warehouse | Call `describe_table()` to verify the column exists |
| `does not match time regex` | CLI Usage | Use ISO 8601 format: `YYYY-MM-DDTHH:MM:SSZ` |
| `schema_version not supported` | Version