oracle

Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).

1.70x

Quality

55%

Does it follow best practices?

Impact

99%

1.70x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/oracle/SKILL.md

Quality

Content

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 solid, actionable skill that provides concrete CLI commands and clear workflows for using the oracle tool. Its main strengths are the executable command examples, the clear golden path workflow with validation steps, and practical guidance on file attachment patterns. Minor weaknesses include some verbosity in the prompt template section and slight redundancy across sections, plus the lack of progressive disclosure into supporting files for advanced topics.

Suggestions

Tighten the prompt template section — Claude can infer what makes a good prompt; reduce to a concise checklist rather than explanatory prose.

Remove the redundant reattach guidance that appears in both 'Golden path' step 4 and the 'Sessions + slugs' section.

Dimension	Reasoning	Score
Conciseness	Generally efficient and assumes Claude's competence, but some sections like the prompt template and 'exhaustive prompt restoration pattern' are somewhat verbose and could be tightened. The explanation of what oracle does in the intro is borderline unnecessary for Claude. Some redundancy between sections (e.g., reattach advice appears twice).	2 / 3
Actionability	Provides concrete, copy-paste-ready commands throughout with specific flags, glob patterns, and real examples. The file attachment patterns, engine selection, session management, and dry-run commands are all fully executable and specific.	3 / 3
Workflow Clarity	The 'Golden path' provides a clear 4-step sequence with an explicit validation checkpoint (dry-run + files-report before spending tokens) and a feedback loop for detached sessions (reattach rather than re-run). The duplicate prompt guard and --force flag guidance adds safety. The workflow is well-sequenced for a tool that involves potentially expensive one-shot operations.	3 / 3
Progressive Disclosure	The content is well-organized with clear section headers and logical grouping, but it's all in a single file with no references to supporting documents. Some sections like the prompt template and exhaustive prompt pattern could be split into separate reference files. However, given no bundle files exist, the monolithic approach is the only option, and the sections are reasonably sized.	2 / 3
	Total	10 / 12 Passed

Description

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 the 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 hard for Claude to know precisely when to select this skill over others. Adding a 'Use when...' clause and specifying concrete 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 configuration of oracle CLI sessions, selection of engines, bundling files with prompts, and attaching files to oracle commands.'

Include natural trigger terms users might say, such as 'oracle command', 'oracle prompt', 'oracle setup', or 'how to use oracle'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('oracle CLI') and lists some areas (prompt + file bundling, engines, sessions, file attachment patterns), but these are categories rather than concrete actions. It says 'best practices for using' which is vague about what specific actions the skill enables.	2 / 3
Completeness	The description partially answers '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' is also weak (just 'best practices'), so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords like 'oracle CLI', 'sessions', 'engines', 'file attachment', and 'file bundling', but these are somewhat technical. Missing natural user phrases like 'how to use oracle', 'oracle command', 'run oracle', or common variations users might say.	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 oracle-related skills. The specific sub-topics (engines, sessions, file attachment patterns) help somewhat but aren't strongly distinctive.	2 / 3
	Total	7 / 12 Passed

Validation

72%

Warnings & errors only

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: fc01b4b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.