Skip to content
cccskills
FreePublished on GitHub

article-illustrations

Turn article ideas into hand-drawn, 16:9 illustrations featuring Grav, a floating character. Plan image placement and visual metaphors, then generate white-background sketches with sparse English labels and review their consistency.

OriginalShow the original description

Generate hand-drawn 16:9 article illustrations with the Grav character IP, sparse annotations, and absurd but clear visual metaphors.

See how to install

Good for

  • Plan illustrations for a blog post
  • Explain an abstract concept through a visual metaphor
  • Keep illustration styles consistent across articles
  • Revise a sketch so Grav drives the action

Files included (1)

  • SKILL.md6.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Article Illustrations — Grav Hand-Drawn Style

Overview

Generate 16:9 landscape hand-drawn illustrations for articles, blog posts, and technical content. Each illustration captures one cognitive anchor point from an article and turns it into a clean, absurd, memorable whiteboard-sketch explanation.

The skill uses a recurring character IP called Grav: a small, round, always-floating figure with dot eyes and a thin antenna. Grav participates in the core action of every illustration — never just decoration.

Repository: vipin-si/article-illustrations

When to Use This Skill

  • Use when writing articles, blog posts, or documentation that need inline illustrations
  • Use when you want to turn abstract concepts into concrete visual metaphors
  • Use when you want a consistent visual language across multiple articles
  • Use when you need hand-drawn explanation sketches, not PPT infographics

How It Works

Step 1: Digest the Article

Read the article and identify cognitive anchor points — core judgments, turning points, input/output loops, before/after contrasts, and common pitfalls. Don't distribute illustrations evenly; prioritize moments that benefit from visual explanation.

Step 2: Plan a Shot List

For each illustration, define:

  • Placement: After which section
  • Theme: What this image is about
  • Core Meaning: The one idea it conveys
  • Structure Type: One of 8 composition patterns (Workflow, System Closeup, Before/After, Role States, Conceptual Metaphor, Layered Method, Map Route, Mini Comic)
  • Grav's Action: What Grav is doing in the scene
  • Annotation Labels: 3–5 short English labels

Step 3: Generate Images

Use the generate_image tool with the built-in prompt template. Each image follows strict style rules:

  • Pure white background, no textures
  • Black hand-drawn line art with slight wobble
  • Sparse red/orange/blue handwritten annotations
  • Grav always floating (never touching surfaces)
  • One core idea per image
  • 40–60% canvas usage, 35%+ whitespace

Step 4: QA Check

Verify each image against the QA checklist: correct format, Grav present and active, original metaphor, clean composition, sparse annotations, correct color usage.

Examples

Example 1: Plan illustrations for an article

Analyze this article and create a shot list of 5 illustrations.
Don't generate images yet — just plan which cognitive anchor points
deserve illustrations and what each image should convey.

<paste article>

Example 2: Generate illustrations directly

Generate 4 Grav-style illustrations for this article.
Requirements: 16:9 landscape, pure white background, black hand-drawn
line art, sparse red/orange/blue English annotations.

<paste article>

Example 3: Single concept illustration

Generate one 16:9 illustration for this concept:
"Trust isn't declared — it's built one piece of evidence at a time."
Grav must perform the core action. Maximum 5 annotation labels.

Example 4: Iterate on a result

This illustration is on the right track, but Grav feels like decoration.
Keep the core meaning but regenerate: make Grav the one actually
driving the structure.

Visual Style

ElementRule
BackgroundPure white — no cream, texture, gradients, or shadows
Line artBlack, hand-drawn, slightly wobbly, not mechanical
WhitespaceMain subject 40–60% of canvas, 35%+ empty space
AnnotationsHandwritten English, 2–5 words each, max 5–8 per image
Color: BlackMain line art, characters, structures, objects
Color: RedKey highlights, problems, warnings, results
Color: OrangeMain flow, paths, arrows, direction
Color: BlueSupplementary notes, feedback, system state
ProhibitedGreen, purple, yellow, pink, gradients, drop shadows, 3D, realistic UI

