Agent skill

Thinking Second Order

by tjboudreaux in tjboudreaux/cc-thinking-skills

When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

MITAuto-check passed

Install Thinking Second Order

skills CLI
$ npx skills add tjboudreaux/cc-thinking-skills --skill thinking-second-order -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tjboudreaux/cc-thinking-skills thinking-second-order --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tjboudreaux/cc-thinking-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/thinking-second-order .claude/skills/thinking-second-order && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
thinking-second-order
GitHub stars
1.6k
Token cost
~747 tokens
SKILL.md length
343 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

  • Works in 5 steps: State decision and first-order effect.… → Chain "and then what?" At least two… → Expand affected parties. Who else reacts… → …
  • SKILL.md covers When to Use, When NOT to Use, Procedure and Output, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Thinking Second Order is an agent skill from tjboudreaux/cc-thinking-skills. When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: 28 eval-informed mental models and critical-thinking skills for Claude Code, GitHub Copilot, Codex, Cursor, and other Agent Skills-compatible tools. The licence is MIT.

Example prompts

  • “/thinking-second-order”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. State decision and first-order effect. One sentence each: action and intended immediate result.
  2. Chain "and then what?" At least two further orders. For each link record: effect, who responds, rough probability (high/med/low), timing…
  3. Expand affected parties. Who else reacts (users, operators, other teams, attackers, markets)? What incentives does the change create or…
  4. Scale test. Ask what happens if everyone does this or usage grows 10x. Mark paths that only appear under scale or repetition.
  5. Prune and decide. Drop speculative links that do not change the choice. Keep only effects that alter go/no-go, design, or mitigations…

What it can do on your machine

Read from SKILL.md and the folder at commit 7b8fece. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Thinking Second Order loads about 747 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 343 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~747

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tjboudreaux/cc-thinking-skills at commit 7b8fece, republished under its MIT licence (© tjboudreaux). 343 words, ~747 tokens.

