Agent skill

Illustration One Line

by MengTo in MengTo/Skills

Draws original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design and coding work.

MITAuto-check passedMarketing & SEO

Install Illustration One Line

skills CLI
$ npx skills add MengTo/Skills --skill illustration-one-line -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MengTo/Skills illustration-one-line --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MengTo/Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agent-skills/illustration/illustration-one-line .claude/skills/illustration-one-line && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
illustration-one-line
GitHub stars
6.7k
Token cost
~5k tokens
SKILL.md length
2,951 words
Files
13 (incl. scripts, references)
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Draws original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design and coding work.

  • Works in 10 steps: Brief. Name the subject and the one… → Pose. Sketch the skeleton as numbers:… → Write a generator (card.mjs) that… → …
  • Asked for one-line
  • SKILL.md covers The look in one sentence, Palette, Line and fill and Characters, plus 7 more sections
  • Runs JavaScript scripts from its folder; calls node

What it does

Illustration One Line is an agent skill from MengTo/Skills. Draws original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design and coding work. One continuous uniform black line (2.3 px at 480 wide) loops and doubles back to draw the whole figure. Flat coral, periwinkle and white patches sit behind the line, wobbly and deliberately knocked 2–6 px out of register like a misprinted riso. Tops carry coral stripe lines, and there is no ground plane, only a squiggle, a curl or a few speed strokes, all on warm beige paper. Covers the…

Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including scripts and reference files (for example `agents/openai.yaml`, `demo/PROMPT.md` and `references/craft.md`).

It sits in Marketing & SEO, covering Product launch strategy. It works with Stripe. The repository describes itself as: Agent skills for designers and builders using Codex, Claude, Cursor, and other AI coding agents. The licence is MIT.

When your agent uses it

  • Asked for one-line
  • Continuous-line
  • Playful doodle illustrations
  • For empty states

Example prompts

  • “Use the illustration-one-line skill to draw original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design…”
  • “/illustration-one-line”

Requirements

  • Node.js

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Brief. Name the subject and the one action that shows it. Pick 1–3 props that say the subject without text.
  2. Pose. Sketch the skeleton as numbers: hip, shoulders, head centre, and centrelines for each limb (4–5 points each) with widths. Choose the…
  3. Write a generator (card.mjs) that imports scripts/oneline.mjs by absolute path. Build tubes, place hands and shoes, and write ONE route…
  4. Hands on paper. For each hand write LEFT or RIGHT, PALM or BACK and the finger direction, then the thumb side (references/craft.md). Pick…
  5. Colour. Add patches (offset, wobble, distinct seeds), stripes, masks.
  6. Render: node scripts/render.mjs card.svg card.png.
  7. Sheet: node scripts/render.mjs --sheet sheet.png examples/flow-state.svg examples/hackathon-sprint.svg examples/juggling-tasks.svg…
  8. Zoom hands, head, feet, every joint where a limb meets a hand or shoe, and every crossing: node scripts/render.mjs card.svg z.png --zoom…
  9. Critique on the five criteria in references/craft.md and the Verify list. Fix, re-render, re-sheet. Four or more rounds is normal.
  10. Lint: node scripts/lint.mjs card.svg --prefix sd- --palette style.json.

What it can do on your machine

Read from SKILL.md and the folder at commit 83a47fe. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Illustration One Line loads about 5k tokens when it runs, and up to ~7.6k if it reads all its reference files. Until then it costs about 226 tokens; SKILL.md has 2,951 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~226
When it runs · the whole SKILL.md, loaded when a task matches
~5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from MengTo/Skills at commit 83a47fe, republished under its MIT licence (© MengTo). 2,951 words, ~4,962 tokens.

Download SKILL.mdSave it as .claude/skills/illustration-one-line/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
illustration-one-line
description
Draws original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design and coding work. One continuous uniform black line (2.3 px at 480 wide) loops and doubles back to draw the whole figure. Flat coral, periwinkle and white patches sit behind the line, wobbly and deliberately knocked 2–6 px out of register like a misprinted riso. Tops carry coral stripe lines, and there is no ground plane, only a squiggle, a curl or a few speed strokes, all on warm beige paper. Covers the palette, a route-building toolkit (tube limbs, hand and shoe loops, wobble patches, masks), poses, composition and a render-critique loop. Use when asked for one-line, single-line, continuous-line, misregistered, riso-style or playful doodle illustrations, for empty states, onboarding, 404 pages, blog headers, feature spots, launch announcements or marketing cards.

