Skip to content
FunCoding

Search

Search docs, Skills and MCP

thinking-effectuation

Under genuine uncertainty with no reliable forecast, inventory means, cap downside at affordable loss, act for commitments, and let goals emerge from controllable moves.

AI 与智能体1.6kskills/thinking-effectuation/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/tjboudreaux/cc-thinking-skills/thinking-effectuation/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Effectuation

Under Knightian uncertainty, start from available means and affordable loss—not a fixed goal and predicted return. Create the path through controllable action and real commitments.

When to Use

  • The market, technology, or problem is novel enough that outcome probabilities are not trustworthy.
  • Means are clearer than the goal: identity, skills, assets, and network exist before a fixed target does.
  • A small action can buy information or a partner commitment without risking ruin.
  • Plans keep breaking because the environment shifts faster than forecasts.

When NOT to Use

  • The path is predictable: known market, knowable unit economics, established playbook → use causal planning.
  • A single wrong step is ruinous or irreversible → de-risk first; do not treat affordable-loss steps as free.
  • The goal is already fixed and resources are the only uncertainty → plan to the goal.
  • Routine execution with settled requirements → act; do not re-inventory means.

Procedure

  1. Inventory means only. List who you are (skills, constraints, values), what you know (domain, tools, data), and who you know (reachable partners, users, resources). Reject "what would be needed for an ideal plan" as input.
  2. Cap affordable loss. State the maximum time, money, reputation, and opportunity cost you can lose and still continue. If the proposed step exceeds any cap, redesign the step smaller or stop.
  3. Choose one controllable next action. Prefer the smallest action that can yield either (a) a real commitment from someone else or (b) discriminating information. Act inside the loss cap; do not optimize expected return.
  4. Seek commitments, not opinions. Share the working means-based offer. Anyone who commits resources, access, or work becomes a co-creator and may reshape the goal. Discard non-committing feedback as non-binding.
  5. Leverage contingencies. Treat surprises as new means: failed hires, competitor moves, off-roadmap requests. Ask "how can this expand control?" not "how do we restore the old plan?"
  6. Update means and goal, then stop or loop. Fold new means and commitments into the inventory; restate the emerging goal. Stop when a viable path is controlled enough to execute, the loss cap is exhausted without traction, or uncertainty collapses into a predictable plan (then switch to causal planning).

Output

Emit an effectuation brief:

  • means: identity / knowledge / network actually available now
  • affordable_loss: hard caps (time, money, reputation, opportunity)
  • next_action: one controllable step inside those caps
  • commitments_sought_or_won: who must put skin in the game, and what changed if they did
  • contingencies_used: surprises turned into means (or none)
  • emerging_goal: current goal shaped by means and commitments (may differ from the starting wish)
  • stop_or_loop: continue under effectuation, switch to causal planning, or halt

Verification

  • Falsify means-first claims: if the brief starts from a fixed goal and backfills resources, rewrite from means or abandon effectuation.
  • Loss-cap check: every recommended action must fit inside stated affordable loss; if not, shrink or stop.
  • Commitment test: progress that depends only on predictions or uncommitted interest is invalid—require at least one real commitment or a cheap information gain.
  • Over-application guard: if a reliable forecast and known playbook exist, do not force effectuation; plan causally.
  • Stop: after one means → loss-cap → action → commitment cycle with an explicit stop/loop decision; do not endless-explore under the effectuation label.

Similar Skills

brand-guidelines
anthropics/skills180k

brand-guidelines

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

AI & agents

internal-comms
anthropics/skills180k

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

AI & agents

template-skill
anthropics/skills180k

template-skill

Replace with description of the skill and when Claude should use it.

AI & agents

mcp-builder
anthropics/skills180k

mcp-builder

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI & agents

algorithmic-art
anthropics/skills180k

algorithmic-art

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

AI & agents

academy-guide
anthropics/skills180k

academy-guide

Stop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.

AI & agents