← ClaudeAtlas

oracle-dba-superlisted

USE FOR ANY Oracle Database request — whether to UNDERSTAND/DESIGN/WRITE (knowledge) or to OPERATE/CHANGE/RECOVER a database (action). Covers SQL & PL/SQL authoring, tuning, schema design, migrations (from PostgreSQL/MySQL/SQL Server/Mongo/Snowflake), JDBC & frameworks, ORDS, SQLcl/MCP, AND full DBA operations: provisioning, backup & recovery (RMAN/Data Pump), patching & upgrades, RAC, Data Guard, GoldenGate, performance/AWR/ASH, space/ASM, users/ roles/privileges, security/TDE/auditing, PDB/multitenant, monitoring/alerting, jobs, flashback, capacity, networking/listener, cloning/refresh, Exadata, OEM, OCI/Autonomous, decommissioning, and ANY ORA-/RMAN-/CRS- error. Trigger even if the user does not name a task or tool. This is the MASTER ROUTER: it sends knowledge questions to the vendored Oracle knowledge base and operational requests to the right tier-gated action domain, always loading the agent-safety patterns and enforcing the autonomy policy (T1 self-exec / T2 dry-run+execute / T3 runbook + human approv
Shreyas70773/oracle-dba-agentic-skills · ★ 0 · API & Backend · score 62
Install: claude install-skill Shreyas70773/oracle-dba-agentic-skills
# Oracle DBA — SUPER Skill Library A single, self-contained library that fuses two layers: - **KNOWLEDGE (the brain)** — `knowledge/`: Oracle's official, source-backed guidance (vendored from `github.com/oracle/skills`, UPL-1.0 — see `NOTICE.md`). Markdown only; the agent reads it and acts through the SQLcl MCP server. Breadth: SQL/PL-SQL, appdev, frameworks, migrations, ORDS, design, performance concepts, security concepts, features, containers, and **agent-safety patterns**. - **ACTION (the hands)** — the 24 domain skills at the root (e.g. `backup-and-recovery/`, `rac-high-availability/`): our tier-gated, **executable** automation — idempotent `.sh`/`.ps1` + `sql/*.sql` + deep T3 runbooks + cron, all sourcing the shared `_common/` harness, wired for native SQLcl-MCP (in-DB) and a custom guarded `oracle-dba-ops` MCP (host ops; see playbook). > **Golden rule:** *knowledge tells you HOW and WHY; action DOES it under the tier policy.* For > any change, consult the relevant `knowledge/` page first, then execute via the action domain. ## How to Use This Library 1. Classify the request: **knowledge/dev/design** vs **operational action**. 2. Knowledge → open `knowledge/SKILL.md` (its routing table) and read only the file you need. 3. Action → open the matching domain's `SKILL.md`, find the task in its **Scope & risk map**, then follow precheck → action (script/sql) → postcheck → rollback. Honor the tier. 4. For ANY destructive/changing operation, also load the