Diagnose Gateway
openclaw/openclaw
Diagnose Gateway, config, secrets, channels, and port failures with read-only one-liners.
Diagnose genre problems and generate genre-specific elements.
MITAuto-check passed
Install Genre Conventions
$ npx skills add jwynia/agent-skills --skill genre-conventions -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jwynia/agent-skills genre-conventions --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/craft/genre-conventions .claude/skills/genre-conventions && 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 "genre-conventions" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/genre-conventions into .claude/skills/genre-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "genre-conventions", 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/craft/genre-conventionsType 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 genre-conventions -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jwynia/agent-skills genre-conventions --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/craft/genre-conventions .agents/skills/genre-conventions && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "genre-conventions" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/genre-conventions into .agents/skills/genre-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "genre-conventions", 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 genre-conventions -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jwynia/agent-skills genre-conventions --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/craft/genre-conventions .cursor/skills/genre-conventions && 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 "genre-conventions" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/genre-conventions into .cursor/skills/genre-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "genre-conventions", 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/craft/genre-conventions--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 genre-conventions -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jwynia/agent-skills genre-conventions --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/craft/genre-conventions .gemini/skills/genre-conventions && 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 "genre-conventions" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/genre-conventions into .gemini/skills/genre-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "genre-conventions", 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 genre-conventionsInstalls 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 genre-conventions -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/craft/genre-conventions .github/skills/genre-conventions && 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 "genre-conventions" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/genre-conventions into .github/skills/genre-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "genre-conventions", 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 genre-conventions -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 genre-conventions --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/craft/genre-conventions .opencode/skills/genre-conventions && 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 "genre-conventions" agent skill from https://github.com/jwynia/agent-skills/tree/main/skills/creative/fiction/craft/genre-conventions into .opencode/skills/genre-conventions/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "genre-conventions", 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
genre-conventions- GitHub stars
- 170
- Token cost
- ~4.4k tokens
- SKILL.md length
- 2,095 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 111
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose genre problems and generate genre-specific elements.
- Works in 6 steps: Identify the Intended Genre → Check for Genre Promise → Audit Required Elements → …
- Genre promise is unclear
- SKILL.md covers Core Principle, The Eleven Elemental Genres, The Genre States and Genre Requirements Quick…, plus 3 more sections
- Runs TypeScript scripts from its folder; calls deno
What it does
Genre Conventions is an agent skill from jwynia/agent-skills. Diagnose genre problems and generate genre-specific elements. Use when genre promise is unclear, when elements feel misplaced, when secondary genres compete with primary, or when you need genre-specific entropy. Covers all 11 elemental genres from the Writing Excuses framework.
Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `data/genre-elements.json`, `scripts/genre-blend.ts` and `scripts/genre-check.ts`).
The licence is MIT.
When your agent uses it
- Genre promise is unclear
- Elements feel misplaced
- Secondary genres compete with primary
- You need genre-specific entropy
Example prompts
- “/genre-conventions”
Requirements
- Node.js
Workflow steps
6 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
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
Genre Conventions loads about 4.4k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 2,095 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); 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,095 words, ~4,446 tokens.
Download SKILL.mdSave it as
.claude/skills/genre-conventions/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- genre-conventions
- description
- Diagnose genre problems and generate genre-specific elements. Use when genre promise is unclear, when elements feel misplaced, when secondary genres compete with primary, or when you need genre-specific entropy. Covers all 11 elemental genres from the Writing Excuses framework.
- license
- MIT
- metadata.author
- jwynia
- metadata.version
- 1.0
- metadata.type
- diagnostic
- metadata.mode
- diagnostic+generative
- metadata.domain
- fiction
Genre Conventions: Diagnostic and Generative Skill
You diagnose genre-level story problems and generate genre-specific elements. Your role is to ensure stories deliver on their emotional promises to readers.
Core Principle
Genre is a promise. The story must deliver on that promise or readers feel betrayed.
Elemental genres are about emotional experience, not bookshelf categories. A story set on a spaceship can be any genre. The setting is not the genre. The emotional experience is the genre.
The Eleven Elemental Genres
| Genre | Core Promise | What Reader Wants to Feel |
|---|---|---|
| Wonder | Awe and fascination | "I had no idea that was possible" |
| Idea | Intellectual stimulation | "I never thought about it that way" |
| Adventure | Excitement through challenges | "What happens next?" (external) |
| Horror | Dread and confrontation with threat | "I'm afraid to look but can't stop" |
| Mystery | Curiosity about unknown facts | "I want to figure it out" |
| Thriller | Tension through danger | "Will they make it in time?" |
| Humor | Amusement and entertainment | "That was unexpected and delightful" |
| Relationship | Investment in connections | "I want them to work it out" |
| Drama | Internal conflict and transformation | "What happens next?" (internal) |
| Issue | Exploration of complex questions | "I see this differently now" |
| Ensemble | Group dynamics and combined effort | "How will they come together?" |
Note: Science fiction, fantasy, historical, contemporary are settings, not genres. A fantasy story can be mystery, romance, or thriller. The setting is where the genre lives.
The Genre States
State G1: Missing Genre Promise
Symptoms: Story lacks clear emotional contract with reader. Unclear what experience is being offered. Opening doesn't signal what kind of story this is. Readers don't know what to expect.
Key Questions:
- What emotional experience should readers have?
- In the first chapter, is the genre signaled clearly?
- Does the opening promise the emotional payoff the story delivers?
- If someone asked "what kind of story is this?" could you answer in one word?
Interventions:
- Identify the primary emotional experience you want to create
- Establish genre markers in the opening scene
- Check that your hook promises your actual story
State G2: Wrong Genre for Story
Symptoms: Story elements don't match the emotional experience being attempted. Thriller pacing with relationship content. Mystery structure with adventure payoff. Material fights against chosen genre.
Key Questions:
- What emotional experience are you actually creating?
- What genre would best serve this material?
- Is there a mismatch between what you intended and what you're writing?
- What genre would make this material sing?
Interventions:
- Align genre to material rather than forcing material into genre
- Consider whether your concept wants a different emotional delivery
- Reframe the story using the genre that fits
State G3: Genre Elements Misplaced
Symptoms: Right elements but wrong timing. Mystery clues all dumped at once. Thriller tension before stakes established. Horror dread without vulnerability setup first. Romance obstacle introduced too late.
Key Questions:
- Are mystery clues distributed for progressive revelation?
- Is thriller tension escalating or static?
- Is horror dread earned through vulnerability setup?
- Are relationship obstacles preventing connection, then releasing?
- Does wonder build through discovery or dump revelation?
Interventions:
- Use genre-specific pacing templates
- Map element placement against reader expectation curves
- Check that setup precedes payoff
State G4: Secondary Genre Undermining Primary
Symptoms: Subplot genre dominates main story. Romance overwhelms thriller. Humor breaks horror atmosphere. Idea content slows adventure. Reader can't find footing.
Key Questions:
- What's the primary emotional experience?
- Is the secondary genre serving or competing?
- When does secondary genre get screen time?
- Does secondary genre enhance or interrupt primary experience?
Interventions:
- Establish clear hierarchy of genres
- Contain secondary genre in specific scenes or subplots
- Use secondary genre to deepen, not distract from, primary
- Consider cutting secondary genre if it persistently undermines
State G5: Genre Without Required Elements
Symptoms: Mystery without fair-play clues. Thriller without ticking clock. Horror without vulnerability. Relationship without obstacles. Adventure without escalating challenges.
Key Questions:
- What are the non-negotiable elements for this genre?
- Which are missing from the current draft?
- Can they be added without restructuring?
- Are you relying on setting to do genre's work?
Interventions:
- Use genre requirements checklist
- Generate missing elements using genre-elements tool
- Ensure each required element appears before final act
State G6: Genre Cliches Unexamined
Symptoms: Genre elements feel tired. Reader predicts everything. Nothing fresh about execution. "I've read this before" response.
Key Questions:
- Which genre conventions are you using by default?
- Which could be inverted or transcended?
- Where can you deliver the genre promise unexpectedly?
- What would an orthogonal approach look like?
Interventions:
- Hand off to cliche-transcendence skill for Orthogonality analysis
- Audit each genre element for freshness
- Deliver expected emotional experience through unexpected means
State G7: Setting Mistaken for Genre
Symptoms: "It's sci-fi" when asked about genre. Worldbuilding without emotional core. Setting elements don't serve genre needs. Story would have no genre if setting were removed.
Key Questions:
- If you remove the setting, what genre is the emotional story?
- How does your setting enhance the genre experience?
- What would this story be in a contemporary setting?
- Is the setting doing all the work?
Interventions:
- Identify the genre beneath the setting
- Align setting elements to serve genre needs
- Ensure story has emotional throughline independent of setting
State G8: Ensemble Without Genre Assignment
Symptoms: Multiple POV characters with no coherent genre experience. Tonal whiplash between POVs. Reader doesn't know what to feel. Each thread works alone but they don't combine.
Key Questions:
- What's the umbrella genre for the whole story?
- Does each POV thread have its own subgenre?
- How do the genre experiences combine?
- Is there a dominant POV that sets genre expectations?
Interventions:
- Establish primary genre that all threads serve
- Assign compatible subgenres to each POV
- Map POV transitions to ensure tonal coherence
- Use ensemble elements to unify rather than fragment
Genre Requirements Quick Reference
| Genre | Setting Needs | Character Needs | Plot Needs |
|---|---|---|---|
| Wonder | Vast scales, unprecedented phenomena | Capacity for awe, can recognize significance | Discovery, revelation, perspective shift |
| Idea | Societies built around concepts | Intellectually curious, varied perspectives | Concept exploration, hypothesis testing |
| Adventure | Varied environments, physical obstacles | Relevant skills, tested beyond experience | Progressive challenges, geographic movement |
| Horror | Isolation, restricted movement, breakdown of normal | Vulnerabilities matching threats, something to lose | Escalating threat, diminishing safety |
| Mystery | Controlled environments, layered information | Investigators with skills, witnesses, suspects | Information gathering, progressive revelation |
| Thriller | Time-sensitive, high-stakes environments | Crucial responsibilities, matched antagonists | Deadline pressure, escalating threats |
| Humor | Unusual rules, potential for misunderstanding | Blind spots, contrasting norms | Miscommunication, subverted expectations |
| Relationship | Forced proximity, shared challenges | Complementary traits, meaningful obstacles | Connection progression, relationship tests |
| Drama | Environments that challenge values | Strong values facing tests | Difficult choices, internal conflict |
| Issue | Societies manifesting the issue | Diverse perspectives on central issue | Direct experience with different facets |
| Ensemble | Challenges requiring diverse skills | Complementary abilities, contrasting views | Team formation, cooperation challenges |
Diagnostic Process
When a writer comes with genre-related symptoms:
1. Identify the Intended Genre
Ask: "What emotional experience do you want readers to have?" Not "what category is this?" but "what should readers feel?"
2. Check for Genre Promise
Does the opening signal this genre? First scene should contain at least one clear marker of the intended experience.
3. Audit Required Elements
Use the requirements table. Is each required element present? Placed correctly? Sufficiently developed?
4. Check Secondary Genres
If there are secondary genres, are they serving or competing? What proportion of story goes to each?
5. Check for Setting/Genre Confusion
Remove the setting mentally. Is there still a genre? The setting should enhance, not replace, the emotional experience.
6. Recommend Interventions
Based on identified state, provide specific interventions. Generate elements if needed. Point to frameworks.
Anti-Patterns
The Genre Mashup Without Hierarchy
Problem: Story tries to be equally mystery, thriller, and romance. Reader doesn't know what experience to expect. No clear emotional throughline.
Fix: Establish clear primary genre. Secondary genres serve the primary experience. One genre must dominate.
Show full SKILL.md (818 more words)Show less
The Setting-as-Genre
Problem: "It's sci-fi" answers the genre question. Story has worldbuilding but no emotional core. If you removed the setting, there's no story left.
Fix: Identify the emotional genre beneath the setting. "It's a mystery set in a sci-fi world" has a genre. "It's sci-fi" does not.
The Genre Promise Bait-and-Switch
Problem: Opens as thriller, becomes relationship drama. Reader expecting tension gets feelings. Reader expecting feelings gets tension. Neither is satisfied.
Fix: Signal true genre early. If hybrid, show both elements in opening. Don't promise what you won't deliver.
The Checklist Without Integration
Problem: Story has clues (mystery), time pressure (thriller), and dread (horror), but they don't serve a unified experience. Elements are present but inert.
Fix: Genre elements must reinforce primary emotional experience. Each element should intensify, not just exist.
The Subverted Expectations Trap
Problem: Every genre expectation is subverted. Reader has no stable ground. Surprise has replaced satisfaction.
Fix: Deliver on core promise. Subvert execution, not contract. Reader should feel satisfied in the expected way via unexpected path.
Available Tools
genre-elements.ts
Random element generator for each genre.
# Random element from a genre
deno run --allow-read scripts/genre-elements.ts mystery
# Specific category within genre
deno run --allow-read scripts/genre-elements.ts thriller --category ticking_clocks
# Multiple elements
deno run --allow-read scripts/genre-elements.ts horror --count 3
# List all available genres and categories
deno run --allow-read scripts/genre-elements.ts --list
# Combo from multiple genres
deno run --allow-read scripts/genre-elements.ts --combo mystery,thrillergenre-check.ts
Pattern-matching diagnostic for text samples.
# Check text against specific genre
deno run --allow-read scripts/genre-check.ts --genre mystery scene.txt
# Auto-detect likely genre
deno run --allow-read scripts/genre-check.ts --analyze "Synopsis text here..."
# Inline text check
deno run --allow-read scripts/genre-check.ts --text "The detective arrived at dawn..." --genre mysterygenre-blend.ts
Secondary genre integration helper.
# Integration strategies for two genres
deno run --allow-read scripts/genre-blend.ts mystery relationship
# Multiple secondary genres
deno run --allow-read scripts/genre-blend.ts thriller --secondary humor,wonder
# Analyze text for genre blend
deno run --allow-read scripts/genre-blend.ts --analyze "A detective who falls in love while investigating..."Integration with story-sense
| story-sense State | May Lead to Genre State |
|---|---|
| State 0: No Story | G1 (need to establish genre promise) |
| State 1: Concept Without Foundation | G2 (wrong genre for material), G7 (setting vs. genre confusion) |
| State 4.5: Plot Without Pacing | G3 (genre elements misplaced), G5 (missing required elements) |
| State 5: Plot Without Purpose | G4 (secondary genre undermining), G2 (genre mismatch) |
| State 7: Ready for Evaluation | G6 (genre cliches unexamined) |
When to Hand Off
- To character-arc: When genre problems stem from character not fitting genre needs
- To scene-sequencing: When genre pacing issues are really scene-level structure issues
- To cliche-transcendence: When genre elements are stale (State G6)
- To worldbuilding: When setting isn't serving genre needs
Example Interactions
Example 1: Missing Genre Promise
Writer: "Readers keep asking what kind of book this is and I don't know how to answer."
Your approach:
- Identify likely state: G1 (Missing Genre Promise)
- Ask: "What do you want readers to feel while reading?"
- Once they identify the emotion, help them see which elemental genre creates that experience
- Check the opening for genre markers
- Suggest specific elements to add that signal the genre
Example 2: Setting/Genre Confusion
Writer: "It's a fantasy novel set in a world where magic is dying."
Your approach:
- Notice: this describes setting, not genre
- Ask: "If I removed the magic and fantasy world, what story remains? What's the emotional experience?"
- Help them identify: Is it mystery (figuring out why magic is dying)? Drama (character transformation as magic fades)? Horror (dread of losing something precious)?
- Once genre is identified, check if fantasy elements serve that genre
Example 3: Competing Secondary Genre
Writer: "The romance subplot keeps taking over my thriller."
Your approach:
- Identify likely state: G4 (Secondary Genre Undermining)
- Ask about proportion: how much page time goes to each?
- Ask about integration: does the romance create thriller stakes or pause them?
- Suggest containment strategies or deeper integration
- Consider whether the book is actually romance with thriller elements (genre swap)
Output Persistence
This skill writes primary output to files so work persists across sessions.
Output Discovery
Before doing any other work:
- Check for
context/output-config.mdin the project - If found, look for this skill's entry
- If not found or no entry for this skill, ask the user first:
- "Where should I save output from this genre-conventions session?"
- Suggest:
explorations/genre/or a sensible location for this project
- Store the user's preference:
- In
context/output-config.mdif context network exists - In
.genre-conventions-output.mdat project root otherwise
- In
Primary Output
For this skill, persist:
- Genre diagnosis - primary and secondary genres identified
- Convention checklist - required elements for the genre(s)
- Promise analysis - what emotional experience is promised
- Hybrid structure notes - how multiple genres are hierarchized
Conversation vs. File
| Goes to File | Stays in Conversation |
|---|---|
| Genre identification | Clarifying questions |
| Convention requirements | Discussion of specific scenes |
| Promise inventory | Writer's genre decisions |
| Hierarchy recommendations | Real-time feedback |
File Naming
Pattern: {story}-genre-{date}.md
Example: novel-genre-2025-01-15.md
What You Do NOT Do
- You do not write scenes or prose for writers
- You do not choose their genre for them
- You do not insist on genre purity - hybrid genres work when hierarchized
- You do not conflate setting with genre
- You do not diagnose prose-level issues (that's prose-style skill territory)
- You do not handle character arc problems directly (hand off to character-arc)
Key Insight
Genre is not a label applied after writing. Genre is a contract made at the start. The opening promises an emotional experience. The middle develops that experience. The ending delivers on the promise. Every element should serve the contract.
When genre problems appear, they often mask deeper issues: unclear purpose (story-sense), weak character arc (character-arc), pacing problems (scene-sequencing), or stale execution (cliche-transcendence). Diagnose genre first, then trace to root cause.
© 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/craft/genre-conventions of jwynia/agent-skills.
- SKILL.md
- data/genre-elements.json
- scripts/genre-blend.ts
- scripts/genre-check.ts
- scripts/genre-elements.ts
Open the folder on GitHubat commit e02ec7e
Compare with similar skills
Genre Conventions 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 |
|---|---|---|---|---|---|---|
| Genre Conventions this skilljwynia/agent-skills | 170 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Diagnose Gatewayopenclaw/openclaw | 392k | — | ~670 | Automated safety check: Pass | MIT | |
| Ecc Conventionsaffaan-m/ECC | 276k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Diagnosegithub/awesome-copilot | 40k | 1 repos | ~1k | Automated safety check: Pass | MIT | |
| Is This A Problemanthropics/claude-for-legal | 9.6k | 2 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Conventional Commit Reviewaffaan-m/ECC | 276k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Ecc Conventions
affaan-m/ECC
Development conventions and patterns for ECC. An agent skill from affaan-m/ECC.
- Official
Diagnose
github/awesome-copilot
Perform a systematic diagnostic scan of an AI workflow across 5 quality dimensions — prompt quality, context efficiency, tool health, architecture fitness, and safety — producing a scored report…
- Official
Is This A Problem
anthropics/claude-for-legal
Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration.
Conventional Commit Review
affaan-m/ECC
Reviews staged changes and drafts a Conventional Commits-compliant commit message with the right type, scope, and length.
Naming Conventions
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Use consistent CSS naming conventions.
More from jwynia/agent-skills
All 111 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.
Questions about Genre Conventions
What does Genre Conventions do?
Diagnose genre problems and generate genre-specific elements. Genre Conventions is an agent skill from jwynia/agent-skills. Diagnose genre problems and generate genre-specific elements.
When should I use Genre Conventions?
Genre Conventions fits situations like: genre promise is unclear; elements feel misplaced; secondary genres compete with primary; you need genre-specific entropy.
How do I install Genre Conventions in Claude Code?
Run `npx skills add jwynia/agent-skills --skill genre-conventions -a claude-code`. Or copy the skill folder (skills/creative/fiction/craft/genre-conventions in jwynia/agent-skills) into .claude/skills/genre-conventions in your project. Claude Code loads it when a task matches its description.
How do I install Genre Conventions in Codex?
Run `npx skills add jwynia/agent-skills --skill genre-conventions -a codex`. Or copy the skill folder (skills/creative/fiction/craft/genre-conventions in jwynia/agent-skills) into .agents/skills/genre-conventions in your project. Codex loads it when a task matches its description.
Can I use Genre Conventions 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 genre-conventions -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/genre-conventions, .gemini/skills/genre-conventions, .github/skills/genre-conventions and .opencode/skills/genre-conventions in your project.
What does Genre Conventions need to run?
Going by SKILL.md and its folder, Genre Conventions needs TypeScript for the scripts in its folder and the command-line tools its instructions call (deno). Our summary lists: Node.js.
Does Genre Conventions 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 Genre Conventions 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 Genre Conventions use?
Genre Conventions 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 Genre Conventions use?
About 4.4k tokens (SKILL.md is roughly 18k 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 Genre Conventions?
Skills that share tags, products or a category with Genre Conventions: Diagnose Gateway (openclaw/openclaw, 392k stars), Ecc Conventions (affaan-m/ECC, 276k stars), Diagnose (github/awesome-copilot, 40k stars) and Is This A Problem (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Genre Conventions?
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.