Accounts Payable Automation
v1.0.0Automate accounts payable with invoice processing, approval routing, payment optimization, vendor management, month-end close, key metrics, and fraud prevent...
⭐ 0· 650·1 current·1 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the SKILL.md and README: both describe AP automation (invoice processing, approvals, vendor management, fraud controls). No unrelated binaries, env vars, or config paths are requested.
Instruction Scope
SKILL.md contains operational guidance and templates for AP workflows. It does not instruct the agent to read local files, access environment variables, or transmit arbitrary data to external endpoints. It does reference external paid context packs and tools (URLs) but only as optional resources.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is written to disk or downloaded by the skill itself.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. The content asks for user-provided process details but does not request secrets or unrelated service tokens.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent system presence or to modify other skills or agent-wide settings.
Assessment
This skill appears coherent and low-risk as an instruction-only AP framework. Before using: (1) do not paste real sensitive data (full bank account numbers, unredacted TINs, or credentials) into the agent; (2) verify any external links or paid context packs independently (they point to a GitHub Pages domain, but confirm the vendor and payment flow); (3) if you act on implementation recommendations, ensure automation components (OCR, payment gateways, vendor-bank-change procedures) are implemented with appropriate access controls, logging, and staging tests; (4) require dual control for any real payment or vendor-bank-change operations. If you want a deeper assessment, provide any implementation code or deployment manifests that would be used to automate payments so those artifacts can be reviewed.Like a lobster shell, security has layers — review code before you run it.
accountingvk975begzb112jr8yft37an1s49819s0fapvk975begzb112jr8yft37an1s49819s0fautomationvk975begzb112jr8yft37an1s49819s0ffinancevk975begzb112jr8yft37an1s49819s0flatestvk975begzb112jr8yft37an1s49819s0f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.