Strategy Pattern Implementor

v1.0.0

Implement the Strategy pattern to encapsulate a family of interchangeable algorithms behind a common interface. Use when you have multiple conditional branch...

0· 58·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
Capability signals
CryptoCan make purchasesRequires OAuth token
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name and description match the runtime instructions: locate conditionals, design a Strategy interface, implement ConcreteStrategy classes, and refactor the Context. It does not request unrelated binaries, env vars, or config paths.
Instruction Scope
SKILL.md tells the agent to read and grep the codebase and to edit files (tools: Read, Grep, Edit, TodoWrite). Those actions are appropriate for a refactoring skill but mean the agent will access and modify repository files — ensure you want the agent to have that file-level access and review changes before applying them.
Install Mechanism
Instruction-only skill with no install spec and no code files. Lowest-risk installation footprint (nothing is written to disk by the skill itself).
Credentials
The skill requires no environment variables, credentials, or external config paths. Requested tools relate to code inspection/editing and are proportionate to the stated purpose.
Persistence & Privilege
always:false and no indications the skill modifies other skills or system-wide settings. It can be invoked autonomously (platform default), which is expected for a utility skill; combine with usual caution about autonomous code-modifying agents.
Assessment
This skill is internally consistent for refactoring to the Strategy pattern. Before enabling it, confirm you trust the agent's Read/Edit/Grep/TodoWrite tools because the skill will inspect and may modify your codebase. Prefer running it on a branch or in a sandbox and require explicit review of generated diffs/commits. If you have CI/pre-commit protections, keep them enabled to catch unintended changes. If you want tighter control, restrict the agent to read-only access or limit which files/directories it may edit.

Like a lobster shell, security has layers — review code before you run it.

algorithmsvk971gvav173hv2dhrh0ejq007d84j31pbehavioralvk971gvav173hv2dhrh0ejq007d84j31pbookforgevk971gvav173hv2dhrh0ejq007d84j31pcompositionvk971gvav173hv2dhrh0ejq007d84j31pdesign-patternsvk971gvav173hv2dhrh0ejq007d84j31pgofvk971gvav173hv2dhrh0ejq007d84j31platestvk971gvav173hv2dhrh0ejq007d84j31prefactoringvk971gvav173hv2dhrh0ejq007d84j31pstrategyvk971gvav173hv2dhrh0ejq007d84j31p

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📚 Clawdis

Comments