agentleFS
Sign inStart free
dglogan42dglogan42/Claude-Skills/the-boba-side-cartoon/SKILL.md

the-boba-side-cartoon

Skill0 starsChanged 19 days agoLicence not identifiedView on GitHub

Write and render "The Boba Side" — Bubble Tea News's single-panel gag cartoon slot, staged as an anime/manga-style gag (otaku-culture and bubble-tea-meme sensibilities applied to original characters — chibi, shoujo, seinen, shonen, bishoujo sub-styles) and actually rendered with ImageMagick's `-draw`/inline-MVG primitives to PNG — simple schematic raster shapes carrying anime-style cues (screentone-dot hatching, speed lines, sparkle effects, named spot colors), not genuine polished anime illustration, since there's no image-generation model in this workflow. ImageMagick is the primary renderer, embedded via `<img>` (its SVG *writer* is confirmed broken for multi-shape colored output — geometry survives but fill/stroke colors and all but the last shape are dropped — so PNG is the only reliable output here, unlike this library's other pycairo/SkiaSharp renderers). A compiled C + Win32 GDI path is also verified working as an alternative renderer, though plain GDI can't do bezier curves (straight-edge/circle primitives only). A third verified path — hand-authored SVG (not ImageMagick's broken SVG *writer*) rasterized via Inkscape's CLI (`--export-png-antialias=3`) — sidesteps the SVG-writer bug entirely and gives cleaner linework/screentone than ImageMagick's `-draw`; used for Issue 8's panel. Reuses hard-won lessons from this paper's own rollout: give large fill shapes internal detail so they read at real print size, and watch the 2-page print budget. Use when assembling a Bubble Tea News issue that wants a cartoon slot, or whenever the user wants a one-panel anime-style gag actually drawn. This is a seed skill: sparse by design, built from one format and three verified render methods; expand with more gag premises and meme formats as they come up. Includes an artist-craft pass: artistic question, style pillars, name-before-draw panel plan, and a critique pass before print.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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