Download SKILL.mdSave it as .claude/skills/thinking-second-order/SKILL.md (or your agent's skills folder).
name
thinking-second-order
description
When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.
disable-model-invocation
true

Second-Order Consequence Chains

Do not stop at the intended first effect. Trace what happens next across actors, time, and feedback until the chain stops changing the decision.

When to Use

  • Strategic, policy, incentive, or architecture choices with lasting coupling.
  • The obvious fix feels too easy or has known backfire patterns.
  • Success or scale would create new problems (load, gaming, debt).
  • Need to compare options by delayed effects, not only day-one benefit.

When NOT to Use

  • Local reversible edit with no incentive or cross-component coupling—just ship and observe.
  • Full system structure (stocks, many loops, leverage ranking) is the goal—use systems.
  • Pre-mortem of failure modes for a plan already chosen—use pre-mortem.
  • Pure mechanical changes (rename, format) with no behavioral effect.

Procedure

  1. State decision and first-order effect. One sentence each: action and intended immediate result.
  2. Chain "and then what?" At least two further orders. For each link record: effect, who responds, rough probability (high/med/low), timing (immediate / next cycle / at scale), and whether it feeds back into the original problem (reinforce or counteract).
  3. Expand affected parties. Who else reacts (users, operators, other teams, attackers, markets)? What incentives does the change create or destroy?
  4. Scale test. Ask what happens if everyone does this or usage grows 10x. Mark paths that only appear under scale or repetition.
  5. Prune and decide. Drop speculative links that do not change the choice. Keep only effects that alter go/no-go, design, or mitigations. Revise the action or add guards where second-order harm exceeds first-order gain.

Stop when further "and then what?" no longer changes the decision, or the remaining chain is pure speculation without mechanism.

Output

text
decision: <action>
first_order: <intended immediate effect>
chain:
  - order: 2
    effect: <what>
    actors: <who>
    p: high|med|low
    when: immediate|next_cycle|at_scale
    feedback: none|reinforce|balance
  - order: 3
    ...
scale_if_universal: <one sentence or n/a>
revised_decision: <same | modified action | no-go>
mitigations: <guards for kept risks>

Verification

  • Falsify: If no credible second-order path changes the choice, first-order is enough—stop inventing cascades. If the core issue is multi-loop structure rather than one decision's trail, switch to systems.
  • Stop: End at the first order that no longer affects the decision; do not pad to a fixed depth.
  • Over-application guard: No low-probability sci-fi chains. No treating parameter tweaks as deep strategy. Probability and timing required on kept links; omit decoration without mechanism.

© tjboudreaux, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/thinking-second-order of tjboudreaux/cc-thinking-skills.

Open the folder on GitHubat commit 7b8fece

Compare with similar skills

Thinking Second Order next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Thinking Second Order compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Thinking Second Order this skilltjboudreaux/cc-thinking-skills1.6k—~747Automated safety check: PassMIT
Performing Second Order SQL Injectionmukul975/Anthropic-Cybersecurity-Skills34k—~2.3kAutomated safety check: WarnApache-2.0
Second Order Odesparcadei/Continuous-Claude-v33.9k1 repos~830Automated safety check: NotesMIT
Add Effectremotion-dev/remotion63k—~2.8kAutomated safety check: PassCustom licence
Effect V4ComposioHQ/composio30k—~1kAutomated safety check: PassMIT
CSS Orderthedaviddias/Front-End-Checklist74k—~404Automated safety check: PassMIT

Similar skills

  • Performing Second Order SQL Injection

    mukul975/Anthropic-Cybersecurity-Skills

    Detect and exploit second-order SQL injection vulnerabilities where malicious input is stored in a database and later executed in an unsafe SQL query during a different application operation.

    34k GitHub stars~2.3k tokensUpdated 1 mo ago
    SecurityAuto-check: warnings
  • Second Order Odes

    parcadei/Continuous-Claude-v3

    Problem-solving strategies for second order odes in odes pdes

    3.9k GitHub starsUsed in 1 repo~830 tokens
    Research & ScienceAuto-check: notes
  • Add Effect

    remotion-dev/remotion

    Official

    Add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, Remotion skill updates, formatting, and builds.

    63k GitHub stars~2.8k tokensUpdated today
    Media & CreativeAuto-check passed
  • Effect V4

    ComposioHQ/composio

    Write, review, or upgrade Effect v4 code in the Composio CLI, cli-keyring, and json-schema-to-effect-schema packages, all pinned exactly to effect@4.0.0-rc.117 — Context.Service and explicit layers…

    30k GitHub stars~1k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • CSS Order

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Order CSS files correctly.

    74k GitHub stars~404 tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed
  • Focus Order

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order.

    74k GitHub stars~519 tokensUpdated 3 days ago
    Frontend & DesignAuto-check passed

More from tjboudreaux/cc-thinking-skills

All 26 skills in this repo
  • Thinking Bounded Rationality

    tjboudreaux/cc-thinking-skills

    A skill your agent uses when search or investigation could run forever.

    1.6k GitHub stars~703 tokensUpdated 2 mo ago
    Auto-check passed
  • Thinking Circle Of Competence

    tjboudreaux/cc-thinking-skills

    A skill your agent uses when a specific claim may lack grounding.

    1.6k GitHub stars~733 tokensUpdated 2 mo ago
    Auto-check passed
  • Thinking Lindy Effect

    tjboudreaux/cc-thinking-skills

    A skill your agent uses when longevity of a non-perishable option matters.

    1.6k GitHub stars~650 tokensUpdated 2 mo ago
    Auto-check passed
  • Thinking Via Negativa

    tjboudreaux/cc-thinking-skills

    A skill your agent uses when the reflex is to add a feature, layer, or process.

    1.6k GitHub stars~735 tokensUpdated 2 mo ago
    Auto-check passed
  • Thinking Cynefin

    tjboudreaux/cc-thinking-skills

    When the right response mode is unclear, classify the cause-effect domain first; decompose disorder.

    1.6k GitHub stars~651 tokensUpdated 2 mo ago
    Auto-check passed
  • Thinking Five Whys Plus

    tjboudreaux/cc-thinking-skills

    When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.

    1.6k GitHub stars~881 tokensUpdated 2 mo ago
    Auto-check passed

Questions about Thinking Second Order

What does Thinking Second Order do?

When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing. Thinking Second Order is an agent skill from tjboudreaux/cc-thinking-skills. When a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.

How do I install Thinking Second Order in Claude Code?

Run `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-second-order -a claude-code`. Or copy the skill folder (skills/thinking-second-order in tjboudreaux/cc-thinking-skills) into .claude/skills/thinking-second-order in your project. Claude Code loads it when a task matches its description.

How do I install Thinking Second Order in Codex?

Run `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-second-order -a codex`. Or copy the skill folder (skills/thinking-second-order in tjboudreaux/cc-thinking-skills) into .agents/skills/thinking-second-order in your project. Codex loads it when a task matches its description.

Can I use Thinking Second Order in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tjboudreaux/cc-thinking-skills --skill thinking-second-order -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/thinking-second-order, .gemini/skills/thinking-second-order, .github/skills/thinking-second-order and .opencode/skills/thinking-second-order in your project.

What does Thinking Second Order need to run?

SKILL.md names no scripts, command-line tools or credentials: Thinking Second Order is instructions for the agent only.

Does Thinking Second Order access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Thinking Second Order safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Thinking Second Order use?

Thinking Second Order is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Thinking Second Order use?

About 747 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Thinking Second Order?

Skills that share tags, products or a category with Thinking Second Order: Performing Second Order SQL Injection (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Second Order Odes (parcadei/Continuous-Claude-v3, 3.9k stars), Add Effect (remotion-dev/remotion, 63k stars) and Effect V4 (ComposioHQ/composio, 30k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Thinking Second Order?

tjboudreaux (a GitHub user) maintains it in tjboudreaux/cc-thinking-skills, which has 1,612 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on August 7, 2026.

Source: tjboudreaux/cc-thinking-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.