Chain Reason
v1.0.3Provides detailed, auditable multi-step reasoning traces for complex questions requiring 3+ logical steps, tradeoff analysis, or explicit explanation requests.
⭐ 0· 73·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 promise an explicit reasoning-trace formatter and the SKILL.md contains only templates, rules, and activation guidance for when to emit traces. There are no unrelated env vars, binaries, or install steps requested.
Instruction Scope
The runtime instructions are limited to producing formatted traces and tradeoff analyses and do not direct file I/O, network calls, or credential access. Note: the skill uses keyword triggers (e.g., 'reason', 'how', 'why') which are broad and can cause frequent activation; it also deliberately exposes chain-of-thought style outputs, which may leak internal reasoning if you consider that sensitive.
Install Mechanism
Instruction-only skill with no install spec and no code files; nothing is written to disk and no external packages are downloaded.
Credentials
No environment variables, credentials, or config paths are requested. The SKILL.md does not reference undeclared secrets or external services.
Persistence & Privilege
Skill does not request always:true or system-level persistence. Default autonomous invocation is allowed by platform but the skill itself does not escalate privileges or modify other skills.
Assessment
This skill is coherent for its stated purpose — it simply prescribes how the agent should present multi-step reasoning. Before installing, decide whether you want the agent to emit explicit chain-of-thought traces: those outputs can reveal intermediate reasoning steps and heuristics that you may prefer not to expose (to users, logs, or external systems). Also note the keyword triggers are broad and may cause the skill to activate more often than you expect. If concerned, test in a sandbox, restrict who can invoke the skill, or ask the skill author to narrow triggers (or require an explicit opt-in token) and to include guardrails about omitting sensitive internal heuristics from traces.Like a lobster shell, security has layers — review code before you run it.
latestvk9757nma8121gs0shpk6ntqtdd84rf4y
License
MIT-0
Free to use, modify, and redistribute. No attribution required.