Structure Thinking

v1.0.0

Structured problem analysis and communication using system mapping and hierarchical logic. Use when a request involves messy, multi-factor problems, root-cau...

1· 726·4 current·4 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description (structured problem analysis, system mapping, hierarchical logic) matches the SKILL.md and reference files. All included materials are guidance, templates, and examples that support the stated purpose.
Instruction Scope
Runtime instructions are limited to asking for user inputs, building models, and producing templates/memos. They do not instruct the agent to read system files, call external or hidden endpoints, access environment variables, or exfiltrate data. Prompts reference metrics and trends but expect the user or agent context to provide those, which is appropriate for this type of skill.
Install Mechanism
No install spec and no code files that execute. Instruction-only skill — nothing is downloaded or written to disk as part of installation.
Credentials
The skill declares no required environment variables, no credentials, and no config paths. There are no unexplained secrets or cross-service credentials requested.
Persistence & Privilege
always:false (not force-installed) and disable-model-invocation:false (normal — agent may invoke the skill when eligible). The skill does not request persistent system changes or modify other skills' configs.
Assessment
This skill is a set of templates and step-by-step guidance for structuring messy problems and appears internally consistent. Before installing, confirm that you understand it will ask for context (metrics, owners, constraints) — it does not itself access your systems or secrets. If you plan to let the agent access external data sources (databases, monitoring, or files) to populate metrics, make sure those data-accessing skills/tools are authorized and reviewed separately. If you prefer the agent not to invoke skills autonomously, consider disabling autonomous invocation at the agent/platform level.

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

latestvk97fzdqke10q18s16g7mv5x73d827mbk

License

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

Comments