agentleFS
sandochesandoche/agentic-code-unpacked/skills/xkcd/SKILL.md

xkcd

Skill1 starsChanged 4 days agoMITView on GitHub

Explain source behavior through original stick-figure comics for a PR, branch, codebase, or selected code; requires an image-generation tool.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the bundled source and delivery guide, then capture the target using this installed skill's runtime.

    line 24
  2. Distinctive:

    Follow the comic workflow and storyboard schema.

    line 25
  3. Distinctive:

    Use an available image-generation tool to generate each complete comic, including its dialogue and labels.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Code Comics

Explain meaningful behavior, tricky invariants, and call chains through original black-and-white stick-figure comics with source references and an accessible transcript.

Use

/xkcd pr https://github.com/owner/repo/pull/123 --draft
/xkcd docs billing --files src/billing.ts
/xkcd branch feature/login --count 2 --panels 3

Accept natural language and the harness's native invocation syntax. Interpret PR URLs as pr, named branches as branch, selected files or pasted code as a named docs target, and the whole current repository as codebase.

Generate

  1. Read the bundled source and delivery guide, then capture the target using this installed skill's runtime. Resolve script paths from the skill folder.
  2. Follow the comic workflow and storyboard schema. Choose distinct topics grounded in actual source behavior.
  3. Use an available image-generation tool to generate each complete comic, including its dialogue and labels. Inspect the artwork, render the offline gallery and PNG exports, and return usable artifact paths.

No particular image provider is required. If image generation is unavailable, preserve the storyboard and prompts and report the result as incomplete; do not claim a complete comic. Dependencies and Chromium are set up when needed. The agent handles scripts and JSON. Use direct source when graph tools are unavailable. PR comments require requested live delivery; never publish incomplete artwork, and honor --draft.

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.