Agent skill
consult-oracle
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches. Use when stuck on a very hard problem, when standard approaches have failed, when multiple debugging attempts haven't worked, or when the user says "ask the oracle", "consult oracle", "consult chatgpt", "I'm completely stuck", "I've tried everything", or "nothing is working".
Install this agent skill to your Project
npx add-skill https://github.com/tobihagemann/turbo/tree/main/skills/consult-oracle
SKILL.md
Consult Oracle
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
Configuration
The oracle reads from ~/.turbo/config.json:
{
"oracle": {
"chatgptUrl": "https://chatgpt.com/",
"chromeProfile": "Default"
}
}
| Key | Purpose | Default |
|---|---|---|
chatgptUrl |
ChatGPT URL (e.g., a custom GPT project URL) | https://chatgpt.com/ |
chromeProfile |
Chrome profile directory name | Default |
Step 1: Refresh Cookies
Before running the oracle, refresh ChatGPT cookies from Chrome. Requires timeout of 60000ms. A macOS Keychain password prompt will appear for the user.
python3 scripts/refresh_cookies.py
If the script reports session validation failure, the user needs to log into ChatGPT in Chrome first.
Step 2: Identify Key Files
Find the 2-5 files most relevant to the problem.
Step 3: Formulate the Question
Write a clear, specific problem description. Include what has already been tried and why it failed. Open with a short project briefing (stack, services, build steps). The more context, the better the response.
Step 4: Run the Oracle
Use a generous timeout (60 minutes / 3600000ms). The script loads chatgptUrl from ~/.turbo/config.json automatically. Generate a random tag and persist the response:
ORACLE_TAG=$(head -c 4 /dev/urandom | xxd -p) && mkdir -p .turbo/oracle
python3 scripts/run_oracle.py --prompt "<problem description>" --file <relevant files...> --write-output ".turbo/oracle/$ORACLE_TAG.txt"
Step 5: Run /evaluate-findings Skill
Read the response from .turbo/oracle/$ORACLE_TAG.txt. Run the /evaluate-findings skill on it. Oracle suggestions are starting points — cross-reference with official docs and peer open-source implementations before accepting.
Step 6: Run /apply-findings Skill
Run the /apply-findings skill on the evaluated results.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
review-api-usage
Check API, library, and framework usage in code against official documentation and installed skill knowledge. Flags deprecated APIs, incorrect method signatures, wrong parameter types, version-incompatible patterns, and best-practice violations. Use when the user asks to "review API usage", "check API usage", "verify against docs", "check library usage", "validate API calls", "check against documentation", or "check for deprecated APIs".
resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts). Use when the user asks to "resolve PR comments", "fix review comments", "address PR feedback", "handle review comments", "address review feedback", "respond to PR comments", "answer review questions", or "address code review".
consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving. Use when the user asks to "consult codex", "ask codex", "get codex's opinion", "brainstorm with codex", "discuss with codex", or "chat with codex".
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev infrastructure", or "tooling audit".
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
Didn't find tool you were looking for?