corpus-persona-extraction
Skill17 starsChanged 5 months agoApache-2.0Archived repositoryView on GitHub
Ingest a corpus of session logs (JSONL transcripts, chat exports) and extract a persona profile — vocabulary frequency, unique idioms and coinages, structural analogies — then synthesize an ideal_yearning and archetypal_pattern and append the result to a {persona_id}.lexicon.yaml. Triggers on "extract persona", "build a lexicon", "map the domain language", or any request to process conversation logs into a voice/vocabulary model.
1 other project uses a version of this.
Other versions1 project uses a version of this.
Word for word · 1
- organvm-iv-taxis/a-i--skills★ 17100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository170 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- algorithmic-artSkill
- audio-engineering-patternsSkill
- canvas-designSkill
- creative-writing-craftSkill
- generative-art-algorithmsSkill
- generative-art-deploymentSkill
- generative-music-composerSkill
- interactive-theatre-designerSkill
- modular-synthesis-philosophySkill
- movement-notation-systemsSkill
- narratological-algorithmsSkill
- natural-center-extractionSkill
- react-three-fiber-patternsSkill
- reality-tv-narrative-analyzerSkill
- script-analysis-dramaturgicalSkill
- theme-factorySkill
- three-js-interactive-builderSkill
- data-ingestion-pipelineSkill
- data-pipeline-architectSkill
- data-storytelling-analystSkill
- market-gap-analysisSkill
- ml-experiment-trackerSkill
- prompt-atom-formalizationSkill
- sql-query-optimizerSkill
- systemic-product-analystSkill
- time-series-analystSkill
- accessibility-patternsSkill
- agent-testing-patternsSkill
- api-design-patternsSkill
- artifacts-builderSkill
- backend-implementation-patternsSkill
- browser-extension-patternsSkill
- cli-tool-designSkill
- code-refactoring-patternsSkill
- code-review-checklistSkill
- coding-standards-enforcerSkill
- community-platform-patternsSkill
- configuration-managementSkill
- continuous-learning-agentSkill
- data-backup-patternsSkill
- database-migration-patternsSkill
- deployment-cicdSkill
- docker-containerizationSkill
- dotfile-systems-architectSkill
- error-handling-logging-patternsSkill
- fastapi-patternsSkill
- feature-workflow-orchestratorSkill
- frontend-design-systemsSkill
- fullstack-starter-packSkill
- gcp-resource-optimizerSkill
- htmx-interaction-patternsSkill
- iterative-code-explorationSkill
- json-schema-designSkill
- mcp-builderSkill
- mcp-server-orchestratorSkill
- mobile-platform-architectSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
User coinages outrank standard vocabulary: When the corpus shows an idiosyncratic term for a concept ("vacuum", "organ", "cartridge", …
- Distinctive: line 50
Redact before analysis: run the corpus through secret/PII patterns first.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Corpus Persona-Extraction
Distill how a specific voice thinks and speaks from a pile of session logs, and persist it as a machine-usable lexicon that downstream agents can write against.
Why this exists
Agents that work with a long-running human collaborator keep re-learning the same voice from scratch: the coinages, the load-bearing metaphors, the sentence shapes that mean "yes, proceed" versus "you've missed the point." A lexicon file makes that knowledge durable and composable — voice-enforcement gates can score against it, drafting skills can imitate it, and translation layers (persona storefronts) can project from it.
Core doctrine
- User coinages outrank standard vocabulary. When the corpus shows an idiosyncratic term for a concept ("vacuum", "organ", "cartridge", "liturgy"), the lexicon records the coinage as primary and the standard term as gloss — never the reverse.
- Append-only. Each extraction run adds a dated block. Prior blocks are evidence of drift, not errors to clean up.
- Separate speakers ruthlessly. A transcript interleaves human, assistant, and tool text. Only the persona's own turns feed frequency analysis; assistant paraphrase contaminates the signal.
Workflow
1. Assemble and filter the corpus
- Gather session files; record provenance (paths, date range, message counts) in the extraction header.
- Parse each format to (speaker, timestamp, text) tuples; keep only
speaker == persona_idturns. - Strip quoted/pasted material (code blocks, tool output, copied text) — the persona's own prose only.
- Redact before analysis: run the corpus through secret/PII patterns first; a lexicon must be shareable.
2. Vocabulary frequency
- Tokenize; compute frequency ranks for unigrams/bigrams/trigrams.
- Diff against a general-English baseline: the interesting set is terms whose corpus rank vastly exceeds baseline rank (keyness), not raw frequency.
- Bucket results: domain terms (shared with field), coinages (absent from baseline entirely), and inflections (standard words used in non-standard senses).
3. Idioms and structural analogies
- Idioms: recurring multiword expressions with stable meaning ("fix bases, not outputs", "the soul persists").
- Structural analogies: the source domains the persona habitually maps from — music, anatomy, liturgy, architecture. Record each as
analogy: {source_domain} → {target_domain}with 2-3 verbatim examples. - Register markers: profanity patterns, emphasis habits (caps, em-dashes), sentence-length distribution, imperative density.
4. Synthesize ideal_yearning and archetypal_pattern
These two fields are the lexicon's soul — short synthesized statements, each grounded in ≥3 verbatim quotes:
ideal_yearning— what the persona is reaching toward across all sessions; the recurring wish underneath the tasks. Written as one sentence in the persona's own idiom.archetypal_pattern— the recurring role/shape the persona enacts (e.g. "the conductor who builds the orchestra rather than playing the instrument"). One sentence plus the evidence quotes.
These are hypotheses, marked with extraction date and confidence — later blocks may revise them.
5. Append to the lexicon
# {persona_id}.lexicon.yaml — append block, never rewrite
- extraction:
date: 2026-06-07
corpus: {files: 128, persona_turns: 1432, date_range: [2026-04-17, 2026-06-07]}
redaction: {patterns_run: true, hits_scrubbed: 0}
vocabulary:
coinages:
- term: vacuum
gloss: "an absence that is unrepresented anywhere durable; never a resting state"
examples: ["N/A is a vacuum", "vacuum field burn"]
domain_terms: [...]
inflections: [...]
idioms:
- phrase: "fix bases, not outputs"
meaning: "modify the source/template/pipeline, never the rendered artifact"
analogies:
- source: liturgy/theology
target: configuration management
examples: ["Tier-0 Liturgy", "the Reliquary", "testament"]
register:
profanity: "affection-marker, not hostility"
emphasis: ["em-dash chains", "bold imperatives"]
ideal_yearning: "…" # one sentence, persona's idiom, ≥3 quote citations
archetypal_pattern: "…"6. Report
Emit a short extraction report: new coinages since last block, terms that dropped out (candidate drift), and any revision to yearning/pattern with the evidence that forced it. Commit lexicon + report together.
Anti-patterns
- Extracting from assistant turns. The most common contamination; the lexicon ends up describing the model, not the persona.
- Overwriting prior blocks. Drift between blocks is the most valuable longitudinal signal; preserve it.
- Unredacted lexicons. Verbatim example quotes can carry credentials/PII from the source sessions; redact at extraction time, not later.
- Synthesizing yearning from one loud session. Require cross-session recurrence (≥3 sessions) before a theme reaches the yearning/pattern fields.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

