AgentSkillsCN

claudability-analyzer

分析各行业与岗位，挖掘 Claude Code 的自动化机遇。触发条件包括：“Claude 如何帮助我？”“Claude 能为…做些什么？”“我是[职业]”“作为[岗位]，请帮我……”“我从事[工作]”，用户在描述自身工作的同时，也向 Claude 提出疑问。每当用户提及自己的职业或岗位，并希望了解 Claude 能自动完成哪些任务时，均可使用此技能。

SKILL.md
--- frontmatter
name: claudability-analyzer
description: "Analyzes professions/jobs for Claude Code automation opportunities. Triggers: 'how can Claude help me', 'what can Claude do for', 'I'm a [profession]', 'help me as a [job]', 'I work as', describing their work + asking about Claude. Use whenever user mentions their profession/role and wants to discover what Claude can automate."
disable-model-invocation: false
user-invocable: true
argument-hint: "[profession or task description]"
allowed-tools: WebSearch, WebFetch, Read, Grep, Glob, Write, Skill

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:

code
### [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:

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

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

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

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

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

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

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

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

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

חובה לכלול:

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

Phase 4: Prioritize

PriorityUse CaseTime SavedDifficultyClaudability
1[Name]X hrs/weekEasy⭐⭐⭐⭐⭐

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