State Management
v1.0.0Deep workflow for client (and hybrid) state—modeling domain vs UI state, server cache vs client store, async and consistency, DevTools, persistence, and test...
⭐ 0· 72·0 current·0 all-time
by@clawkk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description (deep state-management workflow) match the SKILL.md content. All guidance is about modeling client/server/UI state, libraries, and testing; no unexplained dependencies, credentials, or unrelated capabilities are requested.
Instruction Scope
SKILL.md is pure advisory content (design stages, rules, checklists). It does not instruct the agent to read files, access environment variables, call external endpoints, or transmit data outside the user's context. The instructions are scoped to interviewing the user, choosing patterns, and giving implementation advice.
Install Mechanism
No install specification or code files are present. This is the lowest-risk form: nothing is written to disk and no third-party packages are pulled in.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate for a purely instructional design/architectural workflow.
Persistence & Privilege
always:false (default) and autonomous invocation is allowed (platform default). This is normal. One minor provenance note: the skill lists no homepage and the source is unknown; that reduces trust but does not create a technical incoherence.
Assessment
This skill is an instruction-only design guide for frontend state management and appears internally consistent and low-risk: it doesn't request creds, install code, or access files. Before installing, consider that the skill has no listed homepage or known source—if provenance matters for your team, prefer skills from trusted authors or inspect SKILL.md yourself. Also remember that although the skill can't execute code itself, an agent using it may suggest code changes or commands—avoid granting the agent repository write/push or cloud credentials unless you intend it to act on your codebase. If you want more assurance, ask the publisher for source or a homepage, or copy the guidance into an internal doc instead of installing the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk977gsyvdkd9m4a2dhezavd8v583g2d0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.