Pre-Mortem Analyst
v1.0.0Imagine the project already failed, then work backward to find why. More powerful than risk assessment because it assumes failure is certain. Use when user says "pre-mortem", "premortem", "imagine this failed", "what could go wrong", "risk analysis", "before we launch", "stress test", "what would kill this", "project risks".
⭐ 4· 3.1k·17 current·18 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (pre-mortem analysis) matches the contents: facilitation steps, templates, examples, and frameworks for imagining failure. There are no unrelated requirements (no env vars, binaries, or installs) that would be unexpected for this purpose.
Instruction Scope
SKILL.md and reference docs provide step-by-step facilitation guidance, output templates, examples, and monitoring suggestions. The instructions do not tell the agent to read files, access environment variables, contact external endpoints, or collect system data beyond the user-provided project context.
Install Mechanism
No install spec or code files that would be written to disk or executed are present. Being instruction-only minimizes supply-chain/code-execution risk.
Credentials
The skill requests no environment variables, credentials, or config paths. This is proportionate for a facilitation/analysis skill that only needs user-provided project context.
Persistence & Privilege
always is false and default autonomous invocation is unchanged. The skill does not request persistent presence, system modification, or access to other skills' config.
Assessment
This skill is instruction-only and internally consistent with being a pre-mortem facilitator. It does not request credentials or install code, so supply-chain and credential-exfiltration risks are low. However, be cautious about the project data you paste into any third-party model or agent — do not include secrets, credentials, or sensitive PII in prompts. If you plan to run pre-mortems on proprietary projects, confirm how your agent/provider handles and stores prompt content and consider running initial tests with redacted or synthetic data. Lastly, review the examples/templates to ensure the output format and level of detail match your team's needs before using it in a live workshop.Like a lobster shell, security has layers — review code before you run it.
latestvk97em51kacd3xg5dbqv100v8c17zxb5k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.