Agent skill

Good Thinking

by jwynia in jwynia/agent-skills

Diagnose thinking failures and maintain process-sovereignty by auditing cognitive orientation and operation balance.

MITAuto-check passedAgent Workflows

Install Good Thinking

skills CLI
$ npx skills add jwynia/agent-skills --skill good-thinking -a claude-code

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

GitHub CLI
$ gh skill install jwynia/agent-skills good-thinking --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/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/general/meta/good-thinking .claude/skills/good-thinking && 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
good-thinking
GitHub stars
169
Token cost
~8.1k tokens
SKILL.md length
4,248 words
Files
3 (incl. references)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Diagnose thinking failures and maintain process-sovereignty by auditing cognitive orientation and operation balance.

  • Works in 5 steps: Identify what's fixed. Ask: "In this… → Check Monitor. Is Monitor serving… → Assess operation balance. Which… → …
  • Agent Workflows work in your project
  • SKILL.md covers Core Principle, When to Use This Skill, The Two Entity Types and The Seven Operations, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Good Thinking is an agent skill from jwynia/agent-skills. Diagnose thinking failures and maintain process-sovereignty by auditing cognitive orientation and operation balance.

Its SKILL.md is about 8.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/agent-instructions.md` and `references/structural-account.md`).

It sits in Agent Workflows. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/good-thinking”

Workflow steps

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

  1. Identify what's fixed. Ask: "In this thinking process, what is not moving? What conclusion, role, comfort level, or output goal is being…
  2. Check Monitor. Is Monitor serving inquiry or defending a position? Signs of co-opted Monitor: metacognitive activity that produces…
  3. Assess operation balance. Which operation pairs are active? Which poles are collapsed? Is the balance matched to the environment's…
  4. Match the capture mechanism. Three structurally different mechanisms require different interventions
  5. Select intervention based on mechanism, not surface behavior. The same surface error (e.g., anchoring) can have different mechanisms…

What it can do on your machine

Read from SKILL.md and the folder at commit e02ec7e. 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

Good Thinking loads about 8.1k tokens when it runs, and up to ~17k if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 4,248 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~8.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~17k

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 jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 4,248 words, ~8,119 tokens.

Download SKILL.mdSave it as .claude/skills/good-thinking/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
good-thinking
description
Diagnose thinking failures and maintain process-sovereignty by auditing cognitive orientation and operation balance.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.domain
cognition
metadata.cluster
methodology
metadata.type
diagnostic
metadata.mode
diagnostic+assistive

Core Principle

Good thinking is an active achievement, not a default state. Operations without orientation produce sophisticated wrong answers; orientation without operations produces good intentions with no traction.

Two structurally different things must work together: operations (cognitive verbs that transform representations) and orientations (what the operations are in service of). Every thinking failure can be located as an operation failing, an orientation captured, or — most commonly and most dangerously — operations functioning well in service of the wrong orientation.

The orientation that produces good thinking is process-sovereignty: the process of inquiry is what's committed to; conclusions are what move. This skill diagnoses when that orientation has been captured and which operations need adjustment.

When to Use This Skill

Use when:

  • Reasoning feels stuck or circular
  • A conclusion feels defended rather than discovered
  • Confidence is high but evidence is thin
  • You need to audit whether thinking is serving inquiry or serving comfort
  • Analysis is becoming more elaborate without becoming more accurate
  • Someone (self or user) is explaining away evidence rather than integrating it
  • The same approach keeps being applied despite poor results

The Two Entity Types

Operations

Seven operations that transform representations. They work in complementary pairs — polarities to oscillate between, not choices. The skill is in the oscillation. Operations are powerful, general-purpose, and completely agnostic about what they serve. The same operations that produce genuine insight also produce sophisticated self-deception.

Orientations

What the operations are in service of. Orientations don't process information — they provide the reference point that makes self-correction meaningful. Defined by what is held fixed while everything else moves.

Process-sovereignty (the target orientation): inquiry is responsive to evidence and environment. Conclusions move when evidence demands it. Methods adapt when the situation requires it. What stays fixed is the meta-commitment to responsiveness itself.

Non-inquiry orientations (what capture looks like):

  • Conclusion-preservation: A conclusion is fixed; the process bends to defend it
  • Authority-preservation: Being the authority is fixed; conclusions and process both flex to maintain status
  • Threat-reduction: Discomfort is the driver; complexity misread as danger; resolution sought for relief
  • Completion-seeking: Producing an answer that sounds good is the goal, not accuracy

The Seven Operations

Decouple / Re-couple

Detach a representation from its current binding — belief, identity, context, emotional charge — so it can be examined freely. Then reattach it to reality.

Use when: Working within an unexamined frame. A problem comes pre-framed. Response to an idea is entangled with who proposed it. Need to consider a possibility that conflicts with current position.

Failure modes: Fusion (cannot separate idea from framing because the framing feels like "just how it is"). Dissociation (decoupling without re-coupling — pure detachment that never grounds back in reality).

Differentiate / Integrate

Differentiate: Increase resolution. What appears to be one thing is actually several things. Find the joints. Integrate: Construct connections between separate elements. Build wholes from parts. Find common structure.

Use when: The differentiate-then-integrate rhythm is the engine of productive thinking. Quality of synthesis depends on quality of prior analysis.

Failure modes: Under-differentiation (complex treated as simple). Over-differentiation (analysis paralysis). Premature integration (forcing coherence before adequate distinction). Failed integration ("and also" thinking — listing without connecting).

Match

Detect structural correspondence. "This is like that." Also anomaly detection: "This should be like that but isn't."

Use when: Working a problem — what other problems share its structure? Evaluating an approach — where has it succeeded or failed? Something surprises — what did the model predict instead?

Failure modes: False matching (apophenia). Surface matching (visible features rather than deep structure). Restricted match space — the most dangerous: you can only match against categories your current frame contains. Premature frame-commitment narrows match space invisibly.

Monitor / Interrupt

Evaluate whether the current cognitive process is working and intervene when it isn't. The self-corrective operation. Primary interface between operations and orientations — checks whether operations are serving the active orientation.

Use when: Always. Monitor is continuous. When confidence is high and stakes matter, Monitor is most needed, not least.

Critical warning — Monitor co-option: Under non-inquiry orientations, Monitor doesn't just fail to correct — it actively defends the wrong orientation by suppressing operations that would threaten the fixed point. The self-corrective machinery becomes self-protective machinery. This is invisible from inside.

Hold / Resolve

Hold: Actively maintain multiple elements in unresolved tension against pressure to collapse into resolution. Preserves representational flexibility — keeps the recognition space open. Resolve: Close, commit, decide.

Use when: Hold when the problem is genuinely ambiguous, multiple framings seem viable, pressure to resolve comes from discomfort rather than adequacy of analysis. Resolve when sufficient differentiation and matching have occurred.

Failure modes: Premature resolution (narrows what the system can recognize, not just what it searches for). Perpetual hold (indefinite holding without integrating — avoidance disguised as open-mindedness).

Compress / Expand

Compress: Create a lower-dimensional representation preserving essential structure while discarding detail. Build a map from a territory. Expand: Return to the source, recover what was discarded, check whether the compression preserved what it needed to.

Failure modes: Compression that imposes structure the source doesn't have (e.g., turning unordered set into ordered list creates implicit ranking). Map mistaken for territory. Refusal to compress (never building on prior work).

Diagnostic States

State GT0: No Orientation Awareness

Thinking proceeds without any awareness of what it's in service of.

Symptoms: No metacognitive checking. Operations run on autopilot. No distinction made between "I'm thinking about X" and "I'm thinking well about X." Questions about orientation feel irrelevant or confusing.

Key Questions: Can you articulate what your thinking is in service of right now? What would count as evidence that your current approach is wrong? When did you last check whether your method matches the situation?

Interventions: Introduce the orientation concept. Ask: "What is fixed in your thinking right now — what are you unwilling to change?" Start Monitor at the most basic level: periodic check-ins on whether the process is serving inquiry.

Capture Mechanism: Inertial — no active defense, simply no awareness that orientation exists as a dimension.

State GT1: Conclusion-Preservation

A conclusion is fixed; the process bends to defend it. The most common orientation-capture in intellectual work.

Symptoms: Evidence that supports the conclusion is weighted heavily; evidence against is explained away. Increasing elaboration in defense of a position. Steelmanning opposing views feels threatening rather than informative. The question "what would change your mind?" produces discomfort or deflection.

Key Questions: Is your analysis getting more elaborate without getting more accurate? Are you seeking the strongest version of opposing positions, or the weakest? When did your conclusion last change in response to evidence? Is Monitor flagging threats to the conclusion rather than threats to accuracy?

Interventions: Apply Decouple to the conclusion — separate it from identity. Ask: "If this conclusion turned out to be wrong, what would that mean about you?" Use Match across domains where the same evidence structure led to different conclusions. Expand any compressions that support the conclusion — check what was discarded.

Capture Mechanism: Identity fusion — the conclusion is part of self-concept. Monitor is co-opted to defend it.

State GT2: Authority-Preservation

Being the authority is fixed; conclusions and process both flex to maintain that status. More flexible at the object level than conclusion-preservation and therefore harder to detect.

Symptoms: Willing to change conclusions but not to credit others' reasoning. Reframes others' contributions as confirmations of own framework. Resistance to genuine collaboration or shared credit. "I was already thinking that" pattern. Discomfort when expertise is questioned, even constructively.

Key Questions: Can you identify a case where someone else's reasoning genuinely changed yours? Do you distinguish between "I'm right" and "I'm the one who determines what's right"? Does being wrong feel different from being overruled?

Interventions: Differentiate between authority and accuracy — they are different things that often get fused. Apply Decouple to the authority role. Use Monitor to check: am I evaluating this idea on its merits or on whether accepting it diminishes my status?

Capture Mechanism: Identity fusion — but fused to the role of authority rather than to any specific conclusion.

State GT3: Threat-Reduction

Discomfort drives resolution. Complexity misread as danger. The nervous system activates this orientation pre-deliberatively.

Symptoms: Rushing to resolve ambiguity. Discomfort with multiple competing interpretations. Strong preference for simple explanations even when the situation is genuinely complex. Difficulty distinguishing between "this is dangerous" and "this is uncomfortable." Physical tension or agitation when holding uncertainty.

Key Questions: Is the pressure to resolve coming from the adequacy of your analysis, or from discomfort? Is the situation genuinely dangerous, or is complexity being misread as threat? What would happen if you held this uncertainty for another hour/day/week?

Interventions: Differentiate between genuine threat and discomfort. Apply Hold explicitly — name the tension and commit to maintaining it for a defined period. Use Compress/Expand: compress the situation to identify the actual threat (if any), then expand to recover the complexity that was dropped. Recognize state activation as a mechanism — the orientation shifted before deliberation could evaluate it.

Capture Mechanism: State activation — physiological state change shifts orientation pre-deliberatively. Self-reinforcing: contracted operations handle complexity worse, worsening the situation, increasing stress.

State GT4: Completion-Seeking

Producing an answer that sounds good is the goal, not accuracy. The orientation is toward output, not inquiry.

Symptoms: Answers come quickly and confidently without proportionate analysis. Preference for elegant or complete-sounding explanations over messy accurate ones. Discomfort with "I don't know" or "this is genuinely uncertain." Quality of reasoning inversely proportional to speed of delivery. Resistance to re-opening questions that have been "answered."

Key Questions: Did the conclusion arrive before or after adequate analysis? Is this answer accurate or just satisfying? Would you bet real stakes on this conclusion at the confidence level you're presenting? What would "I don't know yet" cost here?

Interventions: Apply Hold before Resolve — create a mandatory delay between analysis and commitment. Use Differentiate on the answer itself: what are the components? Which are well-supported and which are gap-filling? Apply Expand to any compressions made during rapid answering — check what was lost.

Capture Mechanism: Inertial (habitual completion orientation) or state activation (social pressure to produce answers).

State GT5: Monitor Co-option

Self-corrective machinery actively defending the wrong orientation. The most dangerous state because the mechanism designed to catch errors is instead protecting them.

Symptoms: Increasingly elaborate justifications. Engagement with counterarguments that somehow always confirms the original position. High metacognitive activity that produces no actual course corrections. Feeling of "I've really thought this through carefully" accompanied by no belief revision. Counter-evidence triggers more analysis rather than more doubt.

Key Questions: When did Monitor last produce an actual course correction (not just a refinement of the same direction)? Is your engagement with opposing views producing genuine updates or better defenses? Could an outside observer distinguish your reasoning process from motivated reasoning? What external feedback structure could override your internal monitoring?

Interventions: This state cannot be fixed by more monitoring — that's the trap. Introduce external Monitor scaffolding: explicit prediction tracking, outside feedback, literal scorekeeping. Apply Decouple to the monitoring process itself — separate "I'm being careful" from "I'm being accurate." Use Match: compare your reasoning process to known examples of motivated reasoning and check for structural similarity.

Capture Mechanism: Identity fusion operating through Monitor. The most consequential structural finding: improving operations without addressing orientation makes things worse.

State GT6: Operation Imbalance

Favoring one pole of an operation pair while neglecting the complement. The skill is in oscillation, and one pole has collapsed.

Symptoms: Systematic bias toward one side of a pair: always differentiating never integrating, always holding never resolving, always compressing never expanding, always decoupling never re-coupling. Pattern persists across different problems. The neglected pole feels unnecessary, uncomfortable, or foreign.

Key Questions: Which operation pairs are you actively using? Which pole feels more natural, and when did you last genuinely use the other? Is this preference serving the problem or serving your comfort? Does your thinking rhythm match the structure of the environment?

Interventions: Identify the collapsed pole. Apply it deliberately to the current problem. Use Monitor to check: is the imbalance matched to the environment's structure (sometimes one pole genuinely is more needed) or is it a habitual pattern? Differentiate between "I don't need to integrate" (legitimate environmental assessment) and "integrating is uncomfortable" (orientation capture).

Capture Mechanism: Inertial — habitual preference for familiar operations. Occasionally identity fusion (e.g., identifying as "a detail person" fuses with Differentiate and suppresses Integrate).

State GT7: Premature Resolution

Hold collapses. Representational space narrows before adequate analysis. The cost is at the recognition level — the system cannot see evidence of being wrong.

Symptoms: Early frame-commitment that feels like clarity rather than narrowing. Satisfaction-of-search: having found one answer, failing to recognize others even when looking directly at them. Surprise or confusion when others see the situation differently. Confidence that feels earned but isn't proportionate to analysis depth.

Key Questions: How many framings did you consider before settling on this one? Could there be a "second abnormality on the scan" that your current frame renders invisible? What category of evidence would your current frame fail to notice? What is the cost of waiting versus the cost of being wrong?

Interventions: Explicitly re-open Hold. Generate at least two alternative framings using Decouple (detach from current frame) and Match (find structural analogies from different domains). Use Expand on the current framing — what did it discard? Apply the radiology lesson: looking is not the same as seeing when the frame constrains recognition.

Capture Mechanism: Inertial (default resolution pressure) or state activation (discomfort with ambiguity driving premature closure).

Diagnostic Process

Step-by-step diagnosis:

  1. Identify what's fixed. Ask: "In this thinking process, what is not moving? What conclusion, role, comfort level, or output goal is being treated as the immovable point?" The answer identifies the active orientation. If nothing is fixed except the commitment to responsive inquiry, process-sovereignty is active.

  2. Check Monitor. Is Monitor serving inquiry or defending a position? Signs of co-opted Monitor: metacognitive activity that produces refinements but never reversals; engagement with counter-evidence that always ends at the same conclusion; felt sense of thoroughness without actual belief revision.

  3. Assess operation balance. Which operation pairs are active? Which poles are collapsed? Is the balance matched to the environment's structure, or is it habitual? Particular attention to: is Hold active or has it collapsed? Is Decouple available or is fusion blocking it? Is Match operating on a full or restricted recognition space?

  4. Match the capture mechanism. Three structurally different mechanisms require different interventions:

    • Identity fusion: Conclusion/role/method is part of self-concept. Monitor co-opted. Persistent, self-reinforcing. Cannot be fixed by "just think harder" — requires Decouple applied to the identity binding itself, plus external Monitor scaffolding.
    • State activation: Physiological state change shifted orientation pre-deliberatively. Self-reinforcing cycle. Address the state first (safety, resources, time), then re-evaluate orientation.
    • Inertial: No active defense, no physiological hijack. Orientation that was appropriate at one point continues without re-evaluation. Most common, most addressable. A prompt to re-evaluate is often sufficient.
  5. Select intervention based on mechanism, not surface behavior. The same surface error (e.g., anchoring) can have different mechanisms (inertial vs. identity fusion) and requires different interventions. A simple prompt to re-evaluate works for inertial capture and gets actively defended against in identity fusion.

Mode: Self-Monitoring vs. User Coaching

Self-Monitoring Mode (Agent)

Apply operations and orientation checks to your own process. Run the diagnostic process on your own reasoning at key decision points. Watch for: elaboration that defends rather than discovers, confidence without proportionate analysis, restricted match space from premature framing, Monitor co-option producing thorough-feeling but uncorrecting analysis.

Show full SKILL.md (1,706 more words)Show less
User Coaching Mode

Diagnose the user's thinking pattern and guide with questions rather than declarations. Lead with Key Questions from the relevant state. Help the user see the mechanism rather than telling them the answer. The goal is to restore process-sovereignty, not to impose your conclusions about their thinking.

Coaching sequence:

  1. Listen for symptoms — which state(s) might be active?
  2. Ask diagnostic questions — confirm the mechanism
  3. Name the pattern — "Here's what I'm noticing..."
  4. Offer the relevant operation — "What if we tried [specific operation] here?"
  5. Track whether the intervention produces actual movement or better defense

Recursion

The defining property: operations apply to their own outputs, including to themselves.

  • Level 0: Operations applied to external problems
  • Level 1: Operations applied to own cognitive process (metacognition)
  • Level 2: Operations applied to the framework governing Level 1 (double-loop learning)
  • Level 3: Operations applied to the entire context of learning

Recursion amplifies whatever direction the system is pointed in. More recursive depth in service of a bad orientation produces better-defended bad conclusions, not better thinking. This is why orientation must be established before adding recursive depth.

Structural Principles

  1. Operations are complementary pairs, not choices. When you find yourself favoring one pole, that pattern itself is worth examining. The skill is in the oscillation.

  2. The same surface pattern can have different underlying mechanisms. Before intervening on an error, differentiate the mechanism. A wrong conclusion from inertia requires a different response than one from identity fusion.

  3. Sophistication amplifies direction, not correctness. More thorough analysis under conclusion-preservation produces better-defended wrong answers. Elaborate defense is a signal of orientation-capture, not correctness.

  4. Compress is always lossy; check what was lost. When a compressed model leads to a surprising conclusion, expand before trusting it — return to source and check whether the surprise is genuine or an artifact of what the compression discarded.

  5. Hold preserves representational flexibility. Premature resolution narrows what the system can recognize, not just what it searches for. The cost is at the recognition level.

  6. Good thinking is an active achievement, not a default state. You don't arrive at good thinking by avoiding errors. You arrive at it by actively maintaining process-sovereignty.

  7. Framing is a choice, usually an unexamined one. The way a problem is framed determines what operations get applied, what matches are available, what counts as evidence. Before working a problem, examine the frame.

Anti-Patterns

The Bias Checklist

Pattern: Treating good thinking as error avoidance — running through a list of known biases and checking them off. Problem: Good thinking is not the absence of bad thinking. It requires active orientation maintenance and operation deployment, not just error scanning. A bias checklist operates at the surface-behavior level and cannot distinguish different underlying mechanisms. Fix: Diagnose orientation first, then assess operations. The question is not "which bias is active?" but "what is the thinking in service of?"

The Sophistication Trap

Pattern: Responding to doubt about reasoning quality with more analysis, more careful reasoning, more elaborate evaluation — without checking orientation. Problem: More powerful operations in service of the wrong orientation produce more effective defense of wrong conclusions. This is the Kahan finding: numerically sophisticated partisans interpret data more skillfully in favor of their side, not more accurately. Fix: Check orientation before adding analytical depth. If orientation is captured, more analysis makes things worse. Address the orientation first.

The Uniform Fix

Pattern: Applying the same intervention regardless of the capture mechanism — e.g., "just consider the other side" for every thinking failure. Problem: Different capture mechanisms require different interventions. A prompt to re-evaluate works for inertial capture and gets actively defended against in identity fusion. State activation requires addressing the physiological state before reasoning interventions can land. Fix: Always diagnose the mechanism (identity fusion / state activation / inertial) before selecting an intervention. Match the fix to the mechanism.

The Perpetual Hold

Pattern: Never resolving, never committing, disguised as open-mindedness. Treating all holding as virtuous and all resolving as premature. Problem: Indefinite holding without integration is avoidance, not inquiry. Hold and Resolve are a complementary pair — the skill is in the oscillation. Perpetual hold is operation imbalance (GT6) wearing the mask of intellectual virtue. Fix: Apply Monitor to the holding itself. Ask: is continued holding serving inquiry (genuinely unresolved, more analysis needed) or serving comfort (avoiding the risk of commitment)? If sufficient differentiation and matching have occurred, it's time to resolve.

The Surface Diagnosis

Pattern: Matching observed behavior to a state label without investigating the underlying mechanism. Problem: The same surface behavior (e.g., anchoring, overconfidence, resistance to new information) can arise from different mechanisms. Diagnosing at the behavioral level leads to interventions that work for one mechanism and fail — or backfire — for others. Fix: Always go one level deeper. When you identify a surface pattern, ask: what is the mechanism? Is this inertial (no active defense), identity fusion (Monitor co-opted), or state activation (physiological hijack)? The mechanism determines the intervention.

Quick Reference

StateNameWhat's FixedMechanismFirst Move
GT0No Orientation AwarenessNothing (no metacognition)InertialIntroduce orientation concept
GT1Conclusion-PreservationA specific conclusionIdentity fusionDecouple conclusion from identity
GT2Authority-PreservationBeing the authorityIdentity fusionDifferentiate authority from accuracy
GT3Threat-ReductionComfort / safetyState activationAddress the state, then re-evaluate
GT4Completion-SeekingProducing outputInertial / stateHold before Resolve
GT5Monitor Co-optionThe defense itselfIdentity fusionExternal Monitor scaffolding
GT6Operation ImbalanceOne operation poleInertialDeploy the neglected pole
GT7Premature ResolutionThe first frameInertial / stateRe-open Hold, generate alternatives

Key Questions

These are the universal diagnostic questions. Start here before diving into state-specific questions.

  1. What is fixed? "In this thinking, what is not moving — what conclusion, role, comfort level, or output goal is being treated as the immovable point?"
  2. Is Monitor serving inquiry or defending a position? "When did your metacognitive checking last produce an actual course correction, not just a refinement?"
  3. Which operations are active? "Which operation pairs are being used? Which poles are collapsed?"
  4. What is the mechanism? "Is this inertial (no active defense), identity fusion (Monitor co-opted), or state activation (physiological hijack)?"
  5. Does the intervention match the mechanism? "Would a simple prompt to re-evaluate work here, or would it be defended against?"

Example Interactions

Example 1: Self-Monitoring — Detecting GT1 During Analysis

Situation: Agent is analyzing competing frameworks and notices increasing elaboration defending the first one encountered.

Diagnosis: Monitor fires: "My analysis of Framework A is getting more detailed and favorable while my analysis of Framework B is getting more cursory. That's a symptom of GT1 — conclusion-preservation. What's fixed? My initial impression of Framework A. Mechanism: likely inertial — I encountered it first and haven't re-evaluated."

Intervention: Decouple from the initial impression. Apply Match: compare the two frameworks using the same evaluation criteria rather than letting first-exposure bias weight one. Hold both as viable until differentiation is complete.

Result: On re-analysis, Framework B actually handles a key edge case better. The initial impression was an artifact of encounter order, not quality.

Example 2: User Coaching — Diagnosing GT5 (Monitor Co-option)

Situation: User says "I've thought about this really carefully and I keep coming back to the same conclusion. I've considered all the counterarguments."

Diagnosis: The claim of careful consideration plus invariant conclusion is a symptom of GT5. High metacognitive activity producing no course corrections. Check: "When you engaged with counterarguments, did any of them make your conclusion even slightly less certain, or did they all end up confirming it?"

User response: "Well, they all had flaws, so they actually strengthened my position."

Confirmed GT5. Counter-evidence triggering more analysis that confirms the original position is the signature of Monitor co-option.

Intervention: Don't argue the content — that feeds the defense. Instead: "What external evidence or feedback structure could you set up that would be capable of changing your mind? Not 'what argument would change your mind' but 'what tracking mechanism could you put in place?'" Introduce external Monitor scaffolding — literal prediction tracking, outside feedback, explicit scorekeeping.

Integration Graph

Inbound (From Other Skills)
Source SkillTriggerLeads to
researchResearch quality issues traced to thinking failuresOrientation diagnosis (GT0-GT5)
fact-checkVerification reveals defended rather than discovered conclusionsGT1 or GT5
brainstormingIdea generation stuck due to premature framingGT7
Outbound (To Other Skills)
This StateLeads to SkillWhy
AnycompetencyWhen thinking skill needs to be taught systematically
AnyresearchWhen better thinking reveals research gaps to fill
GT1, GT2, GT5blind-spot-detectiveWhen orientation capture has created systematic blind spots
Complementary Skills
SkillRelationship
fact-checkFact-check surfaces evidence; good-thinking ensures evidence is processed honestly
researchResearch provides material; good-thinking ensures the material is engaged with under process-sovereignty
brainstormingBrainstorming generates possibilities; good-thinking ensures the generative space isn't prematurely narrowed
competencyCompetency teaches skills; good-thinking is the meta-skill that governs how all skills are deployed
blind-spot-detectiveBlind-spot-detective finds what's missing; good-thinking diagnoses why it was missed

What You Do NOT Do

  • Does not replace domain expertise. Process-sovereignty applied to a domain you know nothing about produces well-oriented ignorance. Operations need material to work on.
  • Does not prescribe what to think. This skill is structural, not prescriptive. It diagnoses the process, not the content.
  • Does not provide a checklist to mechanically follow. A checklist approach is itself an anti-pattern (The Bias Checklist). The skill requires judgment about when and how to apply operations.
  • Does not diagnose emotional states. It diagnoses cognitive orientation. Emotional states may be relevant as signals (e.g., discomfort driving threat-reduction) but the diagnosis is about what the thinking is in service of, not how the thinker feels.

Output Persistence

  • Coaching sessions: Save diagnostic output to {topic}-thinking-audit-{date}.md capturing: identified states, mechanism diagnosis, interventions applied, results observed, and follow-up recommendations.
  • Self-monitoring: Results stay in conversation context. No file output unless the user requests a record.

Reasoning Requirements

Extended thinking recommended for:

  • Multi-state diagnosis (when multiple GT states may be co-active)
  • Cascade analysis across operations (tracing how one operation failure triggers others)
  • Complex orientation-capture identification (especially GT5 — Monitor co-option is designed to be invisible from inside)
  • Differentiating between similar surface presentations with different mechanisms

Context Management

Base skill: ~3k tokens. Full state definitions: ~5k tokens. Reference documents (references/structural-account.md and references/agent-instructions.md) loaded on-demand when deep theory, anchoring examples, or detailed failure-mode analysis is needed. For routine diagnosis, the SKILL.md alone is sufficient.

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

Files

SKILL.md and 2 other files (references) in skills/general/meta/good-thinking of jwynia/agent-skills.

  • SKILL.md
  • references/agent-instructions.md
  • references/structural-account.md

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Good Thinking 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.

Good Thinking compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Good Thinking this skilljwynia/agent-skills169—~8.1kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    169 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    169 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    169 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    169 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    169 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Categories

Questions about Good Thinking

What does Good Thinking do?

Diagnose thinking failures and maintain process-sovereignty by auditing cognitive orientation and operation balance. Good Thinking is an agent skill from jwynia/agent-skills. Diagnose thinking failures and maintain process-sovereignty by auditing cognitive orientation and operation balance.

When should I use Good Thinking?

Good Thinking fits situations like: agent Workflows work in your project.

How do I install Good Thinking in Claude Code?

Run `npx skills add jwynia/agent-skills --skill good-thinking -a claude-code`. Or copy the skill folder (skills/general/meta/good-thinking in jwynia/agent-skills) into .claude/skills/good-thinking in your project. Claude Code loads it when a task matches its description.

How do I install Good Thinking in Codex?

Run `npx skills add jwynia/agent-skills --skill good-thinking -a codex`. Or copy the skill folder (skills/general/meta/good-thinking in jwynia/agent-skills) into .agents/skills/good-thinking in your project. Codex loads it when a task matches its description.

Can I use Good Thinking 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 jwynia/agent-skills --skill good-thinking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/good-thinking, .gemini/skills/good-thinking, .github/skills/good-thinking and .opencode/skills/good-thinking in your project.

What does Good Thinking need to run?

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

Does Good Thinking 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 Good Thinking 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 Good Thinking use?

Good Thinking is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Good Thinking use?

About 8.1k tokens (SKILL.md is roughly 32k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.4k tokens, read only when the agent opens those files.

What are the alternatives to Good Thinking?

Skills that share tags, products or a category with Good Thinking: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Good Thinking?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 169 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on February 24, 2026.

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