SKILLEMALL.ai
GitHub ↗ RU Sign in

BC pre-mortem

Runs a pre-mortem that sorts launch risks into evidenced tigers, paper tigers and unspoken elephants, each with an owner. Use when a big launch, build or migration is coming, or the team has a bad feeling it cannot name.

borghei/Claude-Skills Agent Skills author: borghei 9 files · 1 script body ≈ 1 885 tokens Open the sourcegithub.com↗ analyzed 7 h ago

Runs a pre-mortem that sorts launch risks into evidenced tigers, paper tigers and unspoken elephants, each with an owner.

As a process C 55/100 · Has gaps — References files that are not bundled: references/*.md

AnalyzerOperations and projectstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
92/100
safety, quality, tests
Safety 60%
96
Quality 40%
86
Run on models
none yet
Process rating
C
55/100
Has gaps
References files that are not bundled: references/*.md
Tools and files w 18
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 4

✓ No critical or high findings

Medium and low: 4
  • low Risky intent intent-offensive-security examples/shared-dashboards-v1-pre-mortem.md:159
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)
    - Penetration test on the embed flow scheduled
    fixture
  • low Risky intent intent-offensive-security examples/shared-dashboards-v1-pre-mortem.md:162
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)
    - Bug bounty pre-announcement to the security
    fixture
  • low Risky intent intent-offensive-security examples/shared-dashboards-v1-pre-mortem.md:378
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)
    - Penetration test (R3) is COMPLETE and clean
    fixture
  • low Risky intent intent-offensive-security examples/shared-dashboards-v1-pre-mortem.md:408
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (test fixture / example file)
    - **Launch readiness gate is explicit.** All 14 Tigers in progress + all 3 Elephants resolved + penetration test + DPIA + indexing controls. Without these, the launch slips. The slip authority is name
    fixture

Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: references/*.md

Process rating: all ten parameters 55/100

Will not run. References files that are not bundled: references/*.md
  • 0Tools and files. 1 referenced file(s) missing: references/*.md
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 55Failures and branches. 1 branches
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 19 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1885 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 220: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 19 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)
  • +3All 1 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.