SkillAgentSearch skills...

digital-eguide

A two-spread digital e-guide preview — page 1 is a cover (display title, author, "What's inside" stats, table of contents teaser); page 2 is a spread (lesson body with pull-quote and a step list). Lifestyle / creator brand tone

Install / Use

npx skills add nexu-io/open-design --skill digital-eguide

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Our assessment of digital-eguide

digital-eguide scores 90/100 on our quality scale, 148th of 1,630 Development & Engineering skills we index (top 10%).

Its SKILL.md is 3.6 KB long, split into 3 sections with 1 code example: a solid amount of guidance for an agent.

With 97,896 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
12/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so digital-eguide is actively maintained.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

digital-eguide compared with similar skills

All 4 of these similar skills score higher than digital-eguide; compare them before choosing.

SkillScoreStarsUpdatedFormat
digital-eguide (this skill)by nexu-io9097.9ktodaySKILL.md
Agent-Reachby Panniantong10085.3k9d agoCLAUDE.md
ai-job-searchby MadsLorentzen10043.9k3d agoCLAUDE.md
claude-howtoby luongnv8910041.7k5d agoCLAUDE.md
algorithmic-artby anthropics100177.9k2d agoSKILL.md

Frequently asked questions

How do I install digital-eguide?
Run npx skills add nexu-io/open-design --skill digital-eguide. The install tabs above show the steps for each supported agent.
Which AI agents does digital-eguide work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is digital-eguide safe to use?
It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is digital-eguide still maintained?
The repository was last updated today, so digital-eguide is actively maintained.

name: digital-eguide description: | A two-spread digital e-guide preview — page 1 is a cover (display title, author, "What's inside" stats, table of contents teaser); page 2 is a spread (lesson body with pull-quote and a step list). Lifestyle / creator brand tone. Use when the brief asks for an "e-guide", "digital guide", "lookbook", "lead magnet", "creator guide", "playbook", "PDF guide", or "电子指南". triggers:

  • "e-guide"
  • "digital guide"
  • "lead magnet"
  • "lookbook"
  • "creator guide"
  • "playbook"
  • "pdf guide"
  • "ebook"
  • "电子指南"
  • "电子书" od: mode: prototype platform: desktop scenario: marketing preview: type: html entry: index.html design_system: requires: true sections: [color, typography, layout, components] craft: requires: [typography, typography-hierarchy, typography-hierarchy-editorial, rtl-and-bidi] example_prompt: "Design 'The Creator's Style & Format Guide' — cover page and one inside spread, lifestyle creator brand."

Digital E-Guide Skill

Produce a two-page digital guide preview side-by-side. Cover on the inline-start, inside spread on the inline-end. Lifestyle creator tone, lots of negative space, serif display headings, careful column rhythm.

Workflow

  1. Read the active DESIGN.md (injected above). Pick a serif display token for the title (italic ligatures encouraged), a body serif for long-form, and a mono token for stats / labels.
  2. Pick the topic + author from the brief. Generate a real title (e.g. "The Creator's Style & Format Guide"), a real subtitle, and a one-line author byline.
  3. Layout — center two pages on a tinted backdrop:
    • Page 1 — cover:
      • Eyebrow ("STYLE & FORMAT GUIDE FOR CREATORS").
      • Display title with mixed weights and one italic flourish word ("The Creator's Style & Format guide" — & and guide italic).
      • 3-cell stat row ("16 PRINCIPLES OF STYLE", "38 DOS & DON'TS", "1 BLOCK, ZERO TEMPLATES") in mono, separated by ·.
      • "What's inside" header with a 2-column TOC (chapters + page numbers in mono, leader dots).
      • Footer: "FIND YOUR VOICE" + page 01 mono.
      • Subtle decorative dot or sticker (CSS) in a corner.
    • Page 2 — spread:
      • Eyebrow with chapter number + name ("CHAPTER 02 · TONE").
      • Display sub-title ("Write like you talk — only sharper.").
      • 2-column body: opening paragraph + a numbered 4-step list ("01 Pick the rule", "02 Drop the filler"…).
      • Pull-quote pinned to inline-end: for Latin scripts use large italic display and accent color; for Arabic, Persian, and Urdu use regular or light emphasis (no italics); for Hebrew use regular or light emphasis (no italics). Include attribution. (script-aware)
      • Bottom strip with "EXERCISE" callout (mono label + 1 sentence prompt in italic).
      • Footer: chapter title + page 18 mono.
  4. Write a single HTML document:
    • <!doctype html> through </html>, CSS inline.
    • Pages are 600×860 paper-tone cards with 6px shadow, slight rotation opposing each other (±0.6deg) for a magazine-on-desk feel.
    • data-od-id on cover, spread, toc, pull-quote, exercise.
  5. Self-check:
    • Type hierarchy is editorial — title owns page 1, sub-title owns page 2.
    • Italic accent appears once per page.
    • Mono used only for labels, stats, and TOC numbers.

Output contract

Emit between <artifact> tags:

<artifact identifier="eguide-slug" type="text/html" title="E-Guide — Title">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact, nothing after.

Related Skills

View on GitHub
GitHub Stars97.9k
CategoryDevelopment
Updated15h ago
Forks11.4k

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions