agentleFS
Sign inStart free
auth-02auth-02/skills/how-to/SKILL.md

how-to

Skill1 starsChanged 5 months agoMITView on GitHub

Turn a sequence of screenshots/images into a polished "how-to guide" PDF: typeset cover page, every image on a uniform card layout, footer slide counter, optional numbered step headers, and patching-out of unwanted UI. Use whenever the user wants screenshots/images turned into a styled walkthrough, tutorial, onboarding, or guide PDF. Also use for a guide PDF with NO source images (documenting skills, an API, a concept) — slides are generated as styled HTML → PNG first, then assembled.

  • Installs packages

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prompt-master, write-a-skill and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ttmouseSkill

    prompt-master

    提示词主控 - 智能选择合适的领域skill并生成提示词，支持自动领域分类和调度

    Also in 3 projects that use this

  • simo97Skill

    write-a-skill

    Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. semtexfromua/vibe-typing★ 3same name
    2. aditya-vermax/skills★ 1same name
    3. VGBRO/claude-skills★ 1same name
    4. innovationengines/skills-repo★ 0same name
    5. kshyam/opencode-and-claude-skills★ 0same 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 repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always verify: After building, render a page or two of the PDF to thumbnails and Read them — confirm the cover, layout, any …

    line 41

“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

how-to — styled guide PDF

Build a clean, consistent walkthrough PDF. Every page is the same size with a shadowed white card, a 1px border around the image, and an optional footer slide counter. Page 1 is an optional typeset cover.

This skill has two flows. Decide which applies, then read that flow's reference file in full and follow it — the detailed steps, the script, and the JSON config schema all live there. Don't work from this page alone.

Pick the flow

If…FlowThen readDriver script
The user gave you images (screenshots, exported diagrams)1 — assemblereferences/flow-images.mdscripts/build_guide_pdf.py
The user wants a guide but there are no images (skills, an API, a concept, a checklist)2 — generate, then assemblereferences/flow-content.mdscripts/render_slides.py → scripts/build_guide_pdf.py

Flow 2 first generates styled slides from content (HTML → PNG via headless Chrome, in the design aesthetic by default), then hands those PNGs to Flow 1's assembler. So Flow 2 uses both reference files; start with flow-content.md.

Before you start (both flows)

  • Dependencies. Assembling needs Pillow (python3 -c "import PIL"; if missing, pip install Pillow). Generating (Flow 2) also needs headless Chrome — present on macOS at /Applications/Google Chrome.app.
  • Scratch space. Working files (configs, HTML, PNGs) live fine in a temp dir like /tmp/<name>-guide/; only the final PDF needs a real home.
  • Always verify. After building, render a page or two of the PDF to thumbnails and Read them — confirm the cover, layout, any patches/headers, and (Flow 2) that fonts loaded. Adjust the config and re-run if needed.
  • Examples. references/guide.json (assembler) and references/slides.json (generator) are complete, real configs to copy from.

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.

Check your setup, free