Agent skill

Graphic Ebook

by Varnan-Tech in Varnan-Tech/opendirectory

Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.

MITAuto-check passedDocuments & Office

Install Graphic Ebook

skills CLI
$ npx skills add Varnan-Tech/opendirectory --skill graphic-ebook -a claude-code

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

GitHub CLI
$ gh skill install Varnan-Tech/opendirectory graphic-ebook --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/Varnan-Tech/opendirectory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/graphic-ebook .claude/skills/graphic-ebook && 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
graphic-ebook
GitHub stars
674
Token cost
~5k tokens
SKILL.md length
2,076 words
Files
8 (incl. scripts, references, assets)
Skills in repo
61
Repo updated
First seen
Licence
MIT

At a glance

Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.

  • Works in 8 steps: Brief Intake → Complete Intake → Internal Architecture → …
  • User says create an ebook
  • SKILL.md covers Critical Rules, Step 1: Brief Intake, Step 2: Complete Intake and Step 3: Internal Architecture, plus 5 more sections
  • Runs Shell scripts from its folder; calls bash

What it does

Graphic Ebook is an agent skill from Varnan-Tech/opendirectory. Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a nurture asset", or "make a PDF report".

Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including scripts, reference files and assets (for example `README.md`, `evals/evals.json` and `references/design-system.md`). Compatibility notes: ["claude-code","gemini-cli","github-copilot"]

It sits in Documents & Office, covering Multi-tenancy, Report writing and Content marketing. The repository describes itself as: AI Agent Skills built for Founders who hate Marketing. The licence is MIT.

When your agent uses it

  • User says create an ebook
  • Design a lead magnet
  • Make a PDF guide
  • Build a gated content piece

Example prompts

  • “create an ebook”
  • “design a lead magnet”
  • “make a PDF guide”
  • “/graphic-ebook”

Requirements

  • A Bash shell
  • Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"]

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Brief Intake
  2. Complete Intake
  3. Internal Architecture
  4. Page Structure
  5. Content Draft
  6. HTML Generation
  7. Self-QA
  8. Output

What it can do on your machine

Read from SKILL.md and the folder at commit 62e437a. 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 1 file in scripts/ (Shell), which the agent can run.

    Shell commands in SKILL.md call:

    • bash

    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.

  • Compatibility

    ["claude-code","gemini-cli","github-copilot"]

    From compatibility in the SKILL.md frontmatter.

Context cost

Graphic Ebook loads about 5k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 2,076 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~92
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
~16k

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 Varnan-Tech/opendirectory at commit 62e437a, republished under its MIT licence (© Varnan-Tech). 2,076 words, ~4,980 tokens.

Download SKILL.mdSave it as .claude/skills/graphic-ebook/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
graphic-ebook
description
Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. 3–10 pages, 9 style presets, 11 page layout types. Trigger when user says "create an ebook", "design a lead magnet", "make a PDF guide", "build a gated content piece", "write a B2B ebook", "design a white paper", "create a nurture asset", or "make a PDF report".
compatibility
["claude-code","gemini-cli","github-copilot"]
author
OpenDirectory
version
1.0.0

graphic-ebook

Creates professionally designed B2B SaaS e-books — lead magnets, gated guides, nurture assets, white papers. HTML + CSS → print-ready PDF. 3–10 pages.

Critical Rules

Before any step, these rules are absolute:

  1. Every page MUST fit within A4 canvas (1200×1697px). No content overflow.
  2. All scalable font sizes use clamp(). Fixed px only for borders/structural elements.
  3. Single self-contained HTML. All CSS inline. Font CDN <link> only external dependency.
  4. Never dump HTML in chat. Save to file, show summary only.
  5. Body copy is primary. Line-height ≥ 1.75 on all text-column and text-sidebar pages. Max-width ≤ 65ch for single-column body.
  6. No generic AI slop: no Inter as display font, no purple-to-blue gradient on white, no "Thank You" closing.
  7. Visual rhythm: never place 2+ text-column pages back-to-back. Break with chapter-intro, quote-callout, or stat-grid.
  8. Before generating HTML, commit to a design direction: one tone, one signature element, one background system. Generic = failure. Each ebook must be distinctly designed for its audience and subject — not a template.
  9. * { -webkit-print-color-adjust: exact !important; print-color-adjust: exact !important; } — mandatory global CSS. Chromium strips all background colors in PDF without this.
  10. Every page except cover must have a page footer: page number + brand name. Absolute position at bottom of each .slide.

Step 1: Brief Intake

Four required fields. If all four are present in the user's prompt: skip to Step 2.

If any are missing, ask exactly:

"To create your ebook, I need four things:

  1. Topic — what is the ebook about? (be specific: "5 ways to reduce CAC" not "marketing tips")
  2. Audience — who reads it? (role, company size, pain point: "Customer Success Managers at 50–500 person SaaS companies struggling with churn")
  3. Desired action — what should the reader do after? (book a demo, download a template, share with team)
  4. Content — do you have existing content, or should I draft from the topic?"

Stop and wait. Do not read reference files. Do not generate any HTML or outline.


Step 2: Complete Intake

Ask all 9 questions in one message, grouped. Defaults apply if skipped.

Content

  1. Page count — 3–5 (quick guide / checklist) / 6–8 (standard guide) / 9–10 (deep dive) (default: 6)
  2. Key takeaways — 3–5 things the reader should know or do after reading (informs chapter structure)
  3. Brand name — company or product name for cover and footer (or "skip")
  4. Brand logo — URL or "none"

Design 5. Style — clean-slate / midnight-editorial / matt-gray / product-minimal / mint-pixel-corporate / warm-earth / brutalist / magazine-red / soft-cloud / "show me options" (default: clean-slate) 6. Chapter count — how many main sections? (default: derived from page count)

Output 7. CTA details — demo booking / newsletter signup / template download / other (default: "book a demo") 8. Contact info — email + URL for closing CTA page (or "I'll add later") 9. Slug — filename slug (e.g., "reduce-churn-guide-2025"; derived from topic if skipped)

Defaults:

QuestionDefault
Page count6
Key takeawaysderive from topic
Brand namenone
Brand logonone
Styleclean-slate
Chapter countderived from page count
CTA detailsbook a demo
Contact infoplaceholder (flagged in checklist)
Slugkebab-case of topic

If style = "show me options": Generate 3 single-page HTML previews (cover page only) saved to .claude-design/previews/style-a.html, style-b.html, style-c.html. Open each automatically. Ask user to pick before Step 3.


Step 3: Internal Architecture

Derive internally. Never show this to the user.

Chapter → page mapping:

PagesTypical structure
3cover + [1 content page] + closing-cta
4cover + [1 chapter-intro + 1 text-column] + closing-cta
5cover + toc + [1 chapter-intro + 1 text-column] + closing-cta
6cover + toc + [2 chapter-intros + 1 text-column] + closing-cta
8cover + toc + [3 chapter-intros + 2 content pages] + closing-cta
10cover + toc + [4 chapter-intros + 3 content pages] + key-takeaways + closing-cta

TOC rule: Include for ebooks ≥ 6 pages. For 3–5 page ebooks, use a "What's inside" bullet list on the cover page or skip entirely.

Three-point CTA architecture (for ebooks ≥ 6 pages):

  1. Intro CTA (after page 2) — subtle 1-line inline mention: "explore our [tool] at [url]"
  2. Mid-ebook CTA (after a stat-grid or chapter-intro) — small .callout--stat or .callout--tip box with 1-line CTA
  3. Closing CTA (final page) — full-page, primary conversion action

Visual rhythm check: If 2+ consecutive text-column pages appear in the plan → insert quote-callout or stat-grid between them before proceeding.

Design direction (derive from style preset + audience — never shown to user):

DecisionDerive from
ToneWhat emotional register does this audience expect? (authoritative, editorial, energetic, calm, warm…)
Signature elementONE visual device used consistently: oversized decorative numerals, diagonal accent bar, dot-grid overlay, gradient mesh on cover, rule lines, geometric shape bleed. Pick one. Use it.
Background systemHow do backgrounds vary across pages? Cover and chapter-intros = most distinctive. Content pages quieter but NOT all-white. Closing CTA = dark or full-accent inversion. No 3+ consecutive pages with identical background.
Motion styleWhat do .reveal animations do? Pick one and stay consistent: translateY(16px) → 0, scale(0.97) → 1, translateX(-12px) → 0. Stagger delays 0.1s apart.
Unforgettable detailWhat is the ONE thing a reader will remember about the design? Name it before writing any CSS.

If no strong direction is derivable from style preset alone, ask yourself: what would a top-tier design agency produce for this specific audience and topic? Then execute that.

Body copy density limits:

  • text-column 1-col: 180–250 words max per page
  • text-column 2-col: 280–380 words max (140–190 per column)
  • text-sidebar: 140–180 words main + ≤70 words sidebar
  • chapter-intro: 40–60 words (teaser only)
  • quote-callout: 30–45 words
  • stat-grid: 3–6 metrics, minimal labels

Step 4: Page Structure

Read references/page-library.md before planning.

Output a numbered list with [layout-type] labels per page. Example for 6-pager:

Page 1: [cover] — title, subtitle, brand
Page 2: [toc] — 3 chapter titles + page numbers
Page 3: [chapter-intro] — Chapter 1 opener
Page 4: [text-column] — Chapter 1 body (1-column)
Page 5: [stat-grid] — 4 key metrics
Page 6: [closing-cta] — demo booking CTA + contact

Confirm with user before Step 5.


Step 5: Content Draft

Write per-page copy in plain text (no HTML). Rules per layout type:

  • cover: title (≤10 words, leads with value or tension — not a generic label) + subtitle (≤15 words) + optional category label + brand name
  • toc: chapter titles (≤6 words each) + corresponding section numbers. Clean, numbered list.
  • chapter-intro: chapter number (decorative) + chapter title (≤8 words) + teaser paragraph (2–3 sentences)
  • text-column (1-col): section heading + body paragraphs. Max 250 words. Prose > bullets. Every sentence earns its place.
  • text-column (2-col): same rules, 140–190 words per column. Use for comparisons, step pairs, dual perspectives.
  • text-sidebar: main body (140–180 words) + sidebar callout type (tip / warning / stat / quote / checklist) with max 70 words
  • quote-callout: pull quote ≤40 words + attribution (name, title, company or source)
  • stat-grid: 3–6 metrics — number + label + 1-line context. Optional: 1-sentence narrative below.
  • key-takeaways: 5–8 takeaways, ≤15 words each, imperative where possible
  • closing-cta: headline ≤5 words (imperative) + 1-sentence body + CTA action + email + URL (both required)

Forbidden words (no exceptions): "powerful", "seamless", "game-changing", "leverage", "innovative", "revolutionary", "transform", "cutting-edge", "robust", "unlock", "scalable" (as filler).


Step 6: HTML Generation

Read ALL of these before generating. Do not paraphrase or summarize them — read the actual files.

This skill's references:

  • references/design-system.md
  • references/page-library.md
  • references/style-presets.md

Bundled asset (exact path — include FULL verbatim contents in <style> block):

  • assets/viewport-base.css — bundled inside this skill's directory

Path resolution: All paths prefixed assets/ or scripts/ are relative to the directory containing this SKILL.md file. In Claude Code after install: ~/.claude/skills/graphic-ebook/assets/ and ~/.claude/skills/graphic-ebook/scripts/. Resolve the actual path from the SKILL.md file location before reading.

Generation Rules
  1. Single self-contained HTML. All CSS inline. Font CDN <link> only external dependency.

  2. Include FULL verbatim contents of viewport-base.css inside the <style> block.

  3. Add A4 portrait overrides AFTER viewport-base.css (in the same <style> block):

css
/* A4 portrait overrides */
html { scroll-snap-type: none; scroll-behavior: auto; }
.slide {
  width: 100vw;
  height: 100vh;
  height: 100dvh;
  overflow: hidden;
  display: flex;
  flex-direction: column;
  position: relative;
  scroll-snap-align: none;
}
/* CRITICAL: prevents Chromium from stripping backgrounds in PDF */
* { -webkit-print-color-adjust: exact !important; print-color-adjust: exact !important; }
  1. Each page = <section class="slide"> — required for export-pdf.sh page detection.

  2. Comment each page: /* === PAGE N: LAYOUT-TYPE === */

  3. Body text: clamp(0.875rem, 1.25vw, 1.05rem), line-height: 1.75, max-width: min(65ch, 100%) on all <p> in text-column and text-sidebar layouts.

  4. Stat numbers: hero at clamp(3rem, 8vw, 5.5rem) in accent color. Supporting at clamp(2.5rem, 7vw, 5rem) in secondary color.

  5. No images available → CSS-generated visuals only (gradients, geometric shapes, dot patterns, abstract elements). Never show placeholder boxes.

  6. No SlidePresentation JS. Include only minimal IntersectionObserver for .reveal animations.

  7. Chapter number decoration (on chapter-intro pages):

css
.chapter-number-deco {
  font-family: var(--font-display);
  font-size: clamp(6rem, 18vw, 14rem);
  font-weight: var(--display-weight);
  opacity: 0.06;
  position: absolute;
  top: -0.1em;
  right: var(--page-padding);
  line-height: 1;
  color: var(--accent);
  pointer-events: none;
  user-select: none;
}
  1. Typed callout boxes (for text-sidebar pages):
