Observer Pattern Implementor
v1.0.0Implement the Observer pattern to establish one-to-many dependencies where changing one object automatically notifies and updates all dependents. Use when a...
⭐ 0· 78·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
Name, description, and declared required tools (Read, Write, TodoWrite, optional Grep/Glob) match an implementation/refactor skill for the Observer pattern. There are no unrelated environment variables, binaries, or install steps requested.
Instruction Scope
SKILL.md instructs the agent to audit code, define interfaces, implement Attach/Detach/Notify, consider push vs pull, and optionally implement a ChangeManager; it explicitly requires a codebase or detailed design. The instructions require reading and writing the user's codebase (expected for a refactor) but do not direct the agent to read unrelated system files, access secrets, or send data to external endpoints.
Install Mechanism
No install spec and no code files to write to disk by the skill itself. This is an instruction-only skill (lowest install risk).
Credentials
The skill requires no environment variables, credentials, or config paths. The only required capabilities are code-reading and code-writing tools, which are proportionate to the described refactor task.
Persistence & Privilege
always:false (default) and model invocation not disabled — normal for a user-invocable skill. The skill does not request permanent elevated privileges or modification of other skills' configurations.
Assessment
This skill appears internally consistent and intended to refactor your code to implement the Observer pattern. Before running it: 1) Make a backup or create a feature branch so you can review changes; 2) Require the agent to produce a diff/PR rather than applying changes directly if you want human review; 3) Ensure automated tests run after the refactor (observer changes can introduce subtle ordering, consistency, or lifetime bugs); 4) Limit the agent's file-write scope to the relevant project directories; 5) Review any produced changes for dangling-reference handling, notification timing, and whether a ChangeManager (more complex) is actually needed. If you want extra assurance, ask the agent to list exactly which files it will modify before applying edits.Like a lobster shell, security has layers — review code before you run it.
behavioralvk97chw9s567qnwqpmdek7dv6tn84kcj8bookforgevk97chw9s567qnwqpmdek7dv6tn84kcj8change-managervk97chw9s567qnwqpmdek7dv6tn84kcj8design-patternsvk97chw9s567qnwqpmdek7dv6tn84kcj8event-systemvk97chw9s567qnwqpmdek7dv6tn84kcj8gofvk97chw9s567qnwqpmdek7dv6tn84kcj8latestvk97chw9s567qnwqpmdek7dv6tn84kcj8mediatorvk97chw9s567qnwqpmdek7dv6tn84kcj8mvcvk97chw9s567qnwqpmdek7dv6tn84kcj8observervk97chw9s567qnwqpmdek7dv6tn84kcj8publish-subscribevk97chw9s567qnwqpmdek7dv6tn84kcj8singletonvk97chw9s567qnwqpmdek7dv6tn84kcj8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis