AgentSkillsCN

zudoesa-articlify

通过委托 zudoesa-writer 子代理，将对话情境转化为 esa 文章。当用户：(1) 希望根据对话内容撰写 esa 文章；(2) 提出“撰写 esa 文章”、“esa 文章”、“以 esa 风格写作”、“为 esa 整理文章”时，可使用此技能。该技能会从对话中收集背景信息，制定详细的写作大纲，并将任务委托给写作子代理。

SKILL.md
--- frontmatter
name: zudoesa-articlify
description: >
  Convert conversation context into an esa article by delegating to the zudoesa-writer subagent. Use
  when: (1) User wants to write an esa article based on what was discussed, (2) User says 'write esa
  article', 'esa記事', 'esaに書いて', 'articlify for esa'. This skill gathers context from the
  conversation, creates a detailed writing brief, and delegates to the writer subagent.

Articlify for esa

Convert the current conversation into an esa article by crafting a detailed writing brief and delegating to the zudoesa-writer subagent.

Workflow

Step 1: Gather context from conversation

Review the conversation history and identify:

  • •What topic was discussed
  • •What was tried (approaches A, B, C...)
  • •What worked and what didn't
  • •Key technical details, code snippets, commands
  • •The conclusion or final approach taken
  • •Any opinions or insights expressed
  • •Images: Any images attached to the conversation (screenshots, diagrams, etc.)

Step 1.5: Handle images (if any)

If images were provided in the conversation (attached screenshots, diagrams, etc.):

  1. •Determine the article slug from the topic (e.g., 20260209-package-json-organization)
  2. •Create the image directory in the esa repo:
    code
    mkdir -p /Users/takazudo/repos/work/takazudo-esa-writing/doc/static/img/articles/YYYYMMDD-slug/
  3. •Copy each image to that directory with a descriptive filename:
    code
    cp /path/to/source/image.png /Users/takazudo/repos/work/takazudo-esa-writing/doc/static/img/articles/YYYYMMDD-slug/descriptive-name.png
  4. •Record the image paths for the writing brief. The markdown reference format is:
    code
    ![alt text](/img/articles/YYYYMMDD-slug/descriptive-name.png)

Step 2: Craft the writing brief

Create a detailed, self-contained prompt that the writer subagent can use without any conversation context. The brief must include:

  1. •Article topic: Clear one-line description
  2. •Background: Why this was done, what motivated it
  3. •Story arc: The journey (tried X, it failed because Y, then tried Z which worked)
  4. •Technical details: Specific code, commands, configurations, error messages
  5. •Key points to cover: Bullet list of must-include content
  6. •Images: If images were copied in Step 1.5, list each with its markdown path and a description of what it shows and where it should be placed in the article
  7. •Conclusion: What was the outcome, what was learned
  8. •Tone guidance: Any specific angle or framing (if applicable)

The brief should be written so that someone with zero context could write the full article from it alone.

Step 3: Delegate to subagent

Use the Task tool to spawn the zudoesa-writer subagent:

code
Task tool:
  subagent_type: zudoesa-writer
  prompt: [the detailed writing brief from Step 2]

The subagent will:

  • •Read the repo's writing style guides
  • •Write the article in Japanese following esa conventions
  • •Save to the articles directory
  • •Run formatting checks

Step 4: Report back

After the subagent completes, report:

  • •The file path of the created article
  • •A brief summary of what was written

Important Notes

  • •The writing brief is the ONLY context the subagent receives - make it thorough
  • •Include actual code snippets, error messages, and command outputs in the brief
  • •If the conversation involved multiple topics, ask the user which one to articlify
  • •Images must be copied BEFORE delegating - the subagent cannot see conversation images
  • •Include the full markdown image reference paths in the brief so the subagent can embed them
  • •$ARGUMENTS can provide additional guidance on focus or angle