agentleFS
Sign inStart free
alfredxwalfredxw/denova/skills/chapter-illustration/SKILL.md

chapter-illustration

Skill990 starsChanged 4 months agoApache-2.0View on GitHub

Generate one spoiler-free illustration for the current or specified chapter and save it under workspace assets/writing.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this Skill when the author requests an illustration for a chapter or the editor sends /chapter-illustration.

    line 10
  2. Distinctive:

    Use the chapter path explicitly provided by the user.

    line 15
  3. Very specific:

    If no chapter is focused, identify the most recent chapter from the workspace summary or chapters/ directory.

    line 17
  4. Distinctive:

    Read the target chapter before composing the image prompt.

    line 18
  5. Distinctive:

    Write a clear Chinese image prompt containing the subject, scene, composition, lighting, style, and mood, with explicit negative …

    line 20
  6. Very specific:

    Call the general generate_image tool with:

    line 21
  7. Distinctive:

    After the tool returns, briefly report what was generated and tell the user to use the illustration card's insertion action.

    line 28
  8. Distinctive:

    Do not generate batches of candidates.

    line 33
  9. Distinctive:

    Do not use file-write tools to insert Markdown image syntax into the chapter.

    line 34
  10. Distinctive:

    If the user asks to insert the result, prefer the UI insertion action.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Chapter Illustration

Use this Skill when the author requests an illustration for a chapter or the editor sends /chapter-illustration.

Workflow

  1. Determine the target chapter path:
    • Use the chapter path explicitly provided by the user.
    • Otherwise, use the chapter currently focused in the IDE context.
    • If no chapter is focused, identify the most recent chapter from the workspace summary or chapters/ directory.
  2. Read the target chapter before composing the image prompt. If the selected path is not a chapter, ask the user to select one.
  3. Choose a visually compelling, spoiler-free moment from the chapter. Do not reveal future reversals, hidden identities, or undisclosed canon.
  4. Write a clear Chinese image prompt containing the subject, scene, composition, lighting, style, and mood, with explicit negative constraints against text, watermarks, and logos.
  5. Call the general generate_image tool with:
    • purpose: chapter_illustration.
    • target_path: the target chapter's relative path.
    • prompt: the complete Chinese image prompt.
    • alt_text: a Chinese description suitable for a Markdown image.
    • size: optionally choose a supported 2K, 3K, or 4K size based on the composition; otherwise omit it and use the default policy.
    • output_format: png or jpeg; omit it when uncertain.
  6. After the tool returns, briefly report what was generated and tell the user to use the illustration card's insertion action. Do not repeat the Markdown image reference in a fenced code block. Do not edit the chapter prose automatically.

Constraints

  • Generate exactly one chapter illustration per request.
  • Do not generate batches of candidates.
  • Do not use file-write tools to insert Markdown image syntax into the chapter.
  • If the user asks to insert the result, prefer the UI insertion action.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free