Designer Cognition
v1.0.0设计师认知 Skill —— SOUL五律适配视觉设计，设计系统碰撞+可访问性红线+迭代记忆
⭐ 0· 47·0 current·0 all-time
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 SKILL.md all describe a design-cognition utility (SOUL 五律, design-system checks, accessibility, iteration memory). There are no unexpected env vars, binaries, or credentials requested that would be unrelated to this purpose.
Instruction Scope
The instructions direct the agent to maintain local design memory (design_log/{date}.md, iteration_history/, component_library/, etc.) and to follow explicit checklist rules. They do not ask the agent to read system secrets or unrelated files. Minor note: the SKILL.md implies writing files but provides no path-safety constraints — the agent will need file-write permissions and an operator should confirm where these files will be stored.
Install Mechanism
This is an instruction-only skill with no install spec or code. SKILL.md and README show a CLI command 'clawhub install designer-cognition' but no install manifest is included. That mismatch is low-risk but the user should verify what 'clawhub install' would actually do before running it.
Credentials
No required environment variables, credentials, or config paths are declared or referenced. The skill's behavior does not require external tokens or unrelated service access.
Persistence & Privilege
always is false and the skill does not request elevated platform privileges or changes to other skills. It suggests creating local memory files (normal for an agent memory pattern) but does not demand permanent global presence.
Assessment
This skill appears coherent for a design-cognition helper and does not request secrets or external endpoints. Before installing or allowing an agent to use it: 1) verify what 'clawhub install designer-cognition' actually does (there is no install spec in the package); 2) confirm where the agent will write memory files and limit write permissions to an appropriate project directory; 3) review the referenced GitHub repo and license if you plan to pull code; and 4) if your agent has network/file access, ensure it cannot write outside the intended workspace or exfiltrate data.Like a lobster shell, security has layers — review code before you run it.
latestvk97evnd1ywkfm82wnxs88s8drn83yjdh
License
MIT-0
Free to use, modify, and redistribute. No attribution required.