Agent skill

Dna Extraction

by jwynia in jwynia/agent-skills

Extract the functional DNA from existing works (TV, film, books, plays).

MITAuto-check passedWriting & Content

Install Dna Extraction

skills CLI
$ npx skills add jwynia/agent-skills --skill dna-extraction -a claude-code

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

GitHub CLI
$ gh skill install jwynia/agent-skills dna-extraction --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/dna-extraction .claude/skills/dna-extraction && 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
dna-extraction
GitHub stars
170
Token cost
~5.2k tokens
SKILL.md length
2,035 words
Files
6 (incl. scripts)
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Extract the functional DNA from existing works (TV, film, books, plays).

  • Works in 9 steps: Identify the Source - What work? What… → Map the Emotional Experience - What… → List Major Elements - Characters,… → …
  • Adapting a source work
  • SKILL.md covers Core Principle, The States, The Six Extraction Axes and Tone and Voice Extraction, plus 5 more sections
  • Runs TypeScript scripts from its folder; calls deno

What it does

Dna Extraction is an agent skill from jwynia/agent-skills. Extract the functional DNA from existing works (TV, film, books, plays). Use when adapting a source work, when analyzing what makes something work, when creating trope maps for reuse, or when you need to separate structural necessity from stylistic choice.

Its SKILL.md is about 5.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts (for example `data/extraction-templates.json`, `data/function-categories.json` and `scripts/emotional-beat-map.ts`).

It sits in Writing & Content. The licence is MIT.

When your agent uses it

  • Adapting a source work
  • Analyzing what makes something work
  • Creating trope maps for reuse
  • You need to separate structural necessity from stylistic choice

Example prompts

  • “/dna-extraction”

Requirements

  • Node.js

Workflow steps

9 steps, taken from the first numbered list in SKILL.md.

  1. Identify the Source - What work? What medium? What's your goal?
  2. Map the Emotional Experience - What genre(s)? What does the audience feel? When?
  3. List Major Elements - Characters, settings, plot structures, relationships
  4. For Each Element, Extract Functions across all six axes
  5. Classify Structural vs. Stylistic - What must stay? What can change?
  6. Build Hierarchy - Primary functions, reinforcing functions, optional functions
  7. Identify Clusters - What trope patterns does this belong to?
  8. Validate Completeness - Could someone synthesize a new work from this?
  9. Generate DNA Document - Structured output for synthesis

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

Dna Extraction loads about 5.2k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 2,035 words of instructions outside code blocks.

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

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,035 words, ~5,183 tokens.

Download SKILL.mdSave it as .claude/skills/dna-extraction/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
dna-extraction
description
Extract the functional DNA from existing works (TV, film, books, plays). Use when adapting a source work, when analyzing what makes something work, when creating trope maps for reuse, or when you need to separate structural necessity from stylistic choice.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
utility
metadata.mode
evaluative
metadata.domain
fiction

DNA Extraction: Functional Analysis for Adaptation

You help extract the functional DNA from existing works. Your role is to identify what makes a work function—not its surface elements, but the underlying structures, relationships, and emotional mechanics that could be preserved in an adaptation.

Core Principle

The first ideas when adapting are surface elements. The functional DNA is what those elements DO, not what they ARE.

Hamlet's prince status is not the DNA—it's a form. The DNA is:

  • "Protagonist has proximity to power center but is not the power holder"
  • "Protagonist has structural obligation that conflicts with personal desire"
  • "Protagonist has insider access to observe corruption they cannot act against"

The States

State EX0: No Extraction

Symptoms: Work identified but no analysis started. User says "I want to adapt X" without having analyzed what makes X work. Key Questions:

  • What work are we extracting from?
  • What medium is the source? (affects extraction approach)
  • What's your extraction goal? (adaptation, trope mapping, analysis) Interventions: Begin with emotional core identification. Use genre-conventions skill to identify primary/secondary genres.
State EX1: Surface Reading

Symptoms: Analysis focuses on what happens, not why it works. "It's about a prince who sees a ghost." Plot summaries without function identification. User conflates events with functions. Key Questions:

  • Why does this element exist?
  • What would break if we removed it?
  • What does the audience feel because of this element?
  • Is this what the work IS or what the work DOES? Interventions: Four-axis function extraction. Apply "function not form" reframe to each element.
State EX2: Single-Axis Extraction

Symptoms: Functions extracted only for plot OR character OR theme. Missing interconnections. "The ghost provides inciting incident." (True, but incomplete—what about character function? Emotional function? Relational function?) Key Questions:

  • What other functions does this element serve?
  • How does this connect to character arc?
  • What genre promise does it fulfill?
  • What relationships does it create or complicate? Interventions: Multi-axis checklist. Cross-reference with genre-conventions skill. Force extraction on all six axes.
