agentleFS
friuns2friuns2/openclaw-android-assistant/skills/oracle/SKILL.md

oracle

Skill573 starsChanged 39 days agoMITView on GitHub

Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.

  • Reads credentials

59 other projects use a version of this, 29 of them edited; 28 of 28 edited versions we compared changed its rules.

How people change it

28 of 28 edited versions changed its rules, and some changes recur.

Of the 28 edited versions we compared: 28 made changes of their own.

Rules people drop

  1. Use browser mode for long Pro thinking; API mode for explicit API calls.dropped by 28 of 28
  2. If the run detaches/timeouts: reattach to the stored session. Do not blindly re-run.dropped by 28 of 28
  3. Leave .env, key files, and auth tokens out of attachments unless the user asks to include them.dropped by 28 of 28
  4. If the binary isn't installed: npx -y @steipete/oracle --help (avoid pnpx here; sqlite bindings).dropped by 4 of 28
  5. Does not follow symlinks.dropped by 4 of 28

Rules people add

  1. Default workflow here: --engine browser with GPT‑5.2 Pro in ChatGPT. This is the common “long think” path: ~10 minutes to ~1 hour is normal; expect a stored session you can reattach to.added by 28 of 28
  2. Use browser mode for the usual GPT‑5.2 Pro workflow; use API only when you explicitly want it.added by 28 of 28
  3. If the run detaches/timeouts: reattach to the stored session (don’t re-run).added by 28 of 28
  4. Does not follow symlinks (glob expansion uses followSymbolicLinks: false).added by 4 of 28
  5. Use --files-report (and/or --dry-run json) to spot the token hogs before spending.added by 4 of 28
  6. If you need hidden/advanced knobs: npx -y @steipete/oracle --help --verbose.added by 4 of 28
  7. API runs require explicit user consent before starting because they incur usage costs.added by 4 of 28
  8. When you know this will be a long investigation, write a prompt that can stand alone later:added by 4 of 28

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, BlueBubbles and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • jiulingyunSkill

    BlueBubbles

    为Clawdbot构建或更新BlueBubbles外部通道插件(扩展包,REST发送/探测,webhook入站)。

    Also in 18 projects that use this

  • hkyutongSkill

    openclaw-release-maintainer

    Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

    Also in 4 projects that use this

  • seedprodSkill

    voice-call

    Start voice calls via the OpenClaw voice-call plugin.

    Also in 17 projects that use this

  • seedprodSkill

    food-order

    Reorder Foodora orders + track ETA/status with ordercli. Never confirm without explicit user approval. Triggers: order food, reorder, track ETA.

    Also in 5 projects that use this

  • AtomicBot-aiSkill

    taskflow

    Also in 6 projects that use this

  • +2 more from seedprod

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use browser mode for long Pro thinking.

    line 43
  2. Distinctive:

    If the run detaches/timeouts: reattach to the stored session.

    line 44
  3. Very specific:

    If the binary isn't installed: npx -y @steipete/oracle --help (avoid pnpx here.

    line 50
  4. Very specific:

    Default-ignored dirs: node_modules, dist, coverage, .git, .turbo, .next, build, tmp (skipped unless explicitly passed as literal …

    line 79
  5. Distinctive:

    Does not follow symlinks.

    line 81
  6. Very specific:

    Use --slug "<3-5 words>" to keep session IDs readable.

    line 101
  7. Very specific:

    Leave .env, key files, and auth tokens out of attachments unless the user asks to include them.

    line 116

“Common” is measured: kept by at least 6 in 10 of the 49 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

oracle

Oracle bundles a prompt + selected files for one second-model pass. Treat output as advisory; verify against code + tests.

Main path

Current CLI default model: gpt-5.5-pro. Browser engine is useful for long ChatGPT Pro runs; API engine is useful when OPENAI_API_KEY or Azure config is ready.

Recommended defaults:

  • Preview first: --dry-run summary --files-report
  • Browser long run: --engine browser --model gpt-5.5-pro
  • API explicit: --engine api --model gpt-5.5

Golden path

  1. Pick a tight file set (fewest files that still contain the truth).
  2. Preview payload + token spend (--dry-run + --files-report).
  3. Use browser mode for long Pro thinking; API mode for explicit API calls.
  4. If the run detaches/timeouts: reattach to the stored session. Do not blindly re-run.

Commands (preferred)

  • Help:
    • oracle --help
    • If the binary isn't installed: npx -y @steipete/oracle --help (avoid pnpx here; sqlite bindings).
  • Preview (no tokens):
    • oracle --dry-run summary -p "<task>" --file "src/**" --file "!**/*.test.*"
    • oracle --dry-run full -p "<task>" --file "src/**"
  • Token sanity:
    • oracle --dry-run summary --files-report -p "<task>" --file "src/**"
  • Browser run (main path; long-running is normal):
    • oracle --engine browser --model gpt-5.5-pro -p "<task>" --file "src/**"
  • Manual paste fallback:
    • oracle --render --copy -p "<task>" --file "src/**"
    • Note: --copy is a hidden alias for --copy-markdown.

Attaching files (--file)

--file accepts files, directories, and globs. You can pass it multiple times; entries can be comma-separated.

  • Include:
    • --file "src/**"
    • --file src/index.ts
    • --file docs --file README.md
  • Exclude:
    • --file "src/**" --file "!src/**/*.test.ts" --file "!**/*.snap"
  • Defaults (implementation behavior):
    • Default-ignored dirs: node_modules, dist, coverage, .git, .turbo, .next, build, tmp (skipped unless explicitly passed as literal dirs/files).
    • Honors .gitignore when expanding globs.
    • Does not follow symlinks.
    • Dotfiles filtered unless opted in via pattern (e.g. --file ".github/**").
    • Files > 1 MB rejected.

Engines (API vs browser)

  • Auto-pick: api when OPENAI_API_KEY is set; otherwise browser.
  • Browser supports GPT + Gemini only; use --engine api for Claude/Grok/Codex or multi-model runs.
  • Browser attachments:
    • --browser-attachments auto|never|always (auto pastes inline up to ~60k chars then uploads).
  • Remote browser host:
    • Host: oracle serve --host 0.0.0.0 --port 9473 --token <secret>
    • Client: oracle --engine browser --remote-host <host:port> --remote-token <secret> -p "<task>" --file "src/**"

Sessions + slugs

  • Stored under ~/.oracle/sessions (override with ORACLE_HOME_DIR).
  • Runs may detach or take a long time (browser + Pro often does). If the CLI times out: do not re-run; reattach.
    • List: oracle status --hours 72
    • Attach: oracle session <id> --render
  • Use --slug "<3-5 words>" to keep session IDs readable.
  • Duplicate prompt guard exists; use --force only when you truly want a fresh run.

Prompt template (high signal)

Oracle starts with zero project knowledge. Assume the model cannot infer your stack, build tooling, conventions, or "obvious" paths. Include:

  • Project briefing (stack + build/test commands + platform constraints).
  • "Where things live" (key directories, entrypoints, config files, boundaries).
  • Exact question + what you tried + the error text (verbatim).
  • Constraints ("don't change X", "must keep public API", etc).
  • Desired output ("return patch plan + tests", "give 3 options with tradeoffs").

Attachments

  • Leave .env, key files, and auth tokens out of attachments unless the user asks to include them.

"Exhaustive prompt" restoration pattern

For long investigations, write a standalone prompt + file set so you can rerun days later:

  • 6-30 sentence project briefing + the goal.
  • Repro steps + exact errors + what you tried.
  • Attach all context files needed (entrypoints, configs, key modules, docs).

Oracle runs are one-shot; the model doesn't remember prior runs. "Restoring context" means re-running with the same prompt + --file … set (or reattaching a still-running stored session).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.