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 ./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 explicit trigger guidance. 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. Adding a 'Use when...' clause and converting topic areas into specific actions would significantly improve it.
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 and configuring engines, managing sessions, and attaching files.'
Include natural trigger terms users might say, such as 'oracle command line', 'oracle prompt', 'oracle session management', or 'how to use oracle'.
| 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' at a high level (best practices for oracle CLI usage) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, 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'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 since it's a specific tool, but 'best practices' is generic and could overlap with other CLI-related or oracle-related skills. The lack of explicit triggers increases conflict risk. | 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, actionable reference for the oracle CLI with concrete commands, good file attachment documentation, and practical session management guidance. Its main weaknesses are the lack of explicit validation/verification checkpoints integrated into workflows and some sections that could be tighter or split out for better progressive disclosure. The prompt template section, while useful, veers toward generic advice that could be more concise.
Suggestions
Add an explicit verification step after oracle runs complete (e.g., 'Review output against actual code; run tests to confirm suggestions before applying') integrated into the Golden Path workflow rather than just mentioned in the header.
Consider splitting the 'Prompt template' and 'Exhaustive prompt restoration pattern' sections into a separate PROMPTING.md reference file to keep the main skill leaner and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanations (e.g., explaining what oracle does conceptually, the 'Oracle starts with zero project knowledge' paragraph restates what's obvious from the tool's nature). The prompt template section borders on generic advice. Some tightening possible but not egregiously verbose. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready commands throughout — dry-run, browser run, file attachment patterns with glob syntax, session reattachment, remote browser hosting. The file attachment section includes specific include/exclude examples and documents real behavioral defaults (1MB limit, .gitignore honoring, etc.). | 3 / 3 |
Workflow Clarity | The 'Golden path' provides a clear 4-step sequence, and the session reattachment flow is well-documented. However, there's no explicit validation checkpoint — e.g., after a browser run completes, there's no 'verify the output against X' step. The guidance to 'verify against code + tests' is mentioned once at the top but not integrated into the workflow as a checkpoint. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and logical grouping. However, for a skill of this length (~100 lines), some sections like the prompt template guidance and the 'exhaustive prompt restoration pattern' could be split into referenced files. No bundle files exist to offload detail, and everything is inline in one document. | 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
- attilaczudor/Test
- Commit
b4fc4af
- 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.