AI coding agents

If you build on ADM with an AI coding agent — Claude Code, or anything else that reads skill files — you can hand it ADM’s rules instead of letting it guess. We ship a set of agent skills: short instruction files that tell an agent how this product actually works.

Without them an agent writes plausible-looking PL/SQL that does not run, because ADM’s two most important rules are invisible in a signature: a session needs a context before anything is permitted, and no ADM package commits. It will also reach for adm_document_versions.file_content to read a file, which is empty when that document lives in object storage.

What you get

Nine skills, each a single self-contained file:

Skill	Covers
adm-plsql	Establishing a security context, transaction ownership, catching ADM errors, and the rules that keep your code upgradeable. The one to read first.
adm-documents	Uploading, versioning, reading content back, mime types, retention and legal hold, comments and annotations.
adm-folders	Paths and ids, building nested structures, renaming and moving, and how the trash treats a whole subtree.
adm-querying	The reporting views, the core tables, restricting a query to what one user may see, and joining ADM ids to your own tables.
adm-search-and-tags	Tags and tag values, full-text search, faceted search.
adm-sharing-and-permissions	Permission checks, internal shares, public link shares, embed tokens, users and groups.
adm-hooks	The three hook events, and how raising in a hook refuses an upload.
adm-zip	Packing and expanding archives, the size guards, and the rollback they need.
adm-ai-rag	AI Pack only: RAG collections, chunk search and generated answers.

They describe the public API only. Nothing marked @private appears in them, which is what keeps an agent from building on plumbing that changes between releases.

Installing them

The skills/ folder ships in the release archive next to install.sql. Copy it into the project you are working in:

mkdir -p <your-project>/.claude/skills
cp -R skills/adm-* <your-project>/.claude/skills/

Or once, for every project on your machine:

cp -R skills/adm-* ~/.claude/skills/

Start a new agent session afterwards. The agent picks a skill up when the task matches it; you can also name one directly — “use the adm-documents skill”.

What they do not do

• They are not a substitute for the reference. The API reference is generated from the installed package specs, so it is always in step with your database. The skills are the parts that a signature cannot express.
• They do not grant anything. An agent calling ADM is subject to exactly the same context, role and permission checks as any other caller.
• They are versioned with the product. These match ADM 26.1. If a skill and the reference disagree, the reference is right — and please tell us, because it means the skill is wrong.

Also refer to

• Extensibility — the four supported ways to build on ADM, and the rules that keep an upgrade uneventful
• Managing the filesystem from the database
• The security model
• Error handling