thinking-patterns/SKILL.md
# Thinking Patterns Skill Longitudinal cognitive pattern analysis across months of recorded conversations. Extracts evidence-based dimensions from Fathom transcripts, synthesizes cross-session patterns, and detects blind spots you can't see yourself. ## Usage ``` /thinking-patterns # full analysis, default period (3 months) /thinking-patterns --dry-run # corpus stats + batch plan only /thinking-patterns --period 2026-01 2026-02 # custom date
npx skillsauth add glebis/claude-skills thinking-patternsInstall 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.
Longitudinal cognitive pattern analysis across months of recorded conversations. Extracts evidence-based dimensions from Fathom transcripts, synthesizes cross-session patterns, and detects blind spots you can't see yourself.
/thinking-patterns # full analysis, default period (3 months)
/thinking-patterns --dry-run # corpus stats + batch plan only
/thinking-patterns --period 2026-01 2026-02 # custom date range
| Dimension | Framework | |-----------|-----------| | Cognitive distortions | Burns' 10 categories | | Problem framing | Discourse analysis | | Conceptual metaphors | Lakoff & Johnson / MIPVU | | Hedging & certainty | Epistemic marker taxonomy | | Code-switching | Bilingual cognition research | | Decision moments | GDMS + behavioral markers | | Emotional indicators | Russell's Circumplex + ACT | | Avoidance & deflection | ACT experiential avoidance | | Agency language | Narrative Identity Theory | | Competing commitments | Immunity to Change (Kegan) | | Role/register markers | Sociolinguistic analysis | | Energy signals | Engagement markers |
Plus: "The 5 Things You Don't See" summary.
ai-research/YYYYMMDD-thinking-patterns-analysis.md## ResearchStage 0: Corpus Discovery (~30s, orchestrator)
├── Find transcripts, classify, extract Gleb's speech
└── Load reference docs, plan batches
Stage 1: Per-Transcript Extraction (~3 min, 10-13 parallel sonnet agents)
├── Each agent processes 1-4 transcripts
└── Returns structured JSON per transcript (12 dimensions)
Stage 2: Aggregation (~30s, orchestrator)
├── Parse JSONs, de-duplicate, cluster
└── Package into 5 synthesis bundles
Stage 3: Cross-Session Synthesis (~2 min, 5 parallel sonnet agents)
├── Narratives + Metaphors + Language
├── Decisions + Problem Framing + Biases
├── Avoidance + Energy + Execution Gap
├── Role Shifts + Developmental Markers
└── Blind Spot Detection
Stage 4: Output (~1 min, orchestrator)
└── Compile, save, link
~$3.50 per full run, ~6 minutes runtime.
documentation
Cut a software release and maintain a tiered compatibility policy. Use when the user wants to release, ship a version, bump the version, tag a release, write a changelog, or update COMPATIBILITY. Config-driven via release.config.json; bumps version files, runs a readiness gate, updates COMPATIBILITY.md tiers and deprecations, tags (→ release workflow), and reports closed issues. Teaches the underlying standards as it runs.
development
Sync and manage bilingual (EN/RU) library content for agency-docs. Use when adding, updating, or reviewing library articles. Handles translation, sync checks, and Russian stylistic review.
development
This skill should be used to watch a long-running background job (ffmpeg/media encode, qmd or other embedding/vector-DB run, batch agent/LLM pipeline, or a real-browser/agent-browser daemon) until it finishes or wedges, then deliver a verdict (done, needs-attention, or blocked) plus the exact next command, without burning dozens of manual poll commands. Triggers on "babysit this job", "watch this until it's done", "ping me when the encode/embed/batch finishes", "is this background process stuck", "monitor this ffmpeg/qmd run", or any request to wait on a long-running process and be told when it's complete or hung.
development
Use when the user wants Claude Code, Codex, or other AI coding/business agents to work together as peers. This skill should be used whenever the user mentions coordinating Claude Code and Codex, agent handoffs, multi-agent workflows, parity, respect, pushback between agents, deciding which agent should lead, or turning a business/code workflow into a two-agent operating model.