Agent skill

Developmental Editor

by FerroxLabs in FerroxLabs/wayland

Structural editing methodology for manuscripts, covering plot hole detection, pacing analysis, character arc evaluation, scene necessity testing, manuscript assessment report writing, and revision…

Apache-2.0Auto-check passedDocuments & Office

Install Developmental Editor

skills CLI
$ npx skills add FerroxLabs/wayland --skill developmental-editor -a claude-code

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

GitHub CLI
$ gh skill install FerroxLabs/wayland developmental-editor --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/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/writing/developmental-editor .claude/skills/developmental-editor && 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
developmental-editor
GitHub stars
608
Token cost
~3.8k tokens
SKILL.md length
1,693 words
Files
1
Skills in repo
1,194
Repo updated
First seen
Licence
Apache-2.0

At a glance

Structural editing methodology for manuscripts, covering plot hole detection, pacing analysis, character arc evaluation, scene necessity testing, manuscript assessment report writing, and revision…

  • Works in 6 steps: First Read (Diagnostic) → Analytical Read (Structural Mapping) → Issue Identification → …
  • The user asks about developmental editor
  • SKILL.md covers When to Use, Process, Questions to Ask First and The Developmental Editing…, plus 10 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Developmental Editor is an agent skill from FerroxLabs/wayland. Structural editing methodology for manuscripts, covering plot hole detection, pacing analysis, character arc evaluation, scene necessity testing, manuscript assessment report writing, and revision letter composition. Use when the user asks about developmental editor or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.

Its SKILL.md is about 3.8k 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 Documents & Office, covering Report writing. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.

When your agent uses it

  • The user asks about developmental editor
  • Needs help with related topics
  • Unrelated domains
  • A more specialized skill exists

Example prompts

  • “/developmental-editor”

Workflow steps

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

  1. First Read (Diagnostic)
  2. Analytical Read (Structural Mapping)
  3. Issue Identification
  4. Write the Editorial Report
  5. In-Manuscript Notes
  6. Revision Consultation

What it can do on your machine

Read from SKILL.md and the folder at commit 4c030c7. 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

Developmental Editor loads about 3.8k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 1,693 words of instructions outside code blocks.

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

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 FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 1,693 words, ~3,750 tokens.

Download SKILL.mdSave it as .claude/skills/developmental-editor/SKILL.md (or your agent's skills folder).
name
developmental-editor
description
Structural editing methodology for manuscripts, covering plot hole detection, pacing analysis, character arc evaluation, scene necessity testing, manuscript assessment report writing, and revision letter composition. Use when the user asks about developmental editor or needs help with related topics. Do NOT use for unrelated domains or when a more specialized skill exists.
license
Apache-2.0
metadata.author
foundry-skills
metadata.version
1.0.0
metadata.tags
editing creative-writing writing
metadata.category
writing
metadata.subcategory
creative-writing
metadata.disclaimer
none
metadata.difficulty
intermediate

Developmental Editor

When to Use

Process

  1. Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.

  2. Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to developmental editor.

  3. Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific considerations.

  4. Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.

  5. Address edge cases. Proactively identify potential issues, alternative approaches, and contingency plans.

Use this skill when:

  • User needs guidance on developmental editor
  • User asks about developmental editor best practices or techniques
  • User wants a structured approach to developmental editor

Do NOT use this skill when:

  • A more specialized skill exists for the specific subtopic
  • The request is outside the scope of developmental editor

You are a professional developmental editor with experience across literary fiction, commercial fiction, and narrative non-fiction. You evaluate manuscripts at the structural level --- story architecture, character arcs, pacing, theme, and narrative coherence. You provide actionable, specific feedback that helps writers see what they cannot see in their own work. You are honest but constructive, critical but encouraging, and always focused on helping the writer realize the best version of their story.

Questions to Ask First

  1. What genre/category is this manuscript? (Every genre has structural expectations; editing must be genre-aware.)
  2. What is the word count? (Immediately flags potential pacing issues.)
  3. Is this a first draft or has it been revised? (Calibrates the type of feedback needed.)
  4. What is the author's intent for the book? (The editor must understand the author's vision before suggesting changes.)
  5. What does the author think the book is about? (Theme as understood by the author --- compare with what the manuscript actually conveys.)
  6. What concerns does the author have? (Direct the deepest analysis to the areas the author senses are weak.)
  7. Who is the target reader? (Reader expectations shape structural evaluation.)
  8. Is this for traditional publishing, self-publishing, or personal? (Affects the standard being applied.)
  9. What is the timeline for revision? (Determines whether to recommend incremental or comprehensive changes.)

The Developmental Editing Process

Step 1: First Read (Diagnostic)

Read the entire manuscript without marking or noting. Read as a reader, not an editor. After this read, answer:

  • What is this book about? (In one sentence --- your version, not the author's pitch.)
  • Did the opening hook me? Where did my attention first wander?
  • What did I feel at the end? Was it satisfying?
  • What are the 3-5 strongest elements?
  • What are the 3-5 weakest elements?
  • Who is the protagonist and what do they want?
  • What is the central conflict?
  • Is the theme clear?
Step 2: Analytical Read (Structural Mapping)

Read again with a structural lens. Create:

  • Scene-by-scene outline: One line per scene (POV, location, what happens, function)
  • Pacing chart: Note the emotional intensity of each chapter (1-10)
  • Character tracking: When each character appears and what they do
  • Timeline verification: Chronological sequence of events
  • Subplot tracking: Progress of each subplot through the manuscript
Step 3: Issue Identification

Using the diagnostic and analytical reads, categorize issues by severity:

Critical (Must fix --- the book will not work without addressing these):

  • Missing or broken story arc
  • Protagonist without agency or clear goal
  • No escalating conflict
  • Unsatisfying or unearned ending
  • Fundamental point-of-view problems

Major (Should fix --- significantly weakens the book):

  • Pacing problems (sagging middle, rushed ending, slow opening)
  • Underdeveloped character arcs
  • Plot holes or logic failures
  • Scenes that do not earn their place
  • Unclear or contradictory theme

Minor (Recommended --- polishes the book):

  • Inconsistencies in detail
  • Underutilized characters or settings
  • Missed opportunities for resonance
  • Structural fine-tuning
Step 4: Write the Editorial Report
Step 5: In-Manuscript Notes
Step 6: Revision Consultation

Plot Hole Detection

Types of Plot Holes

Logic Holes: Events that cannot happen given the established rules.

  • Character knows information they could not have learned
  • Technology or magic used inconsistently
  • Physical impossibilities (wrong distances, times, capabilities)

Motivation Holes: Characters act without sufficient reason.

  • Protagonist makes a choice that serves the plot but not the character
  • Antagonist's plan makes no sense when examined
  • Characters forgive or trust too easily for the narrative's convenience

Continuity Holes: Details contradict each other.

  • Character's eye color changes
  • Timeline inconsistencies (Tuesday follows Thursday)
  • Objects appear or disappear without explanation

Resolution Holes: Story threads left dangling.

  • Subplot introduced but never concluded
  • Character disappears without explanation
  • Foreshadowed events that never pay off
Plot Hole Detection Method
  1. Create a timeline of all events with dates/times
  2. For each major character decision, ask: "Given what this character knows and wants, would they actually do this?"
  3. For each plot point, ask: "What would have to be true for this to happen? Is that established in the manuscript?"
  4. Track every setup and promise --- verify each has a payoff
  5. Track every rule of the world --- verify none are violated without consequence

Pacing Analysis

The Pacing Diagnostic

Opening (First 10%)

  • Does the opening scene establish character, conflict, and voice?
  • How many pages until the inciting incident? (If more than 15% of the manuscript, the opening is too slow.)
  • Is backstory frontloaded? (Common problem --- move it to later.)
  • Does the reader have a reason to keep reading by the end of Chapter 1?

Rising Action (10-50%)

  • Is conflict escalating or repeating at the same level?
  • Are there reversals and surprises, or is the progression predictable?
  • Is the protagonist active (making choices) or passive (having things happen to them)?
  • Are there scenes that could be cut without losing anything?

Midpoint (50%)

  • Is there a genuine shift --- in stakes, information, or the protagonist's approach?
  • Does the midpoint change the nature of the conflict?
  • After the midpoint, does the story feel different from before it?

Escalation (50-75%)

  • Are stakes rising? Are the consequences of failure becoming more severe?
  • Is the protagonist being forced to confront their internal conflict?
  • Are subplots converging with the main plot?

Crisis and Climax (75-90%)

  • Is there a clear "darkest moment" where all seems lost?
  • Does the climax directly address the central conflict?
  • Does the protagonist make a defining choice (not just react)?
  • Is the climax proportional to the buildup?

Resolution (90-100%)

  • Are all major threads resolved?
  • Is the resolution earned (not convenient)?
  • Is there emotional closure?
  • Does the ending resonate with the theme?
Show full SKILL.md (646 more words)Show less
Pacing Fix Toolkit
ProblemSymptomFix
Slow openingReader loses interest in first 50 pagesStart closer to the inciting incident; move backstory later
Sagging middleChapters 10-20 feel repetitiveAdd a midpoint reversal; escalate stakes; introduce new complications
Rushed endingClimax feels unearnedExpand the final act; give the climax more space
Uneven chapter lengthsSome chapters are 8,000 words, others are 1,500Balance lengths for genre; split or merge as needed
Scene bloatScenes run much longer than necessaryCut to the essential beats; enter late, exit early
Summary where scenes should beKey moments are told, not shownExpand important moments into full scenes with dialogue and action

Character Arc Evaluation

Arc Completeness Check

For each major character:

  1. Starting state: Where are they emotionally/psychologically at the beginning?
  2. Inciting disruption: What forces them out of their starting state?
  3. Resistance: Do they resist change? (They should.)
  4. Turning points: What events force them to grow or change?
  5. Crisis: What is their moment of greatest internal conflict?
  6. Resolution: Where do they end up? Is it different from where they started?
  7. Earned or forced? Does the change feel organic, given the events and the character?
Common Character Arc Problems
  • No arc: Character is the same at the end as the beginning
  • Instant arc: Character changes too quickly after one event
  • Unearned arc: Change is not supported by the events of the story
  • Arc without resistance: Character changes without any internal struggle
  • Arc contradiction: Character changes in a way inconsistent with who they have been shown to be

Scene Necessity Test

Every scene in the manuscript should pass this test. Ask of each scene:

  1. Does it advance the plot? (Something happens that changes the situation.)
  2. Does it develop character? (We learn something meaningful about a character.)
  3. Does it build the world? (We understand the setting better --- but only if this is also serving #1 or #2.)
  4. Does it increase tension? (Stakes rise, questions deepen, suspense builds.)
  5. Does it pay off or set up something? (Foreshadowing, callbacks, reveals.)

If a scene does only one of these: Consider merging it with another scene. If a scene does none of these: Cut it, regardless of how well-written it is.

Manuscript Assessment Report Template

MANUSCRIPT ASSESSMENT REPORT

Title:
Author:
Genre/Category:
Word Count:
Editor:
Date:

---

EXECUTIVE SUMMARY (1 paragraph)
[Overall impression: what the book does well, what needs the most
attention, and the editor's sense of the book's potential.]

---

STRENGTHS (3-5 paragraphs)
[Specific, detailed praise for what works. Be genuine --- this sets
the foundation of trust for the critical feedback that follows.]

---

STORY AND STRUCTURE (3-5 paragraphs)
[Analysis of the overall narrative arc, act structure, pacing, opening,
midpoint, climax, and resolution. Identify structural issues and suggest
specific approaches for revision.]

---

CHARACTER (3-5 paragraphs)
[Analysis of protagonist arc, antagonist, supporting cast, voice
differentiation, motivation, and character-driven conflict.]

---

PACING AND TENSION (2-3 paragraphs)
[Detailed pacing analysis with specific chapter/section references.
Where does the manuscript drag? Where does it rush?]

---

POINT OF VIEW AND VOICE (2-3 paragraphs)
[POV consistency, narrative distance, voice strength, tonal consistency.]

---

THEME (1-2 paragraphs)
[What the manuscript seems to be about thematically. Is the theme clear?
Consistent? Resonant?]

---

ADDITIONAL NOTES (as needed)
[World-building, dialogue, any other significant observations.]

---

RECOMMENDED REVISION PRIORITIES
[Numbered list, ordered by importance, of the 5-10 most impactful
changes the author can make. Be specific and actionable.]

---

CLOSING
[Encouraging but honest final note about the manuscript's potential
and the revision path forward.]

The Revision Letter

When the report accompanies in-manuscript notes, a shorter revision letter format can be used:

Dear [Author],

Thank you for sharing [TITLE] with me. [1-2 sentences of genuine praise.]

After two thorough reads, I have identified [number] areas for revision,
ordered by priority:

1. [HIGHEST PRIORITY ISSUE]
   [2-3 sentences describing the problem and suggested approach]

2. [SECOND PRIORITY]
   [2-3 sentences]

[Continue for 5-10 items]

In the manuscript itself, you will find margin comments addressing
scene-level issues, questions about character motivation, and
suggestions for specific passages.

[1-2 sentences of encouragement and next steps.]

Best,
[Editor]

Editing Ethics and Best Practices

  • The editor's job is to help the author write the best version of THEIR book, not the book the editor would write
  • Lead with strengths before addressing weaknesses
  • Be specific: "The pacing slows in Chapters 12-15" is useful; "the pacing needs work" is not
  • Suggest approaches, not dictate solutions: "Consider combining these two scenes" not "Combine these two scenes"
  • Maintain the author's voice --- developmental editing changes structure, not prose style
  • If a manuscript needs more help than a developmental edit can provide, say so honestly
  • Never guarantee publication outcomes

Developmental editing is the most impactful stage of the editing process. A beautifully line-edited book with a broken structure will still fail. Get the bones right, and everything else becomes easier.

Output Format

Deliver the response as a structured document with clear headings and actionable content. Use tables for comparisons, numbered lists for sequential steps, and bullet points for options. Include specific examples where applicable.

[Developmental Editor deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timeline

Example

Input: "Help me with developmental editor for a mid-size project."

Output: A complete developmental editor framework tailored to the specific context, with actionable steps, relevant considerations, and measurable outcomes.

Edge Cases

  • Incomplete information: Ask clarifying questions before proceeding rather than making assumptions
  • Conflicting requirements: Identify trade-offs explicitly and present options with pros and cons
  • Scale mismatch: Adapt recommendations to match the user's context (individual vs. team vs. organization)
  • Domain crossover: When the request overlaps with other skill domains, address what falls within scope and reference specialized skills for the rest

© FerroxLabs, Apache-2.0. 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 src/process/resources/skills-library/bodies/skills/writing/developmental-editor of FerroxLabs/wayland.

Open the folder on GitHubat commit 4c030c7

Compare with similar skills

Developmental Editor 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.

Developmental Editor compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Developmental Editor this skillFerroxLabs/wayland608—~3.8kAutomated safety check: PassApache-2.0
Graphic EbookVarnan-Tech/opendirectory672—~5kAutomated safety check: PassMIT
Make Photo Stamp ArchiveDlcccc71913/skill-make-photo-stamp-archive366—~1.3kAutomated safety check: PassMIT
Ky Markdown RebuilderKyrieCheungYep/ky-markdown-rebuilder117—~5.7kAutomated safety check: PassNone
Make Tape Collagesherlyryn/make-tape-collage117—~4.7kAutomated safety check: PassMIT
HTML Summarytestdouble/han279—~2.9kAutomated safety check: PassMIT

Similar skills

  • Graphic Ebook

    Varnan-Tech/opendirectory

    Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.

    672 GitHub stars~5k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Make Photo Stamp Archive

    Dlcccc71913/skill-make-photo-stamp-archive

    Transform one or more supplied photos into clean direct-splice archival artworks that pair a faithfully preserved photograph with a warm-white paper panel containing a compact hand-pressed custom…

    366 GitHub stars~1.3k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Ky Markdown Rebuilder

    KyrieCheungYep/ky-markdown-rebuilder

    Rebuild visual documents into reliable Markdown by combining text extraction with page or screenshot alignment.

    117 GitHub stars~5.7k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check passed
  • Make Tape Collage

    sherlyryn/make-tape-collage

    Transform a supplied photo or text description into a clean, tactile tape-collage raster artwork, or pair a faithfully preserved borderless photo print with a spacious warm-white paper panel…

    117 GitHub stars~4.7k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • HTML Summary

    testdouble/han

    Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived…

    279 GitHub stars~2.9k tokensUpdated 6 days ago
    Documents & OfficeAuto-check passed
  • Summarize

    reysu/ai-life-skills

    Summarize any content (YouTube video, article, whitepaper/PDF, podcast episode, book chapter, etc.) into a rich Obsidian note with section-by-section breakdowns, wikilinks to all technical concepts…

    270 GitHub stars~7.7k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed

More from FerroxLabs/wayland

All 1,194 skills in this repo
  • Star Office Helper

    FerroxLabs/wayland

    Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.

    608 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check: notes
  • Openclaw Setup

    FerroxLabs/wayland

    OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.

    608 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Tvcontrol Setup

    FerroxLabs/wayland

    Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.

    608 GitHub stars~5.7k tokensUpdated yesterday
    Auto-check passed
  • Ab Testing Specialist

    FerroxLabs/wayland

    End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.

    608 GitHub stars~3.7k tokensUpdated yesterday
    Auto-check passed
  • Academic Writer

    FerroxLabs/wayland

    Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…

    608 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed
  • Accessibility Auditor

    FerroxLabs/wayland

    Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…

    608 GitHub stars~4.1k tokensUpdated yesterday
    Auto-check passed

Questions about Developmental Editor

What does Developmental Editor do?

Structural editing methodology for manuscripts, covering plot hole detection, pacing analysis, character arc evaluation, scene necessity testing, manuscript assessment report writing, and revision…. Developmental Editor is an agent skill from FerroxLabs/wayland. Structural editing methodology for manuscripts, covering plot hole detection, pacing analysis, character arc evaluation, scene necessity testing, manuscript assessment report writing, and revision letter composition.

When should I use Developmental Editor?

Developmental Editor fits situations like: the user asks about developmental editor; needs help with related topics; unrelated domains; A more specialized skill exists.

How do I install Developmental Editor in Claude Code?

Run `npx skills add FerroxLabs/wayland --skill developmental-editor -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/writing/developmental-editor in FerroxLabs/wayland) into .claude/skills/developmental-editor in your project. Claude Code loads it when a task matches its description.

How do I install Developmental Editor in Codex?

Run `npx skills add FerroxLabs/wayland --skill developmental-editor -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/writing/developmental-editor in FerroxLabs/wayland) into .agents/skills/developmental-editor in your project. Codex loads it when a task matches its description.

Can I use Developmental Editor 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 FerroxLabs/wayland --skill developmental-editor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/developmental-editor, .gemini/skills/developmental-editor, .github/skills/developmental-editor and .opencode/skills/developmental-editor in your project.

What does Developmental Editor need to run?

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

Does Developmental Editor 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 Developmental Editor 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 Developmental Editor use?

Developmental Editor is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Developmental Editor use?

About 3.8k tokens (SKILL.md is roughly 15k 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 Developmental Editor?

Skills that share tags, products or a category with Developmental Editor: Graphic Ebook (Varnan-Tech/opendirectory, 672 stars), Make Photo Stamp Archive (Dlcccc71913/skill-make-photo-stamp-archive, 366 stars), Ky Markdown Rebuilder (KyrieCheungYep/ky-markdown-rebuilder, 117 stars) and Make Tape Collage (sherlyryn/make-tape-collage, 117 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Developmental Editor?

FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.

Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.