OpenParable
Skip to content
← Back to skills

Stac Troubleshooter

Testing & Quality
stac-troubleshooter

Stac Troubleshooter is an Agent Skill for testing & quality published in the StacDev/stac repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Diagnose Stac build, deploy, rendering, caching, and navigation issues using repeatable checks. Use when users report stac build finding no screens, deploy mismatches, runtime unknown widget/action errors, cache staleness, or migration regressions.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/StacDev/stac/blob/HEAD/skills/stac-troubleshooter/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/stac-troubleshooter, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Stac Troubleshooter

Overview

Use this skill to run structured diagnostics and return precise fixes for Stac project issues.

Workflow

  1. Run scripts/stac_doctor.py --project-root <path> for baseline checks.
  2. Run scripts/check_build_outputs.py --project-root <path> --expected-dir stac/.build.
  3. Triage using focused playbooks under references/.
  4. Return root cause, fix commands, and post-fix verification steps.

Required Inputs

  • Project root path.
  • Failing command and output (if available).
  • Affected route/screen name (if runtime issue).

Output Contract

  • Classify issue as setup/build/deploy/runtime/cache/navigation.
  • Provide exact remedial commands and expected outcomes.
  • Include one verification command or file check per fix.

References

  • Read references/error-playbooks.md for common Stac errors and fixes.
  • Read references/cache-debug.md for stale content and cache strategy checks.
  • Read references/navigation-debug.md for route/action stack behavior.
  • Read references/migration-cheatsheet.md for JSON-to-Dart migration mapping.
  • Read references/known-gotchas.md for recurring pitfalls.

Scripts

  • scripts/stac_doctor.py --project-root <path> [--json]
  • scripts/check_build_outputs.py --project-root <path> --expected-dir stac/.build