T09 · Insecure Skill Coding Practices
- Location
scripts/index.js:107- Finding
Appian API Key Disclosure Through an Unvalidated Package Download URL
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill does what it says, but it handles Appian credentials and exported application ZIPs in ways that create review-worthy security risk.
Install only if you are comfortable granting the skill an Appian API key that can export applications and with exported application ZIPs being saved locally. Prefer a hardened version that validates the package download origin, ignores or sanitizes remote filenames, avoids duplicate retained ZIPs, and documents how to remove stored exports.
scripts/index.js:107Appian API Key Disclosure Through an Unvalidated Package Download URL
scripts/index.js:112Arbitrary File Overwrite Through an Unsanitized Content-Disposition Filename
The skill declares access to sensitive capabilities via environment variables and external network calls, but it does not constrain tool scope with explicit permissions or allowed-tools. That leaves the agent runtime free to grant broader-than-necessary access, increasing the risk of unintended data access or outbound requests if the implementation or surrounding orchestration is abused.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
---
name: appian-discovertechdebt
description: Scan an Appian application for tech debt by finding objects whose SAIL definitions reference outdated versioned functions (marked by Appian with a _v suffix such as _v1, _v2). Use periodically or before a release to surface deprecated function usage. Trigger phrases — "find Appian tech debt", "check Appian for outdated functions", "scan Appian for deprecated SAIL", "which Appian objects use old functions", "audit Appian tech debt". IMPORTANT — credentials (APPIAN_BASE_URL, APPIAN_API_KEY) are already configured in the system; do NOT ask the user for them before running.
metadata:
clawdbot:
emoji: "🔧"
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## 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
The skill downloads the full exported Appian application ZIP and persists it to disk in the user's home directory, then duplicates it into the current working directory. That behavior exceeds the minimal requirement to scan for deprecated SAIL functions in-memory and creates unnecessary at-rest copies of potentially sensitive application source/configuration, increasing exposure to local users, backups, workspace syncing, or later accidental disclosure.