Skip to content
TrustedSkillsbeta
Back to all skills

Premortem

Checked
parcadei·vlatest·other·MIT

The Premortem skill simulates a "what if" scenario before development to proactively identify potential risks and improve project outcomes.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add parcadei/continuous-claude-v3 --skill premortem -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

parcadei

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned parcadei/continuous-claude-v3 at d07ff4b06b.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d07ff4b06b
Manifest
.claude/skills/premortem/SKILL.md
Scanned
1 file, 420 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The premortem skill facilitates a structured brainstorming session to proactively identify potential failure points in a plan or project. It guides the AI agent to imagine a future scenario where the plan has failed and then work backward to determine what could have gone wrong. This process helps uncover hidden risks and allows for preventative measures to be taken.

When to use it

  • Before launching a new product feature: Identify potential issues before release.
  • Planning a complex marketing campaign: Anticipate roadblocks and adjust strategies accordingly.
  • Embarking on a significant organizational change: Uncover unforeseen consequences early on.
  • Preparing for a critical presentation or negotiation: Consider what could derail the outcome and plan responses.

Key capabilities

  • Simulates future failure scenarios.
  • Elicits potential causes of failure through backward reasoning.
  • Facilitates identification of hidden risks.
  • Promotes proactive problem-solving.

Example prompts

  • "Let's do a premortem for the launch of our new mobile app."
  • "Imagine our project to migrate to a new CRM has failed spectacularly. What went wrong?"
  • "Conduct a premortem on our proposed marketing strategy for Q4."

Tips & gotchas

The skill is most effective when used with teams or individuals who are willing to honestly consider potential failure points. A diverse group can provide varied perspectives and uncover a wider range of risks.