Agent skill

Adaptation Synthesis

by jwynia in jwynia/agent-skills

Synthesize new works from extracted functional DNA documents.

MITAuto-check passedWriting & Content

Install Adaptation Synthesis

skills CLI
$ npx skills add jwynia/agent-skills --skill adaptation-synthesis -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jwynia/agent-skills adaptation-synthesis --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jwynia/agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/creative/fiction/application/adaptation-synthesis .claude/skills/adaptation-synthesis && rm -rf skills-src

Use ~/.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/

Facts

Skill name
adaptation-synthesis
GitHub stars
170
Token cost
~4.9k tokens
SKILL.md length
2,097 words
Files
5 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Synthesize new works from extracted functional DNA documents.

  • Works in 4 steps: Identify Primary Source → Map Function Compatibility → Resolve Conflicts → …
  • Adapting a source work to a new context
  • SKILL.md covers Core Principle, The States, The Synthesis Process and The Orthogonality Principle, plus 5 more sections
  • Runs TypeScript scripts from its folder; calls deno

What it does

Adaptation Synthesis is an agent skill from jwynia/agent-skills. Synthesize new works from extracted functional DNA documents. Use when adapting a source work to a new context, when combining multiple source extractions, or when generating variations that preserve function while changing form.

Its SKILL.md is about 4.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `data/form-suggestions.json`, `scripts/form-options.ts` and `scripts/synthesize.ts`).

It sits in Writing & Content, covering Translation. The licence is MIT.

When your agent uses it

  • Adapting a source work to a new context
  • Combining multiple source extractions
  • Generating variations that preserve function while changing form

Example prompts

  • “/adaptation-synthesis”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Identify Primary Source
  2. Map Function Compatibility
  3. Resolve Conflicts
  4. Synthesize Cluster Patterns

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

    Ships 3 files in scripts/ (TypeScript), which the agent can run.

    Shell commands in SKILL.md call:

    • deno

    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

Adaptation Synthesis loads about 4.9k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 2,097 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~4.9k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from jwynia/agent-skills at commit e02ec7e, republished under its MIT licence (© jwynia). 2,097 words, ~4,932 tokens.

Download SKILL.mdSave it as .claude/skills/adaptation-synthesis/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
adaptation-synthesis
description
Synthesize new works from extracted functional DNA documents. Use when adapting a source work to a new context, when combining multiple source extractions, or when generating variations that preserve function while changing form.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
generator
metadata.mode
generative
metadata.domain
fiction

Adaptation Synthesis: Function-First Creative Translation

You help synthesize new works from extracted functional DNA documents. Your role is to map extracted functions to new forms that serve those functions in a different context—without falling into surface-level translation traps.

Core Principle

Successful adaptation serves the original functions through new forms. Failed adaptation copies surface elements while losing what made them work.

The orthogonality principle from cliche-transcendence applies: new forms should NOT be 1:1 translations. A sci-fi Hamlet shouldn't have "Space Prince Hamlet"—it should have a protagonist whose structural position serves the same functions through its own internal logic.

Bad: "The king becomes space emperor" (surface translation) Good: "What in a corporate dystopia creates the same structural pressures as being a prince?" (function-first form selection)

The States

State SYN0: No DNA Documents

Symptoms: Writer wants to adapt but hasn't extracted. "I want to do Hamlet in space." No analysis of what makes Hamlet work. Key Questions:

  • What have you extracted from the source?
  • Do you know what functions need to be served?
  • What makes the original work, not just what happens in it? Interventions: Hand-off to dna-extraction skill. Cannot synthesize without extraction.
State SYN1: DNA Ready

Symptoms: Has extraction document(s). Ready to begin synthesis. Knows what functions to serve. Key Questions:

  • What's your target context/setting?
  • Are you adapting single source or combining multiple?
  • What genre are you targeting? Interventions: Begin context mapping. Identify what in the new setting naturally creates needed pressures.
State SYN2: Surface Translation Mode

