Scenario Development

v1.0.0

Develop multiple future scenarios to prepare for uncertainty. Use for long-term strategic planning, risk management, and helping organizations think about th...

0· 81·0 current·0 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
Name and description match the SKILL.md content: a methodology for developing future scenarios. The skill requires no binaries, env vars, or config paths — proportional to an instruction-only planning aid.
Instruction Scope
SKILL.md provides structured steps, templates, and output formats for scenario planning. It uses input placeholders (e.g., $ARGUMENTS) but does not instruct reading unrelated system files, accessing secrets, or transmitting data to external endpoints.
Install Mechanism
No install spec and no code files are included (instruction-only). This is the lowest-risk install model; nothing is written to disk or executed by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths — consistent with an offline guidance/template skill.
Persistence & Privilege
Flags show always:false and normal model invocation. The skill does not request persistent presence or elevated privileges and does not modify other skills or system settings.
Assessment
This skill is an instruction-only scenario-planning template and appears coherent and low-risk. Before installing, consider: (1) Source verification — the registry metadata has no homepage and an opaque owner ID; if provenance matters, ask the publisher for more information. (2) Data sensitivity — the skill will rely on whatever input you provide (placeholders like $ARGUMENTS); avoid pasting confidential or proprietary data into prompts if you do not want it used in generated scenarios. (3) Output review — use the generated scenarios as facilitation material and verify facts/assumptions; the skill is a methodology, not a domain expert. If you need networked integrations, custom templates, or handling of sensitive inputs, prefer a vetted skill with clear provenance and explicit permissions.

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

latestvk97exkjt0czw5rw4cd1tamhvax83c7qz

License

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

Comments