oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
68
55%
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 but lacks concrete actions and an explicit 'Use when...' clause. It reads more like a table of contents than a skill description, making it difficult 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 configuration of oracle CLI sessions, selection of engines, bundling files with prompts, and attaching file patterns.'
Include natural trigger terms users might say, such as 'oracle command line', 'oracle prompt', 'oracle session management', 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 somewhat vague about what specific actions the skill enables. | 2 / 3 |
Completeness | Describes what (best practices for oracle CLI usage) but has no 'Use when...' clause or equivalent explicit trigger guidance. The 'when' is entirely missing, which per the rubric should cap completeness at 2, and since the 'what' is also weak (just 'best practices'), this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'oracle CLI', 'prompt', 'file bundling', 'engines', 'sessions', and 'file attachment patterns'. However, it's unclear if users would naturally use terms like 'file bundling' or 'engines' — these feel more like internal jargon. Missing common variations a user might say like 'oracle command', 'oracle tool', or 'running oracle'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'oracle CLI' provides some distinctiveness, but 'best practices' is generic and could overlap with other CLI-related or tool-usage skills. The specific sub-topics (engines, sessions) help somewhat but aren't strongly distinctive without clearer scoping. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
77%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, actionable skill that provides concrete CLI commands and clear workflows for using the oracle tool. Its main strengths are the executable command examples, the explicit golden path with validation steps, and the practical session management guidance. Minor weaknesses include some verbosity in the prompt template and restoration pattern sections, and the lack of content splitting for what is a moderately long single-file skill.
Suggestions
Tighten the 'Prompt template' and 'Exhaustive prompt restoration pattern' sections — they overlap and could be merged into a single concise section with a bullet-list template rather than prose explanation.
Consider splitting engine details (API vs browser, remote hosting) and session management into separate referenced files if the skill grows further.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient and assumes Claude's competence, but some sections are slightly verbose — e.g., the 'Prompt template' section explains what oracle doesn't know, and the 'exhaustive prompt restoration pattern' section repeats concepts already covered. The safety section is brief but could be trimmed. Overall mostly lean but not maximally tight. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands for every workflow (dry-run, browser run, file attachment, session reattachment, remote hosting). File glob patterns, flag names, and specific model identifiers are all explicit and executable. | 3 / 3 |
Workflow Clarity | The 'Golden path' provides a clear 4-step sequence with a validation checkpoint (dry-run + files-report before spending tokens) and explicit error recovery (reattach on timeout instead of re-running). The duplicate prompt guard and --force flag add another safety layer. The workflow for destructive/expensive operations (token spend) includes preview steps. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and logical grouping, but everything is inline in a single file with no references to external files. For a skill of this length (~100 lines) covering multiple distinct topics (engines, sessions, file attachment, prompt templates, remote hosting), some content could be split out. However, no bundle files exist, so this is somewhat justified. | 2 / 3 |
Total | 10 / 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
- Hung-Reo/hungreo-openclaw
- Commit
a5bf5e0
- 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.