Vertical Professional Services
Domain-knowledge primer for the professional-services vertical (agencies, consulting firms, creative studios) so architect/pm don't spec naively against PSA incumbents (Scoro, Productive, Accelo, Ruddr, BigTime). Supplies the vocabulary, the non-obvious billing/margin rules, the entities a real proposal/portal/time/profitability product must model, and the per-product wedge. Applied by architect/pm during spec authoring for any of the four products in this vertical — proposals, client-portal, time-invoicing, profitability.
Install
npx skills add jeremybrasher/grokbot-skills --skill vertical-professional-servicesgit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/vertical-professional-services ~/.claude/skills/vertical-professional-servicesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Vertical: professional services — bill time, defend margin, sell the scope Agencies, consulting firms, and creative studios sell hours and deliverables, not units. Their economics are unintuitive: revenue can rise while margin collapses, and the document that wins the work (the proposal/SOW) is also where margin leaks. Incumbents (Scoro, Productive, Accelo, Ruddr, BigTime — collectively "PSA", professional-services automation) model this correctly; a naive build does not. Spec against the real domain. ## 1. Domain vocabulary - **SOW (statement of work)** — the binding scope: deliverables, timeline, price, terms. It IS the contract and the upsell surface. - **Engagement types**: **project** (fixed scope/price), **retainer** (recurring fee for a capacity/hours bucket), **T&M** (time & materials — bill actuals). - **Utilization rate** — billable hours ÷ available hours. The first lever of margin. - **Realization rate** — billed amount ÷ standard value of hours worked (i.e. how much of what you *could* bill you actually invoiced and collected). The second lever. - **Billable vs non-billable** — every time entry carries this flag; non-billable (admin, sales, rework) is pure cost. - **WIP (work in progress)** — unbilled-but-delivered work; revenue earned, not yet invoiced. Agencies carry it for weeks. - **Blended rate** — single effective $/hour across a mixed-seniority team on an engagement (vs per-person rate cards).
Details
- Skill name
vertical-professional-services- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/vertical-professional-services/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Vertical Professional Services skill do?
Domain-knowledge primer for the professional-services vertical (agencies, consulting firms, creative studios) so architect/pm don't spec naively against PSA incumbents (Scoro, Productive, Accelo, Ruddr, BigTime). Supplies the vocabulary, the non-obvious billing/margin rules, the entities a real proposal/portal/time/profitability product must model, and the per-product wedge. Applied by architect/pm during spec authoring for any of the four products in this vertical — proposals, client-portal, time-invoicing, profitability.
How do I install the Vertical Professional Services skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill vertical-professional-services. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Vertical Professional Services popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
1031 Exchange Guide
39lionelsimai/claude-skills-collection
Guide 1031 exchange processes and requirements. TRIGGERS - Use when user needs help with 1031-exchange-guide related tasks.
Triage Issue Reports
38jeremybrasher/grokbot-skills
Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation. Observe required inputs first; HOLD when they are missing rather than guessing.
30 60 90 Plan
39lionelsimai/claude-skills-collection
Create 30-60-90 day plans for new hires. TRIGGERS - Use when user needs help with 30-60-90-plan related tasks.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.