AgentStack
SKILL verified MIT Self-run

Oracle Apex Export

skill-andre-simplifica-oracle-apex-ai-skills-oracle-apex-export · by andre-simplifica

Use to guide or execute Oracle APEX 24.2 export/snapshot work with SQLcl, distinguishing official snapshots, temporary read-only exports, App Builder fallback, and Git publication according to the project profile.

No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-andre-simplifica-oracle-apex-ai-skills-oracle-apex-export

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Oracle Apex Export? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Oracle APEX Export

Generic skill for exporting Oracle APEX 24.2 applications.

Before Running

  1. Read .oracle-apex-ai/project-profile.md.
  2. Confirm app id, workspace, SQLcl connection, and official snapshot folder.
  3. Confirm whether the intent is an official snapshot or temporary inspection.
  4. Check git status if there is a repository.

Modes

  • Official snapshot: updates the project's versioned folder, validates the diff, and may generate commit/push.
  • Temporary inspection: exports to /tmp for read-only analysis. Do not stage, import, or replace the snapshot.
  • Builder fallback: used when SQLcl/wallet/network fails and the profile allows manual export through App Builder.

Rules

  • Official snapshots must use the export options defined in the project profile.
  • Prefer split/readable exports for source control when supported.
  • Supporting Objects must follow the project's decision; do not assume.
  • Do not mix an APEX snapshot with unrelated changes.
  • Do not treat a temporary export as the official artifact.

Validation

  • install.sql is present for split exports.
  • application/ is present.
  • readable/ is present when the project requires readable YAML.
  • Snapshot README/metadata is updated when the project requires it.
  • Diff is limited to the expected scope.
  • No duplicate files or accidental downloads.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.