Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
64
48%
Does it follow best practices?
Impact
99%
1.70xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/oracle/SKILL.mdQuality
Discovery
32%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 identifies a specific tool (oracle CLI) and lists topic areas it covers, but lacks concrete actions and an explicit 'Use when...' clause. It reads more like a table of contents than a skill description, making it harder for Claude to know precisely when to select this skill over others.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about oracle CLI commands, configuring oracle sessions, attaching files to oracle prompts, or selecting oracle engines.'
Replace 'Best practices for using' with specific concrete actions, e.g., 'Guides structuring oracle CLI prompts, bundling files for context, selecting engines, managing sessions, and attaching files.'
Include natural trigger terms users might say, such as 'oracle command', 'oracle prompt', 'oracle session management', or 'oracle file attachment'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain ('oracle CLI') and lists some areas (prompt + file bundling, engines, sessions, file attachment patterns), but these are topic areas rather than concrete actions. It says 'best practices for using' which is somewhat vague about what specific actions the skill enables. | 2 / 3 |
Completeness | Describes what the skill covers (best practices for oracle CLI usage) but has no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing, which per the rubric should cap completeness at 2, and the 'what' is also weak (just 'best practices'), so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'oracle CLI', 'prompt', 'file bundling', 'engines', 'sessions', and 'file attachment patterns' which are relevant keywords, but these are fairly technical terms. Missing natural user phrases like 'how to use oracle', 'oracle commands', or 'oracle configuration'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'oracle CLI' is a fairly specific tool which helps with distinctiveness, but the phrase 'best practices' is generic and could overlap with other oracle-related or CLI-related skills. The parenthetical topics help narrow scope somewhat. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, practical skill that provides highly actionable CLI guidance with real commands and flag combinations. Its main weaknesses are some verbosity in explanatory sections (prompt template advice, restoration pattern overlap) and a lack of explicit validation/error-recovery workflows beyond the basic 'reattach if timeout' guidance. The structure is good but could benefit from splitting advanced topics into separate referenced files.
Suggestions
Add explicit validation checkpoints to the golden path — e.g., after step 2 (dry-run), specify what to check in the output before proceeding, and after the run completes, how to verify the response quality.
Trim the 'Prompt template' section — Claude already knows how to write good prompts; focus only on oracle-specific requirements (e.g., 'oracle has zero project context' is useful, but 'include exact question + what you tried' is generic advice).
Consolidate the 'exhaustive prompt restoration pattern' into the Sessions section since it largely repeats the one-shot nature and reattach guidance already covered.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary explanations (e.g., 'Oracle bundles your prompt + selected files into one "one-shot" request so another model can answer with real repo context' is somewhat redundant given the description). The prompt template section explains things Claude would know about writing good prompts. Some sections like the 'exhaustive prompt restoration pattern' overlap with earlier content. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready commands throughout — dry-run, browser run, file attachment patterns with glob syntax, session management commands, and remote browser hosting. Every section includes specific CLI flags and realistic examples. | 3 / 3 |
Workflow Clarity | The 'Golden path' provides a clear 4-step sequence, but lacks explicit validation checkpoints beyond the dry-run preview. There's no feedback loop for when oracle output is wrong or when browser sessions fail beyond 'reattach'. The session timeout recovery is mentioned but not structured as a clear error-recovery workflow. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and logical grouping, but everything is inline in a single file. For a skill of this length (~100 lines with substantial detail on engines, sessions, file patterns, and prompt templates), some content like the remote browser setup or the exhaustive prompt pattern could be split into referenced files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
b3cef5f
Table of Contents
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.