ljg-blind

Analyzes daily AI conversation logs to detect cognitive blind spots and recommends a targeted WeRead chapter.

7.3k|818|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/lijigang/ljg-skills --skill ljg-blind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ljg-blind
Source: https://github.com/lijigang/ljg-skills/tree/main/skills/ljg-blind
Command: npx skills add https://github.com/lijigang/ljg-skills --skill ljg-blind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It reveals structural thinking habits that make certain truths systematically invisible to you—patterns you cannot see yourself—by scanning your own AI conversation history and pairing the finding with a precise book chapter to correct it.

Core Features & Use Cases

  • Blind Spot Detection: Scans a chosen day's Codex session logs (default yesterday) for five signal types: avoided questions, spinning frameworks, single-lens thinking, unchecked assumptions, and adjacent unexplored areas.
  • Targeted Reading Prescription: Searches WeRead (WeChat Reading) via its API, selects the single most relevant book chapter, estimates reading time, and generates an encoded web reader link.
  • Archived Analysis Note: Writes a structured org-mode note with evidence-backed analysis, the selected chapter, and why it addresses the specific blind spot.
  • Use Case: After a day of intensive AI-assisted thinking, run the scan to discover you repeatedly framed every problem through one mental model, then receive a 20-minute chapter that introduces the missing perspective.

Quick Start

Ask the AI to scan yesterday's conversations for my thinking blind spots and recommend a WeRead chapter to fix the top one.

Frequently Asked Questions about ljg-blind

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze my AI chat history for thinking blind spots?

Run the scan with an optional date argument; it reads Codex session JSONL files for that day, filters your actual user messages, and checks them against five blind spot signal types with quoted evidence. The output is an org-mode note naming one blind spot with supporting quotes.

How does the WeRead chapter recommendation work?

It extracts core keywords from the detected blind spot, searches the WeRead API for books rated 7.5 or higher, picks the most relevant chapter from the table of contents, estimates reading time from word count, and generates an encoded web reader URL.

Can I scan a specific date instead of yesterday?

Yes, pass a date in YYYY-MM-DD format as an argument to scan that day's conversations instead of the default yesterday. The tool checks both the target and previous day session directories to handle timezone boundaries.

What happens if there are no conversations on the target day?

If the day's genuine user input is under 200 characters or missing entirely, the output explicitly states the data was too sparse rather than fabricating a blind spot. The skill refuses to invent findings without evidence.

Why does the WeRead reader link return a 404 error?

Raw bookId and chapterUid values cannot be used directly in web reader URLs. They must be encoded with the bundled WeReadWebUrl.ts Bun script, which produces the /web/reader/{encodedBookId}k{encodedChapterUid} format the site accepts.