Command Pattern Implementor
v1.0.0Implement the Command pattern to encapsulate requests as objects, enabling parameterized operations, queuing, logging, and undo/redo. Use when you need to de...
⭐ 0· 84·0 current·0 all-time
byHung Quoc To@quochungto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description match the SKILL.md and reference guide: all required items (invoker, receiver, commands, history, macro) are relevant. No unrelated binaries, credentials, or config paths are requested.
Instruction Scope
Runtime instructions and the reference guide stay on-topic: they describe design and implementation steps (interfaces, state capture, copying, persistence for crash recovery). They do mention logging/persistent history (writing/reading command logs) which is expected for this feature but should be implemented with usual security care.
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The optional tools (TodoWrite, Read, Write, Grep, Bash) are appropriate for editing and inspecting a codebase.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request persistent system presence or modify other skills' configs. The guidance to implement persistent command logs is a design detail, not an automatic privilege escalation.
Assessment
This is a coherent, instruction-only design/implementation guide for the Command pattern. Before using it in your codebase: 1) review any code you write for persistent history to ensure logs are written to safe locations and don't serialize sensitive data; 2) when implementing Store/Load/replay, validate and authenticate any data read from disk before executing it (to avoid executing attacker-controlled payloads); 3) in languages without GC, follow the MacroCommand ownership guidance to avoid leaks; and 4) test undo/redo fidelity (consider Memento for exact restoration). If you require help turning these instructions into safe code for your platform/language, request a code implementation review.Like a lobster shell, security has layers — review code before you run it.
behavioralvk97830c2bs5xedcc05xxr0380x84j3bdbookforgevk97830c2bs5xedcc05xxr0380x84j3bdcommandvk97830c2bs5xedcc05xxr0380x84j3bddesign-patternsvk97830c2bs5xedcc05xxr0380x84j3bdgofvk97830c2bs5xedcc05xxr0380x84j3bdhistoryvk97830c2bs5xedcc05xxr0380x84j3bdinvokervk97830c2bs5xedcc05xxr0380x84j3bdlatestvk97830c2bs5xedcc05xxr0380x84j3bdmacrovk97830c2bs5xedcc05xxr0380x84j3bdreceivervk97830c2bs5xedcc05xxr0380x84j3bdredovk97830c2bs5xedcc05xxr0380x84j3bdtransactionvk97830c2bs5xedcc05xxr0380x84j3bdundovk97830c2bs5xedcc05xxr0380x84j3bd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis