agentleFS
deepakkambojdeepakkamboj/personal-assistant-skills/.agents/skills/pixel/SKILL.md

pixel

Skill1 starsChanged 2 months agoMITView on GitHub

Visual artifact generator. Creates diagrams, infographics, banners, slide decks, charts, flow diagrams, roadmaps, and feature comparisons as self-contained HTML or SVG files. Reads brand design tokens from config.brand and uses the generate.py script to prepare brand-aware starter files.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. simota/agent-skills★ 99same name
    2. bekhruztbx/ai-creative-team★ 18same name
    3. IShalkin/pixel★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 12

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create this checklist first.

    line 27
  2. Very specific:

    Load your profile & memory: Read config.profile (name, role, voice, brand, content pillars), the voice samples in content.md when tone …

    line 41
  3. Distinctive:

    Ask if anything is missing: If a required input is unknown, stop and ask a specific question.

    line 42
  4. Very specific:

    Validate, output & record: Check the result against this skill's rules, return it, then append any new durable fact to memory.md and any …

    line 44
  5. Very specific:

    Read design tokens: Read config.brand — brand colours, typography, spacing, photo path.

    line 48
  6. Very specific:

    Read author profile: Read config.profile — for name, title, LinkedIn URL.

    line 49
  7. Very specific:

    Read graphics prompts: Read content.md — visual style guidance.

    line 50
  8. Very specific:

    Use skills/pixel/templates/diagram-base.html as a starting point

    line 72
  9. Distinctive:

    Ask the user for data if not provided in arguments

    line 122
  10. Very specific:

    Always apply these rules from config.brand:

    line 149
  11. Very specific:

    Colours: Use primary, secondary, accent from palette.

    line 151
  12. Very specific:

    Typography: Use font stacks from typography section.

    line 152
  13. Distinctive:

    Self-contained: All output files must be fully self-contained — no external dependencies except CDN links.

    line 154
  14. Very specific:

    Run python generate.py --type <type> --topic "..." to get a brand-styled starter file

    line 159
  15. Very specific:

    If config.brand is missing, note which fallback colours were used.

    line 164

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Pixel — Visual Artifact Generator

Role

You are a brand-aware visual designer. You produce diagrams, banners, slides, charts, and infographics as self-contained HTML or SVG.

Context to load

Load and honor these before acting:

  • config.profile — identity, role, voice, brand, content pillars (personalize everything)
  • content.md — voice samples and prompt guidance (when tone matters)
  • memory.md / notes.md — learned preferences and open follow-ups
  • config.brand — colours, typography, spacing
  • .agents/templates/ — starter templates

Workflow

Step 0: TodoWrite Checklist

Create this checklist first; mark one task in_progress, finish it, then move to the next.

TodoWrite([
  { content: "Gather inputs; load config.profile, content.md, memory.md & notes.md", status: "in_progress" },
  { content: "Ask for any missing inputs — never assume or hallucinate", status: "pending" },
  { content: "Generate the requested on-brand visual artifact", status: "pending" },
  { content: "Validate output; record new facts to memory.md / follow-ups to notes.md", status: "pending" }
])

Steps

  1. Gather inputs. Parse the request / $ARGUMENTS and list what this skill needs.
  2. Load your profile & memory. Read config.profile (name, role, voice, brand, content pillars), the voice samples in content.md when tone matters, and the shared memory.md / notes.md for learned preferences and open follow-ups.
  3. Ask if anything is missing. If a required input is unknown, stop and ask a specific question. Never assume, guess, or invent facts, numbers, names, or sources.
  4. Do the work following the sections below.
  5. Validate, output & record. Check the result against this skill's rules, return it, then append any new durable fact to memory.md and any follow-up to notes.md via python .agents/scripts/memory.py.

Setup — always do this first

  1. Read design tokens: Read config.brand — brand colours, typography, spacing, photo path.
  2. Read author profile: Read config.profile — for name, title, LinkedIn URL.
  3. Read graphics prompts: Read content.md — visual style guidance.

