stac-troubleshooter
Automates diagnostic checks for Stac projects to resolve build, deploy, and runtime errors.
Install
mkdir -p .claude/skills/stac-troubleshooter && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7135" && unzip -o skill.zip -d .claude/skills/stac-troubleshooter && rm skill.zipInstalls to .claude/skills/stac-troubleshooter
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.Key capabilities
- →Perform baseline diagnostic checks on Stac builds
- →Validate build output against expected directories
- →Triage errors using dedicated playbooks
- →Provide verification steps for applied fixes
How it works
Runs specialized diagnostic Python scripts that verify system state and compare findings against error-pattern playbooks.
Inputs & outputs
When to use stac-troubleshooter
- →Fixing Stac build errors
- →Debugging deployment mismatches
- →Resolving navigation issues
About stac-troubleshooter
Runs structured scripts to identify configuration mismatches, cache staleness, or migration issues in Stac projects. Provides fix commands and verification steps.
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.
When not to use it
- →Debugging non-Stac architecture frameworks
- →Manual code fixes without tool verification
Prerequisites
Limitations
- →Fixes are specific to the Stac ecosystem
- →Requires valid project structure for scripts to run
How it compares
It uses repeatable diagnostic scripts to ensure consistent fixes rather than relying on LLM guesswork.
Compared to similar skills
stac-troubleshooter side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| stac-troubleshooter (this skill) | 1 | 6mo | Review | Intermediate |
| vercel-advanced-troubleshooting | 3 | 27d | Caution | Advanced |
| replit-incident-runbook | 0 | 27d | Caution | Intermediate |
| analyzing-logs | 14 | 27d | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by StacDev
View all by StacDev →You might also like
vercel-advanced-troubleshooting
jeremylongshore
Execute apply Vercel advanced debugging techniques for hard-to-diagnose issues. Use when standard troubleshooting fails, investigating complex race conditions, or preparing evidence bundles for Vercel support escalation. Trigger with phrases like "vercel hard bug", "vercel mystery error", "vercel impossible to debug", "difficult vercel issue", "vercel deep debug".
replit-incident-runbook
jeremylongshore
Execute Replit incident response procedures with triage, mitigation, and postmortem. Use when responding to Replit-related outages, investigating errors, or running post-incident reviews for Replit integration failures. Trigger with phrases like "replit incident", "replit outage", "replit down", "replit on-call", "replit emergency", "replit broken".
analyzing-logs
jeremylongshore
Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.
sentry
openai
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
obsidian-incident-runbook
jeremylongshore
Troubleshoot Obsidian plugin failures with systematic incident response. Use when plugins crash, data is corrupted, or users report critical issues with your Obsidian plugin. Trigger with phrases like "obsidian crash", "obsidian plugin broken", "obsidian incident", "debug obsidian failure", "obsidian emergency".
obsidian-observability
jeremylongshore
Set up comprehensive logging and monitoring for Obsidian plugins. Use when implementing debug logging, tracking plugin performance, or setting up error reporting for your Obsidian plugin. Trigger with phrases like "obsidian logging", "obsidian monitoring", "obsidian debug", "track obsidian plugin".