Illustration: One-line

A loose, energetic style: a figure in mid-action drawn as one long wandering black line, with colour laid underneath as offset patches, as if a second print colour slipped. It suits upbeat product moments (launches, sprints, flow, celebrations) where an interior scene would be too heavy. Use illustration-halftone-line for black open line with dot-screen tones and no colour. Use illustration-ink-sketch for a wobbly brush outline around a cute critter. Use illustration-two-colour-brush for thick brush outlines with solid black shapes and one mint ink.

Extracted from a set of 42 original design-and-coding cards in 14 styles; the three cards in examples/ are this style's shipped cards.

The look in one sentence

One continuous black line draws the whole figure, and flat coral, periwinkle and white patches sit behind it, deliberately knocked 2–6 px out of register.

Palette

Measured from the three examples (1x renders): paper 87–89% of the pixels, ink about 2%, white patches about 3%, periwinkle 2.3–3.7%, coral 0.8–2.8%.

RoleHexWhere it goes
Paper#ece7dafull-bleed background rect, square, no rx
Ink#1d1b1athe one line, every prop line, code glyphs, speed strokes, the eye, solid dots
Coral#f2846eface and hand patches, stripe lines on tops, a sun, one accent patch per prop, code dashes
Periwinkle#8790f4trousers, hair, screens and props, ground patches, code dashes
White#fffffftops and sleeves, shoes, cups, clouds, ground patches
  • Masks use #fff and #000 inside <mask> only; they never show.
  • Never: other colours, gradients, opacity, outlines on patches, grey, a second ink colour, black fills larger than a 1.9 px dot.
  • Coral is skin and small accents; it never fills trousers or a whole top. Periwinkle never fills skin.

Line and fill

  • One ink group: <g id="xx-ink" fill="none" stroke="#1d1b1a" stroke-width="2.3" stroke-linecap="round" stroke-linejoin="round">. Every ink path inherits it.
  • Weights at 480 wide: 2.3 for the figure line and props; 2.0–2.1 for a long motion path or clock hands; 1.8 for code glyphs (</>); coral stripe lines 1.9; coded colour dashes 2.3.
  • The figure is ONE path (id="xx-figure") of smooth cubic segments, 1-decimal coordinates. Separate short strokes are allowed only for the eye, a hem or cuff, and props. Each prop is its own single wandering line too.
  • Smoothness comes from the spline: every route point is [x, y] or [x, y, k] with tension k (1 smooth, 0.4–0.6 soft corner at elbows, knees and collars, 0 sharp for glyph corners).
  • Colour is never bounded by the line. Patches are separate closed blobs drawn first, in <g id="xx-patches">, then stripes and dashes in <g id="xx-accents">, then the ink on top.
  • Off-register: offset each patch 2–6 px from the shape it colours (T(pts, dx, dy)), and wobble its edge (wobble, amp 0.8–1.5 for hands and faces, 1.4–2.4 for limbs, 2.2–3 for big areas). Use a different integer seed per patch. Let patches fall short of one side and spill past the other.
  • Stripes: 3–5 coral lines across a top, following the body's curve, stopping 2–4 px short of the contour, 1.9 wide. Sleeves get 1–2 short stripes.
  • Masks: where the line passes behind something (an arm over a laptop, a fist round a baton, a motion path behind a juggled object), knock it out with a <mask> holding the front shape's silhouette in black. Add a black stroke of 2–10 px to open a gap. C.mask() builds it.