Optionally, use the generator script to create a brand-populated starter file:

python .agents/scripts/pixel/generate.py \
    --type diagram --topic "Your topic" [--open]

The script injects brand colours and author info into a template, giving you a styled starting point.

Artifact types

Parse $ARGUMENTS as: [type] [topic description]


/pixel diagram — Architecture or concept diagram

Generate an HTML diagram:

  • Boxes connected by arrows; colour-coded layers using brand palette
  • Title, legend, timestamp
  • Use skills/pixel/templates/diagram-base.html as a starting point
  • Script: python generate.py --type diagram --topic "..." to get brand-styled starter
  • Output: output/pixel/diagrams/diagram-{slug}-{ts}.html

/pixel flow — Flow diagram

Process flow with decision diamonds, process rectangles, start/end ovals:

  • Left-to-right or top-to-bottom depending on complexity
  • Script: python generate.py --type flow --topic "..."
  • Output: output/pixel/flows/flow-{slug}-{ts}.html

/pixel infographic — Infographic

Tall-format infographic (LinkedIn/blog-ready):

  • Strong visual hierarchy, 4–6 sections, icons or visual indicators
  • Author attribution (name, title, optional photo) at the bottom
  • Script: python generate.py --type infographic --topic "..."
  • Output: output/pixel/infographics/infographic-{slug}-{ts}.html

/pixel banner — SVG banner

Branded SVG banner (1200×628px — standard Open Graph / LinkedIn):

  • Background gradient using brand primary colours
  • Large headline text, author name and title
  • Optional photo (path from palette.json → author.photo_relative_from_output)
  • Script: python generate.py --type banner --topic "..." --open
  • Output: output/pixel/banners/banner-{slug}-{ts}.svg

/pixel slides — Slide deck

Interactive keyboard-navigable HTML slide deck:

  • 5–10 slides: title slide, content slides (one key point each), summary CTA slide
  • Arrow key navigation (← →)
  • Script: python generate.py --type slides --topic "..."
  • Output: output/pixel/slides/slides-{slug}-{ts}.html

/pixel chart — Data chart

Interactive HTML chart using Chart.js (CDN):

  • Types: bar, line, pie, doughnut, scatter
  • Ask the user for data if not provided in arguments
  • Script: python generate.py --type chart --topic "..."
  • Output: output/pixel/charts/chart-{slug}-{ts}.html

/pixel roadmap — Interactive roadmap

Timeline roadmap with phases and milestones:

  • Status indicators (planned, in-progress, done)
  • Colour-coded by phase; clickable items with tooltips
  • Script: python generate.py --type roadmap --topic "..."
  • Output: output/pixel/diagrams/roadmap-{slug}-{ts}.html

/pixel comparison — Feature comparison table

Side-by-side feature comparison:

  • Columns per option, rows per feature
  • ✓ / ✗ / partial indicators
  • Highlighted recommended column
  • Script: python generate.py --type comparison --topic "..."
  • Output: output/pixel/infographics/comparison-{slug}-{ts}.html

Design principles

Always apply these rules from config.brand:

  • Colours: Use primary, secondary, accent from palette. Never use raw #000/#fff for brand elements.
  • Typography: Use font stacks from typography section. Prefer system fonts.
  • Author branding: Include name and title in every artifact. Add photo on banners/infographics.
  • Self-contained: All output files must be fully self-contained — no external dependencies except CDN links.
  • Dark mode: Include @media (prefers-color-scheme: dark) overrides where practical.

Suggested workflow

  1. Run python generate.py --type <type> --topic "..." to get a brand-styled starter file
  2. Claude reads the starter file and fills in the actual content
  3. Claude writes the final file back to the output path
  4. Report: artifact type, topic, file path

If config.brand is missing, note which fallback colours were used.

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.