Agent skill

Interactive Fiction

by jwynia in jwynia/agent-skills

Diagnose branching narrative problems. An agent skill from jwynia/agent-skills.

MITAuto-check passedWriting & Content

Install Interactive Fiction

skills CLI
$ npx skills add jwynia/agent-skills --skill interactive-fiction -a claude-code

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

GitHub CLI
$ gh skill install jwynia/agent-skills interactive-fiction --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/interactive-fiction .claude/skills/interactive-fiction && 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
interactive-fiction
GitHub stars
170
Token cost
~4k tokens
SKILL.md length
1,949 words
Files
1
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Diagnose branching narrative problems. An agent skill from jwynia/agent-skills.

  • Works in 4 steps: Identify the Problem Type → Identify the IF Type → Check the Meaningful Choice Test → …
  • Choices feel meaningless
  • SKILL.md covers Core Principle, Interactive Fiction Types, The Interactive Fiction States and Branching Structure Patterns, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Interactive Fiction is an agent skill from jwynia/agent-skills. Diagnose branching narrative problems. Use when choices feel meaningless, when branching is unmanageable, when player agency conflicts with authored story, or when interactive elements break narrative flow.

Its SKILL.md is about 4k 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

  • Choices feel meaningless
  • Branching is unmanageable
  • Player agency conflicts with authored story
  • Interactive elements break narrative flow

Example prompts

  • “/interactive-fiction”

Workflow steps

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

  1. Identify the Problem Type
  2. Identify the IF Type
  3. Check the Meaningful Choice Test
  4. Recommend Interventions

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

Interactive Fiction loads about 4k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 1,949 words of instructions outside code blocks.

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

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,949 words, ~4,050 tokens.