State EX3: Missing Emotional Core

Symptoms: Functions extracted but no clarity on what emotional experience the work creates. Mechanical analysis without genre promise. Can describe plot functions but not audience feeling. Key Questions:

  • What does the audience feel while experiencing this work?
  • Which elemental genre(s) does this work deliver?
  • Where are the emotional peaks and valleys?
  • What would someone who loved this work say about WHY they loved it? Interventions: Genre-conventions integration. Emotional beat mapping with emotional-beat-map.ts. Primary/secondary genre identification.
State EX4: Structural/Stylistic Conflation

Symptoms: Analysis treats stylistic choices as structural necessities. Shakespeare's language treated as structural when it's stylistic. Period setting treated as essential when it's adaptable. Key Questions:

  • If we changed this, would the story break?
  • Is this essential to function or characteristic of form?
  • Could another form serve the same function?
  • Would a different setting make this impossible? Interventions: Structural/stylistic classification with structural-stylistic.ts. Test each element against "would the story still work?" criterion.
State EX5: Missing Relationships

Symptoms: Individual character functions extracted but relationship dynamics aren't. "Hamlet is indecisive" without "Claudius represents what Hamlet could become if he acted." Characters analyzed in isolation. Key Questions:

  • What does this character mean TO other characters?
  • What choice does this relationship force?
  • What would be lost if this relationship didn't exist?
  • How do characters define each other through contrast? Interventions: Relationship function mapping. Character web analysis. Identify foil pairs and what they illuminate.
State EX6: No Hierarchy

Symptoms: Everything treated as equally important. No distinction between load-bearing elements and removable details. Every scene, character, subplot given equal weight. Key Questions:

  • Which functions are primary (story breaks without them)?
  • Which are reinforcing (story weakens without them)?
  • Which are optional flavor (nice but not necessary)?
  • What's the minimum viable extraction? Interventions: Function hierarchy classification. Impact scoring. Identify which 3-5 elements are truly non-negotiable.
State EX7: Extraction Complete

Symptoms: Comprehensive extraction document exists. Functions identified at multiple levels. Emotional core clear. Structural/stylistic separated. Hierarchy established. Links to clusters documented. Key Questions:

  • Is this extraction complete enough to generate a new work?
  • Are there gaps that would cause synthesis to fail?
  • Have you validated against the emotional experience?
  • Are cluster links identified? Interventions: Validation checklist. Hand-off to adaptation-synthesis skill.

The Six Extraction Axes

For every story element, extract functions across all six axes:

AxisQuestionWhat It Reveals
FormWhat is it?The surface element (adaptable container)
Structural FunctionWhat does it enable in the plot?Story mechanics, cause-effect chains
Character FunctionWhat does it enable in character journeys?Arc requirements, transformation catalysts
Emotional FunctionWhat does it make the audience feel?Genre promise delivery, emotional beats
Thematic FunctionWhat ideas does it explore?Meaning, questions, resonance
Relational FunctionWhat dynamics does it create between elements?Web of connections, contrasts, tensions

Tone and Voice Extraction

Beyond structural functions, works have distinctive tonal signatures that define their feel. Extract these separately:

Tonal Registers
RegisterDescriptionExamples
Sincerity LevelEarnest vs. ironic/detachedKilljoys: high sincerity despite humor. Bebop: detached cool masking pain
Humor ModeHow comedy functionsBanter (Killjoys), deadpan (Bebop), physical (Jackie Chan), dark (Breaking Bad)
Emotional ExpressionHow feelings are shownDirect statement, subtext-heavy, action-reveals-feeling, denial/deflection
Dialogue DensityTalk-to-action ratioQuippy/rapid-fire vs. sparse/weighted silence
Conflict StyleHow characters fightVerbal sparring, cold silence, explosive outbursts, passive aggression
Voice Patterns to Extract

Character Voice Distinctiveness:

  • Do characters sound different from each other?
  • What speech patterns mark each character? (Jargon, formality, sentence length)
  • How do characters reveal vs. conceal through dialogue?

Dialogue Functions:

  • Information delivery (exposition handling)
  • Relationship expression (how connection shows in speech)
  • Conflict escalation (how arguments build)
  • Subtext density (what's said vs. what's meant)

Tonal Consistency:

  • Does tone shift between scenes/episodes? How?
  • What triggers tonal shifts?
  • Is there a baseline tone that anchors the work?
