← Back to Skills Marketplace
1386
Downloads
1
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install privacy-cards
Description
Create and manage Privacy.com virtual cards. Use for generating single-use cards, merchant-locked cards, listing cards, setting spending limits, pausing/closing cards, and viewing transactions via the Privacy.com API.
Usage Guidance
This skill's instructions legitimately use Privacy.com APIs, but the package metadata omits the required PRIVACY_API_KEY — that's an internal inconsistency you should question before installing. Do not provide a production API key unless you trust the skill owner. Prefer testing with a sandbox key first, and only grant least-privilege credentials needed. Ask the publisher why the metadata doesn't declare the required env var and whether the skill stores or transmits your key anywhere beyond api.privacy.com. Monitor and rotate keys if you test or use this skill; avoid giving enterprise-level keys that return PAN/CVV unless absolutely necessary.
Capability Analysis
Type: OpenClaw Skill
Name: privacy-cards
Version: 1.0.0
The skill bundle is benign. It provides instructions and examples for interacting with the Privacy.com API to manage virtual cards. All network requests are directed to legitimate Privacy.com domains (api.privacy.com, sandbox.privacy.com), and the API key is handled securely via an environment variable. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts designed to subvert the agent's intended function or perform unauthorized actions. The `references/api.md` file contains only documentation and a benign Python example for webhook verification.
Capability Assessment
Purpose & Capability
The SKILL.md accurately describes Privacy.com card management and shows curl examples against api.privacy.com; that matches the stated purpose. However the registry metadata does not declare the API key (PRIVACY_API_KEY) as a required environment variable or primary credential even though the runtime instructions require it. This mismatch is an incoherence between declared requirements and actual capability.
Instruction Scope
The runtime instructions are narrowly scoped to calling Privacy.com endpoints (create/list/update cards, query transactions, webhook verification). They do not instruct reading unrelated files, system paths, or contacting external endpoints outside the official Privacy.com domains. Examples correctly note sandbox vs production differences.
Install Mechanism
No install spec and no code files are present (instruction-only). This is low-risk from an installation perspective because nothing will be downloaded or written to disk by an installer.
Credentials
The instructions require a PRIVACY_API_KEY (sensitive financial API key) but the registry metadata lists no required env vars or primary credential. Requesting an API key to manage virtual cards is proportionate to the skill's purpose, but omitting that requirement from metadata is a red flag: it makes it unclear how the agent runtime will be authorized or how the key will be supplied/used. The API key grants control over payment instruments and potentially access to transaction data and, with higher privileges, PAN/CVV — so ensure only the minimum-privilege key is used (prefer sandbox for testing).
Persistence & Privilege
always:false (normal). The skill is user-invocable and model invocation is allowed (default). While autonomous invocation is standard, pairing autonomous invocation with access to a financial API increases potential impact if the key is provided — verify trust in the skill and owner before granting credentials.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install privacy-cards - After installation, invoke the skill by name or use
/privacy-cards - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is Privacy Cards?
Create and manage Privacy.com virtual cards. Use for generating single-use cards, merchant-locked cards, listing cards, setting spending limits, pausing/closing cards, and viewing transactions via the Privacy.com API. It is an AI Agent Skill for Claude Code / OpenClaw, with 1386 downloads so far.
How do I install Privacy Cards?
Run "/install privacy-cards" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Privacy Cards free?
Yes, Privacy Cards is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Privacy Cards support?
Privacy Cards is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Privacy Cards?
It is built and maintained by JohnieLee (@johnielee); the current version is v1.0.0.
More Skills