Appian Unnamed Objects

Exports an Appian application and scans every object XML file for objects whose tag is empty or missing. Reports type, name, and UUID for each offending object.

Usage

node {baseDir}/scripts/index.js <applicationUuid>

Example

node {baseDir}/scripts/index.js _a-0000de15-1f1c-8000-5130-010000010000_12559

IMPORTANT: credentials are pre-configured

APPIAN_BASE_URL and APPIAN_API_KEY are already injected by OpenClaw at runtime. Never ask the user for credentials before running this skill. Just execute it with the UUID the user provided.

How users can ask for this

• "Find Appian objects without descriptions in application "
• "Which Appian objects are undocumented in "
• "Audit Appian missing descriptions in "
• "Check Appian documentation coverage for "

What it does

1. Calls the Appian v2 Deployment Management API to export the application as a ZIP.
2. Parses the ZIP in-process (no shell extraction) using Node.js built-ins — one object per XML file, type from directory name.
3. Iterates every XML file outside META-INF/.
4. For each object, checks whether or is absent or blank.
5. Prints a grouped report of offending objects.

After running

Relay the full skill output to the user exactly as printed — do not summarize, paraphrase, or omit any lines.

The output already contains every object type, name, and UUID in a compact readable format. Your job is to forward it verbatim, then offer to help further. Do not replace the list with a vague count like "15 objects were found" — the user needs the actual names and details.

External endpoints

• POST ${APPIAN_BASE_URL}/deployments — triggers the export
• GET ${APPIAN_BASE_URL}/deployments/{uuid} — polls for completion
• GET — downloads the resulting ZIP

Security

• Credentials (APPIAN_BASE_URL, APPIAN_API_KEY) are read from environment variables (injected by OpenClaw at runtime). If not injected, falls back to appian.json in the current working directory.
• The ZIP is written to ~/appian-exports/ and mirrored to CWD/appian-exports/ when running in a container.
• No data is sent to any third-party service.
• No shell commands are executed; ZIP extraction uses Node.js built-in zlib.