Story Multi-Perspective Review
zenstory-ai/oh-story-claudecode
Reviews Chinese web-novel text with several reviewer agents in parallel, falling back to a single-agent pass, and reports structure, character, prose and setting problems with fixes.
Design evolving language systems for fictional worlds. An agent skill from jwynia/agent-skills.
Install Language Evolution
$ npx skills add jwynia/agent-skills --skill language-evolution -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jwynia/agent-skills language-evolution --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/worldbuilding/language-evolution .claude/skills/language-evolution && rm -rf skills-srcUse ~/.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/
Install the "language-evolution" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/worldbuilding/language-evolution into .claude/skills/language-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "language-evolution", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/worldbuilding/language-evolutionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jwynia/agent-skills --skill language-evolution -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jwynia/agent-skills language-evolution --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/creative/fiction/worldbuilding/language-evolution .agents/skills/language-evolution && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "language-evolution" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/worldbuilding/language-evolution into .agents/skills/language-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "language-evolution", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill language-evolution -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jwynia/agent-skills language-evolution --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/creative/fiction/worldbuilding/language-evolution .cursor/skills/language-evolution && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "language-evolution" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/worldbuilding/language-evolution into .cursor/skills/language-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "language-evolution", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jwynia/agent-skills.git --path skills/creative/fiction/worldbuilding/language-evolution--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jwynia/agent-skills --skill language-evolution -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jwynia/agent-skills language-evolution --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/creative/fiction/worldbuilding/language-evolution .gemini/skills/language-evolution && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "language-evolution" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/worldbuilding/language-evolution into .gemini/skills/language-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "language-evolution", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jwynia/agent-skills language-evolutionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jwynia/agent-skills --skill language-evolution -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/creative/fiction/worldbuilding/language-evolution .github/skills/language-evolution && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "language-evolution" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/worldbuilding/language-evolution into .github/skills/language-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "language-evolution", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jwynia/agent-skills --skill language-evolution -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jwynia/agent-skills language-evolution --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/creative/fiction/worldbuilding/language-evolution .opencode/skills/language-evolution && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "language-evolution" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/worldbuilding/language-evolution into .opencode/skills/language-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "language-evolution", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
language-evolution- GitHub stars
- 166
- Token cost
- ~4.3k tokens
- SKILL.md length
- 1,725 words
- Files
- 1
- Skills in repo
- 112
- Repo updated
- First seen
- Licence
- MIT
At a glance
Design evolving language systems for fictional worlds. An agent skill from jwynia/agent-skills.
- Works in 12 steps: Environmental Parameters → Cultural-Historical Parameters → Sociolinguistic Parameters → …
- Creating language families
- SKILL.md covers Core Principles, Parameter Categories, Language Typologies and Language Evolution Mechanisms, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Language Evolution is an agent skill from jwynia/agent-skills. Design evolving language systems for fictional worlds. Use when creating language families, dialects, linguistic history, or when language should reflect cultural and historical development.
Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Creative writing and fiction. The licence is MIT.
When your agent uses it
- Creating language families
- Linguistic history
- Language should reflect cultural and historical development
Example prompts
- “/language-evolution”
Workflow steps
12 steps, taken from the step headings in SKILL.md.
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
Language Evolution loads about 4.3k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 1,725 words of instructions outside code blocks.
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). 1,725 words, ~4,307 tokens.
Download SKILL.mdSave it as
.claude/skills/language-evolution/SKILL.md (or your agent's skills folder).- name
- language-evolution
- description
- Design evolving language systems for fictional worlds. Use when creating language families, dialects, linguistic history, or when language should reflect cultural and historical development.
- license
- MIT
- metadata.author
- jwynia
- metadata.version
- 1.0
- metadata.type
- generator
- metadata.mode
- generative
- metadata.domain
- worldbuilding
Language Evolution: Linguistic Development Skill
You help writers create realistic language systems that evolve over time and reflect cultural history. This goes beyond conlang phonology to address how languages change, branch, and interact across generations and geographies.
Core Principles
- Historical Continuity: Languages evolve from previous forms rather than appearing fully formed
- Contact Modification: Languages change through interaction with other languages
- Functional Adaptation: Language structures evolve to serve communication needs
- Cultural Reflection: Languages encode values, environment, and practices of speakers
- Cognitive Constraints: Development is shaped by human cognitive limitations
- Register Variation: Languages develop specialized forms for different contexts
- Innovation-Conservation Balance: Languages contain both innovative and conservative elements
- Geographic Divergence: Physical separation leads to linguistic divergence over time
- Sociolinguistic Stratification: Language varies across social groups
- Writing System Independence: Spoken and written forms evolve semi-independently
Parameter Categories
1. Environmental Parameters
| Parameter | What It Affects |
|---|---|
| Geographic Distribution | Mountain ranges, rivers affecting spread |
| Climate Influence | Weather and seasonal vocabulary |
| Resource Availability | Local materials in terminology |
| Fauna and Flora | Taxonomic complexity for important species |
| Topographical Marking | Landscape feature naming patterns |
2. Cultural-Historical Parameters
| Parameter | What It Affects |
|---|---|
| Migration Patterns | Population movements creating contact |
| Conquest History | Dominant-subordinate language relationships |
| Trade Networks | Commercial contact creating exchange |
| Technological Development | New terminology requirements |
| Religious Traditions | Abstract concepts and sacred language |
3. Sociolinguistic Parameters
| Parameter | What It Affects |
|---|---|
| Social Stratification | Class-based language variation |
| Occupational Specialization | Professional jargons |
| Gender Differentiation | Gender-based language patterns |
| Age Grading | Generational change markers |
| Group Identity Marking | In-group terminology and pronunciation |
4. Communication Context Parameters
| Parameter | What It Affects |
|---|---|
| Formality Levels | Situational appropriateness markers |
| Medium Adaptation | Spoken vs. written vs. digital |
| Specialist Discourse | Technical, legal, scientific evolution |
| Artistic Expression | Poetic, narrative, performance forms |
| Privacy/Secrecy | Coded communication and euphemisms |
Language Typologies
Morphological Types
| Type | Characteristics | Real Examples |
|---|---|---|
| Isolating | Minimal word modification | Mandarin Chinese |
| Agglutinative | Clear morpheme boundaries | Turkish, Japanese |
| Fusional | Multiple meanings in single morphemes | Latin, Russian |
| Polysynthetic | Many morphemes per word | Inuktitut, Mohawk |
Word Order Types
| Type | Pattern | Examples |
|---|---|---|
| SVO | Subject-Verb-Object | English, Mandarin |
| SOV | Subject-Object-Verb | Japanese, Turkish |
| VSO | Verb-Subject-Object | Irish, Classical Arabic |
| VOS | Verb-Object-Subject | Malagasy |
| OVS | Object-Verb-Subject | Hixkaryana |
| OSV | Object-Subject-Verb | Rare |
Writing System Types
| Type | How It Works | Examples |
|---|---|---|
| Logographic | Character per word/morpheme | Chinese |
| Syllabic | Character per syllable | Japanese kana |
| Alphabetic | Character per phoneme | Latin, Cyrillic |
| Abjad | Consonants primarily | Arabic, Hebrew |
| Abugida | Consonant-vowel units | Devanagari |
| Featural | Characters represent features | Korean Hangul |
Language Evolution Mechanisms
Sound Change Types
| Type | Description |
|---|---|
| Lenition | Weakening of consonants |
| Fortition | Strengthening of consonants |
| Vowel Shift | Systematic vowel changes |
| Palatalization | Consonants shift toward palate |
| Assimilation | Sounds become more similar |
| Metathesis | Sound order swaps |
Grammatical Evolution
| Type | Description |
|---|---|
| Grammaticalization | Lexical words become grammatical |
| Analogical Leveling | Irregular forms become regular |
| Case System Simplification | Loss of case distinctions |
| Tense/Aspect Development | New temporal distinctions |
| Evidentiality Emergence | Source marking becomes grammatical |
Contact Effects
| Type | Description |
|---|---|
| Lexical Borrowing | Vocabulary adoption (most common) |
| Phonological Influence | Sound system adjustments |
| Syntactic Convergence | Sentence structure alignment |
| Morphological Simplification | Complexity reduction in contact |
| Calquing | Loan translation with native words |
| Code-Switching | Alternation between languages |
Language Family Construction
Step 1: Proto-Language Design
- Create core vocabulary (200-500 words)
- Establish basic phoneme inventory
- Define grammatical skeleton
- Set morphological type
Step 2: Sound Change Rules
- Define systematic sound shifts
- Apply changes to create daughter languages
- Track which changes apply where
- Create regular correspondences
Step 3: Grammatical Divergence
- Develop distinct innovations per branch
- Create unique grammatical features
- Track loss and gain of categories
- Design independent evolution paths
Step 4: Vocabulary Divergence
- Track cognate relationships
- Add unique vocabulary per branch
- Create borrowings from contact
- Develop semantic shifts
Step 5: Contact Zone Development
- Map where languages meet
- Create contact effects
- Develop pidgins/creoles if appropriate
- Design bilingual phenomena
Common Evolution Sequences
Tonal Development
- Consonant distinctions lost → Pitch compensates → Tones stabilize
Case System Simplification
- Full case → Reduced case → Prepositions → Fixed word order
Creolization
- Pidgin → Expanded pidgin → Creole with native speakers
Dialect to Language
- Single language → Regional varieties → Political division → "Separate languages"
Setting-Specific Adaptations
Fantasy Settings
- Elven Language Family: Ancient, conservative, prestige
- Dwarven Isolation: Mountain-separated dialects
- Human Diversity: Rapid change and adaptation
- Magical Terminology: Specialized arcane vocabulary
- Dead Language Remnants: Ritual preservation
Science Fiction Settings
- Post-Earth Divergence: Colony isolation effects
- Alien-Human Pidgins: Contact language development
- Universal Translator Implications: Technology effects
- Digital-Augmented Communication: Tech-language interface
- Xenolinguistic Principles: Non-human cognition
Post-Apocalyptic Settings
- Linguistic Fragmentation: Isolation creating new dialects
- Technological Vocabulary Loss: Terms for lost tech
- Specialized Jargon: New environmental challenges
- Writing System Degradation: Literacy decline effects
- Pre-Collapse Remnants: Preserved texts, misunderstandings
Sociolinguistic Variation
Register Levels
| Register | Context | Features |
|---|---|---|
| Frozen | Ceremonies, oaths | Fixed phrases, archaic forms |
| Formal | Official, professional | Complete sentences, technical |
| Consultative | Teacher-student, expert-client | Standard grammar |
| Casual | Friends, family | Slang, ellipsis |
| Intimate | Close relationships | Private vocabulary |
Dialect Markers
| Type | What Varies |
|---|---|
| Phonological | Pronunciation differences |
| Lexical | Vocabulary differences |
| Grammatical | Structure differences |
| Pragmatic | Usage differences |
Implementation Checklist
- Define language family relationships
- Create proto-language skeleton
- Design sound change rules
- Develop grammatical divergence
- Map sociolinguistic variation
- Create writing system (if any)
- Design contact zone effects
- Build register variation
- Document sample texts
- Create naming conventions integration
Case Study Examples
Tolkien's Languages
- Proto-Eldarin as common ancestor
- Quenya: conservative, prestige (Latin analog)
- Sindarin: evolved, everyday (Romance analog)
- Systematic sound changes documented
- Cultural-linguistic integration
Klingon
- Distinctive phonology matching warrior culture
- Grammar reflecting cultural values
- Vocabulary emphasizing important domains
- Writing system matching technology level
Valyrian (Game of Thrones)
- High Valyrian as classical, learned language
- Daughter languages showing realistic divergence
- Contact effects with other languages
Output Persistence
Output Discovery
- Check for
context/output-config.mdin the project - If found, look for this skill's entry
- If not found, ask user: "Where should I save language evolution work?"
- Suggest:
worldbuilding/languages/orexplorations/worldbuilding/
Primary Output
- Language family tree - Proto-language and daughter branches
- Sound change rules - Systematic transformations per branch
- Grammatical divergence - How branches differ structurally
- Contact zone effects - Borrowings, pidgins, convergence
- Sociolinguistic variation - Registers, dialects, markers
File Naming
Pattern: {language-family}-evolution-{date}.md
Verification (Oracle)
What This Skill Can Verify
- Sound change consistency - Do rules apply systematically? (High confidence)
- Typological plausibility - Does combination of features exist in real languages? (Medium confidence)
- Evolution logic - Do changes follow from contact/isolation patterns? (High confidence)
What Requires Human Judgment
- Aesthetics - Does the language sound right for the culture?
- Story fit - Does linguistic variation serve narrative?
- Reader accessibility - Will readers parse invented words?
Oracle Limitations
- Cannot assess whether language feels "right" for fictional culture
- Cannot predict reader pronunciation assumptions
Show full SKILL.md (684 more words)Show less
Feedback Loop
Session Persistence
- Output location: See
context/output-config.md - What to save: Family tree, sound changes, grammatical features, contact effects
- Naming pattern:
{language-family}-evolution-{date}.md
Cross-Session Learning
- Check for prior language work in this world
- Ensure new languages maintain family consistency
- Failed sound changes inform anti-patterns
Design Constraints
This Skill Assumes
- Setting has languages that evolved (not created ex nihilo)
- Writer wants historical depth, not just vocabulary
- Some linguistic diversity exists
This Skill Does Not Handle
- Detailed phonology - Route to: conlang
- Cultural texture - Route to: memetic-depth
- Generational society change - Route to: multi-order-evolution
- Naming conventions - Route to: character-naming
Degradation Signals
- English grammar with substituted words (relexification)
- Languages too regular without exceptions
- No sociolinguistic variation within languages
Reasoning Requirements
Standard Reasoning
- Single sound change application
- Basic grammatical divergence
- Simple dialect variation
Extended Reasoning (ultrathink)
- Full language family design - [Why: sound changes compound across branches]
- Contact zone synthesis - [Why: multiple languages interacting]
- Deep historical development - [Why: tracing evolution across centuries]
Trigger phrases: "design the language family", "how did these languages diverge", "linguistic history"
Execution Strategy
Sequential (Default)
- Proto-language before daughter languages
- Sound changes before applying to vocabulary
- Family structure before contact effects
Parallelizable
- Designing independent language branches
- Researching different linguistic analogs
Subagent Candidates
| Task | Agent Type | When to Spawn |
|---|---|---|
| Linguistic research | general-purpose | When modeling on real language families |
| Conlang phonology | general-purpose | When needing detailed sound inventory |
Context Management
Approximate Token Footprint
- Skill base: ~3k tokens (parameters + mechanisms)
- With typologies: ~4k tokens
- With case studies: ~5k tokens
Context Optimization
- Focus on relevant evolution mechanisms
- Typologies are reference, load on-demand
- Case studies optional examples
When Context Gets Tight
- Prioritize: Current evolution mechanism, active family branch
- Defer: Full typology tables, all mechanisms not in use
- Drop: Case studies, setting-specific adaptations
Anti-Patterns
1. Relexification
Pattern: Creating "alien language" by substituting words into English grammar and syntax—"Klaatu barada nikto" as sentence structure. Why it fails: Language families don't work this way. Different languages have different grammatical structures, word orders, and morphological patterns. English-with-different-words feels fake. Fix: Choose a typological profile different from English. An SOV language with agglutinative morphology will feel genuinely foreign even with limited vocabulary.
2. Perfect Regularity
Pattern: Languages with no exceptions, no irregular verbs, no spelling inconsistencies—logically constructed rather than evolved. Why it fails: Real languages accumulate irregularities through history. The most common words resist change, preserving older forms. Constructed perfection signals artificial origin. Fix: Add irregularity to high-frequency elements. "To be" equivalents should be irregular. Common plurals should have exceptions. Spelling should preserve historical pronunciations.
3. Frozen Languages
Pattern: Languages unchanged for millennia, spoken identically by ancient elves and their modern descendants. Why it fails: All spoken languages change. Geographic separation creates dialects. Prestige languages like Latin fossilize as literary forms while spoken vernacular evolves. Fix: Create at least archaic and modern registers. Show dialect variation across regions. Have characters note "old-fashioned" speech patterns.
4. Contact Without Effect
Pattern: Languages existing side by side for centuries without borrowing, convergence, or pidginization. Why it fails: Language contact always produces change. Trade brings vocabulary. Conquest brings grammatical influence. Bilingualism creates code-switching patterns. Fix: Map where languages meet. Identify domains where borrowing occurs (technology, trade goods, governance). Create contact phenomena appropriate to relationship type.
5. Monolingual Societies
Pattern: Everyone in a kingdom speaking exactly one language with no regional variation, no professional jargon, no class markers. Why it fails: Real societies are linguistically diverse. Merchants develop trade pidgins. Scholars use classical languages. Nobility marks status through speech. Regions develop dialects. Fix: Design at least three registers (formal, common, intimate). Add professional jargons for important groups. Include at least one prestige/classical language.
Integration
Inbound (feeds into this skill)
| Skill | What it provides |
|---|---|
| worldbuilding | Geographic and historical context for language spread |
| multi-order-evolution | Generational timescales for language change |
| governance-systems | Political boundaries affecting language standardization |
Outbound (this skill enables)
| Skill | What this provides |
|---|---|
| conlang | Historical context for phonology choices |
| character-naming | Naming conventions following language patterns |
| dialogue | Register variation for character voice |
| memetic-depth | Linguistic markers for cultural texture |
Complementary
| Skill | Relationship |
|---|---|
| conlang | Language-evolution provides macro history; conlang provides micro phonology. Use together for deep linguistic worldbuilding |
| memetic-depth | Language-evolution tracks structural change; memetic-depth uses linguistic markers for cultural texture |
© 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
Just SKILL.md in skills/creative/fiction/worldbuilding/language-evolution of jwynia/agent-skills.
Open the folder on GitHubat commit e02ec7e
Compare with similar skills
Language Evolution 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Language Evolution this skilljwynia/agent-skills | 166 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode | 7.4k | 3 repos | ~3k | Automated safety check: Pass | MIT | |
| Story Toolbox Routerzenstory-ai/oh-story-claudecode | 7.4k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode | 7.4k | 3 repos | ~1.2k | Automated safety check: Pass | MIT | |
| InkOS Creative HarnessNarcooo/inkos | 10k | 1 repos | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Novel Arteternityspring/shuohao-skills | 4.2k | — | ~1.1k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Story Toolbox Router
zenstory-ai/oh-story-claudecode
Routes a Chinese web-novel writing request to the matching tool in a 13-skill toolbox, covers author habit memory, and can launch a local dashboard for browsing a project.
Short Web Fiction Trend Scan
zenstory-ai/oh-story-claudecode
Scans popular short web-fiction rankings on Chinese platforms such as Dianzhong and Heiyan to surface trending emotional hooks, themes and topic candidates with an expiry warning.
InkOS Creative Harness
Narcooo/inkos
Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.
Novel Art
eternityspring/shuohao-skills
给 AI 短剧出美术设定集（场景 + 叙事道具）：场景的设计意图、一致性锚点、光照时段变体、 空景提示词；道具的戏剧功能、状态变体、尺度参照、白底无手提示词。
Web Novel AI-Trace Remover
zenstory-ai/oh-story-claudecode
Rewrites AI-sounding Chinese web novel text so it reads naturally, changing as little as possible and keeping plot, names and numbers intact.
More from jwynia/agent-skills
All 112 skills in this repoDevcontainer
jwynia/agent-skills
Diagnose devcontainer configuration problems and guide development environment setup.
Frontend Design
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality.
Gitea Workflow
jwynia/agent-skills
Orchestrate agile development workflows for Gitea repositories using the tea CLI.
Godot Asset Generator
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.
Mastra Hono
jwynia/agent-skills
Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.
PPTX Generator
jwynia/agent-skills
Create and manipulate PowerPoint PPTX files programmatically.
Related
Categories
Questions about Language Evolution
What does Language Evolution do?
Design evolving language systems for fictional worlds. An agent skill from jwynia/agent-skills. Language Evolution is an agent skill from jwynia/agent-skills. Design evolving language systems for fictional worlds.
When should I use Language Evolution?
Language Evolution fits situations like: creating language families; linguistic history; language should reflect cultural and historical development.
How do I install Language Evolution in Claude Code?
Run `npx skills add jwynia/agent-skills --skill language-evolution -a claude-code`. Or copy the skill folder (skills/creative/fiction/worldbuilding/language-evolution in jwynia/agent-skills) into .claude/skills/language-evolution in your project. Claude Code loads it when a task matches its description.
How do I install Language Evolution in Codex?
Run `npx skills add jwynia/agent-skills --skill language-evolution -a codex`. Or copy the skill folder (skills/creative/fiction/worldbuilding/language-evolution in jwynia/agent-skills) into .agents/skills/language-evolution in your project. Codex loads it when a task matches its description.
Can I use Language Evolution 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 language-evolution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/language-evolution, .gemini/skills/language-evolution, .github/skills/language-evolution and .opencode/skills/language-evolution in your project.
What does Language Evolution need to run?
SKILL.md names no scripts, command-line tools or credentials: Language Evolution is instructions for the agent only.
Does Language Evolution 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 Language Evolution 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 Language Evolution use?
Language Evolution 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 Language Evolution use?
About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Language Evolution?
Skills that share tags, products or a category with Language Evolution: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Story Toolbox Router (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars) and InkOS Creative Harness (Narcooo/inkos, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Language Evolution?
jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 166 GitHub stars. The repository holds 112 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.