Character: Grav

  • Small round body (pebble/potato shape)
  • Two dot eyes (slightly asymmetric)
  • One thin bent antenna with tiny circle tip
  • Thin stick legs that dangle without touching surfaces
  • Always hovering — visible gap between Grav and any surface
  • Expression: calm, focused, deadpan
  • Role: active participant in the system, never decoration

Best Practices

  • ✅ Start with a shot list before generating images
  • ✅ Invent a new metaphor for every illustration — never reuse compositions
  • ✅ Make Grav the action protagonist, not a bystander
  • ✅ Keep it absurd but structurally clear
  • ✅ Use color sparingly — when in doubt, use black
  • ❌ Don't make PPT infographics or formal flowcharts
  • ❌ Don't add title bars or decorative frames
  • ❌ Don't let Grav touch the ground or stand on surfaces
  • ❌ Don't make Grav cute, smiling, or emoji-like

Limitations

  • Requires access to an image-generation tool that can follow composition, line-art, and annotation constraints.
  • The recurring Grav character style can drift between generations; verify every output against the QA checklist.
  • Text in generated images may be misspelled or distorted, so short labels and post-generation review are required.
  • The style is intended for explanatory article illustrations, not photorealistic product imagery or brand-final artwork.

Common Pitfalls

  • Problem: Illustration looks like a PPT slide Solution: Remove 30% of elements, increase whitespace, make it weirder

  • Problem: Grav is just standing next to the action Solution: Redesign so Grav IS the mechanism — becomes the funnel, dangles from the lever, is suspended inside the machine

  • Problem: Same metaphor as a previous illustration Solution: Replace the physical object entirely — same concept, different analogy

Additional Resources

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Assess a new or existing AI project by examining its code, goals, and constraints. Recommend skills confirmed to exist in the available registry, then outline tasks and implementation phases with dependencies, completion criteria, and checks.

  • Planning the first steps of a new AI project
  • Assessing technical issues in an existing project
  • Selecting relevant skills from an available registry
sickn33/agentic-awesome-skills48.2KUpdated Oct 21, 2026

007

FreeSummary

Review code and infrastructure for security risks, map potential threats, and plan stronger defenses. The skill covers OWASP checks, attack and defense exercises, and incident response, with validation required for each environment.

  • Reviewing code and infrastructure security
  • Mapping threats with STRIDE or PASTA
  • Planning stronger security settings
sickn33/agentic-awesome-skills48.2KUpdated Oct 21, 2026

Turn a repeatable task into an Andru.ia skill with clear inputs, outputs, examples, and limits. Draft SKILL.md, check the folder structure and required validations, and prepare a pull request describing the changes for review.

  • Creating a skill for a repeatable task
  • Improving an existing skill’s examples and limits
  • Validating skill files and preparing a pull request
sickn33/agentic-awesome-skills48.2KUpdated Oct 21, 2026

Prepare an industry briefing once a project's sector is defined. It covers sector context, potentially applicable regulations, familiar interface patterns, technology choices, and risks, while separating verified evidence from hypotheses and questions requiring further review.

  • Researching industry requirements before product design
  • Checking regulations for a project's jurisdiction
  • Choosing interface patterns familiar to target users
sickn33/agentic-awesome-skills48.2KUpdated Oct 21, 2026

Create presentation drafts from text, outlines, or documents through the 2slides API. Match a reference image's style, choose themes, add AI voice narration, and export slide images or audio for review and use.

  • Create a presentation from text or an outline
  • Summarize a document into slides
  • Match slide styling to a reference image
sickn33/agentic-awesome-skills48.2KUpdated Oct 21, 2026

Plan a 360-degree or peer feedback process and create empty response templates from confirmed requirements. Produces consistent CSV, SQL, JSON Schema, or Notion property mappings while keeping visibility choices and scoring configuration separate.

  • Plan an anonymous peer feedback process
  • Create a CSV template for feedback responses
  • Align feedback fields across SQL and JSON Schema
sickn33/agentic-awesome-skills48.2KUpdated Oct 21, 2026

See all skills by sickn33

Report a problem with this skill