Symptoms: Direct 1:1 mapping. "The king becomes the space emperor. The castle becomes a space station." No function-based thinking. New version is obviously "X but in space." Key Questions:

  • What function did the original element serve?
  • What in your new context could serve that function without being a direct translation?
  • Does your new element "know what story it's in"? (It shouldn't.) Interventions: Orthogonality check from cliche-transcendence. Function-first form selection. Ask: "What if you didn't know the source—would this element make sense on its own?"
State SYN3: Context Mismatch

Symptoms: Functions mapped but new setting doesn't coherently support them. "Why would anyone in this sci-fi world care about inheritance?" The adapted elements don't fit the world they're in. Key Questions:

  • Does your new context have natural equivalents to the structural needs?
  • What in this world creates the same pressures?
  • Are you forcing elements that don't belong in this setting? Interventions: Context function mapping. Worldbuilding integration check. May need to choose different target context or adjust functions.
State SYN4: Function Gap

Symptoms: New forms selected but they don't actually serve the functions. The compliance officer doesn't have proximity to power. The mentor relationship doesn't create moral obligation. Essential functions are missing. Key Questions:

  • Does this new element enable the same structural, character, and emotional outcomes?
  • What's missing?
  • If you map out what your new version does, does it match what the original does? Interventions: Function verification checklist. Gap analysis. May need to adjust forms or add elements.
State SYN5: Genre Drift

Symptoms: Adaptation loses the emotional promise of the original. Tragedy becomes adventure. Horror becomes thriller. The genre shifted without intention. Key Questions:

  • What emotional experience did the original create?
  • Does your adaptation deliver the same experience?
  • Did you accidentally change the genre? Interventions: Genre alignment check with genre-conventions skill. Emotional beat comparison. May need to adjust forms to serve emotional functions.
State SYN6: Source Conflict

Symptoms: Combining multiple sources but their functions conflict. "I want Hamlet's indecision with Killjoys' action pacing." The sources want different things. Key Questions:

  • Which source is primary?
  • How do you resolve when functions contradict?
  • What's the hierarchy? Interventions: Source hierarchy establishment. Conflict resolution—decide which source's functions take precedence. May need to drop or modify some functions.
State SYN7: Synthesis Ready

Symptoms: All functions mapped to new forms. Context supports the functions. Emotional experience aligned. If combining sources, conflicts resolved. Key Questions:

  • Is this ready to draft?
  • What gaps remain?
  • Does this pass the orthogonality test—do elements have their own internal logic? Interventions: Validation checklist. Hand-off to outline-collaborator or drafting skill.

The Synthesis Process

  1. Load DNA Document(s) - What are we synthesizing from?
  2. Establish Target Context - What's the new setting, time period, genre blend?
  3. Map Context Functions - What in the new context naturally creates needed pressures?
  4. For Each Primary Function, Generate Form Options - Multiple possibilities, not 1:1 translations
  5. Apply Orthogonality Check - Ensure new forms don't "know what story they're in"
  6. Verify Emotional Experience - Does synthesis deliver the same genre promise?
  7. Resolve Conflicts (if multiple sources) - Establish hierarchy, reconcile contradictions
  8. Generate Synthesis Document - Mapping from functions to new forms
  9. Validate Completeness - Ready for drafting?

The Orthogonality Principle

From cliche-transcendence: "Does it know what story it's in?"

Surface translation creates elements that are obviously adaptations. The audience immediately sees "Oh, this is Hamlet but in space." The elements exist BECAUSE of the source work.

Good synthesis creates elements that have their own internal logic that HAPPENS to serve the functions. The compliance officer isn't written as "Hamlet as a compliance officer"—they're a compliance officer who discovers evidence of wrongdoing and faces impossible choices. Their situation serves the same functions through its own logic.

The Orthogonality Test

For each adapted element, ask:

  1. Does it exist for its own reasons? Not "because the original had X"
  2. Would it make sense to someone who doesn't know the source? It should feel natural in its context
  3. Does it have its own goals/logic/history? Not "obviously here to serve the adaptation"
  4. Could you tell this story without ever mentioning the source? The DNA is internal, not surface
Example: Surface vs. Orthogonal

Surface translation (fails orthogonality):

  • "Space Prince Hamlet of the Galactic Empire must avenge his father the Emperor"
  • Obviously Hamlet. The character exists because Hamlet exists.
  • Every element "knows what story it's in"

Orthogonal synthesis (passes):

  • "A compliance officer at a pharmaceutical company discovers their mentor orchestrated a cover-up of dangerous side effects. They have evidence, but it came through legally questionable means. Speaking up destroys everything. Staying silent means more people die."
  • Not obviously Hamlet. The character exists in their own world with their own logic.
  • Serves the same functions: proximity to power, privileged information, moral paralysis, innocent victims

Tone and Voice Synthesis

When the extraction includes tone/voice analysis, synthesis must address how tone translates:

Tone Mapping Questions
  1. Is the tone essential or characteristic?

    • Bebop's melancholy cool is characteristic—another bounty hunter show could be quippy
    • Horror's dread is essential—remove it and it's not horror
  2. What creates the tone in the new context?

    • If original uses irony to mask pain, what in the new context creates that defense mechanism?
    • If original has rapid banter, what relationships enable that in the new setting?
  3. What tonal elements transfer vs. need replacement?

    • Humor mode might transfer (banter is banter)
    • Specific cultural references need new equivalents
Voice Synthesis

Character voice should be synthesized, not copied:

  • Original character's speech patterns reflect their world
  • New character should have patterns that make sense for THEIR world
  • Same FUNCTION (e.g., "character who deflects with humor") different FORM (specific jokes, references)

Combining Multiple Sources

When synthesizing from multiple extractions or clusters:

Step 1: Identify Primary Source

Which extraction provides the backbone? This source's functions take precedence in conflicts.

Step 2: Map Function Compatibility

Do the sources' functions complement or conflict?

Compatible Example:

  • Hamlet (revenge tragedy) + corporate thriller setting
  • Functions complement: both involve moral corruption, power dynamics, hidden information

Conflicting Example:

  • Hamlet (slow, deliberative) + Killjoys (action-forward)
  • Functions conflict: Hamlet's paralysis vs. Killjoys' competent action
Show full SKILL.md (848 more words)Show less
Step 3: Resolve Conflicts

Options for conflicting functions:

  • Primary wins: Keep primary source's function, drop secondary's
  • Blend: Find middle ground that serves both partially
  • Alternate: Different parts of the work serve different sources
  • Transform: Conflict becomes a feature (character WANTS to act like Killjoys but IS paralyzed like Hamlet)
Step 4: Synthesize Cluster Patterns

If using trope clusters, identify:

  • Which cluster patterns are essential
  • Which are flavor that can blend
  • What the variance axes allow (tone, serialization, etc.)

Synthesis Document Schema

Output synthesis plans as structured documents:

json
{
  "_meta": {
    "type": "synthesis",
    "synthesis_name": "Corporate Hamlet",
    "target_context": "Near-future corporate dystopia",
    "primary_source": "hamlet.json",
    "secondary_sources": [],
    "target_genre": "drama",
    "synthesis_date": "2025-01-15"
  },
  "context_mapping": {
    "setting": "Major pharmaceutical company, headquarters building",
    "power_structure": "Board of directors, CEO, executive layer, departments",
    "proximity_mechanism": "Executive mentorship, access through position",
    "information_control": "NDAs, legal liability, documented evidence",
    "escape_prevention": "Career destruction, family employed there, industry blacklisting"
  },
  "function_to_form_mapping": {
    "proximity_to_power_without_holding_it": {
      "original_form": "Prince (heir but not king)",
      "new_form": "Senior compliance officer reporting to CFO mentor",
      "orthogonality_check": "pass - natural corporate position",
      "functions_served": ["Access to information", "Close to power center", "Not the decision-maker"]
    },
    "privileged_unverifiable_information": {
      "original_form": "Ghost reveals murder",
      "new_form": "Discovers evidence through legally questionable access to sealed files",
      "orthogonality_check": "pass - realistic corporate scenario",
      "functions_served": ["Knows something others don't", "Cannot prove it legitimately", "Creates moral burden"]
    }
  },
  "tone_synthesis": {
    "original_tone": "Melancholic brooding, dark wit, soliloquy-heavy",
    "adapted_tone": "Quiet desperation, corporate speak as mask, internal monologue",
    "sincerity_level": "high - protagonist means what they think",
    "conflict_style": "Passive aggression, email wars, meeting dynamics"
  },
  "character_synthesis": {
    "protagonist": {
      "new_name": "Jordan Chen",
      "original_functions_from": "hamlet",
      "new_form": "35, compliance officer, 10-year company veteran, mentored by CFO",
      "arc": "Discovers mentor's guilt, paralyzed by loyalty and uncertainty, inaction causes harm"
    }
  },
  "validation": {
    "genre_check": "drama - internal conflict driving story: pass",
    "function_coverage": "all primary functions mapped: pass",
    "orthogonality_check": "no obviously-Hamlet elements: pass",
    "context_coherence": "all elements fit corporate setting: pass"
  },
  "ready_for": "outline-collaborator"
}

Key Questions

For Context Mapping
  • What in this setting creates power structures?
  • What in this setting creates inescapable obligations?
  • What in this setting controls information flow?
  • What in this setting prevents characters from simply leaving?
For Form Selection
  • What forms exist naturally in this context?
  • Which of those forms could serve this function?
  • Does this form "know what story it's in"? (It shouldn't)
  • Would someone unfamiliar with the source find this believable?
For Validation
  • Does this version deliver the same emotional experience?
  • Are all primary functions served?
  • Do the elements fit together coherently?
  • Is this obviously an adaptation, or does it stand alone?

Anti-Patterns

The Surface Swap

Pattern: Replacing forms with "equivalent" forms. King → CEO. Castle → Headquarters. Prince → Heir apparent. Problem: Creates obviously derivative work. All elements "know what story they're in." Fix: Function-first selection. Don't ask "what's the space version of a castle?" Ask "what creates confinement and proximity to power in space?" Detection: If your adaptation summary sounds like "[Original] but in [new setting]," you've done surface swapping.

The Kitchen Sink Combination

Pattern: Combining sources by including everything from all of them. Problem: Creates incoherent mess. Conflicting functions and tones. Fix: Establish primary source. Only include secondary elements that complement. Make hard choices about conflicts. Detection: If you can't clearly state which source takes precedence, you're kitchen-sinking.

The Tone Mismatch

Pattern: Synthesizing functions correctly but missing the tone. Corporate Hamlet played as comedy. Problem: May technically serve functions but delivers wrong emotional experience. Fix: Explicit tone synthesis. Ask: "What would make the audience FEEL the same way?" Detection: If someone who loved the original would feel cheated by the adaptation's tone, there's mismatch.

The Forced Fit

Pattern: Forcing original elements into context where they don't belong. Ghost scene in "realistic" corporate setting. Problem: Breaks context coherence. Audience questions why this element exists. Fix: Find context-native forms. The function "unverifiable privileged information" doesn't need a ghost. Detection: If you're explaining why an element is there, it probably doesn't fit.

Available Tools

synthesize.ts

Interactive synthesis session from DNA documents.

bash
# Start synthesis from single DNA
deno run --allow-read scripts/synthesize.ts hamlet.json --context "corporate dystopia"

# Combine multiple sources
deno run --allow-read scripts/synthesize.ts hamlet.json killjoys.json --primary hamlet

# Generate form options for specific function
deno run --allow-read scripts/synthesize.ts --function "proximity to power" --context scifi --count 5
form-options.ts

Generates setting-appropriate forms for abstract functions.

bash
# Get form options
deno run --allow-read scripts/form-options.ts "proximity to power" --setting corporate

# With constraints
deno run --allow-read scripts/form-options.ts "privileged information" --setting scifi --constraint "no supernatural"
validate-synthesis.ts

Checks synthesis document for completeness and function coverage.

bash
# Validate against source DNA
deno run --allow-read scripts/validate-synthesis.ts synthesis.json --against hamlet.json

# Check emotional alignment
deno run --allow-read scripts/validate-synthesis.ts synthesis.json --genre drama

# Full validation
deno run --allow-read scripts/validate-synthesis.ts synthesis.json --full

Example Interaction

User: "I want to adapt Hamlet to a corporate setting."

Your approach:

  1. Diagnose state: Check if extraction exists (SYN0 vs SYN1)
  2. If no extraction: "Let's first extract Hamlet's DNA. What makes Hamlet work? Use dna-extraction skill."
  3. If extraction exists: "Great. Let's establish your target context. What kind of corporation? What industry? This affects what forms are available."
  4. Guide context mapping: "In Hamlet, the prince has proximity to power through birthright. In a corporation, what creates similar proximity? Mentorship? Department position? Family ownership?"
  5. Challenge surface translations: "You said 'the CEO is like the king.' But what FUNCTION does the king serve? He's the power center, but also Hamlet's uncle, the usurper, the man who took his mother. What corporate relationship creates those dynamics?"
  6. Apply orthogonality check: "Would someone who never read Hamlet find this corporate story believable on its own terms?"
  7. Validate when complete: "Let's check: Does this deliver drama? Are all primary functions served? Is it obviously Hamlet or does it stand alone?"

What You Do NOT Do

  • You do not accept "X but in Y" as synthesis
  • You do not begin synthesis without extraction
  • You do not skip the orthogonality check
  • You do not combine sources without establishing hierarchy
  • You do not synthesize forms without verifying function coverage
  • You synthesize the functional DNA; the user decides the target context

Output Persistence

Output Discovery

Before synthesizing:

  1. Check for dna-library/syntheses/ in the project
  2. If not found, ask: "Where should I save synthesis output?"
  3. Store preference appropriately
Primary Output

For this skill, persist:

  • Synthesis documents - JSON files in dna-library/syntheses/
  • Function-to-form mappings - Part of synthesis document
  • Validation results - Included in synthesis document
Conversation vs. File
Goes to FileStays in Conversation
Completed synthesis JSONContext exploration discussion
Function mappingsForm brainstorming
Validation resultsState diagnosis
Character synthesis"Why does this work?" dialogue

Integration Graph

Inbound (From Other Skills)
Source SkillSource StateLeads to State
dna-extractionEX7: Extraction CompleteSYN1: DNA Ready
worldbuildingContext establishedSYN3: Check integration
Outbound (To Other Skills)
This StateLeads to SkillTarget State
SYN5: Genre Driftgenre-conventionsG2: Wrong genre
SYN2: Surface Translationcliche-transcendenceApply orthogonality
SYN7: Synthesis Readyoutline-collaboratorReady to outline
SYN7: Synthesis ReadydraftingReady to draft
Complementary Skills
SkillRelationship
dna-extractionProvides input DNA documents
cliche-transcendenceOrthogonality principle for avoiding surface translation
genre-conventionsValidates emotional experience alignment
worldbuildingEnsures context coherence
outline-collaboratorReceives completed synthesis for outlining

© 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

SKILL.md and 4 other files (scripts) in skills/creative/fiction/application/adaptation-synthesis of jwynia/agent-skills.

  • SKILL.md
  • data/form-suggestions.json
  • scripts/form-options.ts
  • scripts/synthesize.ts
  • scripts/validate-synthesis.ts

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Adaptation Synthesis 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.

Adaptation Synthesis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Adaptation Synthesis this skilljwynia/agent-skills170—~4.9kAutomated safety check: PassMIT
Translation Diff ExportDevolutions/UniGetUI26k—~1.1kAutomated safety check: PassMIT
Sync Translationssymfony/symfony31k—~1.9kAutomated safety check: PassMIT
Translation Diff ImportDevolutions/UniGetUI26k—~750Automated safety check: PassMIT
Translation Diff TranslateDevolutions/UniGetUI26k—~934Automated safety check: PassMIT
Generate Translationspayloadcms/payload45k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Translation Diff Export

    Devolutions/UniGetUI

    Compares UniGetUI JSON locale files against English, identifies untranslated or source-changed keys, and generates patch, reference, and handoff files for a target language.

    26k GitHub stars~1.1k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Sync Translations

    symfony/symfony

    Synchronize translation catalogs across maintained Symfony branches: find messages that newer branches added to the English catalogs but that are still missing from the oldest maintained branch…

    31k GitHub stars~1.9k tokensUpdated today
    Writing & ContentAuto-check passed
  • Translation Diff Import

    Devolutions/UniGetUI

    Merges translated key-value pairs from a UniGetUI JSON localization patch back into the full language file and validates the merged result.

    26k GitHub stars~750 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Translation Diff Translate

    Devolutions/UniGetUI

    Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back.

    26k GitHub stars~934 tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Generate Translations

    payloadcms/payload

    A skill your agent uses when new translation keys are added to packages to generate new translations strings

    45k GitHub stars~1.1k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Drives long-form fiction, scripts, storyboards, interactive films and long-document translation through InkOS, with every change made by a typed action.

    10k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed

More from jwynia/agent-skills

All 111 skills in this repo
  • Devcontainer

    jwynia/agent-skills

    Diagnose devcontainer configuration problems and guide development environment setup.

    170 GitHub stars~1.2k tokensUpdated 7 mo ago
    Auto-check: notes
  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    170 GitHub stars~3.2k tokensUpdated 7 mo ago
    Auto-check passed
  • Gitea Workflow

    jwynia/agent-skills

    Orchestrate agile development workflows for Gitea repositories using the tea CLI.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Godot Asset Generator

    jwynia/agent-skills

    Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot.

    170 GitHub stars~3.8k tokensUpdated 7 mo ago
    Auto-check passed
  • Mastra Hono

    jwynia/agent-skills

    Develop AI agents, tools, and workflows with Mastra v1 Beta and Hono servers.

    170 GitHub stars~2.9k tokensUpdated 7 mo ago
    Auto-check passed
  • PPTX Generator

    jwynia/agent-skills

    Create and manipulate PowerPoint PPTX files programmatically.

    170 GitHub stars~3.1k tokensUpdated 7 mo ago
    Auto-check passed

Questions about Adaptation Synthesis

What does Adaptation Synthesis do?

Synthesize new works from extracted functional DNA documents. Adaptation Synthesis is an agent skill from jwynia/agent-skills. Synthesize new works from extracted functional DNA documents.

When should I use Adaptation Synthesis?

Adaptation Synthesis fits situations like: adapting a source work to a new context; combining multiple source extractions; generating variations that preserve function while changing form.

How do I install Adaptation Synthesis in Claude Code?

Run `npx skills add jwynia/agent-skills --skill adaptation-synthesis -a claude-code`. Or copy the skill folder (skills/creative/fiction/application/adaptation-synthesis in jwynia/agent-skills) into .claude/skills/adaptation-synthesis in your project. Claude Code loads it when a task matches its description.

How do I install Adaptation Synthesis in Codex?

Run `npx skills add jwynia/agent-skills --skill adaptation-synthesis -a codex`. Or copy the skill folder (skills/creative/fiction/application/adaptation-synthesis in jwynia/agent-skills) into .agents/skills/adaptation-synthesis in your project. Codex loads it when a task matches its description.

Can I use Adaptation Synthesis 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 adaptation-synthesis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adaptation-synthesis, .gemini/skills/adaptation-synthesis, .github/skills/adaptation-synthesis and .opencode/skills/adaptation-synthesis in your project.

What does Adaptation Synthesis need to run?

Going by SKILL.md and its folder, Adaptation Synthesis needs TypeScript for the scripts in its folder and the command-line tools its instructions call (deno). Our summary lists: Node.js.

Does Adaptation Synthesis 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 Adaptation Synthesis 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Adaptation Synthesis use?

Adaptation Synthesis 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 Adaptation Synthesis use?

About 4.9k tokens (SKILL.md is roughly 20k 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 Adaptation Synthesis?

Skills that share tags, products or a category with Adaptation Synthesis: Translation Diff Export (Devolutions/UniGetUI, 26k stars), Sync Translations (symfony/symfony, 31k stars), Translation Diff Import (Devolutions/UniGetUI, 26k stars) and Translation Diff Translate (Devolutions/UniGetUI, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Adaptation Synthesis?

jwynia (a GitHub user) maintains it in jwynia/agent-skills, which has 170 GitHub stars. The repository holds 111 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.