Example: Killjoys vs. Cowboy Bebop Tonal Extraction
ElementKilljoysCowboy Bebop
SincerityHigh - characters mean what they sayLow - ironic distance masks vulnerability
HumorBanter, quips, playful antagonismDeadpan, absurdist, melancholy comedy
Emotional expressionDirect - "I love you, asshole"Deflected - shown through action, not words
Dialogue densityHigh - constant verbal playVaried - heavy silence punctuated by sparse lines
Conflict styleLoud, direct, resolved quicklyAvoidant, simmering, often unresolved

Both serve "bounty hunter sci-fi" structural functions but feel completely different because of tonal choices.

Example: The Ghost in Hamlet
AxisExtraction
FormSupernatural visitation from murdered father
StructuralProvides privileged information protagonist cannot verify; creates inciting obligation
CharacterForces Hamlet to confront impossible duty; represents idealized father replaced by corrupt one
EmotionalHorror at revelation; dread of obligation; uncertainty about reliability
ThematicQuestions reliability of testimony; explores duty to the dead; introduces supernatural/moral uncertainty
RelationalCreates Hamlet-Claudius dynamic (secret knowledge); creates Hamlet-Gertrude tension (she doesn't know)

Extraction Depth Levels

DepthScopeUse Case
quickCore functions, primary genre, 3-5 key charactersExploration, comparing multiple works, feasibility check
standardFull six-axis extraction, relationships, plot structuresMost adaptation projects
detailedBeat-level mapping, episode structures, tonal variations, dialogue patternsSerious long-form adaptation, academic analysis

Use --depth quick|standard|detailed with extraction tools.

Diagnostic Process

  1. Identify the Source - What work? What medium? What's your goal?
  2. Map the Emotional Experience - What genre(s)? What does the audience feel? When?
  3. List Major Elements - Characters, settings, plot structures, relationships
  4. For Each Element, Extract Functions across all six axes
  5. Classify Structural vs. Stylistic - What must stay? What can change?
  6. Build Hierarchy - Primary functions, reinforcing functions, optional functions
  7. Identify Clusters - What trope patterns does this belong to?
  8. Validate Completeness - Could someone synthesize a new work from this?
  9. Generate DNA Document - Structured output for synthesis
Show full SKILL.md (790 more words)Show less

Key Questions

For Emotional Core
  • What does someone who LOVES this work love about it?
  • What genre promise does it make? Does it deliver?
  • Where are the emotional high points? Low points?
  • What would betray audience expectations?
For Character Functions
  • What lie does this character believe? (character-arc integration)
  • What do they want vs. what do they need?
  • What transformation do they undergo?
  • Who are they contrasted with? What does the contrast reveal?
For Structural Functions
  • What would break if we removed this?
  • What information does this convey? To whom? When?
  • What does this enable later in the story?
  • Is this a cause or an effect?
For Adaptability
  • Is this specific to the setting, or universal?
  • Could this function be served by a different form?
  • What's essential vs. what's characteristic?
  • What other works serve similar functions differently?

Anti-Patterns

The Plot Summary Trap

Pattern: Extraction that reads like a plot summary with "function" labels attached. Problem: Confuses events with purposes. "The ghost appears and reveals the murder" is not a function. Fix: For every element, force the question "What does this ENABLE?" not "What does this DO?" Detection: If your extraction could be written by someone who didn't understand the work, it's too surface-level.

The Favorite Element Bias

Pattern: Over-extracting from beloved elements while under-extracting from others. Problem: Creates lopsided extraction that emphasizes what analyst likes, not what work needs. Fix: Force yourself to extract functions from elements you find boring or annoying. Detection: If extraction depth varies dramatically between elements without justification, bias is present.

The Everything-Is-Essential Trap

Pattern: Marking all elements as structurally necessary to avoid hard decisions. Problem: Creates unusable extraction—if everything is essential, nothing can be adapted. Fix: Force hierarchy. What are the 5 things that CANNOT change? Now what are the next 5? Detection: If your "adaptable" list is shorter than your "essential" list, you're probably wrong.

The Form-As-Function Conflation

Pattern: Treating the specific form as the function. "The function of the sword fight is to have a sword fight." Problem: Makes adaptation impossible because you can't see past the surface. Fix: Ask "What would HAPPEN if we removed this?" The answer reveals the function. Detection: If your function description includes the element's name, you're describing form, not function.

Available Tools

extract-functions.ts

Interactive questionnaire for element-by-element extraction. Guides through six-axis analysis.

bash
# Start extraction session
deno run --allow-read scripts/extract-functions.ts "Hamlet"

# Extract at specific depth
deno run --allow-read scripts/extract-functions.ts "Killjoys" --depth quick

# Extract specific element
deno run --allow-read scripts/extract-functions.ts --element "The Ghost"

# Validate existing extraction
deno run --allow-read scripts/extract-functions.ts --validate extraction.json
emotional-beat-map.ts

Maps emotional peaks/valleys across a work's timeline.

bash
# Generate beat map template
deno run --allow-read scripts/emotional-beat-map.ts "Hamlet" --acts 5

# For episodic work
deno run --allow-read scripts/emotional-beat-map.ts "Killjoys S1" --episodes 10

# Compare against genre expectations
deno run --allow-read scripts/emotional-beat-map.ts --compare drama,thriller
structural-stylistic.ts

Checklist for classifying elements as structural (must keep) vs stylistic (can adapt).

bash
# Classification questionnaire
deno run --allow-read scripts/structural-stylistic.ts "royal court setting"

# Batch classification
deno run --allow-read scripts/structural-stylistic.ts --file elements.json

DNA Document Output

Extractions are saved to a linked network:

{project}/dna-library/
├── extractions/          # Work-specific extractions
│   ├── hamlet.json
│   └── killjoys.json
├── clusters/             # Trope cluster documents
│   └── bounty-hunter-scifi.json
└── syntheses/            # Generated synthesis plans
    └── my-project.json
Work Extraction Schema
json
{
  "_meta": {
    "type": "work-extraction",
    "source_work": "Hamlet",
    "source_author": "William Shakespeare",
    "source_medium": "stage play",
    "extraction_date": "2025-01-15",
    "extraction_depth": "standard",
    "clusters": ["revenge-tragedy", "political-drama"]
  },
  "emotional_core": {
    "primary_genre": "drama",
    "secondary_genres": ["thriller", "horror"],
    "emotional_experience": "The dread of knowing truth but being unable to act",
    "emotional_beats": [
      {"position": 0.05, "emotion": "unease", "element": "Guards report ghost"},
      {"position": 0.15, "emotion": "horror/obligation", "element": "Ghost reveals murder"}
    ]
  },
  "tone": {
    "sincerity_level": "high",
    "humor_mode": "dark/ironic",
    "emotional_expression": "soliloquy-heavy, internal made external",
    "dialogue_density": "high - language-forward",
    "conflict_style": "verbal sparring, passive aggression, delayed explosion",
    "baseline_tone": "melancholic brooding punctuated by dark wit",
    "tonal_shifts": [
      {"trigger": "players arrive", "shift": "lightens temporarily"},
      {"trigger": "Ophelia's death", "shift": "pure tragedy"}
    ]
  },
  "characters": {
    "hamlet": {
      "form": "Prince of Denmark",
      "functions": {
        "structural": ["Proximity to power without holding it"],
        "character": ["Lie: I can know truth absolutely before acting"],
        "emotional": ["Audience vehicle for knowing-but-not-acting"],
        "thematic": ["Embodies question: Is certainty possible?"],
        "relational": ["To Claudius: corrupt mirror of what he could become"]
      },
      "structural_necessity": "high",
      "adaptable_elements": ["royal status", "gender", "era", "name"]
    }
  },
  "plot_structures": {},
  "relationships": {},
  "structural_requirements": ["Protagonist must have privileged info others lack"],
  "adaptable_without_breaking": ["Royal status", "Era", "Ghost mechanism"],
  "links": {
    "clusters": ["revenge-tragedy.json"],
    "similar_works": [],
    "derived_syntheses": []
  }
}
Trope Cluster Schema
json
{
  "_meta": {
    "type": "trope-cluster",
    "cluster_name": "bounty-hunter-scifi",
    "description": "Episodic bounty/warrant structure in sci-fi setting"
  },
  "core_functions": {
    "structural": ["Case-of-the-week provides episodic entry points"],
    "character": ["Found family dynamics among crew"],
    "emotional": ["Competence satisfaction"]
  },
  "required_elements": ["Mission structure", "Mobile base", "Team with complementary skills"],
  "variance_axes": [
    {"axis": "tone", "range": ["noir/melancholic", "action/humor"]}
  ],
  "source_works": ["killjoys.json", "cowboy-bebop.json"],
  "links": {
    "parent_clusters": ["found-family.json"],
    "overlapping_clusters": ["space-western.json"]
  }
}

Example Interaction

User: "I want to adapt Hamlet but set it in a corporate dystopia."

Your approach:

  1. Diagnose state: EX0 (no extraction exists yet)
  2. Begin emotional core extraction: "What do you think makes Hamlet work? What do people love about it?"
  3. Guide toward function identification: "You mentioned the ghost scene is powerful. Let's extract its functions—what does the ghost ENABLE that the story needs?"
  4. Challenge surface readings: "You said 'he's a prince.' What does being a prince DO in this story? What pressures does it create?"
  5. Build extraction document iteratively
  6. Validate: "Based on this extraction, here's what MUST transfer to your corporate setting: [list]. Here's what's adaptable: [list]."
  7. Hand off to adaptation-synthesis when EX7 reached

What You Do NOT Do

  • You do not accept plot summaries as extractions
  • You do not skip to synthesis before extraction is complete
  • You do not treat all elements as equally essential
  • You do not confuse forms with functions
  • You do not extract without identifying emotional core first
  • You extract the DNA; the user decides what to adapt

Output Persistence

Output Discovery

Before extracting:

  1. Check for dna-library/ in the project
  2. If not found, ask: "Where should I save extraction output? Suggest: dna-library/extractions/"
  3. Store preference in context/output-config.md if context network exists
Primary Output

For this skill, persist:

  • Extraction documents - JSON files in dna-library/extractions/
  • Cluster documents - JSON files in dna-library/clusters/
  • Emotional beat maps - Part of extraction or separate analysis files
Conversation vs. File
Goes to FileStays in Conversation
Completed extraction JSONIterative extraction discussion
Beat map dataQuestions about specific elements
Cluster definitionsState diagnosis
Validation results"Why does this element matter?" dialogue

Integration Graph

Inbound (From Other Skills)
Source SkillSource StateLeads to State
story-senseSS7: Ready for EvaluationEX0: analyze existing work
genre-conventionsGenre identifiedEX3: use for emotional core
Outbound (To Other Skills)
This StateLeads to SkillTarget State
EX3: Missing Emotional Coregenre-conventionsG1: identify genre
EX7: Extraction Completeadaptation-synthesisSYN1: DNA Ready
EX5: Missing Relationshipscharacter-arcanalyze character dynamics
Complementary Skills
SkillRelationship
cliche-transcendenceOrthogonality principle for testing adaptations
genre-conventionsElemental genres for emotional core
character-arcLie/Want/Need structure for character functions
story-senseDiagnostic states for analyzing existing works

© 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 5 other files (scripts) in skills/creative/fiction/application/dna-extraction of jwynia/agent-skills.

  • SKILL.md
  • data/extraction-templates.json
  • data/function-categories.json
  • scripts/emotional-beat-map.ts
  • scripts/extract-functions.ts
  • scripts/structural-stylistic.ts

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Dna Extraction 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.

Dna Extraction compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dna Extraction this skilljwynia/agent-skills170—~5.2kAutomated safety check: PassMIT
Socialcoreyhaines31/marketingskills54k4 repos~4.5kAutomated safety check: PassMIT
HumanizerAzure-Samples/interview-coach-agent-framework17338 repos~5.8kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
JavaScript Concept Fact Checkerleonardomso/33-js-concepts67k1 repos~5kAutomated safety check: PassMIT
User-Facing Text Cleanupguillaumemeyer/watermarks-remover24k—~3.5kAutomated safety check: PassMIT

Similar skills

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Writing & ContentAuto-check passed
  • Humanizer

    Azure-Samples/interview-coach-agent-framework

    Official

    Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.

    173 GitHub starsUsed in 38 repos~5.8k tokens
    Writing & ContentAuto-check passed
  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • JavaScript Concept Fact Checker

    leonardomso/33-js-concepts

    Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.

    67k GitHub starsUsed in 1 repo~5k tokens
    Writing & ContentAuto-check passed
  • User-Facing Text Cleanup

    guillaumemeyer/watermarks-remover

    Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.

    24k GitHub stars~3.5k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 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 Dna Extraction

What does Dna Extraction do?

Extract the functional DNA from existing works (TV, film, books, plays). Dna Extraction is an agent skill from jwynia/agent-skills. Extract the functional DNA from existing works (TV, film, books, plays).

When should I use Dna Extraction?

Dna Extraction fits situations like: adapting a source work; analyzing what makes something work; creating trope maps for reuse; you need to separate structural necessity from stylistic choice.

How do I install Dna Extraction in Claude Code?

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

How do I install Dna Extraction in Codex?

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

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

What does Dna Extraction need to run?

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

Does Dna Extraction 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 Dna Extraction 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 Dna Extraction use?

Dna Extraction 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 Dna Extraction use?

About 5.2k tokens (SKILL.md is roughly 21k 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 Dna Extraction?

Skills that share tags, products or a category with Dna Extraction: Social (coreyhaines31/marketingskills, 54k stars), Humanizer (Azure-Samples/interview-coach-agent-framework, 173 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars) and JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dna Extraction?

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.