css
.callout { border-left: 3px solid; border-radius: var(--card-radius, 4px); padding: clamp(0.75rem, 1.5%, 1.1rem); }
.callout-label { font-size: clamp(0.58rem, 0.8vw, 0.68rem); font-weight: 700; letter-spacing: 0.12em; text-transform: uppercase; margin-bottom: 0.5em; }
.callout--tip      { background: rgba(22, 163, 74, 0.07);  border-color: #16A34A; }
.callout--tip      .callout-label { color: #16A34A; }
.callout--warning  { background: rgba(217, 119, 6, 0.07);  border-color: #D97706; }
.callout--warning  .callout-label { color: #D97706; }
.callout--stat     { background: rgba(var(--accent-rgb, 100,100,100), 0.07); border-color: var(--accent); }
.callout--stat     .callout-label { color: var(--accent); }
.callout--quote    { background: var(--bg-elevated); border-color: var(--divider); font-style: italic; }
.callout--quote    .callout-label { color: var(--text-muted); }
.callout--checklist { background: rgba(8, 145, 178, 0.07);  border-color: #0891B2; }
.callout--checklist .callout-label { color: #0891B2; }
  1. Page footer (on every page except cover):
css
.page-footer {
  position: absolute;
  bottom: 0; left: 0; right: 0;
  padding: clamp(0.5rem, 1%, 0.625rem) var(--page-padding);
  display: flex;
  justify-content: space-between;
  align-items: center;
  border-top: 1px solid var(--divider);
  font-family: var(--font-body);
  font-size: clamp(0.55rem, 0.75vw, 0.65rem);
  font-weight: 600;
  letter-spacing: 0.1em;
  text-transform: uppercase;
  color: var(--text-muted);
}

HTML: <div class="page-footer"><span>[Brand Name]</span><span>[N]</span></div>

  1. 2-column layout: display: grid; grid-template-columns: 1fr 1fr; gap: clamp(2rem, 4%, 3.5rem); with border-right: 1px solid var(--divider) on left column.

  2. Text-sidebar layout: display: grid; grid-template-columns: 2fr 1fr; gap: clamp(1.5rem, 3%, 2.5rem);

Show full SKILL.md (741 more words)Show less
Design Quality Rules (from frontend-design principles)

These govern the aesthetic ambition of every generated ebook. Applied after structural rules, before output.

Typography:

  • Display font must have character at large sizes. Plus Jakarta Sans 800, Instrument Serif, Syne, Lora, Fraunces — all acceptable. Inter at display weight = immediate slop signal.
  • Never use the same font weight for two consecutive hierarchy levels. Cover title (800) → chapter heading (700) → section heading (700, smaller size) → body (400/500).
  • Pair a display font with a refined body font when the preset supports it (e.g. Instrument Serif + Inter, Syne + IBM Plex Sans). Single-font stacks must use weight contrast instead.

Backgrounds and atmosphere:

  • Cover MUST have a significant decorative ::before or ::after pseudo-element creating visual depth: ghost letter at opacity: 0.04–0.06, geometric shape bleed, radial gradient overlay, or dot/line grid pattern.
  • Chapter-intro pages MUST visually contrast with adjacent content pages — use var(--bg-alt) or a style-appropriate alt treatment.
  • Content pages (text-column, text-sidebar) can be white/neutral, but the stat-grid and quote-callout pages should carry a distinct background (alt section bg, elevated card, or accent inversion).
  • Closing CTA: always dark or full-accent inversion — never light. It is the conversion moment.
  • CSS texture patterns when appropriate: radial-gradient(circle, var(--accent) 1px, transparent 1px) dot grids; repeating-linear-gradient rule lines; ::before with clipped geometric shapes.

Spatial composition:

  • Generous whitespace on chapter-intro pages — the visual openness signals a chapter break.
  • At least one element per ebook should break the standard grid: oversized chapter deco number that bleeds off-screen right, quote mark that overlaps content, stat number that dominates 60%+ of its column.
  • Avoid centered layouts unless the preset explicitly calls for it (quote-callout is the only centered-by-default layout).

Motion:

  • All .reveal animations use consistent direction derived from design direction step.
  • Stagger delays: 0.05s increments, max 0.5s cumulative. Nothing slower than 0.65s duration.
  • Stat items in stat-grid: stagger by index for cascade effect.
  • No animation on structural elements (footers, borders, rules). Animation = content appearing, not layout materializing.

The unforgettable detail rule: Before writing the first line of CSS, name the ONE element that makes this ebook unmistakably designed — not just competently assembled. That element gets the most CSS investment. If you cannot name it, you have not thought hard enough about the design.


Step 7: Self-QA

Fix every failure before proceeding to output. Do not skip this step.

Layout & rendering:

  • Every .slide has height:100vh; height:100dvh; overflow:hidden
  • * { -webkit-print-color-adjust: exact !important; print-color-adjust: exact !important; } present globally
  • All scalable font sizes use clamp()
  • No content overflows at 1200×1697 — review each page's density
  • No placeholder boxes visible
  • No -clamp(), -min(), -max() directly (wrap negatives in calc(-1 * ...))

Structure:

  • Page count matches Step 4 plan
  • Every page uses class="slide" on <section> only
  • All layout types from Step 4 present in correct order
  • TOC included for ebooks ≥ 6 pages

Reading quality:

  • Body text line-height ≥ 1.75 on text-column and text-sidebar pages
  • Single-column body text max-width ≤ 65ch
  • No 2+ consecutive text-column pages without visual break
  • TOC has chapter titles + section/page numbers
  • Chapter-intro pages have .chapter-number-deco (opacity 0.06–0.08)
  • Every page except cover has .page-footer with page number + brand name
  • Sidebar callout boxes use typed CSS class (.callout--tip/warning/stat/quote/checklist)

Design quality:

  • Style preset tokens applied consistently (from references/style-presets.md)
  • No slop patterns (see references/design-system.md DO NOT USE list)
  • Typography hierarchy: cover title >> chapter heading >> section heading >> body (2:1 min ratio between levels)
  • Stat numbers visually dominant — no body copy at same visual weight
  • Cover has a significant decorative ::before/::after element — not just text on a flat color
  • Chapter-intro pages visually distinct from content pages (different bg or treatment)
  • Closing CTA uses dark or full-accent inversion background — never light
  • No 3+ consecutive pages with identical background color
  • Signature element from design direction step is present and visible
  • At least one layout element breaks the grid (oversized deco number, bleed shape, dominant stat)
  • Reveal animations consistent direction and stagger — not random per-element

Content:

  • No forbidden words anywhere
  • Cover title ≤10 words, leads with value or tension
  • Quote callout ≤40 words
  • Closing CTA: imperative headline + email + URL (both mandatory — QA fails without both)
  • TOC matches actual page structure
  • Three-point CTA present for ebooks ≥ 6 pages

Step 8: Output

bash
mkdir -p ebook/[slug]

Write main HTML: ebook/[slug]/index.html Open: open ebook/[slug]/index.html

Per-page split (always generate): Extract each <section class="slide"> into standalone HTML files with full <style> block, no JS: ebook/[slug]/page-01.html, page-02.html, … (zero-padded 2 digits)

PDF export (always run):

bash
bash [skill-root]/scripts/export-pdf.sh \
  ebook/[slug]/index.html \
  ebook/[slug].pdf --portrait

[skill-root] = the directory containing this SKILL.md. Resolve it before running (e.g. ~/.claude/skills/graphic-ebook in Claude Code after install).

Cleanup: Delete .claude-design/previews/ if style preview files were generated in Step 2.

Summary (no HTML in chat):

## Ebook: [title]
Date: [today] | Style: [style] | Pages: [N] | Format: A4 portrait
Brand: [brand name] | Topic: [topic]

Files
  Main:      ebook/[slug]/index.html
  Per-page:  ebook/[slug]/page-01.html → page-0N.html
  PDF:       ebook/[slug].pdf

Checklist
- [ ] Replace contact info placeholders (email + URL on closing page)
- [ ] Replace brand logo initials with real asset
- [ ] Verify TOC section numbers match actual page positions
- [ ] Proof all stat accuracy (page [N])
- [ ] Review body copy — no page should feel overflowed
- [ ] Test PDF opens correctly (page count = [N])

© Varnan-Tech, 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 7 other files (scripts, references, assets) in skills/graphic-ebook of Varnan-Tech/opendirectory.

  • SKILL.md
  • README.md
  • assets/viewport-base.css
  • evals/evals.json
  • references/design-system.md
  • references/page-library.md
  • references/style-presets.md
  • scripts/export-pdf.sh

Open the folder on GitHubat commit 62e437a

Compare with similar skills

Graphic Ebook 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.

Graphic Ebook compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Graphic Ebook this skillVarnan-Tech/opendirectory674—~5kAutomated safety check: PassMIT
Ky Markdown RebuilderKyrieCheungYep/ky-markdown-rebuilder117—~5.7kAutomated safety check: PassNone
Summarizereysu/ai-life-skills269—~7.7kAutomated safety check: PassMIT
CSV To Executive Reportskrun-dev/skrun210—~1.1kAutomated safety check: PassMIT
PDF Sizethedaviddias/Front-End-Checklist74k—~597Automated safety check: PassMIT
Lead MagnetOpenClaudia/openclaudia-skills713—~3kAutomated safety check: PassMIT

Similar skills

  • Ky Markdown Rebuilder

    KyrieCheungYep/ky-markdown-rebuilder

    Rebuild visual documents into reliable Markdown by combining text extraction with page or screenshot alignment.

    117 GitHub stars~5.7k tokensUpdated 3 mo ago
    Documents & OfficeAuto-check passed
  • Summarize

    reysu/ai-life-skills

    Summarize any content (YouTube video, article, whitepaper/PDF, podcast episode, book chapter, etc.) into a rich Obsidian note with section-by-section breakdowns, wikilinks to all technical concepts…

    269 GitHub stars~7.7k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Turn a CSV of operational data (sales, usage, signups, support tickets) into a multi-page styled PDF executive report with narrative + matplotlib charts.

    210 GitHub stars~1.1k tokensUpdated 16 days ago
    Documents & OfficeAuto-check passed
  • PDF Size

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing a site that publishes downloadable PDFs (reports, white papers, legal documents, manuals).

    74k GitHub stars~597 tokensUpdated 3 days ago
    Documents & OfficeAuto-check passed
  • Lead Magnet

    OpenClaudia/openclaudia-skills

    Create lead magnets and gated content to capture email subscribers and leads.

    713 GitHub stars~3k tokensUpdated 21 days ago
    Documents & OfficeAuto-check passed
  • PDF Generation

    glebis/claude-skills

    Professional PDF generation from markdown using Pandoc with Eisvogel template and EB Garamond fonts.

    390 GitHub stars~1.3k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from Varnan-Tech/opendirectory

All 61 skills in this repo
  • Docs From Code

    Varnan-Tech/opendirectory

    Generates and updates README.md and API reference docs by reading your codebase's functions, routes, types, schemas, and architecture.

    674 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Graphic Chart

    Varnan-Tech/opendirectory

    Generates data visualization charts (bar, line, area, pie, doughnut, scatter, radar, treemap) as PNG using Apache ECharts v6.

    674 GitHub stars~2.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Graphic Gif

    Varnan-Tech/opendirectory

    Creates animated looping GIFs from CSS animations (default) or AI image-to-video.

    674 GitHub stars~3k tokensUpdated 1 mo ago
    Auto-check passed
  • Map Your Market

    Varnan-Tech/opendirectory

    Given a product description, category keywords, or competitor names (any combination), searches Reddit, Hacker News, GitHub Issues, G2, and Google Trends for the real pains your market experiences…

    674 GitHub stars~4.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Newsletter Digest

    Varnan-Tech/opendirectory

    Aggregates RSS feeds from the past week, synthesizes the top stories using Gemini, and publishes a newsletter digest to Ghost CMS.

    674 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Podcast Transcript Fetcher

    Varnan-Tech/opendirectory

    A skill your agent uses when fetching, searching, or analyzing transcripts from Lenny's Podcast, Dwarkesh Podcast, Cheeky Pint, 20VC, or A16z Podcast.

    674 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check: notes

Questions about Graphic Ebook

What does Graphic Ebook do?

Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF. Graphic Ebook is an agent skill from Varnan-Tech/opendirectory. Creates professionally designed B2B SaaS e-books in HTML + CSS, exported as print-ready PDF.

When should I use Graphic Ebook?

Graphic Ebook fits situations like: user says create an ebook; design a lead magnet; make a PDF guide; build a gated content piece.

How do I install Graphic Ebook in Claude Code?

Run `npx skills add Varnan-Tech/opendirectory --skill graphic-ebook -a claude-code`. Or copy the skill folder (skills/graphic-ebook in Varnan-Tech/opendirectory) into .claude/skills/graphic-ebook in your project. Claude Code loads it when a task matches its description.

How do I install Graphic Ebook in Codex?

Run `npx skills add Varnan-Tech/opendirectory --skill graphic-ebook -a codex`. Or copy the skill folder (skills/graphic-ebook in Varnan-Tech/opendirectory) into .agents/skills/graphic-ebook in your project. Codex loads it when a task matches its description.

Can I use Graphic Ebook 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 Varnan-Tech/opendirectory --skill graphic-ebook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/graphic-ebook, .gemini/skills/graphic-ebook, .github/skills/graphic-ebook and .opencode/skills/graphic-ebook in your project.

What does Graphic Ebook need to run?

Going by SKILL.md and its folder, Graphic Ebook needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell. Compatibility (from SKILL.md): ["claude-code","gemini-cli","github-copilot"].

Does Graphic Ebook 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 Graphic Ebook 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 Graphic Ebook use?

Graphic Ebook 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 Graphic Ebook 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 11k tokens, read only when the agent opens those files.

What are the alternatives to Graphic Ebook?

Skills that share tags, products or a category with Graphic Ebook: Ky Markdown Rebuilder (KyrieCheungYep/ky-markdown-rebuilder, 117 stars), Summarize (reysu/ai-life-skills, 269 stars), CSV To Executive Report (skrun-dev/skrun, 210 stars) and PDF Size (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Graphic Ebook?

Varnan-Tech (a GitHub organization) maintains it in Varnan-Tech/opendirectory, which has 674 GitHub stars. The repository holds 61 skills in this directory. The repository was last updated on August 16, 2026.

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