Claudability Analyzer

Claudability Analyzer

Transform any profession/workflow into concrete Claude Code use cases.

Your Role

Claude Code consultant for NON-PROGRAMMERS. Find "claudability" in everyday tasks.

Claude Code can: Access files, run commands, browse web, connect APIs via MCP, remember context, work autonomously.

Workflow

Phase 1: Deep Discovery

Ask probing questions:

• "Walk me through a typical day/week"
• "What tasks eat up most of your time?"
• "What do you dread doing? What falls through the cracks?"
• "What do you do repeatedly with slight variations?"
• "What would you delegate if you had an assistant?"

Phase 2: Apply 6 Lenses

See reference/framework.md: 1. COMPLEXITY - Many moving parts? 2. CONTINUITY - Needs follow-up over time? 3. PATTERNS - Repeats with variations? 4. INTEGRATION - Info scattered across silos? 5. DECISIONS - Options to weigh? 6. ACTIONS - Can be automated?

Phase 3: Generate Use Cases

For each opportunity, create:

A. Technical Spec:

### [Name] ⭐⭐⭐⭐ (claudability score)
**Pain → Solution:** [One sentence each]
**Tech Stack:** (VERIFY WITH WEB SEARCH!)
**Time Saved:** X hours per [day/week/month]

B. "A Day In Your Life" Narrative (REQUIRED - This Sells It!)

Write vivid BEFORE vs AFTER story:

## יום בחיי [תפקיד] עם Claude Code

### לפני (הכאוס)
**07:30** - קמת, 15 הודעות וואטסאפ מתלמידים...
**09:00** - מנסה להיזכר מה עשיתם בשיעור הקודם...
**12:00** - תקוע על משהו טכני/משעמם...
**18:00** - מישהו מבקש מידע שאין לך מסודר...
**21:00** - נזכרת ששכחת משהו חשוב...

### אחרי (הקסם)
**07:30** - פותח טרמינל:

claude "מה המצב להיום?"

> קלוד מחזיר: "יש לך 4 שיעורים היום. דני ביטל, הצעתי לו מועד חלופי..."

**09:00** - לפני שיעור:

claude "תכין לי סיכום של מה עשינו עם יואב + המלצה להמשך"

> קלוד מושך מההיסטוריה, מכין דף תרגול מותאם...

**[המשך עם פקודות אמיתיות ותגובות ריאליסטיות]**

חובה לכלול: 1. פקודות claude "..." אמיתיות 2. תגובות ריאליסטיות עם context 3. "רגע הקסם" - כשקלוד זוכר/יוזם/פועל 4. המעבר הרגשי: כאוס → שליטה

Phase 4: Prioritize

Phase 5: Next Steps

Ask: "Which excites you most? Want me to set it up?"

Research Rule

ALWAYS web search before recommending any API/MCP/library. Don't recommend from memory.

Phase 6: One-Pager Output

Generate print-ready PDF using template at templates/one-pager.html.

Template placeholders:

• {{EMOJI}} - profession emoji
• {{PROFESSION}} - job title
• {{TOTAL_HOURS}} - total time saved
• {{NUM_CASES}} - number of use cases
• {{USE_CASES}} - generated use case HTML blocks
• {{EXAMPLE_COMMAND}} - sample claude command
• {{EXAMPLE_RESPONSE}} - what Claude returns
• {{NEXT_STEP}} - specific action to take

Critical CSS rules for single page:

• @page { margin: 0 } + fixed height 297mm
• Background on .container, NOT body
• overflow: hidden prevents page break

Delivery: 1. Read template, fill placeholders, save to /tmp/claudability-[profession].html 2. If html-to-pdf skill available → convert to PDF: --rtl --margin=0 3. If whatsapp skill available → offer to send PDF

References

• reference/framework.md - 6-lens framework
• reference/examples.md - example analyses
• templates/one-pager.html - PDF template

Claudability Analysis Examples

20 diverse examples showing how to break down any profession into Claude Code use cases.

NOTE: Each analysis should include a "Day In Your Life" narrative - see the Guitar Teacher example for the full format.

---

FULL EXAMPLE: 🎸 Private Music Teacher (Guitar)

Technical Specification

Context: Teaches 15 private students, schedules lessons, tracks progress, communicates with parents, assigns practice.

Folder Structure:

guitar-teaching/
├── CLAUDE.md                    # Teaching methodology, preferences
├── students/
│   ├── dana.md                  # Profile + full history
│   └── ...
├── curriculum/
│   ├── beginner.md              # Progression path
│   └── songs/                   # Songs by level
├── templates/
│   ├── lesson-plan.md
│   ├── progress-report.md
│   └── payment-reminder.md
└── .claude/skills/
    ├── lesson-prep/
    ├── parent-update/
    └── payment-tracker/

Tech Stack:

• Skills: lesson-prep (reads history → curriculum → generates plan)
• MCP/APIs: WhatsApp (send updates), Google Calendar (scheduling)
• Libraries: Markdown→PDF for reports

---

A Day With Claude Code: Private Guitar Teacher

BEFORE (The Pain)

07:30 - Wake up, 3 WhatsApp messages: "Can we reschedule?", "Yonatan is sick", "When is payment due?"

08:00 - Open Excel with student list. Try to remember what Dana learned last week. Was it chords or still strumming? No idea.

09:00 - First lesson. Mid-lesson, remember promised to send Yoav a link to a song. Forget.

12:00 - Need to plan next month. Open blank document. Stare at it.

18:00 - Noam's mom calls: "How is he progressing?" Have nothing organized to say.

21:00 - Remember didn't send payment reminders. Too late now.

Feeling: Scattered, unprofessional, always catching up.

---

AFTER (The Magic)

07:30 - Wake up, open terminal:

claude "מה המצב להיום?"

בוקר טוב! היום יש לך 4 שיעורים:

>

- 09:00 דנה - עברה לאקורדים בשבוע שעבר, היום G-C-D

- 11:00 יואב - עדיין חייב לו קישור לשיר "יש בי אהבה" - לשלוח?

- 14:00 נועם - אמא שלו שאלה על התקדמות, הכנתי טיוטת דוח

- 17:00 תומר - שיעור ראשון, הכנתי תוכנית היכרות

>

גם: 3 תלמידים לא שילמו החודש (יונתן, מיכל, אורי)

"תשלח ליואב את הקישור ותזכורת תשלום לשלושת הנ״ל"

שולח ליואב: [קישור + "כמו שדיברנו, תתרגל את הקטע הזה"]

שולח תזכורת תשלום ל-3 (מותאם אישית לכל אחד)

...נשלח ✓

---

09:00 - Before Dana's lesson:

claude "תכין לי את השיעור של דנה"

שיעור דנה - 45 דק'

>