Characters

  • Proportions: figures 190–240 px tall in action (53–67% of the card height). The head is 41–48 px tall, so about 1:5. Limbs are tubes: arms 18–21 px wide at the shoulder tapering to 8.6–9.5 at the wrist; legs 27–28 at the hip to 12–13.5 at the ankle.
  • Head: a profile facing the direction of travel, 41–48 px tall. Route it in either direction. Up the throat into FACE_R (chin, lips, nose, brow as soft corners), over the crown and hair, down a ROUND back of the skull to the nape. Or the reverse, rev(FACE_R). The EAR_R C-loop is optional. Drop it if it doesn't read at 8x: an ear plus a flat hairline made a test head read as a helmet. The eye is a separate short closed-lid arc (EYE_R) and there is no mouth stroke (the profile carries the smile). A coral face patch covers the front half of the face, offset 1–2 px toward the profile, and leaves the back of the head bare paper.
  • Hair: a periwinkle patch behind the hair outline (ponytail, bun loop, short crop), or curly hair drawn as trochoid loops (curls(), r 3–3.5, 4–5 loops) with no patch.
  • Torso: there is no separate torso outline. The back contour, the arm sides and the belly are all parts of the route. A white top patch covers the chest, offset −4, −3, plus white sleeve patches built with blob() from the arm centreline.
  • Limbs: build each with tube(centreline, widths) and route DOWN one side, round the hand or shoe, and back UP the other side. Put tension 0.4–0.6 on the elbow or knee point so it bends crisply. Keep a gripping wrist 45–60 px from its shoulder: a handle 48 px from the shoulder folded a test arm into a chicken wing (forearm 15 px, upper arm 33).
  • Joints with hands and shoes: check where a limb side meets a placed shape at 8x. If the shape's first point sits behind the limb edge, the line hooks back on itself. Drop that point (shape.slice(1)) or shift the shape 3–4 px.
  • Sitting astride or on a prop (a rocket, a stool, a chair): draw only the near leg, in front of the prop, and mask the prop's line with the figure's own route used as a silhouette (C.mask('m-rider', [[route, 5]])). For that, start and end the route at the same place, such as the heel.
  • Hands are small loose loops, 19–27 px long (local shapes × 1.1–1.3), with a coral patch behind, offset 2–3 px. Shapes in the toolkit: HAND.mitten (swinging, thumb notch), HAND.fist (round a handle, knuckle bumps), HAND.tray (open palm carrying something), HAND.open (catching, thumb hooked out), spreadHand() (waving, four separate finger loops and a thumb), CLAMP (fist from the side gripping an edge). Never a plain oval.
  • Handedness: decide LEFT or RIGHT, PALM or BACK and the finger direction with the table in references/craft.md, then flip the shape (place(..., flip)) so its thumb lobe lands on that side. The comment above each shape in scripts/oneline.mjs says which side its thumb is on.
  • Feet: SHOE loops, 30–35 px long (× 1.25–1.3), with a white patch, offset 3–4 px. A small heel loop is allowed on one shoe.
  • Loops: 2–4 cursive loops per figure, radius 3–5, at a waistband, a heel, a knee, a bun or the end of a ponytail (loopAt(), cornerLoop()). More reads as scribble. A loop in the middle of a leg reads as a mistake.
  • Poses: big and diagonal, never standing still. Leaping between two objects, sprinting with the body pitched 11° forward, balancing on one leg while juggling. Lean the upper body by rotating its points about the hips (rot()) before routing.

Decor and props

  • 1–3 context props, each one wandering line plus one offset patch: braces { }, a laptop with </>, a stopwatch, a coffee cup, a bug, a sun drawn as a loading ring. Props tie into the motion: a squiggle trails into a stopwatch, one looping path threads the juggled objects.
  • Motion: 3 parallel speed strokes behind the figure (26–52 px long, 13–16 apart), or a squiggle trail with one loop.
  • Ground: no ground plane. Use a short squiggle with a loop under the planted foot (90–110 px wide, 1 px under the sole) with a white or periwinkle patch, or nothing when the figure is airborne.
  • Code: </> glyphs in 1.8 px ink on a screen or baton, and "code" as rows of coral and periwinkle squiggle dashes (squig(), 2.3 px).
  • Never: text, UI panels, sparkles, confetti, outlined boxes, a horizon line, shadows.

Composition

  • Card: <rect id="xx-paper" x="0" y="0" width="480" height="360" fill="#ece7da"/> first. Then <defs> (masks), patches, accents, ink.
  • The whole drawing spans about 245–377 px wide and 240–284 px tall, centred. Keep 30–40 px clear at every edge (top ≥ 36).
  • The figure carries the card: 190–240 px tall, placed so its direction of travel has more room ahead than behind. Props sit in the open space it moves toward or past.
  • Density: sparse. Paper 86–89% of the pixels; about 12–17 patches and 15–40 ink paths in total.
  • A big prop (rocket, board) gets a patch covering 60–75% of it, offset 4–6 px. A patch filling the whole prop reads as a solid white shape and outweighs the figure. Keep the figure 190 px or taller next to a big prop: scale the upper body about the hip if it looks small.
  • Build in a local frame and map it to the card with one function: makeCard('sd-', { map: pts => … }) applies it to every line, patch, accent, mask and dot (scale 1.05–1.1 about a centre, plus a shift). To face the other way, mirror x in the map (map: pts => mirrorX(pts, 240)), and draw </> glyphs and any lettering with C.raw.line(...), which skips the map, so they don't mirror.

Techniques

1. The toolkit. scripts/oneline.mjs (no dependencies, seeded) holds the curve maths and the card assembly: smooth, tube, blob, wobble, place, T, rev, rot, lowest, curls, squig, loopAt, cornerLoop, arc, the local shapes (HAND.*, spreadHand(), CLAMP, SHOE, FACE_R, EYE_R, EAR_R) and makeCard(prefix, { map }) with line, accent, patch, mask, dot (all mapped), raw.* (the same, unmapped), dots (debug) and svg(debug, ariaLabel). Patches and lines share one id namespace, so name patches after their colour (porthole-peri, shoe-white): a test card failed lint with two porthole ids. Run node scripts/oneline.mjs --demo /abs/work/demo.svg from the skill folder (write it into your work folder, not the skill) and render it: an arm with a mitten, a leg with a shoe on a ground squiggle, a profile head, patches, a stripe and code dashes.

2. A limb route. Down the R side, round the hand, back up the L side:

js
import { makeCard, tube, blob, place, rev, T, ang, HAND, PERI, WHITE, CORAL } from '/abs/path/to/illustration-one-line/scripts/oneline.mjs';
const C = makeCard('sd-');
const arm = [[150, 120], [170, 132], [190, 146, 0.5], [212, 136], [232, 124]];   // shoulder, elbow (k 0.5), wrist
const W = [18, 16, 13.5, 11, 9], a = tube(arm, W);
const hand = place(HAND.mitten, arm[4], ang(arm[3], arm[4]), 1.2);           // +y wrist corner first
C.line('arm', [...a.R, ...hand, ...rev(a.L)]);                               // in a figure, splice this into the one route
C.patch('sleeve', T(blob(arm.slice(0, 3), W.slice(0, 3), 1.05), 3, -3), WHITE, 1.4, 4);
C.patch('hand', T(place([[0, -5], [12, -5], [17, 0], [12, 7], [2, 6]], arm[4], ang(arm[3], arm[4]), 1.2), 2, -3), CORAL, 0.8, 5);

Local shapes run from their +y wrist corner, round the tip, to the −y corner. Going down a limb's L side instead, use rev(shape) or flip = true.

3. Knock-out masks. const m = C.mask('m-arm', [[armSilhouettePts, 2]]); C.line('laptop', lapPts, m); hides the laptop's line under the arm. For a path that threads several objects, pass each object's silhouette with stroke 9–10 so the path stops short of them with a gap.

4. Ground the planted foot. const sole = lowest(route); then draw the squiggle at sole[1] + 1.1 with T(pts, sole[0], sole[1] + 1.1). A foot meant to stand must sit on it, not float above.

5. A whole-figure route order (the sprinter in examples/hackathon-sprint.svg, authored facing right). Every contour is visited once: ground squiggle behind → planted shoe top → front of the trailing leg up → crotch → lead leg underside → lead shoe → shin front → knee → thigh top into the belly → far arm underside → fist → far arm top → shoulder → short neck → FACE_R → crown → ponytail → back of the skull → ear → nape → near arm top → mitten → near arm underside → armpit → back → waistband loop → seat → back of the trailing leg → heel loop → sole → toe → ground squiggle ahead. A seated rider runs heel → calf → thigh underside → seat → back → raised arm → hand → nape → skull → bun loop → rev(FACE_R) → throat → near arm → fist → belly → thigh top → shin → shoe → back to the heel.

