oracle
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 ./openclaw/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 but lacks concrete actions and an explicit 'Use when...' clause. It reads more like a table of contents than a skill description, making it hard 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, bundling files with prompts, configuring engines, managing sessions, or attaching files.'
Replace 'Best practices for using' with specific concrete actions, e.g., 'Guides structuring oracle CLI prompts, bundling files into requests, selecting and configuring engines, managing sessions, and attaching files.'
Include natural trigger term variations users might say, such as 'oracle command line', 'oracle tool', 'oracle prompt', or 'oracle file attachments'.
| 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 vague about what specific actions the skill enables. | 2 / 3 |
Completeness | It partially addresses 'what' (best practices for oracle CLI usage) but has no explicit 'when' clause or trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is weak (just 'best practices'), so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'oracle CLI', 'prompt', 'file bundling', 'engines', 'sessions', and 'file attachment patterns'. However, it lacks common user-facing variations—users might say things like 'oracle command', 'oracle tool', 'bundle files', or 'attach files to oracle'. Coverage is partial. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'oracle CLI' is fairly specific and narrows the domain, but 'best practices' is generic and could overlap with other oracle-related or CLI-related skills. The parenthetical topics help somewhat but don't fully disambiguate. | 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 commands and patterns for using the oracle tool. Its main strengths are concrete command examples and good coverage of common workflows. Weaknesses include some redundancy between sections, missing validation/error-recovery workflows for when things go wrong, and all content being inline rather than progressively disclosed for a skill of this length.
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.
Consolidate the 'exhaustive prompt restoration pattern' section with the 'prompt template' section to reduce redundancy, or move the restoration pattern to a separate reference file.
Add a brief troubleshooting/error-recovery workflow for common failure modes (e.g., browser session hangs, token limit exceeded, attachment rejected) with specific recovery commands.
| 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 flags and real command 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.