CtrlK
BlogDocsLog inGet started
Tessl Logo

oracle

Oracle second-model review: bundle prompts/files, debug, refactor, design.

64

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/oracle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, executable CLI skill: concrete commands throughout, a golden path with validation and recovery steps, and no filler. The main weakness is structural — everything, including advanced debugging and provider-routing details, is inlined in one long file instead of being split into one-level-deep references.

Suggestions

Move advanced troubleshooting (perf-trace, remote browser host, 1Password key injection, local-checkout debugging) into a references/ file and link to it from a short 'Advanced' section, keeping SKILL.md to the golden path and core commands.

Deduplicate the repeated 'API runs require explicit user consent' note so it appears once.

Consider moving the flag-level details of `--file` include/exclude/defaults into a reference, keeping only a few illustrative examples inline.

DimensionReasoningScore

Conciseness

The body is dense with tool-specific facts (flag behavior, default-ignored dirs, token caps, exit codes) and explains nothing Claude already knows. Minor trim opportunities remain: API-consent is stated twice ("API runs require explicit user consent" appears in both Engines and API preflight) and the 1Password/local-checkout debugging steps are peripheral to the main workflow. Not 5: those small redundancies keep it short of 'every token earns its place'.

4 / 5

Actionability

Every section gives copy-paste-ready commands with concrete flags and arguments, e.g. `npx -y @steipete/oracle --dry-run summary -p "<task>" --file "src/**" --file "!**/*.test.*"`, `oracle status --hours 72`, and the exact `op item get` injection. The common cases (preview, browser run, reattach, preflight) are all covered by specific examples.

5 / 5

Workflow Clarity

The 'Golden path' section gives a clear 4-step sequence (pick tight file set → preview with `--dry-run` + `--files-report` → run → reattach on detach/timeout) with an explicit pre-send validation checkpoint and an error-recovery loop ('don't re-run; reattach' with `oracle status` / `oracle session <id>`). Guardrails (duplicate-prompt guard, exit codes, conflicting flags) add explicit failure handling.

5 / 5

Progressive Disclosure

Sections are well-organized with clear headers, but the entire ~135-line reference lives inline in SKILL.md with no bundle files at all; advanced troubleshooting (perf-trace, remote browser host, 1Password key injection, building the local checkout) is material that clearly belongs in a separate reference file. Not 4: no references exist to be 'mostly clear', and the one-file layout means content that should be separate is inline.

3 / 5

Total

17

/

20

Passed

Description

66%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names the tool and several concrete capabilities, but it omits any 'use when' trigger guidance and lacks common synonyms a user would naturally say when reaching for this skill. It is a competent, slightly compressed one-liner rather than a complete trigger-rich description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants a second opinion from another model, mentions Oracle/GPT/ChatGPT, or asks to cross-check, debug, refactor, or design with an external model.'

Include natural synonyms users would say — 'second opinion', 'ask another model', 'GPT', 'ChatGPT' — to widen trigger coverage.

State the 'what' more fully in one clause, e.g. 'Bundles a prompt plus selected repo files into a one-shot request to a second model (API or browser)', so the capability is unambiguous.

DimensionReasoningScore

Specificity

"bundle prompts/files, debug, refactor, design" lists several concrete actions (bundle prompts and files into a request; use it for debugging, refactoring, design work), matching the anchor for several specific actions with minor coverage gaps. Not 5: 'debug, refactor, design' are compressed generic verbs and coverage is not comprehensive (no mention of API/browser engines or session reattach); not 3: more than 1-2 concrete actions are named.

4 / 5

Completeness

The 'what' is stated ("Oracle second-model review: bundle prompts/files"), but there is no 'when' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4: the 'when' is not weakly implied, it is entirely absent.

3 / 5

Trigger Term Quality

Natural trigger words are present: 'review', 'second-model', 'bundle', 'debug', 'refactor', 'design' — the phrases a user asking for a second-model opinion would say. Not 5: common synonyms like 'second opinion', 'ask GPT/ChatGPT', or 'cross-check with another model' are missing.

4 / 5

Distinctiveness Conflict Risk

Naming the tool ('Oracle') and its niche ('second-model review') makes it mostly distinct from other skills, with only minor overlap risk from the broad tail verbs 'debug, refactor, design'. Not 5: those generic verbs could let it trigger on ordinary code-review or debugging requests.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
steipete/agent-scripts
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.