6. Patch recipe (offsets T(dx, dy), wobble amp, from the examples' generators). Top: the chest outline, (−4, −3), amp 2.4–2.6. Sleeves: blob(arm.slice(0, 3), W, 0.95–1.05), (±2–3, −3), amp 1.4–1.6. Trousers: blob(leg, W, 1.0), (5, 3), amp 2.2–2.4. Face: head-local [[6,-12],[16,-8],[22,2],[19,13],[9,15],[5,2]], (2, −1), amp 1.1–1.5. Hair: (−3, −2), amp 1.2–1.6. Hands: a 5–6 point blob of the hand, (2–3, ±2–3), amp 0.8–1.2. Shoes: [[-6,-2],[10,-3],[22,3],[22,10],[4,11],[-7,8]] through the shoe's own place(), (3–4, 2–3), amp 1.2. Props: (3–5, ±3), amp 1–1.8. Every seed different.

Show full SKILL.md (997 more words)Show less

Failure modes

  • Hackathon Sprint shipped at 6.5. Judges named the head shape, the planted back foot and a weak hackathon cue. On the card, the skull is small next to the ponytail, the planted loop shoe reads as a blob, and a </> baton plus a stopwatch don't say "hackathon". Don't copy that card's head or back foot, and give the subject a prop that names it.
  • Mitten blobs for hands. The first Flow State hands were ovals. Use a shape with a thumb lobe or separate fingers, and a coral patch behind it.
  • A loop on the knee reads as a mistake. The first Flow State legs had a loop mid-leg and crossing lines. Put loops at ends (heel, waistband, hair) and taper legs from hip to ankle with a clean knee bend.
  • The colour fits the line exactly. Then it is an ordinary flat fill and the print-slip look is gone. Offset every patch 2–6 px, let it spill on one side and fall short on the other.
  • Patches read as stains. Wobble amp above 3, or blobs with no relation to a body part. Keep amp 0.8–3 and one patch per part.
  • It became a normal line drawing. Too many separate strokes (a torso outline, each finger, a separate face). Keep the figure one route; only the eye, hems and props are separate.
  • Line crossings behind objects. The route passes under an arm or a held object and both lines show. Mask the hidden part.
  • Weight drift. A 1.4 px or 3 px stroke anywhere breaks the set. Use 2.3 for ink, 1.8 for glyphs and 1.9 for stripes.
  • Floating feet. A planted foot hovering above its squiggle. Measure the sole with lowest() and place the squiggle 1.1 px under it.
  • Duplicate ids. A patch and a line given the same name. Suffix every patch with its colour.
  • Hooks at joints and a chicken-wing arm. See Characters. Both showed up in the self-test card and only at 8x zoom.

Examples

  • examples/flow-state.svg: "Flow State". A leap with one arm flung back (spreadHand-style open hand) and the near arm clamping a laptop (CLAMP, masked). Curly hair from curls(), headphones, two code braces drawn as single strokes with white patches, code dashes, a sun as a loading ring, speed strokes, a trail squiggle.
  • examples/hackathon-sprint.svg: "Hackathon Sprint". A sprint facing left: the figure is authored facing right and mirrored in G, with </> drawn in card space. A fist round a baton (masked), a swinging mitten, a ponytail, a waistband loop, a stopwatch tied into a squiggle, speed strokes. The weakest card: see Failure modes.
  • examples/juggling-tasks.svg: "Juggling Tasks". Balancing on one leg with a tray hand under a laptop and an open hand just releasing. One looping motion path threads a cup and a bug (masked with stroke 9–10), a short ground squiggle with a periwinkle patch, a bun loop.

Workflow

Run every command from this skill's folder. Card paths can be absolute.

  1. Brief. Name the subject and the one action that shows it. Pick 1–3 props that say the subject without text.
  2. Pose. Sketch the skeleton as numbers: hip, shoulders, head centre, and centrelines for each limb (4–5 points each) with widths. Choose the facing and the lean. Choose an id prefix (sd-).
  3. Write a generator (card.mjs) that imports scripts/oneline.mjs by absolute path. Build tubes, place hands and shoes, and write ONE route for the figure: start at a free end (a hand, a foot or a ground squiggle), go round every limb, and end at another free end. Render with C.svg(true) to see numbered route points while you work.
  4. Hands on paper. For each hand write LEFT or RIGHT, PALM or BACK and the finger direction, then the thumb side (references/craft.md). Pick the shape and the flip.
  5. Colour. Add patches (offset, wobble, distinct seeds), stripes, masks.
  6. Render: node scripts/render.mjs card.svg card.png.
  7. Sheet: node scripts/render.mjs --sheet sheet.png examples/flow-state.svg examples/hackathon-sprint.svg examples/juggling-tasks.svg card.svg. Ask "same hand, same set?": line weight, how loose, patch offsets, density, paper share.
  8. Zoom hands, head, feet, every joint where a limb meets a hand or shoe, and every crossing: node scripts/render.mjs card.svg z.png --zoom x,y,w,h --scale 8. Do the thumb proof from references/craft.md. The hands live inside the one route, so you can't recolour them. Instead, in a throwaway copy, put a red circle (r 2.2) on the thumb tip and a blue one on the index tip, both mapped through the same place() call, then delete the copy.
  9. Critique on the five criteria in references/craft.md and the Verify list. Fix, re-render, re-sheet. Four or more rounds is normal.
  10. Lint: node scripts/lint.mjs card.svg --prefix sd- --palette style.json.

Verify

  • Paper rect #ece7da full-bleed, no rx; only paper, ink, coral, periwinkle and white appear.
  • The figure is one <path>; apart from it there are only the eye, hems, props, speed strokes and squiggles.
  • Every ink stroke is 2.3 (glyphs 1.8, a long motion path 2.0–2.1); stripes 1.9 coral; caps and joins round.
  • No patch matches its contour: each is offset 2–6 px and wobbly, and no two share a seed.
  • The face patch is coral, covers the front of the face only, and the eye is a closed-lid arc.
  • Hands have a thumb lobe or separate fingers, a coral patch, and the thumb on the correct side (thumb proof done).
  • 2–4 loops at ends (hair, heel, waistband, a knee at most once); no loop mid-limb.
  • Lines that pass behind an arm or object are masked; no accidental crossings at 8x.
  • The pose is a diagonal action; the planted foot sits 1 px on its squiggle, or the figure is clearly airborne.
  • 30–40 px clear at every edge; paper looks as dominant as on the examples (they measure 87–89%); 12–17 patches; a big prop's patch covers only 60–75% of it.
  • The subject reads at 1x from the action and props, with no text.
  • Patch ids carry a colour suffix, and lint.mjs --palette style.json passes with no ERROR or WARN.

© MengTo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (scripts, references) in agent-skills/illustration/illustration-one-line of MengTo/Skills.

  • SKILL.md
  • agents/openai.yaml
  • demo/PROMPT.md
  • demo/index.html
  • demo/preview.jpg
  • examples/flow-state.svg
  • examples/hackathon-sprint.svg
  • examples/juggling-tasks.svg
  • references/craft.md
  • scripts/lint.mjs
  • scripts/oneline.mjs
  • scripts/render.mjs
  • style.json

Open the folder on GitHubat commit 83a47fe

Compare with similar skills

Illustration One Line next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Illustration One Line compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Illustration One Line this skillMengTo/Skills6.7k—~5kAutomated safety check: PassMIT
Mvp Launchooiyeefei/ccc495—~1.1kAutomated safety check: PassMIT
Technical Launch Plannerjamesrochabrun/skills2161 repos~3.8kAutomated safety check: PassMIT
Getxapi ConnectLeoYeAI/openclaw-marketing-skills1k1 repos~715Automated safety check: PassCustom licence
ProducthuntReScienceLab/opc-skills1.8k—~467Automated safety check: PassApache-2.0
Micro SaaS Launchernicepkg/auto-company1958 repos~1.3kAutomated safety check: PassNone

Similar skills

  • Mvp Launch

    ooiyeefei/ccc

    Web app MVP launch checklist knowledge. An agent skill from ooiyeefei/ccc.

    495 GitHub stars~1.1k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed
  • Technical Launch Planner

    jamesrochabrun/skills

    Plan and execute technical product launches for developer tools, APIs, and technical products.

    216 GitHub starsUsed in 1 repo~3.8k tokens
    Marketing & SEOAuto-check passed
  • Getxapi Connect

    LeoYeAI/openclaw-marketing-skills

    Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.

    1k GitHub starsUsed in 1 repo~715 tokens
    Marketing & SEOAuto-check passed
  • Producthunt

    ReScienceLab/opc-skills

    Search and retrieve content from Product Hunt. An agent skill from ReScienceLab/opc-skills.

    1.8k GitHub stars~467 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Micro SaaS Launcher

    nicepkg/auto-company

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software.

    195 GitHub starsUsed in 8 repos~1.3k tokens
    Marketing & SEOAuto-check passed
  • Directory Submissions

    coreyhaines31/marketingskills

    When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery.

    54k GitHub starsUsed in 2 repos~6.7k tokens
    Marketing & SEOAuto-check passed

More from MengTo/Skills

All 39 skills in this repo
  • Draws hand-authored SVG spot illustrations in a bold pop-geometric style for design and coding scenes.

    6.7k GitHub stars~5.1k tokensUpdated 5 days ago
    Auto-check passed
  • Draws a slim, long-limbed character acting out one coding or design moment as an outline-free flat SVG card, in a fixed measured palette with confetti and no ground line.

    6.7k GitHub stars~4.9k tokensUpdated 5 days ago
    Auto-check passed
  • Draws flat vector spot illustrations of lanky people doing design and coding things, with solid black as a main fill, for empty states, onboarding and error pages.

    6.7k GitHub stars~5.2k tokensUpdated 5 days ago
    Auto-check passed
  • Draws cozy animal scenes as hand-authored 480x360 SVG cards in a grainy, risograph-like gouache style on hot pink, for empty states, headers and marketing cards.

    6.7k GitHub stars~5.2k tokensUpdated 5 days ago
    Auto-check passed
  • Draws hand-authored SVG spot illustrations in a halftone line style for design and coding scenes.

    6.7k GitHub stars~4.7k tokensUpdated 5 days ago
    Auto-check passed
  • Draws hand-inked cartoon critters and living objects as SVG cards (480x360), each acting out a coding or design idea.

    6.7k GitHub stars~4.6k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Illustration One Line

What does Illustration One Line do?

Draws original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design and coding work. Illustration One Line is an agent skill from MengTo/Skills. Draws original hand-written SVG spot illustrations in the One-line style, joyful action figures doing design and coding work.

When should I use Illustration One Line?

Illustration One Line fits situations like: asked for one-line; continuous-line; playful doodle illustrations; for empty states.

How do I install Illustration One Line in Claude Code?

Run `npx skills add MengTo/Skills --skill illustration-one-line -a claude-code`. Or copy the skill folder (agent-skills/illustration/illustration-one-line in MengTo/Skills) into .claude/skills/illustration-one-line in your project. Claude Code loads it when a task matches its description.

How do I install Illustration One Line in Codex?

Run `npx skills add MengTo/Skills --skill illustration-one-line -a codex`. Or copy the skill folder (agent-skills/illustration/illustration-one-line in MengTo/Skills) into .agents/skills/illustration-one-line in your project. Codex loads it when a task matches its description.

Can I use Illustration One Line in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MengTo/Skills --skill illustration-one-line -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/illustration-one-line, .gemini/skills/illustration-one-line, .github/skills/illustration-one-line and .opencode/skills/illustration-one-line in your project.

What does Illustration One Line need to run?

Going by SKILL.md and its folder, Illustration One Line needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node). Our summary lists: Node.js.

Does Illustration One Line access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Illustration One Line safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Illustration One Line use?

Illustration One Line is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Illustration One Line use?

About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.6k tokens, read only when the agent opens those files.

What are the alternatives to Illustration One Line?

Skills that share tags, products or a category with Illustration One Line: Mvp Launch (ooiyeefei/ccc, 495 stars), Technical Launch Planner (jamesrochabrun/skills, 216 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars) and Producthunt (ReScienceLab/opc-skills, 1.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Illustration One Line?

MengTo (a GitHub user) maintains it in MengTo/Skills, which has 6,694 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.

Source: MengTo/Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.