← Back to Skills Marketplace
390
Downloads
0
Stars
1
Active Installs
9
Versions
Install in OpenClaw
/install otc-confirmation
Description
One-Time Confirmation code security mechanism for sensitive agent operations. Generates a cryptographically secure single-use code, delivers it via a private...
Usage Guidance
Before installing or enabling this skill: 1) Manually inspect the three shell scripts (generate_code.sh, send_otc_email.sh/send_email_smtp.sh, verify_code.sh) to confirm they do not echo the code, do not log secrets, and that credentials are not passed on the command line in a way visible via ps. 2) Run the skill in a non-production sandbox first and test the state-file lifecycle and permission bits (state dir mode 700, state file mode 600). 3) Use a dedicated SMTP account with limited privileges and rotate its password if compromised. 4) If you enable a custom backend script, verify it is trusted and executable only by your user. 5) Be aware the 'agent must not read the state file' is a procedural control — a compromised agent running as the same OS user could read it; consider isolating the guard (different user, container, or stricter sandbox). 6) Note the SKILL.md includes prompt-injection discussion — review the docs and templates so you are comfortable there are no instructions that would weaken your agent's system prompt or security posture. If you want extra assurance, have a security-savvy reviewer audit the scripts for credential handling (curl usage, logging, process args) prior to production use.
Capability Analysis
Type: OpenClaw Skill
Name: otc-confirmation
Version: 3.1.0
The 'otc-confirmation' skill bundle is a well-designed security tool providing a human-in-the-loop confirmation mechanism for AI agents. It implements a 'zero-knowledge' architecture where the agent generates and verifies codes via secure local state files (mode 600) without ever seeing the code in its own context or logs. The scripts (generate_code.sh, send_otc_email.sh, verify_code.sh) use cryptographically secure entropy and follow defensive programming practices. Furthermore, the bundle includes an extensive 'Security Architecture Pack' with Python reference implementations for audit logging and permission guarding, specifically designed to protect against prompt injection and unauthorized command execution.
Capability Assessment
Purpose & Capability
The skill is an OTC/email confirmation system and it requires SMTP credentials and curl to send email — these requirements are expected and proportionate. The bundle contains both production-ready shell scripts (generate/send/verify) and Python reference implementations, which matches the README claim of two implementation paths. Declared primaryEnv (OTC_EMAIL_RECIPIENT) and required env vars align with the stated purpose.
Instruction Scope
The SKILL.md instructs the agent to call the included scripts and to keep the code in a permission-restricted state file; that is within scope. However, the document also contains examples and discussion of prompt-injection and 'system prompt override' patterns (pre-scan flagged these). Those appear to be explanatory examples in the threat model rather than instructions to override guards, but you should review the SKILL.md and scripts to confirm no lines attempt to change agent system prompts or perform out-of-band data collection. The skill asks that the agent 'not read the state file' — this is a policy constraint in docs and not an enforced OS-level guarantee; a compromised agent running as the same OS user could still access the file.
Install Mechanism
No remote install or arbitrary downloads — this is an instruction-only skill with bundled scripts and docs. That reduces supply-chain risk compared with fetching executables from unknown URLs. The only external binary dependency declared is curl, which is reasonable for SMTP-over-curl email sending.
Credentials
The skill requires SMTP credentials (OTC_SMTP_USER and OTC_SMTP_PASS) and an email recipient. Those are necessary for its stated function. However, SMTP credentials are sensitive; inspect scripts to ensure credentials are not exposed (for example, passed as literal args visible in process listings or written to logs). SKILL.md references additional optional env vars (SMTP_HOST/PORT, OTC_EMAIL_BACKEND, OTC_CUSTOM_EMAIL_SCRIPT) which are reasonable but should be audited when enabling backends or custom scripts.
Persistence & Privilege
The skill does not request always:true and is user-invocable. It does not claim to modify other skills or system-wide agent configuration. Its stated behavior (create per-user state dir and state file) is standard for this type of guard and scoped to the skill.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install otc-confirmation - After installation, invoke the skill by name or use
/otc-confirmation - Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.1.0
AI DevOps Agent Security Pack (12 files) + README bilingual rewrite + Python reference implementations
v3.0.4
otc-confirmation 3.0.4
- Updated documentation in SKILL.md with minor corrections and improved clarity.
- No code or functionality changes; this release is documentation-only.
v3.0.3
3.0.3 Changelog
- Updated README.md for improved documentation clarity and setup instructions.
- No code or functionality changes; this is a documentation-only update.
v3.0.2
v3.0.2: Declare OTC_SMTP_USER and OTC_SMTP_PASS in metadata requires.env
v3.0.1
v3.0.1: Fix metadata and reindex.
v3.0.0
v3.0: Zero-stdout security model - code flows through state file (mode 600), never printed. Crypto-secure /dev/urandom generation. Atomic single-use enforcement. No silent fallbacks. No arbitrary file sourcing. Proper metadata declaration. Sanitized docs.
v2.0.1
otc-confirmation 2.0.1
- Added four new files: _meta.json, references/enforcement-discipline.md, and bilingual email templates (email_template_en.txt, email_template_zh.txt)
- Updated documentation and changelog
- Improved and refined email sending scripts (send_email_smtp.sh, send_otc_email.sh) for better flexibility and clarity
- Enhanced enforcement and configuration references
v2.0.0
Major upgrade: Zero-dependency SMTP, multiple email backends, enhanced documentation, OpenClaw config integration
v1.0.0
Initial release
Metadata
Frequently Asked Questions
What is Otc Confirmation?
One-Time Confirmation code security mechanism for sensitive agent operations. Generates a cryptographically secure single-use code, delivers it via a private... It is an AI Agent Skill for Claude Code / OpenClaw, with 390 downloads so far.
How do I install Otc Confirmation?
Run "/install otc-confirmation" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Otc Confirmation free?
Yes, Otc Confirmation is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Otc Confirmation support?
Otc Confirmation is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Otc Confirmation?
It is built and maintained by Lewis Liu (@lewis-404); the current version is v3.1.0.
More Skills