Individual skill

oracle-apex-object-lock

Use for installing, upgrading, auditing, retaining, uninstalling, and enforcing the cooperative PK_DEV_OBJECT_LOCK runtime before editing, compiling, replacing, or testing versioned PL/SQL and other supported objects in a shared Oracle DEV schema.

skills/oracle-apex-object-lock/SKILL.md

Read pinned source

Source commit bf2f06a47ba958fd222f18930b6e42c71637a790

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
20
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Oracle APEX Object Lock

Coordinate changes to live, versioned database objects in a shared DEV schema. This skill ships the table, indexes, views, package, audit, installation, validation, retention, and guarded uninstall scripts required by the runtime.

## Determine Runtime State

Read [installation.md](references/installation.md), then run the read-only `assets/database/audit-installation.sql` through the project's approved SQLcl connection.

Classify the result:

- `INSTALLED`: all required objects are valid and the runtime version is compatible.
- `ABSENT`: none of the required objects exists.
- `PARTIAL`: only part of the runtime exists or an object is invalid.
- `INCOMPATIBLE`: the package exists but does not expose the required runtime version.
Back to top