← Back to Skills Marketplace
solarspiker

Appian Deploy

by solarspiker · GitHub ↗ · v1.2.3 · MIT-0
cross-platform ⚠ suspicious
148
Downloads
0
Stars
0
Active Installs
5
Versions
Install in OpenClaw
/install appian-deploy
Description
Deploy (import) an Appian package ZIP into an Appian environment. Use when the user wants to push, import, or deploy a package file to an Appian environment.
README (SKILL.md)

Appian Deploy

Imports a package ZIP into the Appian environment using the v2 Deployment Management API. Polls until a terminal status and prints a full object summary.

Usage

node {baseDir}/scripts/index.js \x3CzipPath> \x3CdeploymentName> [description] [customizationFilePath]

Example

node {baseDir}/scripts/index.js "./appian-exports/MyPackage.zip" "Prod Release 1.2"

Exported packages are saved to ./appian-exports/ by appian-export.

Run appian-inspectpkg first to validate before deploying. If the environment requires approval, the deployment will return PENDING_REVIEW — check Appian Designer's Deploy view to approve.

External endpoints

  • POST ${APPIAN_BASE_URL}/deployments — triggers the import
  • GET ${APPIAN_BASE_URL}/deployments/{uuid} — polls for completion

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.
  • The package ZIP is uploaded only to your configured Appian environment.
  • No data is sent to any third-party service.
  • No shell commands are executed; all operations use Node.js built-in APIs.
Usage Guidance
This skill appears to do what it says: it uploads a ZIP to your Appian environment using the provided APPIAN_BASE_URL and APPIAN_API_KEY. Before installing, note two small issues: (1) the script requires Node.js to run but the skill metadata doesn't list Node as a required binary — ensure your environment provides Node; (2) if APPIAN_BASE_URL/APPIAN_API_KEY aren't injected, the script searches up to 5 parent directories for an appian.json and will load any uppercase KEY=VALUE pairs it finds into process.env (this can import unrelated secrets/config into the process). Also be aware that the script prints payload metadata (deployment JSON and file size) to stdout/stderr, which may appear in agent logs. If those behaviors are acceptable for your environment, the skill is coherent and proportionate to its stated purpose.
Capability Analysis
Type: OpenClaw Skill Name: appian-deploy Version: 1.2.3 The skill is a legitimate utility for deploying Appian packages using the official Appian Deployment Management API. The code in `scripts/index.js` follows the logic described in `SKILL.md`, using standard Node.js APIs to read local ZIP files and perform authenticated HTTP requests to a user-defined Appian environment. No evidence of data exfiltration to third parties, shell command execution, or malicious prompt injection was found.
Capability Tags
requires-sensitive-credentials
Capability Assessment
Purpose & Capability
Name/description, required env vars (APPIAN_BASE_URL, APPIAN_API_KEY), and the script's network calls all align with deploying a package to Appian. Minor mismatch: the SKILL declares no required binaries but the runtime usage requires Node (the script is invoked with `node`).
Instruction Scope
SKILL.md and the script limit network activity to the configured APPIAN_BASE_URL endpoints and describe uploading only the supplied package/customization file. However, the script will search up to 5 parent directories for an `appian.json` and load any uppercase KEY=VALUE entries it finds into process.env (not just the two Appian vars). Also the script logs payload metadata (deployment JSON and file size) to stdout/stderr which could surface sensitive info in logs.
Install Mechanism
No install spec is provided (instruction-only), which keeps risk low. The package includes a Node.js script (no packaged/install step). This implies the environment must provide Node.js; the skill did not declare a required binary but the script is intended to be run with `node`.
Credentials
Declared env requirements (APPIAN_BASE_URL, APPIAN_API_KEY) are appropriate for the task. But the fallback `appian.json` loader will parse and set any uppercase KEY=VALUE pairs into process.env if they are present and not already set. That behavior can unexpectedly import additional environment values from a config file located in parent directories (search depth 5). Consider whether you want a skill to automatically load arbitrary env entries from nearby files.
Persistence & Privilege
The skill does not request persistent/always-on privileges. It does not modify other skills or system-wide settings. Autonomous invocation is allowed by platform default but is not combined with other high-risk features here.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install appian-deploy
  3. After installation, invoke the skill by name or use /appian-deploy
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.3
- Internal code changes made to scripts/index.js; no user-facing changes. - Functionality and documentation remain the same.
v1.2.2
- No code or documentation changes in this version. - Version bump to 1.2.2; behavior and usage remain the same.
v1.2.1
Version 1.2.1 of appian-deploy - No changes in code or documentation detected. - Maintenance release with no new features or bug fixes.
v1.2.0
- Added support for loading credentials (`APPIAN_BASE_URL`, `APPIAN_API_KEY`) from a local `appian.json` config file if environment variables are not set. - Updated usage docs and examples to reflect preferred package export location (`./appian-exports/`). - Clarified credential handling and fallback mechanism in the documentation.
v1.0.0
Initial release of appian-deploy skill. - Deploys (imports) an Appian package ZIP file to a specified Appian environment using API v2. - Polls deployment status until completion or review is required. - Requires APPIAN_BASE_URL and APPIAN_API_KEY environment variables for authentication. - All uploads are secure; no external data transfers or shell execution. - Detailed usage and security information included in documentation.
Metadata
Slug appian-deploy
Version 1.2.3
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 5
Frequently Asked Questions

What is Appian Deploy?

Deploy (import) an Appian package ZIP into an Appian environment. Use when the user wants to push, import, or deploy a package file to an Appian environment. It is an AI Agent Skill for Claude Code / OpenClaw, with 148 downloads so far.

How do I install Appian Deploy?

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

Is Appian Deploy free?

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

Which platforms does Appian Deploy support?

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

Who created Appian Deploy?

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

💬 Comments