onewave-ai/job-profitability-analyzer
job-profitability-analyzer/SKILL.md
Find out which clients and jobs actually make money -- allocate real costs (labor hours, materials, subs, overhead) against what each job billed, and rank every client by true margin. Most service businesses discover their biggest client is their least profitable.
$ install --global
skillsauthnpx skillsauth add onewave-ai/claude-skills job-profitability-analyzerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 16, 2026, 6:42 AM129.0s1 file scanned
SKILL.md
- name:
- job-profitability-analyzer
- description:
- Find out which clients and jobs actually make money -- allocate real costs (labor hours, materials, subs, overhead) against what each job billed, and rank every client by true margin. Most service businesses discover their biggest client is their least profitable.
- tools:
- Read, Glob, Grep, Write, Bash
- model:
- inherit
Job Profitability Analyzer
Revenue is vanity, margin per job is survival. Service businesses (agencies, contractors, consultancies, trades) routinely lose money on their "best" clients because nobody allocates the hours. Input: invoices/revenue by job or client, time tracking exports, materials/sub costs, payroll rates, and a rough overhead number. Output: profit per job, per client, per service line -- with receipts.
Workflow
- Build the job ledger. Match every revenue line to a job/client. Match every cost: labor (hours x loaded rate -- wages plus taxes/benefits, ~1.25-1.4x base, confirmed with the user), materials and subcontractors from bills, and direct expenses (travel, software attributed to one client).
- Allocate overhead. Rent, admin, insurance, tools spread across jobs -- by labor hours by default (state the method). Show margins both before and after overhead so the user sees direct profitability and true profitability separately.
- Rank.
profitability-report.md: every job and client ranked by margin dollars and margin percent, with the effective hourly rate each client actually pays (revenue minus non-labor costs, divided by hours). This one column reorders most people's client list. - Diagnose the losers. For bottom-quartile jobs: was it underpricing, scope creep (hours ballooned past estimate), expensive labor mix, or unbilled work? Cite the timesheet and invoice evidence per diagnosis.
- Prescribe. Per problem client: the raise-price number that hits target margin, the scope boundary to enforce, or the fire-the-client math (hours freed x effective rate of the best clients). Pair with
pricing-strategyfor the repricing conversation.
Rules
- Loaded labor rates or nothing -- wages alone understate labor cost 25-40% and flatter every margin.
- Unbilled hours are the finding, not noise: track estimated vs. actual vs. billed hours per job explicitly.
- State the overhead allocation method and run the sensitivity: if the ranking flips under a different method, say so.
- No cost data for a job means
INCOMPLETE, not a guess -- and chronic time-tracking gaps get called out as the root problem. - Small samples get honesty: one bad job does not condemn a client; three do. Note the n per client.
- Effective hourly rate is the universal translator -- report it everywhere.
Quick Commands
- "Analyze [files]" -- full workflow
- "Rank my clients" -- client-level table only
- "Why did [job] lose money?" -- single-job autopsy
- "What should I charge [client]?" -- the repricing math
Related Skills
onewave-ai/typography-scale-builder
development
VerifiedTrustedCommunity
Build a complete typographic system -- modular or fluid type scale, line-height and tracking per size, weight roles, and vertical rhythm -- exported as tokens, Tailwind config, and CSS. Pairs with font-pairing-suggester (which picks the fonts; this builds the system they live in).
217SKILL.mdUpdated Jul 16, 2026
onewave-ai/review-response-writer
development
VerifiedTrustedCommunity
Respond to Google, Yelp, and industry reviews in the owner's voice -- gracious on the 5-stars, masterful on the 1-stars. Handles the angry customer, the unfair review, the fake review, and the one that mentions a legal or health issue. Every response written for the thousand future customers reading it.
217SKILL.mdUpdated Jul 16, 2026
onewave-ai/motion-language-designer
tools
VerifiedTrustedCommunity
--- name: motion-language-designer description: Define a product's motion design language -- duration and easing scales, choreography rules, and signature moves -- and export it as tokens plus ready-to-use Framer Motion variants and CSS. The difference between animations and a motion system: everything moves like it belongs to the same product. tools: Read, Glob, Grep, Write, Edit, Bash model: inherit --- # Motion Language Designer Design motion the way type and color get designed: as a system
217SKILL.mdUpdated Jul 16, 2026
onewave-ai/local-seo-optimizer
development
VerifiedTrustedCommunity
Get a local business found on Google -- audit and optimize the Google Business Profile, local pack ranking factors, review velocity, NAP consistency across directories, and location pages. For businesses whose customers search "near me," this outranks everything else in marketing.
217SKILL.mdUpdated Jul 16, 2026