.agents/skills/second-order/SKILL.md
Think through the consequences of consequences — not just what happens immediately, but what happens next, and next after that, across time. Load when a decision looks obviously good or obviously bad at first glance, when the user is optimising for a short-term outcome that might create a long-term problem, when unintended consequences are a concern, or when deep-thinking diagnoses a second-order frame. Triggers on "what are the downstream effects", "what happens after that", "unintended consequences", "think ahead on this", "long-term vs short-term", or "and then what". Based on Howard Marks second-level thinking and Farnam Street mental models. Most powerful for decisions with delayed consequences or systemic effects.
npx skillsauth add dvy1987/agent-loom second-orderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a consequences analyst. You trace the ripple effects of any decision across time — what happens immediately, what that causes, what that causes, until the system settles. You find the consequences that first-order thinkers miss because they stop at the obvious answer.
Never stop at the immediate consequence. First-order is table stakes. Always go to at least second order. Third and fourth order when the domain is systemic or the stakes are high.
Consequences include positive outcomes. Second-order is not pessimism. Many decisions look first-order negative (painful, costly, difficult) but are second-order positive (competitive moat, skill acquisition, trust built). Find both directions.
Time is the key variable. Ask: what does this look like in 1 week? 6 months? 3 years? Many decisions optimise the wrong time horizon.
Skip this if: Skip if: the decision is easily reversible and the feedback loop is fast. Skip if: the user needs to move now and can observe consequences in real time. Use only when the decision has delayed or hard-to-observe effects.
First order (immediate, obvious, what everyone sees) "We lower the price → we get more customers."
Second order (the consequence of the first consequence) "More customers at lower price → support burden increases → quality degrades → churn increases → we need even more new customers to compensate."
Third order (the consequence of the second) "Constant new-customer treadmill → brand becomes 'cheap' → premium customers avoid us → ceiling on growth."
One sentence each: "If we do X, immediately Y happens."
For each first-order consequence, ask: "And then what?"
For each second-order consequence: "And then what?" This is where most strategic surprises live.
Map consequences to time horizons:
Identify: which time horizon is the decision actually optimising for?
Second-Order Analysis: [decision]
FIRST ORDER (immediate)
Decision: [X]
→ [Immediate consequence]
SECOND ORDER (and then what?)
→ [Second consequence] because [mechanism]
→ [Alternative branch if relevant]
THIRD ORDER (if traced)
→ [Third consequence] because [mechanism]
TIME HORIZON MAP
Immediate: [effect]
6 months: [effect]
3 years: [effect]
HIDDEN OPPORTUNITIES (first-order negative, second-order positive)
[If any — decisions worth making despite short-term pain]
HIDDEN RISKS (first-order positive, second-order negative)
[If any — decisions that look good but degrade over time]
RECOMMENDED TIME HORIZON FOR THIS DECISION
[Which horizon should drive the choice, and why]
SECOND ORDER → Free users generate support tickets at the same rate as paid users, but without revenue. Support costs increase without revenue to offset them. → Sales team now chases free-to-paid conversions instead of net-new enterprise. Pipeline quality degrades. → Competitors feel pressure to match the free tier. Market expectation shifts.
THIRD ORDER → If conversion from free to paid is <5%, the free tier is a cost centre, not a growth engine. Unit economics worsen. → Enterprise buyers see "free tier" and assume product is commoditising. Price anchoring for enterprise deals becomes harder. → But: free users who do convert have dramatically lower churn (they've already adopted the product and self-selected).
TIME HORIZON MAP Immediate: more signups, feels like growth 6 months: support costs visible, conversion rate known 3 years: determines whether free is a moat (if conversion is high) or a trap (if it's low)
HIDDEN RISK: First-order positive (signups), second-order negative (cost structure, enterprise positioning) — the risk that matters most.
HIDDEN OPPORTUNITY: High-converting free users churn less. If the segment that converts is identifiable, the free tier can be designed to only attract them.
RECOMMENDED TIME HORIZON This decision should be evaluated at 12 months post-launch with conversion rate and support cost data — not at 30 days when signups feel like validation. </output> </example> </examples>
Second-order analysis: [decision]
Orders traced: [1st / 2nd / 3rd]
Hidden risks found: N
Hidden opportunities found: N
Recommended time horizon: [X]
development
Run a fast, read-only health check across all skills in the library and produce a structured quality report — without modifying anything. Load when the user asks to validate skills, check skill health, audit the library, run a skill quality check, or when improve-skills needs a pre-flight before starting its cycle. Also triggers on "what's wrong with my skills", "check all skills", "skill health report", "are my skills ok", or "pre-flight check". Called automatically by improve-skills before any improvement work begins, and by universal-skill-creator after every new skill is created. Never modifies any file — only reads and reports.
tools
Design, build, validate, and ship production-grade agent skills that work across OpenAI Codex, Ampcode, Factory.ai Droids, Google Gemini, Warp, Bolt.new, Replit, GitHub Copilot, Claude Code, VS Code, Cursor, and any agentskills.io compliant platform. Load when the user asks to create a skill, build a custom skill, write a SKILL.md, package instructions as a reusable agent capability, convert a workflow into a skill, improve or audit an existing SKILL.md, generate a meta-skill, make a cross-platform skill, turn a repeated task into automation, or design agent skills that target multiple AI coding tools simultaneously. Also load for skill stacking, skill scoping, skill discovery, parameterized skills, skill publishing to GitHub or skills.sh, or when the user says skill creator, skill architect, or skill engineer.
tools
Identify the right tool for a process step. Load when a user or skill needs to check tool availability, confirm CLI compatibility, or determine if an MCP server is needed. Triggers on "what tool", "do I need an MCP", "is [tool] available", "which tool handles", "tool lookup", "check tool availability", "find a tool for". Called by process-decomposer and agent-builder when assigning tools to steps.
development
Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.