← Back to Skills Marketplace
solarspiker

Appian Export

by solarspiker · GitHub ↗ · v1.3.0 · MIT-0
cross-platform ⚠ suspicious
135
Downloads
0
Stars
0
Active Installs
7
Versions
Install in OpenClaw
/install appian-export
Description
Export an Appian application or package to a ZIP file by UUID. Use when the user wants to export, download, or back up an Appian application or package from...
README (SKILL.md)

Appian Manager

Exports an Appian application or package as a ZIP using the v2 Deployment Management API.

Usage

# Export an application
node {baseDir}/scripts/index.js \x3CapplicationUuid> [exportName]

# Export a specific package under an application
node {baseDir}/scripts/index.js \x3CapplicationUuid> --package \x3CpackageUuid> [exportName]
Argument Description
applicationUuid UUID of the Appian application
packageUuid UUID of the specific package (use appian-listpkg to list them)
exportName Optional filename override; if omitted Appian's own name (with timestamp) is used

Examples

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

# Export a specific package under that application
node {baseDir}/scripts/index.js _a-0000de15-1f1c-8000-5130-010000010000_12559 --package _a-0007ee60-0f3e-8000-e0f6-01ef9001ef90_137916

The script polls until COMPLETED and saves the ZIP to ~/appian-exports/. When running inside a container (where the working directory differs from ~/appian-exports/), the ZIP is also copied to appian-exports/ inside the current working directory for easy access.

After running

Always report back to the user:

  • The ZIP path printed after ZIP path: (primary location)
  • The Copied to path if printed (accessible in appian-exports/ inside the current working directory)
  • The file size in KB

External endpoints

  • POST ${APPIAN_BASE_URL}/deployments — triggers the export
  • GET ${APPIAN_BASE_URL}/deployments/{uuid} — polls for completion
  • GET \x3CpackageZip URL> — 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, the script falls back to a appian.json file in the current working directory.
  • No data is sent to any third-party service — all requests go to your configured Appian environment.
  • The exported ZIP is written locally to ~/appian-exports/ and never uploaded anywhere.
  • No shell commands are executed; all operations use Node.js built-in APIs.
Usage Guidance
This skill appears to do what it says: it uses APPIAN_BASE_URL and APPIAN_API_KEY to trigger an export, polls for completion, downloads the ZIP, and saves it to ~/appian-exports/ (and also copies it to ./appian-exports/). Before installing or running: (1) ensure the APPIAN_API_KEY you provide has the minimum privileges needed for exports; (2) be aware the script will read a local appian.json up to five parent directories if env vars are missing — avoid leaving credentials in repo files you don't want used; (3) exported ZIPs are written locally, so treat them like any sensitive backup; (4) the agent can invoke skills autonomously by default — if you don't want that, disable autonomous invocation for this skill in your agent settings. Overall the bundle is coherent with its purpose.
Capability Analysis
Type: OpenClaw Skill Name: appian-export Version: 1.3.0 The skill is a legitimate utility for exporting Appian applications and packages using the official Appian Deployment Management API. The script (scripts/index.js) correctly handles authentication via environment variables, polls for export completion, and downloads the resulting ZIP file to a local directory. No evidence of malicious intent, data exfiltration to third parties, or unauthorized command execution was found; the behavior is entirely consistent with the documentation in SKILL.md.
Capability Tags
requires-sensitive-credentials
Capability Assessment
✓ Purpose & Capability
Name/description match the implementation. The only required environment variables are APPIAN_BASE_URL and APPIAN_API_KEY, which are appropriate for calling Appian's Deployment Management API. The code triggers an export, polls status, downloads a package ZIP, and writes it to disk — behaviour consistent with the stated purpose.
✓ Instruction Scope
SKILL.md and scripts/index.js are aligned: they read credentials from environment (with an optional appian.json fallback), call the Appian endpoints listed, poll until completion, and save the ZIP locally. The instructions do not request unrelated files, unexpected network destinations, or arbitrary system scans. The appian.json lookup climbs up to 5 parent directories (documented in code), which is a reasonable convenience but means local repo config files could be used as fallbacks.
✓ Install Mechanism
There is no install spec and the skill includes a small Node.js script. No remote downloads or archive extraction are performed by the skill itself. No package installation is requested by the registry metadata.
✓ Credentials
Only APPIAN_BASE_URL and APPIAN_API_KEY are required (primaryEnv is APPIAN_BASE_URL). Both are necessary for API access; no unrelated secrets or broad permission scopes are requested. The script will also read an optional local appian.json file for these values if environment variables are not present.
✓ Persistence & Privilege
The skill does not request persistent always-on presence (always:false). It writes exported ZIPs to ~/appian-exports/ and copies them into a local appian-exports/ folder in the current working directory; it does not modify other skills or global agent configuration.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install appian-export
  3. After installation, invoke the skill by name or use /appian-export
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
- Update external endpoint from GET `${APPIAN_BASE_URL}/deployment/{uuid}` to GET `${APPIAN_BASE_URL}/deployments/{uuid}` in documentation for accuracy. - No changes to the skill’s core behavior or usage.
v1.2.5
Copy exported ZIP to CWD/appian-exports/ instead of CWD root when running in container
v1.2.4
Copy exported ZIP to CWD when running inside a container (CWD differs from ~/appian-exports/)
v1.2.3
No user-facing changes in this version. - No file changes detected. - Functionality and documentation remain unchanged.
v1.2.2
Version 1.2.2 of appian-export contains no file or documentation changes. - No updates or modifications detected in this release. - Existing functionality and behavior remain unchanged.
v1.2.1
- Changes default export directory from ~/.openclaw/exports/ to ~/appian-exports/. - Updates security section: credentials are now read from environment variables if present, otherwise from appian.json in the working directory. - Adjusts documentation for new export path and credential loading behavior.
v1.0.0
Initial release of the appian-export skill. - Export any Appian application or package to a ZIP file using its UUID. - Supports exporting full applications or specific packages via command line. - Automatically saves ZIPs to `~/.openclaw/exports/` and reports file path and size. - Uses only environment variables (`APPIAN_BASE_URL`, `APPIAN_API_KEY`) for authentication. - Communicates directly with your Appian environment—no third-party data transfer. - All file operations are handled securely with Node.js built-ins (no shell commands).
Metadata
Slug appian-export
Version 1.3.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 7
Frequently Asked Questions

What is Appian Export?

Export an Appian application or package to a ZIP file by UUID. Use when the user wants to export, download, or back up an Appian application or package from... It is an AI Agent Skill for Claude Code / OpenClaw, with 135 downloads so far.

How do I install Appian Export?

Run "/install appian-export" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Appian Export free?

Yes, Appian Export is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Appian Export support?

Appian Export is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Appian Export?

It is built and maintained by solarspiker (@solarspiker); the current version is v1.3.0.

More Skills
self-improving agent
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Clau...
⬇ 463283 · by pskoett
Skill Vetter
Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.
⬇ 259410 · by spclaudehome
Polymarket
Query Polymarket prediction markets. Check odds, find trending markets, search events, track price movements.
⬇ 232503 · by joelchance
Self-Improving + Proactive Agent
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use when...
⬇ 200423 · by ivangdavila
Github
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
⬇ 191115 · by steipete
ontology
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
⬇ 190156 · by oswalpalash

💬 Comments