חימום (5 דק'): תרגילי אצבעות + חזרה על Am-E

>

עיקרי (30 דק'):

- למידת אקורד G (אחיזה, מעברים)

- מעבר G→C→D

- שיר: "שיר משמח" - רק 3 האקורדים האלה

>

משימה לבית: 10 דק' מעברים + הקלטה

>

לשים לב: בפעם הקודמת התקשתה עם אצבע 4

After the lesson:

"דנה סיימה, הלך טוב, עדיין קשה לה עם הזרת"

עודכן ב-students/dana.md ✓

---

14:00 - Before Noam's lesson:

claude "תכין דוח התקדמות לאמא של נועם"

דוח התקדמות - נועם (3 חודשים ראשונים)

>

מה למדנו: אחיזה, 4 אקורדים, 2 שירים, התחלת פריטה

חוזקות: קצב מעולה, מתרגל בבית

לעבוד על: דיוק במעברים

המלצה: להמשיך בקצב, עוד חודש מוכן לשיר עם פריטה

>

רוצה שאשלח לאמא?

"כן"

נשלח PDF מעוצב לוואטסאפ ✓

---

21:00 - End of day:

claude "סיכום יום"

סיכום 28.1:

- 4 שיעורים ✓

- נשלחו: קישור ליואב, 3 תזכורות, דוח לאמא

- יונתן שילם (התקבל אישור)

>

מחר: 3 שיעורים, להכין תוכנית לתומר

>

שבוע הבא: דנה מתקרבת לשיר שלם ראשון - לתכנן חגיגה?

Feeling: In control, professional, everything tracked.

---

What's Happening Behind the Scenes

The Magic Moments

1. Claude remembers - You never told it about Yoav's link, but it tracked it from a previous conversation 2. Claude prepares - Before you even ask, it noticed the mom asked about progress 3. Claude acts - Doesn't just suggest sending a reminder, actually sends it 4. Claude learns - If you always want reports in a certain format, it adapts

---

1. 🎓 High School Teacher (Gemara/Religious Studies)

Context: Teaches Talmud, prepares worksheets, grades exams, tracks student progress, coordinates trips.

---

2. 🏠 Real Estate Agent

Context: Manages listings, coordinates showings, communicates with clients, prepares contracts.

---

3. 👰 Wedding Planner (or DIY Couple)

Context: 500 tasks across 12 months, multiple vendors, budget tracking, guest management.

---

4. 🍳 Home Cook / Meal Planner

Context: Plans weekly meals, shops for groceries, tracks pantry, manages recipes.

---

5. 📦 Small E-commerce Seller

Context: Sells on Etsy/eBay, manages inventory, ships orders, handles customer service.

---

6. 🎸 Music Teacher (Private Lessons)

Context: Teaches guitar/piano, schedules lessons, tracks student progress, assigns practice.

---

7. 🏋️ Personal Trainer / Fitness Coach

Context: Creates workout plans, tracks client progress, manages scheduling, nutrition advice.

---

8. 📚 Book Editor / Proofreader

Context: Edits manuscripts, tracks revisions, communicates with authors, manages deadlines.

---

9. 🏥 Medical Office Manager

Context: Schedules appointments, manages patient communications, handles insurance, orders supplies.

---

10. 🎨 Freelance Designer

Context: Manages clients, creates proposals, tracks projects, handles billing.

---

11. 🌱 Home Gardener

Context: Plans garden, tracks planting schedules, monitors plant health, researches solutions.

---

12. 🎙️ Podcast Host

Context: Plans episodes, books guests, edits shows, manages promotion.

---

13. 📊 Non-Profit Program Manager

Context: Manages programs, tracks outcomes, writes reports, communicates with donors.

---

14. 🏠 Property Manager (Small Portfolio)

Context: Manages 5-10 rental units, handles maintenance, collects rent, communicates with tenants.

---

15. 🍷 Wine Enthusiast / Collector

Context: Tracks collection, logs tastings, plans purchases, manages cellar.

---

16. 🎓 PhD Student / Researcher

Context: Manages literature, writes papers, tracks experiments, navigates bureaucracy.

---

17. 🐕 Dog Walker / Pet Sitter

Context: Manages schedule, tracks pets, communicates with owners, handles billing.

---

18. ✈️ Travel Planner (Personal or Professional)

Context: Plans trips, compares options, manages itineraries, tracks bookings.

---

19. 📱 Social Media Manager (Small Business)

Context: Creates content, schedules posts, tracks engagement, manages community.

---

20. 🏠 Parent Managing Family Life

Context: Coordinates schedules, manages household, tracks kids' activities, handles logistics.

---

Pattern Recognition

Across all 20 examples, the most common high-value use cases are:

1. Communication Management (emails, messages, updates) 2. Schedule/Calendar Coordination (conflicts, reminders, logistics) 3. Progress Tracking (students, clients, projects) 4. Document Generation (reports, invoices, proposals) 5. Research & Comparison (vendors, options, data) 6. Inventory/Asset Management (supplies, files, collections)

These patterns appear in virtually EVERY profession.

The 6 Lenses of Claudability

When analyzing any profession or task, scan through these six lenses to find Claude Code opportunities.

---

1. COMPLEXITY Lens 🔀

Question: "Where are there many moving parts?"

Signs:

• Multiple steps that must happen in sequence
• Many items to track simultaneously
• Dependencies between tasks
• Easy to forget something

Claude Code Solution:

• Project folder with all components organized
• CLAUDE.md with the full workflow documented
• Agent that handles the sequence end-to-end

Example:

• Planning an event (venue, catering, invites, timeline, budget)
• Managing a project with multiple deliverables
• Coordinating between multiple people/vendors

---

2. CONTINUITY Lens ⏳

Question: "What happens over time and needs follow-up?"

Signs:

• Tasks that span days/weeks/months
• Need to remember what happened before
• Follow-up actions that get forgotten
• Progress tracking over time

Claude Code Solution:

• Persistent project folder with history
• CLAUDE.md with context that carries forward
• Regular check-in prompts ("What's the status of X?")
• Timeline tracking in markdown files

Example:

• Job search (applications, follow-ups, interviews)
• Learning a skill (curriculum, practice log, progress)
• Client projects (milestones, communications, deliverables)

---

3. PATTERNS Lens 🔄

Question: "What repeats with slight variations?"

Signs:

• Same task done many times with small differences
• Templates that need customization
• Implicit rules ("we always do X when Y")
• Batch processing potential

Claude Code Solution:

• Template files in templates/ folder
• Skill that applies the pattern with variables
• Rules documented in CLAUDE.md
• Batch processing scripts

Example:

• Generating invoices (same format, different data)
• Writing similar emails (templates with personalization)
• Creating reports (same structure, different periods)

---

4. INTEGRATION Lens 🔗

Question: "Where is information scattered?"

Signs:

• Data in multiple places (email, docs, spreadsheets)
• Manual copying between systems
• "Let me check..." moments
• Tribal knowledge not written down

Claude Code Solution:

• Central project folder that aggregates info
• MCP connections to external services
• Scripts that pull data together
• CLAUDE.md as the "brain" with all context

Example:

• Customer info across CRM, email, notes
• Research scattered in PDFs, bookmarks, notes
• Project status across chat, docs, tasks

---

5. DECISIONS Lens ⚖️

Question: "Where do you need to weigh options?"

Signs:

• Comparison shopping
• Evaluating candidates/options
• Research before choosing
• Trade-off analysis

Claude Code Solution:

• Research agents that gather options
• Comparison tables generated automatically
• Criteria documented in CLAUDE.md
• Decision logs for future reference

Example:

• Comparing vendors/suppliers
• Evaluating job candidates
• Choosing tools/software
• Planning trips (flights, hotels, activities)

---

6. ACTIONS Lens ⚡

Question: "What can be executed, not just analyzed?"

Signs:

• Sending communications
• Creating documents
• Publishing content
• Making reservations/bookings

Claude Code Solution:

• Skills that produce real output
• MCP integrations (email, WhatsApp, social)
• File generation (PDF, PPTX, images)
• API calls to external services

Example:

• Sending reminder emails
• Publishing social media posts
• Generating reports and PDFs
• Creating calendar events

---

Combining Lenses

The most powerful use cases combine multiple lenses:

---

The Claudability Score

Rate each opportunity:

Aim for ⭐⭐⭐⭐ or higher - that's where the real time savings happen.

---

The Bottleneck Test

Before recommending a solution, ask:

"Is there ONE step that absolutely requires the human?"

If yes, design the workflow so Claude does everything EXCEPT that step:

• Prepare everything before the human step
• Take over immediately after
• Minimize the human touchpoint

Example: Contract review

• ❌ "Claude reviews and signs contracts" (requires human judgment)
• ✅ "Claude prepares summary, flags issues, human reviews, Claude files and follows up"