oracle-aidb-docker-setup

Bring up Oracle 26ai Free in Docker, create a project-scoped app user with USERS tablespace + ONNX-friendly grants, and write a `.env` ready for the rest of the build-paths skills. Idempotent — safe to re-invoke. Use when any project needs a fresh local Oracle 26ai instance.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality operational skill: executable end-to-end, with explicit validation, error-recovery feedback loops, and dense non-obvious friction knowledge rather than generic padding. The only weaker dimension is progressive disclosure, where large inline code blocks could be externalized into the bundle.

Suggestions

Move the Step 5/Step 6 Python (smoke SYSTEM connect and app-user creation with the SYSDBA DBMS_VECTOR grant) into scripts/ files (e.g. scripts/create_app_user.py) invoked from the body, keeping SKILL.md as the orchestration overview and improving progressive disclosure.

Either copy the referenced shared/ artifacts (oracle-26ai-free-docker.md, docker-compose.oracle-free.yml) into a local references/ + templates/ dir, or note their canonical shared/ location explicitly, so the one-level-deep references resolve within the skill's own bundle.

Dimension	Reasoning	Score
Conciseness	The body is dense with non-obvious operational friction (ORA-43853 ASSM/JSON requirement, the Apple-Silicon arch-mismatch `su oracle` failure, the ORA-01034 healthcheck false-positive, the SYSDBA-only DBMS_VECTOR grant) — none of which Claude already knows — with no generic-concept padding, matching the score-3 lean-and-efficient anchor.	3 / 3
Actionability	Provides fully executable, copy-paste-ready code throughout (Python password generation, bash arch detection and image pull, oracledb SYSTEM/app-user connects with error handling, complete .env contents), matching the score-3 fully-executable anchor.	3 / 3
Workflow Clarity	Clear numbered sequence (Steps 0–6) with explicit validation checkpoints (smoke SYSTEM connect, smoke app-user connect, `docker compose up --wait` healthcheck), feedback loops (retry on ORA-12541, error-diagnosis checklist on `--wait` failure), and checklists (stop conditions, "What you must NOT do"), matching the score-3 anchor for database operations.	3 / 3
Progressive Disclosure	Step 0 references are well-signaled and one-level-deep and the compose template is externalized, but substantial operational code (Steps 5–6 multi-block Python) stays inline rather than split into scripts/, and the references point to a shared/ location rather than this skill's own bundle — matching the score-2 anchor where content that could be separate remains inline.	2 / 3
	Total	11 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states both capability and an explicit use-trigger, occupying a distinct niche unlikely to conflict with other skills. Its main weakness is trigger-term breadth: the phrasing is technical and narrow, with internal jargon that users would not naturally say.

Suggestions

Broaden the trigger with natural variations a user would actually say — e.g. "Use when setting up Oracle, spinning up a local Oracle database, or running Oracle 26ai Free in Docker" — rather than the single narrow "fresh local Oracle 26ai instance" phrasing.

Drop internal jargon ("build-paths skills") from the user-facing description; it is not a term users would say and adds noise without aiding triggering.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Bring up Oracle 26ai Free in Docker, create a project-scoped app user with USERS tablespace + ONNX-friendly grants, and write a `.env`" — matching the score-3 anchor of enumerating specific concrete actions rather than vague language.	3 / 3
Completeness	Explicitly answers both what (bring up container, create app user, write .env) and when ("Use when any project needs a fresh local Oracle 26ai instance"), matching the score-3 anchor that requires an explicit trigger clause.	3 / 3
Trigger Term Quality	Contains relevant keywords (Oracle 26ai, Docker, .env) but the trigger is narrow ("Use when any project needs a fresh local Oracle 26ai instance") and mixes in internal jargon ("build-paths skills"); it misses common natural variations like "set up Oracle" or "local Oracle database," so it is not the full-coverage level 3.	2 / 3
Distinctiveness Conflict Risk	A clear, narrow niche (Oracle 26ai Free in Docker with a project-scoped app user) with distinct triggers makes it unlikely to fire for an unrelated skill, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: oracle-devrel/oracle-ai-developer-hub
Path: build-paths/skills/oracle-aidb-docker-setup/SKILL.md
Commit: 22d9a38

Reviewed: about 13 hours 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.