Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Quantitative Problem Solving

ASecurity

Use this when something failed or may fail — enumerate failure hypotheses, cost each try, update P(cause|history), and pick the next action by expected value / EVPI.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agents

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill quantitative-problem-solving --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quantitative Problem Solving?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Quantitative Problem Solving
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-quantitative-problem-solving/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-quantitative-problem-solving)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: Quantitative Problem Solving
description: >-
  Use this when something failed or may fail — enumerate failure hypotheses,
  cost each try, update P(cause|history), and pick the next action by expected
  value / EVPI.
---

# Quantitative Problem Solving

Companion to RavenClaude Core. Prefer math over vibes when choosing the next try after failure.

## Stance

1. Failure is information — log it; update beliefs; do not hide it.
2. Retry is not repeat — change hypothesis, method, or observation.
3. Occam as prior — more complex causes get lower prior unless evidence demands them.
4. Score the next poke — rank by expected value (or EV of information), not gut.
5. Stop when EV-negative or wall — escalate with the table, not a novel.

## Workflow 1 — Hypothesis table

Columns: ID, Hypothesis, Prior P0, Complexity (Occam low/med/high), Signature, Ruled out if.

Occam-adjusted prior (simple): unnormalized weight = base_plausibility / (2 ** k), where k = extra-assumptions count. Normalize so priors sum to 1.

Map hypotheses to failure variables: auth, network, permissions, version skew, bad input, wrong target, flake, capacity, logic bug, config drift, and domain-specific ones.

## Workflow 2 — Cost of each try

For each candidate action (probe, fix, rollback, ask human, switch tool), score time, token/money, and blast/risk. Total C(a) = weighted sum; state weights once per session. Irreversible / money / delete get huge risk or require CoS/HITL.

## Workflow 3 — Update from history (Bayes)

After outcome o, set likelihood L(o | Hi) on a coarse scale (0.05, 0.2, 0.5, 0.8, 0.95). Posterior P(Hi | o) proportional to L(o | Hi) * P(Hi); renormalize. Identical blind retries should not move posteriors — design a new observation.

## Workflow 4 — Choose next action

EV(a) = P(solve | a) * U_solve + (1 - P(solve | a)) * U_fail - C(a). Pick the allowed action with max EV. If EV of perfect information exceeds the best probe cost, probe before a heavy fix.

## Deliverable shape

1. Hypothesis table (priors + posteriors)
2. Cost table for candidate tries
3. Chosen action + EV one-liner
4. What would falsify it next
5. Escalation trigger if top actions are blocked

## Anti-patterns

One-and-done abandonment; same failing command on loop; complex conspiracies without Occam penalty; nuclear options without cost; skipping the table when two or more causes remain.

## Credit

Companion to RavenClaude Core — first principles + Occam + Bayesian try-ranking.

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →