Automated summary

This workflow guides the editing of guide chapters, ensuring structural changes propagate to all dependent files.

Strengths

Systematically checks impact of title, template, and canonical term changes.
Automates cross-references updates like README and 'Next:' links.
Enforces consistent style (prescriptive voice, required sections, heading hierarchy).
Includes final verification with the cross-reference-check skill.

Limitations

Does not handle non-structural edits (minor fixes, rewordings).
Relies on presence of '11-failure-modes.md' chapter for footer handling.
Requires manual execution of cross-reference-check after changes.

When to use it

Use this workflow before making any substantive edit to a file in the guide/ directory, especially when changing a title, template reference, or canonical term.

When not to use it

Do not use it for minor corrections (typos, style tweaks) that do not affect the guide's structure.

Security analysis

Safe

Quality score95/100

The skill outlines a workflow for editing guide chapters, ensuring consistency across files. It only instructs reading, searching, and updating markdown files, with no destructive or exfiltration actions. No risk.

No concerns found

How this analysis is made

Examples

Change chapter title

I need to change the title of Chapter 3 from 'Old Title' to 'New Title'. Please follow the edit-chapter workflow.

Update template reference

In chapter 5, I'm replacing the template path 'templates/old.md' with 'templates/new.md'. Run the edit-chapter workflow to ensure all dependencies are updated.

Modify canonical term

I'm changing the canonical term 'five-tier context hierarchy' to 'four-tier context hierarchy' across the guide. Use edit-chapter to update all occurrences.

name: edit-chapter description: Invoke this skill before making substantive edits to any file in guide/ — changing content, titles, template references, or canonical terms. Follow this workflow proactively when editing chapters, not only when the user explicitly requests it. Ensures structural changes propagate to all dependent files.

Edit Chapter

Name: Edit Chapter
Author: Skills Guide Bot

Guided workflow for safely editing a guide chapter. Ensures structural changes propagate to all dependent files.

Before Editing

Read the entire chapter file
Note the current H1 title (line 1)
Note any template paths referenced (lines mentioning templates/)
Note any canonical terms used ("five-tier context hierarchy", "document cascade")

During Editing

Maintain prescriptive voice — no hedging phrases (see .claude/rules/guide-chapter.md)
Preserve required sections: Principles, What the Human Should Do, What the Agent Should Do
Use RecipeVault for examples (not "Beacon")
Keep heading hierarchy: ## for major sections, ### for subsections
Use fenced code blocks with language identifiers

After Editing

Check each condition and take action if true:

If the H1 title changed:

Update README.md chapter listing (lines 45-93)
Update CLAUDE.md if the chapter is referenced there
Update the "Next:" link in the prior chapter's footer

If template references changed:

Verify each referenced template path exists in templates/
If a path was removed or renamed, grep for the old path across the repo

If a canonical term changed:

Search all .md files for the old term
Update every occurrence to match the new term

Always (every edit):

Verify the chapter ends with a Next: footer linking to the correct successor chapter, unless the file is 11-failure-modes.md

The footer must follow this format:

---

Next: [Chapter NN -- Title](NN-slug.md)

If any structural change was made (title, file references, canonical terms):

Run the cross-reference-check skill to verify consistency

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/edit-chapter-mrwak9gg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/edit-chapter-mrwak9gg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/edit-chapter-mrwak9gg/download' --output '.skill-downloads/edit-chapter-mrwak9gg/SKILL.md.part' && mv '.skill-downloads/edit-chapter-mrwak9gg/SKILL.md.part' '.skill-downloads/edit-chapter-mrwak9gg/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/edit-chapter-mrwak9gg/SKILL.md' && test -s '.skill-downloads/edit-chapter-mrwak9gg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/edit-chapter' && cp -R '.skill-downloads/edit-chapter-mrwak9gg' '.claude/skills/edit-chapter'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/edit-chapter-mrwak9gg'

openskills read 'edit-chapter-mrwak9gg'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/edit-chapter-mrwak9gg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

Supabase Docs Authoring

Documentation

Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.

Claude CodeintermediateSafe 108,544

Skills Guide Bot