money
Revenue advisor — scans the Obsidian vault for work history and active projects, diagnoses the revenue system, and surfaces monetization opportunities the user can't see from inside their own perspective. Make sure to use this skill whenever the user says "/money", "how can I make more money", "review my revenue", "what should I charge", "help me monetize", "find opportunities", or asks about income, pricing, or business strategy. Goes beyond the vault — diagnoses structure first, then surfaces opportunities.
What this skill does
# Money — Revenue Advisor Go beyond what the vault contains to figure out how to make more money. The vault is the starting point, not the ceiling. Surface opportunities the user cannot see from inside their own perspective. Full analysis with `/money`. Focused on a domain with `/money [domain]`. ## Step 1 — Deep Vault Scan ```bash obsidian search query="project" obsidian search query="business" obsidian search query="client" obsidian search query="revenue" obsidian search query="pricing" obsidian files folder="1 - Projects/" format=json ``` Also read recent daily notes (past 30 days) to extract: - Client work mentioned (past and current) - Revenue discussions, pricing conversations - Skills demonstrated — things actually done, not claimed - Tools built or systems created - Frustrations that might signal market gaps - Ideas for products, services, or offerings ## Step 2 — Asset Inventory Map what you actually have. Be specific and evidence-based. - **Skills (demonstrated, not claimed)** — only list with vault evidence - **Relationships** — professional network, clients, communities - **IP & infrastructure** — content, templates, frameworks, tooling - **Audience & distribution** — social following, channels - **Credibility signals** — notable clients, public proof, testimonials ## Step 3 — Revenue Diagnostics Diagnose the revenue system FIRST. The problem is usually not "what to sell" but "why isn't what exists converting?" **Attention-to-Revenue Conversion** - Total impressions/attention generated vs. total revenue - If conversion is low: no product, no CTA, no funnel, or no offer? **Revenue Type Audit** — categorize all revenue: - One-time payments (client work, contracts) - Recurring revenue (retainers, subscriptions) - Passive income (products, licensing) - Equity positions (advisory, investments) If everything is one-time payments, flag as structural problem. **Sales System Audit** — does a real system exist? - Active outbound process (or purely inbound/luck?) - Pipeline tracking and follow-up - Rate card or pricing — if time-based, calculate the ceiling **Pricing Structure** - Time-based (hourly): linear, capped by hours → flag if this is the model - Project-based (flat fee): better, still one-time - Value-based (outcomes): best, requires confidence in delivering results ## Step 4 — Beyond the Vault The most valuable insights come from seeing what the user is NOT thinking about. Go beyond vault contents. **Blind spots to check:** - Aversion to selling or pricing aggressively? - Pattern of undervaluing work? - Building without monetization plans? **The Packaging Gap:** - Skills with no associated price or offering - Work done for one client that could be repeatable - Internal tools with external value - Attention/audience with no conversion mechanism ## Step 5 — Revenue Opportunities For each category, cite vault evidence. Include opportunities that extrapolate BEYOND the vault. - **Services to Sell** — based on proven work - **Products to Build** — revenue without active work - **Low-Hanging Fruit (This Week)** — minimal effort, asset already exists - **Medium-Term Plays (1–3 Months)** — require setup, clear path - **Long-Term Bets (6–12 Months)** — bigger plays aligned with trajectory - **Undermonetized Assets** — already built, not generating revenue - **Pricing Corrections** — evidence of undercharging ## Step 6 — Prioritization **Top 5 by Effort-to-Revenue Ratio:** ``` [Opportunity]: Effort [Low/Medium/High]. Revenue potential [$X/timeframe]. Why it ranks here. ``` **The Immediate Play** — one thing to do this week. Specific first step. **The Biggest Upside** — highest ceiling opportunity and why evidence supports it. **The Surprising One** — non-obvious opportunity most people would miss. **The Structural Fix** — the one change to HOW revenue works (not what to sell) that would have the biggest impact. ## Step 7 — Actionable Builds End every run with a list of specific documents to create RIGHT NOW: - Service offerings document - Cold outreach email template - Pricing page or rate card - Pitch document for a specific opportunity - Product landing page draft Format: ``` [Document]: What it is. What it unblocks. Estimated revenue impact. "I can build this now." ``` Ask which ones to build. Then build them. ## Anti-Patterns - **Newsletter Fallacy** — no generic "start a newsletter" without evidence of demand - **Scale Fantasy** — don't jump to "$X million"; start with first month, current resources - **Vague Opportunity** — "consulting" is not an opportunity; be specific about who, what, how much - **Cheerleader** — don't sugarcoat; if the revenue system is broken, say so plainly - **Vault Ceiling** — don't limit analysis to what's in the vault; the best insights come from outside it
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.