agentleFS
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/workshop-workbook-builder/SKILL.md

workshop-workbook-builder

Skill4 starsChanged 6 months agoMITView on GitHub

End-to-end workflow for creating professional workshop participant workbooks for Funnel Junkies events. Use when asked to build, update, or redesign a workshop manual, participant workbook, or training guide — covering content drafting, PDF export, Canva import via MCP, and interactive webpage with fillable exercises and income calculator.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing, establish these four things with the user:

    line 20
  2. Distinctive:

    Every day opens with a 15-minute Quick Win task

    line 50
  3. Distinctive:

    Every day ends with a tangible deliverable the participant can show

    line 51
  4. Distinctive:

    Remove any section that does not serve a beginner in the room

    line 52
  5. Very specific:

    Write each section as a Markdown file.

    line 59
  6. Very specific:

    Read /home/ubuntu/skills/canva-mcp/SKILL.md before proceeding.

    line 100
  7. Very specific:

    Use webdev_init_project to scaffold a React + Tailwind static project.

    line 119
  8. Very specific:

    All exercises as localStorage-backed fillable fields (see references/webpage-components.md for useField and useCheck hooks)

    line 132
  9. Distinctive:

    Never assume "etc." in offer components or content frameworks — always expand the full list.

    line 150
  10. Distinctive:

    Before delivering any version:

    line 156

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Workshop Workbook Builder

Overview

This skill encodes the full process for building a Funnel Junkies workshop participant workbook from a brief to a finished, multi-format deliverable. The process produces three outputs:

  1. A polished PDF workbook (Markdown → PDF via manus-md-to-pdf)
  2. An editable Canva design (PPTX → Canva via MCP import)
  3. An interactive webpage (React + Tailwind with localStorage persistence)

Phase 1: Content Strategy

Before writing, establish these four things with the user:

DecisionQuestions to Ask
Audience levelAre they complete beginners, intermediate, or advanced? Have they heard of funnels before?
Workshop durationHow many days, how many hours per day?
Primary outcomesWhat must participants be able to DO (not know) by the end?
Existing productsWhat specific tools, platforms, and offers will be referenced?

Structure the workbook around momentum, not modules. Each day must end with a tangible visible result — a live page, a first lead, a first outreach sent. Never end a day on theory alone.


Phase 2: Outline

Proven structure for a 3-day beginner workshop:

Pre-Work         → Clear assumptions, define terms, set expectations
Mindset          → Mindset audit, belief shift exercise, signed commitment
AI Tools         → Platform orientation, tool walkthrough, 7-day trial CTA
Day 1            → Foundation: niche, avatar, offer construction, lead magnet
Day 2            → Machine: funnel copy, content creation, hook formulas
Day 3            → Engine: DM bots, 90-day KPI plan, ascension model
Post-Workshop    → 7-day action plan (day-by-day, no gaps)
Calculator       → Income calculator with sliders and months-to-goal
Glossary         → Plain-English definitions of all jargon used

Key rules:

  • Every day opens with a 15-minute Quick Win task
  • Every day ends with a tangible deliverable the participant can show
  • Remove any section that does not serve a beginner in the room
  • VA SOPs belong in a separate "Operator Guide", not the participant workbook

Phase 3: Writing the Workbook

Write each section as a Markdown file. See references/content-guidelines.md for full writing rules.

Module structure:

## Module Title

[2–3 paragraphs: concept explanation and why it matters]

> "Motivational quote." — Author

**Quick Win:** [15-minute hands-on task producing a visible result]

### Exercise: [Title]

**Example:** [Worked example using a real niche]

**Your turn:**
- [Fill-in field 1]
- [Fill-in field 2]

Motivational quotes: At least one per module. Sources: James Clear, Alex Hormozi, Gary Vaynerchuk, Warren Buffett, Henry Ford, Dale Carnegie, Robert Collier, Stephen King, Mark Twain, Abraham Lincoln.

Offer components — always expand in full, never abbreviate: Urgency, Scarcity, Value Stacking, Certainty, Guarantee, Specificity, Exclusivity, Social Proof, Future Pacing, Simplicity.


Phase 4: PDF Export

Compile all day files into a single workbook_final.md with cover page, table of contents, and all sections in order. Then:

manus-md-to-pdf /home/ubuntu/workbook_final.md /home/ubuntu/Workbook_FINAL.pdf

Phase 5: Canva Import

Read /home/ubuntu/skills/canva-mcp/SKILL.md before proceeding.

  1. Generate PPTX using python-pptx — see scripts/generate_pptx.py for the base template
  2. Upload: manus-upload-file /home/ubuntu/Workbook.pptx
  3. Import via MCP:
manus-mcp-cli tool call import-design-from-url --server canva \
  --input '{"url": "<PUBLIC_URL>", "title": "<DESIGN_TITLE>"}'
  1. Return both the edit URL and view URL to the user.

Design tokens: Navy #0d1b2a, Gold #f5c518, White #ffffff. Fonts: Oswald (headings) + Inter (body).


Phase 6: Interactive Webpage

Use webdev_init_project to scaffold a React + Tailwind static project. See references/webpage-components.md for the full component library.

CSS design tokens:

--color-navy: #0d1b2a;
--color-gold: #f5c518;
--color-off-white: #f8f7f4;

Required features:

  • Gold progress bar at the very top of the page (6px, glowing yellow, moves as exercises are completed)
  • Sidebar navigation with active section highlighting via IntersectionObserver
  • All exercises as localStorage-backed fillable fields (see references/webpage-components.md for useField and useCheck hooks)
  • Mindset audit table with independent tick boxes on BOTH Broke (red) and Wealth (gold) columns
  • R10k/pm Calculator with 5 sliders: commission per sale, conversion rate, content posts per day, leads per post, current monthly revenue — outputs: leads/month, sales/month, revenue/month, months to goal, gap analysis (sales and leads still needed)
  • Print button producing clean black-and-white output via CSS @media print
  • AI Tools section with 7-day trial CTA linking to the platform (funneljunkies.club)

Iteration Rules

Request typeAction
Content correction (wrong facts, wrong platform)Edit the specific section only
Design changeUpdate CSS variables and component styles only
New sectionAdd to nav array, ALL_FIELD_IDS array, and JSX in order
Remove sectionRemove from nav, ALL_FIELD_IDS, and JSX simultaneously
"Make it amazing"Offer a numbered list of specific improvements; get approval before implementing

Never assume "etc." in offer components or content frameworks — always expand the full list.


Quality Checklist

Before delivering any version:

  • Every day ends with a tangible visible result
  • No paid ads in lead generation section (beginners have no budget)
  • Dashboard section references only real tools that exist in the platform
  • No affiliate link sharing exercises between participants
  • VA SOPs are not in the participant workbook
  • All offer components are listed in full
  • Progress bar is at the very top of the page
  • Hero section text inputs are white on dark backgrounds
  • Mindset table has tick boxes on BOTH columns
  • Glossary covers all jargon used in the workbook

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.