CtrlK
BlogDocsLog inGet started
Tessl Logo

pantheon-ai/troubleshoot

Search-first troubleshooting with a diagnostic phase — use when an error, bug, or unexpected behaviour is reported.

75

Quality

75%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

search-multi-source.mdreferences/protocols/

Search Protocol

Multi-source search before investigating. 80% of bugs already solved online.

Query Construction

[exact error message] [stack] [framework] [version]

Strip paths, keep error text. Add context keywords.

Sources (in order)

SourceBest forQuery tip
Stack OverflowCommon errors, how-tosite:stackoverflow.com
GitHub IssuesLibrary-specific bugssite:github.com [repo] issues
Official DocsConfig, API usagesite:[framework].dev or site:[docs-url]
RedditWeird edge cases, opinionssite:reddit.com r/[language]

Workflow

  1. WebSearch with constructed query
  2. Scan titles for exact match to symptom
  3. WebFetch top 2-3 promising results
  4. Extract solution or keywords for next search

No Results?

SituationAction
Zero hitsBroaden query (remove version, simplify error)
Hits but wrong contextAdd stack/framework to query
Outdated answersAdd year: [query] 2024 2025
Too genericAdd specific error code or function name

Solution Found?

If solution found → verify it applies to user's context → skip to Learn phase

If partial match → extract keywords → refine search → try again (max 3 iterations)

If nothing after 3 searches → move to Qualify phase

references

protocols

diagnose.md

search-multi-source.md

reference.md

troubleshoot-to-frame-problem-llm.md

SKILL.md

tile.json