Reading a good business or strategy book and actually applying what's in it months later is a genuinely hard problem — most of what gets read ends up compressed into a highlight or a note that never gets revisited. Cangjie Skill is built around a specific bet on how to fix that: instead of producing another summary for a human to read, it runs long-form content — books, podcast transcripts, interviews, long videos — through a structured pipeline that outputs installable Agent Skills, so the methodology inside a source becomes something an AI agent can actually invoke in a real task.
A Seven-Stage Extraction Pipeline
The project calls its method RIA-TV++, and it's a genuinely structured process rather than a single prompt asking a model to "summarize the key points." Seven stages run in sequence: whole-content comprehension using a structural/interpretive/critical/applicability framework adapted from Mortimer Adler's analytical reading method; parallel extraction by five specialized extractors pulling candidate frameworks, principles, cases, counter-examples, and terminology; a triple-verification filter that only keeps a candidate methodology if it has independent supporting evidence in at least two places in the source, can answer a genuinely new question the source doesn't explicitly address, and isn't just common knowledge restated; a structuring step organizing surviving candidates into six dimensions (a quoted excerpt, a rewritten explanation, an example from the source, a projected future use case, executable steps, and known boundaries); a linking stage that maps relationships between the resulting skills; a pressure-testing stage that runs each skill against trick questions and cross-skill confusion tests before it ships; and a final delivery stage that installs anything that passed into a Claude Code or Cursor skills directory.
The Filtering Is the Actual Point
The detail worth taking seriously here is how aggressive the rejection rate is: the project states that only 25-50% of candidate methodologies survive the triple-verification stage. That's a deliberate design choice against the more common failure mode of AI summarization tools — producing a comprehensive-looking output that includes everything, most of which turns out to be restated common sense or context-dependent detail that doesn't generalize. A pipeline that throws away half or more of what it extracts, specifically because it can't prove the surviving content is both independently supported and non-obvious, is making a real trade-off in favor of precision over coverage.
What the Output Actually Looks Like
The delivery isn't a single file — it's a small repository. A completed run produces BOOK_OVERVIEW.md as the whole-content understanding from stage one, INDEX.md as a skill map showing how the extracted skills relate to and depend on each other, individual SKILL.md files for each surviving methodology, a GLOSSARY.md of source-specific terminology, and test-prompts.json recording the trigger scenarios each skill was validated against. Version 2.0.0 added a fifth delivery stage on top of that: a reader-facing DIGEST.md — a long-form summary aimed at a human who wants the substance without reading the entire source — generated alongside the machine-facing skill files, plus the actual installation step that copies validated skills into a Claude Code or Cursor skills directory so they're immediately callable rather than sitting in a repo waiting to be wired up manually.
Built for Long Runs That Might Get Interrupted
Distilling an entire book or a multi-hour video transcript is not a quick job, and version 2.0.0 added infrastructure for that reality directly: a PIPELINE_STATE.md file that tracks which stage is active, what's been produced so far, and the status of each individual skill candidate, so a run can resume where it left off rather than restarting from scratch after an interruption. The same release added chunking strategies for unusually long source material — splitting along natural boundaries like chapters, volumes, or episode breaks — with a serial fallback for cases where parallel extraction across chunks isn't practical. The quality gates got stricter at the same time: a lightweight user confirmation step, blind testing by an independent agent that didn't see the extraction process, cross-skill confusion tests specifically designed to catch two similar skills stepping on each other, and a length cap on quoted excerpts in translated output — a direct, practical response to the copyright question the extraction format raises in the first place.
A Growing Library of Published Skill Packs
The project's own repository lists more than twenty published skill packs built with the pipeline, spanning Warren Buffett's shareholder letters, Charlie Munger's Poor Charlie's Almanack, Influence, Contagious, business and investment texts, a 165-prompt system-prompt design collection, and classical Chinese texts including the Huangdi Neijing and the Sunzi Bingfa — each contributing anywhere from six to twenty-five individual skills depending on how much extractable methodology the source actually contained. A handful of these are external contributions brought in with the original authors' consent, worth noting both as evidence the pipeline generalizes beyond its own author's use and as a reminder that "consent-based" isn't the same as "rights-cleared" when the source material is itself under commercial copyright.
Part of a Named "Distillation" Ecosystem
Cangjie Skill positions itself as one piece of a small, explicitly connected ecosystem: a companion project distills specific people's thinking styles and communication patterns into "human skills," and a separate evolution tool is meant to keep any of these skills current over time as they get used. Cangjie's own scope is content people have written or spoken systematically — the idea being that a book or a long, deliberate interview represents a different kind of distillable value than imitating how a specific individual talks.
The Real Question This Raises: What You're Actually Allowed to Distill
This is the part worth being direct about rather than treating as a footnote. The extraction pipeline's own output structure includes a direct quoted excerpt from the source as one of its six required dimensions, and the tool has already been used, by its own documentation, against dozens of specific, actively-copyrighted, commercially-sold books — not just older public-domain texts. Turning a copyrighted book's frameworks, cases, and direct quotes into a structured, redistributable skill package and publishing that package publicly is a materially different act than writing a personal reading note for your own use, and it sits in territory that copyright law — particularly around derivative works and the scope of fair use for commentary versus wholesale extraction — hasn't cleanly settled for this specific kind of AI-generated output. Before running this against a book you don't hold rights to, and especially before publishing the resulting skill pack anywhere public, it's worth getting real legal guidance specific to your jurisdiction and the specific source material, rather than assuming a personal, non-commercial framing automatically clears it.
Practical Implications
- The extraction methodology is worth studying on its own terms, independent of what source material you'd actually run it against — the triple-verification filter and the six-dimension structuring format are a genuinely more disciplined approach to knowledge distillation than a single-pass summarization prompt.
- Applying it to your own team's internal documents, meeting transcripts, or proprietary playbooks is the clearly safe use case — content you actually hold rights to, being turned into agent-callable structure rather than left in a wiki nobody rereads.
- Applying it to commercially copyrighted books you don't hold rights to, and then distributing the result, is the use case that needs real legal scrutiny before you do it, not after.
- The pressure-testing stage is a genuinely transferable idea for anyone building Agent Skills generally — designing trick questions and cross-skill confusion tests before a skill ships is a discipline most skill-building processes skip entirely.
Practical Takeaway
Cangjie Skill's extraction pipeline — parallel candidate generation, triple verification, structured six-dimension output, and pressure-testing before delivery — is a legitimately well-thought-out approach to a real problem: most consumed content never gets structured into something reusable. The methodology is worth learning from directly, whether or not you use the tool itself, and it's worth applying first to content you actually own or have clear rights to before extending it to material you don't.
Teams building internal knowledge-distillation pipelines or evaluating Agent Skills for institutional knowledge capture can get hands-on architecture help from Woyce Technologies.
FAQ
What is Cangjie Skill?
Cangjie Skill is an open-source pipeline that extracts methodologies from long-form content — books, podcasts, interviews, long videos — and structures them into installable Claude Code and Cursor Agent Skills, using a seven-stage process it calls RIA-TV++.
How does Cangjie Skill decide what's worth extracting?
Candidate methodologies must pass a triple-verification filter: independent supporting evidence in at least two places in the source, the ability to answer a question the source doesn't explicitly address, and genuine non-obviousness rather than restated common knowledge. Only 25-50% of candidates typically survive.
Is it legal to run Cangjie Skill against a copyrighted book?
This is a genuine open question rather than a settled one. The tool's output structure includes direct quoted excerpts from the source, and turning a copyrighted book into a redistributable skill package — especially one published publicly — raises real derivative-work and fair-use questions that depend on the specific source, jurisdiction, and how the result is used or distributed. Get actual legal advice before doing this with material you don't hold rights to.
What content types does Cangjie Skill support?
Books, long-video transcripts, podcast transcripts, interviews, lectures, courses, long-form articles, and general document collections — anything with extractable, verifiable, transferable methodology in text or transcript form.
Is Cangjie Skill free to use?
It's open source under the GNU AGPL v3.0 license, which has real implications if you modify and redistribute it or offer it as a network service — read the license terms directly before building a service on top of it.
What's the safest way to use Cangjie Skill?
Running it against content you actually own or have clear rights to — internal documentation, your own team's playbooks, transcripts of your own meetings or talks — sidesteps the copyright question entirely and is the most straightforward, defensible use case.
What files does a Cangjie Skill run actually produce?
A structured mini-repository: BOOK_OVERVIEW.md for whole-source understanding, an INDEX.md skill map, individual SKILL.md files per surviving methodology, a GLOSSARY.md, test-prompts.json recording validation scenarios, and, as of version 2.0.0, a reader-facing DIGEST.md summary generated as a separate deliverable alongside the machine-facing skill files.
Can a Cangjie Skill run resume if it's interrupted partway through?
Yes, as of version 2.0.0. A PIPELINE_STATE.md file tracks the active stage, what's been produced so far, and each candidate skill's status, so a long extraction job on a full book or lengthy video transcript can pick back up instead of restarting.
How does Cangjie Skill handle content too long to process in one pass?
Version 2.0.0 added chunking along natural boundaries — chapters, volumes, or episode breaks in a long video series — with a serial-processing fallback for cases where the parallel five-extractor stage isn't practical across every chunk at once.
Is Cangjie Skill only useful for books written in Chinese?
No — the pipeline and its README are available in English, Japanese, and Chinese, and the published skill packs include English-language sources, though the project's own examples so far lean heavily toward Chinese-language business, investment, and classical texts given the maintainer's background as a Chinese-language AI educator.