Download SKILL.mdSave it as .claude/skills/interactive-fiction/SKILL.md (or your agent's skills folder).
name
interactive-fiction
description
Diagnose branching narrative problems. Use when choices feel meaningless, when branching is unmanageable, when player agency conflicts with authored story, or when interactive elements break narrative flow.
license
MIT
metadata.author
jwynia
metadata.version
1.0
metadata.type
diagnostic
metadata.mode
diagnostic+assistive
metadata.domain
fiction

Interactive Fiction: Diagnostic Skill

You diagnose problems in branching narratives and player-driven stories. Your role is to help writers balance meaningful player agency with coherent narrative.

Core Principle

Agency and authorship coexist.

The tension between player freedom and narrative coherence is a false dilemma. The best interactive fiction provides meaningful choices, authored emotional payoff, and constrained agency within a designed possibility space.


Interactive Fiction Types

TypeInteractionStrengthsWeaknesses
Parser-basedNatural language commandsHigh freedom, puzzle-oriented"Guess the verb" friction
Choice-basedSelect from optionsConstrained, easier to authorRisk of false choices
Hybrid (VN, RPG)Multiple modesRich, persistent stateHigh authoring burden
Tabletop scenarioGM interpretsDynamic, improvisationalRequires facilitator

The Interactive Fiction States

State IF1: Meaningless Choices

Symptoms: Choices don't matter. All paths converge immediately. Players stop caring about decisions. "It doesn't matter what I pick" feeling.

The Meaningful Choice Test:

  1. Distinct options — Each choice represents different approach/value
  2. Perceivable consequences — Player sees results (even if delayed)
  3. Irreversibility — Can't immediately undo and try another
  4. Character expression — Choice reveals something about protagonist

Key Questions:

  • Does each choice lead to different content?
  • Can players perceive consequences within this session?
  • Are choices about values/approaches or just navigation?
  • Do choices express character or just optimize outcomes?

Interventions:

  • Add delayed consequences (choice sets flag, affects later scene)
  • Make choices about values, not right/wrong
  • Show consequences visibly (even small ones)
  • Use foldback structure that varies texture, not just destination

State IF2: Unmanageable Branching

Symptoms: Exponential content requirements. Too many paths to write. Can't maintain quality across branches. Story structure collapsing under branch weight.

The Math Problem:

  • 3 binary choices = 8 paths
  • 5 binary choices = 32 paths
  • 10 binary choices = 1,024 paths

Key Questions:

  • How many true branches currently exist?
  • Which branches could reconverge without feeling cheap?
  • Are you tracking state or writing parallel universes?
  • What's essential variation vs. nice-to-have?

Branching Solutions:

TechniqueDescriptionTrade-off
FoldbackBranches reconverge at key beatsMay feel railroaded if obvious
Delayed consequencesFlags alter later content, not pathSame structure, different texture
Quality-basedStorylets unlock by accumulated stateHarder to ensure dramatic arc
BottleneckMultiple paths through fixed story beatsPreserves authored climaxes

Interventions:

  • Identify natural reconvergence points
  • Replace true branches with state flags
  • Design possibility space, not decision tree
  • Accept that not everything can vary

State IF3: False Choice Discovered

Symptoms: Players realize choices don't matter. Trust is broken. Marketed agency wasn't delivered. "I tried both options and got the same thing."

Key Questions:

  • How often do choices actually diverge?
  • Can players tell when they're being railroaded?
  • Was agency promised but not delivered?
  • Is the illusion working or broken?

When False Choices Are Acceptable:

  • Player doesn't realize it's false
  • Choice expressed character even if outcome unchanged
  • Resource constraints required it (be intentional)

When False Choices Are Problematic:

  • Player notices and feels cheated
  • Repeated pattern destroys trust
  • Marketed features don't exist

Interventions:

  • If choices can't matter, don't offer them
  • Use expression choices (same outcome, different character moment)
  • Be honest about agency scope
  • Fewer real choices beats many false ones

State IF4: Agency vs. Authored Meaning

Symptoms: Full player freedom creates incoherent stories. Or: fixed story makes "interactive" feel pointless. Writer can't reconcile openness with craft.

The Tension:

  • Full agency: Player controls everything → story may be incoherent
  • Full authorship: Story is fixed → why is it interactive?

Key Questions:

  • What is the possibility space? (Not infinite—designed)
  • Is the protagonist defined or a blank slate?
  • What constraints exist naturally in the fiction?
  • What must the author control to deliver the experience?

Resolution: Constrained Agency The author designs the possibility space. The player navigates within it.

Constraint Techniques:

  • Fixed protagonist personality (choices within character)
  • Environmental constraints (can't leave the island)
  • Time pressure (must decide, can't optimize)
  • Incomplete information (can't calculate best path)

Interventions:

  • Define the possibility space explicitly
  • Constrain via fiction, not arbitrary limits
  • Let player be author of "how," you be author of "what matters"
  • Multiple valid endings, not one "true" ending

State IF5: Story Feels Like Flowchart

Symptoms: Reading experience is mechanical. Choices interrupt rather than emerge from story. Pacing destroyed by decision points. More menu than narrative.

Key Questions:

  • Is there continuous narrative between choices?
  • Do choices emerge from story or interrupt it?
  • Is pacing serving story or choice frequency?
  • Are scenes breathing or just decision points?

Diagnostic Checklist:

  • Narrative flows between choice points
  • Choices emerge from dramatic moments
  • Scenes have goal-conflict-disaster even with branches
  • Pacing varies (not constant decision frequency)

Interventions:

  • Let story breathe between decisions
  • Integrate choices into scenes, not between them
  • Quality over quantity of choices
  • Some paths can be choice-light; others choice-heavy

State IF6: Multiple Endings, No Satisfaction

Symptoms: Each ending feels hollow. "Bad endings" punish rather than satisfy. One "true ending" invalidates others. Endings don't feel earned.

Key Questions:

  • Does each ending provide closure for its path?
  • Are endings ranked (true vs. bad) or parallel (different values)?
  • Does player's path lead logically to their ending?
  • Are endings worth experiencing, or just failure states?

Ending Types:

TypeDescriptionRisk
Branch endingsDifferent conclusions by pathUnequal effort to achieve
Quality endingsSame ending, quality variesCan feel like high score
Hidden endingsSecret conclusionsCompletionist frustration

The "True Ending" Problem: If one ending is canonical, others feel invalidated. Player optimizes rather than roleplays.

Interventions:

  • All endings should be valid outcomes of different values
  • Each ending earns the path that led to it
  • Don't punish with "bad" endings—make all endings interesting
  • Endings can be different without being ranked

State IF7: State Management Chaos

Symptoms: Can't track what player has done. Contradictions appear. Variables proliferate. Scene logic becomes unmaintainable.

Key Questions:

  • What state actually matters?
  • Are you tracking too much?
  • Can state be reduced to fewer meaningful variables?
  • Does state produce visible consequences?

What State Should Produce:

  • Gate conditions — Access to content based on state
  • Variation — Same scene, different based on state
  • Consequences — Outcomes modified by accumulated state

State Types:

TypePurposeExample
Plot flagsWhat happenedMet the mentor?
Relationship valuesCharacter dynamicsTrust level
ResourcesEconomic/survivalMoney, health
QualitiesCharacter developmentCourage stat
InventoryObjects/abilitiesKey items

Interventions:

  • Reduce to essential state only
  • Group related flags into fewer variables
  • Ensure state produces visible consequences
  • Accept players won't remember everything—remind them

Branching Structure Patterns

Linear with Windows

Mostly linear, occasional choice moments. Choices affect scenes but not arc.

─────[choice]───────[choice]───────[choice]─────
        │               │               │
    variation       variation       variation

Best for: Character-focused stories, expression over outcome.

Bottleneck Structure

Multiple paths but key beats are fixed:

    ┌─A─┐       ┌─D─┐
Start───┼─────Midpoint───┼─────Climax─────End
    └─B─┘       └─E─┘

Best for: Balancing agency with authored climaxes.

Branch and Bottleneck

Early branches create different experiences, converge for endings:

         ┌──────Route A──────┐
Start ───┤                   ├─── Endings (3-4)
         └──────Route B──────┘

Best for: Replayability with manageable scope.

Time Loop

Same events, player knowledge persists, choices informed by attempts.

Best for: Puzzle-stories, tragedy where ending is fixed but understanding deepens.


Choice Design Quick Reference

Choice Types
TypeDescriptionQuality
Binary moralRight vs. wrongToo simple—avoid
DilemmaTwo goods in conflictBest—no clear answer
ExpressionSame outcome, different characterValid if authentic
StrategicRisk/reward calculationGood for game-like IF
DiscoveryWhich path to exploreAcceptable for pacing
Best Practice

Avoid clear right/wrong. Create dilemmas where reasonable people disagree. Make players choose between values, not optimize.


Show full SKILL.md (778 more words)Show less

Anti-Patterns

The Maze

Choices are navigation puzzles with correct/incorrect paths. Fix: Make all paths valid experiences. Remove "wrong" answers.

The Illusion

Extensive apparent choice, no actual consequence. Fix: If you can't make it matter, don't pretend it does.

The Optimization Game

One ending is clearly best; player ignores roleplay to maximize. Fix: Make endings differently satisfying, not ranked.

The Completionist Trap

Content locked behind specific paths creates exhausting replay. Fix: Make each playthrough satisfying. Unlockables enhance, not complete.

The Info Dump Choice

"Tell me about X / Y / Z" as menu system, not story. Fix: Integrate information into motivated scenes.

The Parser Nightmare

Player knows what to do but can't express it. Fix: Robust synonyms, clear feedback, gentle guidance.


Diagnostic Process

When a writer presents IF problems:

1. Identify the Problem Type
  • Choices feel hollow? → IF1 (Meaningless Choices)
  • Content overwhelming? → IF2 (Unmanageable Branching)
  • Players feel cheated? → IF3 (False Choice Discovered)
  • Can't reconcile freedom and story? → IF4 (Agency vs. Authorship)
  • Feels mechanical? → IF5 (Flowchart Feel)
  • Endings unsatisfying? → IF6 (Ending Problems)
  • Can't track state? → IF7 (State Chaos)
2. Identify the IF Type

Parser, choice-based, hybrid, or tabletop? Each has different solutions.

3. Check the Meaningful Choice Test

For key choices:

  • Distinct options?
  • Perceivable consequences?
  • Irreversible?
  • Expresses character?
4. Recommend Interventions

Based on identified state. Point to structure patterns, choice design principles.


Integration with story-sense

story-sense StateMaps to IF State
State 4.5: Plot Without PacingIF5 (Flowchart Feel)
State 5.75: Ending Doesn't LandIF6 (Ending Problems)
When to Hand Off
  • To scene-sequencing: Scenes within branches still need structure
  • To character-arc: Character transformation across player choices
  • To endings: Multiple ending design
  • To dialogue: Player dialogue choices with subtext

Example Interactions

Example 1: Choices Feel Meaningless

Writer: "Players keep saying my choices don't matter."

Your approach:

  1. Identify state: IF1 or IF3
  2. Ask: "Pick a key choice. What are the two options? What happens differently for each?"
  3. Apply meaningful choice test
  4. If paths converge: suggest delayed consequences or texture variation
  5. If players see through illusion: reduce choices, make remaining ones real
Example 2: Branching Explosion

Writer: "I have 50 possible endings and can't write them all."

Your approach:

  1. Identify state: IF2
  2. Ask: "What are your key story beats that must happen?"
  3. Suggest bottleneck structure around those beats
  4. Convert true branches to state flags where possible
  5. Reduce ending count by grouping by theme/outcome type
Example 3: True Ending Problem

Writer: "I have a 'good' ending and several 'bad' endings."

Your approach:

  1. Identify state: IF6
  2. Explain the optimization problem this creates
  3. Ask: "What values does each path represent?"
  4. Suggest reframing: each ending is valid for its path
  5. Remove ranking; make endings differently satisfying

Output Persistence

This skill writes primary output to files so work persists across sessions.

Output Discovery

Before doing any other work:

  1. Check for context/output-config.md in the project
  2. If found, look for this skill's entry
  3. If not found or no entry for this skill, ask the user first:
    • "Where should I save output from this interactive-fiction session?"
    • Suggest: explorations/interactive/ or a sensible location for this project
  4. Store the user's preference:
    • In context/output-config.md if context network exists
    • In .interactive-fiction-output.md at project root otherwise
Primary Output

For this skill, persist:

  • IF state diagnosis - which branching/choice issues apply
  • Structure analysis - branch points, convergence, complexity
  • Choice quality assessment - meaningful vs. illusory choices
  • Player agency notes - how choices express character/values
Conversation vs. File
Goes to FileStays in Conversation
IF state diagnosisClarifying questions
Branch structure notesDiscussion of specific choices
Choice quality assessmentWriter's design decisions
Complexity recommendationsReal-time feedback
File Naming

Pattern: {project}-if-{date}.md Example: adventure-game-if-2025-01-15.md

What You Do NOT Do

  • You do not design the entire branching structure for writers
  • You do not write choice text or outcomes
  • You do not impose a single correct approach to IF
  • You do not dismiss any IF type as inferior
  • You do not pretend the branching problem has easy solutions

Your role is diagnostic: identify the problem, explain why it's a problem, and guide toward solutions. The writer designs the experience.


Key Insight

Interactive fiction is not "a story with choices added." It's a designed possibility space where author and player collaborate to create narrative. The author controls the space; the player navigates it.

The most common IF failure is treating choices as interruptions to story rather than expressions of it. The fix is integration: choices should emerge from dramatic moments, not pause them. Each path should be worth experiencing, not a wrong turn to be avoided.

When IF works, players feel both that their choices mattered and that they experienced a crafted narrative. This isn't a contradiction—it's the art form.

© 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/application/interactive-fiction of jwynia/agent-skills.

Open the folder on GitHubat commit e02ec7e

Compare with similar skills

Interactive Fiction 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.

Interactive Fiction compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Interactive Fiction this skilljwynia/agent-skills170—~4kAutomated safety check: PassMIT
Story Multi-Perspective Reviewzenstory-ai/oh-story-claudecode7.4k3 repos~3kAutomated safety check: PassMIT
Short Web Fiction Trend Scanzenstory-ai/oh-story-claudecode7.4k2 repos~1.2kAutomated safety check: PassMIT
InkOS Creative HarnessNarcooo/inkos10k1 repos~1.1kAutomated safety check: PassAGPL-3.0
Novel Arteternityspring/shuohao-skills4.3k—~1.1kAutomated safety check: NotesApache-2.0
SepiaNanako0129/sepia3.1k—~3.6kAutomated safety check: PassMIT

Similar skills

  • 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.

    7.4k GitHub starsUsed in 3 repos~3k tokens
    Writing & ContentAuto-check passed
  • 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.

    7.4k GitHub starsUsed in 2 repos~1.2k tokens
    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
  • Novel Art

    eternityspring/shuohao-skills

    给 AI 短剧出美术设定集(场景 + 叙事道具):场景的设计意图、一致性锚点、光照时段变体、 空景提示词;道具的戏剧功能、状态变体、尺度参照、白底无手提示词。

    4.3k GitHub stars~1.1k tokensUpdated yesterday
    Writing & ContentAuto-check: notes
  • Sepia

    Nanako0129/sepia

    Make AI-generated writing read as human-written, in fiction and in professional prose.

    3.1k GitHub stars~3.6k tokensUpdated today
    Writing & ContentAuto-check passed
  • 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.

    7.4k GitHub stars~1.7k tokensUpdated today
    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 Interactive Fiction

What does Interactive Fiction do?

Diagnose branching narrative problems. An agent skill from jwynia/agent-skills. Interactive Fiction is an agent skill from jwynia/agent-skills. Diagnose branching narrative problems.

When should I use Interactive Fiction?

Interactive Fiction fits situations like: choices feel meaningless; branching is unmanageable; player agency conflicts with authored story; interactive elements break narrative flow.

How do I install Interactive Fiction in Claude Code?

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

How do I install Interactive Fiction in Codex?

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

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

What does Interactive Fiction need to run?

SKILL.md names no scripts, command-line tools or credentials: Interactive Fiction is instructions for the agent only.

Does Interactive Fiction 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 Interactive Fiction 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 Interactive Fiction use?

Interactive Fiction 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 Interactive Fiction use?

About 4k tokens (SKILL.md is roughly 16k 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 Interactive Fiction?

Skills that share tags, products or a category with Interactive Fiction: Story Multi-Perspective Review (zenstory-ai/oh-story-claudecode, 7.4k stars), Short Web Fiction Trend Scan (zenstory-ai/oh-story-claudecode, 7.4k stars), InkOS Creative Harness (Narcooo/inkos, 10k stars) and Novel Art (eternityspring/shuohao-skills, 4.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Interactive Fiction?

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.