13 skills from 7 contributors
Operations
Builder direction note
Turns client or stakeholder feedback on something already built (a staging page, a deck, a PDF, a mockup) into a numbered change note for the person who builds it (designer, developer, editor). Reads the feedback and the live thing, sorts each comment by what it changes for the user to confirm, finds every other place the same line or number appears, and writes "Hey [builder], [client] went through [the thing]..." with exact old and new copy, grouped by asset, and a closing ask for timing. Use when the user says "/direction", "translate this into direction for [builder]", "help me pass this along to [builder]", "what do I need to pass along to the designer", "write this as a note to [builder]", "[client] also sent this", "create a task for [builder] for [person]'s request", or pastes a client email of revisions and asks what changes. Never sends anything.
Gary MagnoneFractional Operations Leader, HighriseFinance
Cash runway forecast
Use this skill when the firm is profitable on paper and still worried about payroll, or before any commitment that spans a few months. Produces a thirteen-week view of money in and money out, the weeks that go tight, what causes each one, and the two or three moves that fix them while there is still time. Also use for "can we afford this hire", "will we make payroll", "cash flow forecast", "when do we get tight".
Tapajyoti (Tukan) DasCEO, Gia
Operations
CEO exec assistant
Use this skill when the person running a small agency needs to know what the week actually demands, pulled from the project tool and the calendar rather than from memory. Produces a short brief: what is committed today and this week, what is at risk, what the calendar makes impossible, and the three things to do first. Also use for "what's on this week", "am I missing anything", "catch me up before Monday", "what's slipping".
Christian BeckCOO and Managing Partner, Five FourFinance
Client profitability read
Use this skill when the firm is busy and the money does not reflect it, or before any decision about which clients to keep. Produces what each client actually earns per hour once revisions, account management and unbilled calls are counted, ranked, with the ones losing money named. Also use for "which clients actually make money", "effective hourly rate", "why are we busy and broke", "is this client worth it".
Tapajyoti (Tukan) DasCEO, Gia
Finance
Late payment chase
Use this skill when invoices are sitting unpaid and nobody has decided who chases them or how. Produces the aged list, who to chase in what order, the message for each stage from a nudge to a stop-work notice, and the point where it stops being an admin problem. Also use for "they haven't paid", "chase the invoice", "AR is a mess", "how do I ask for money without wrecking the relationship".
Bailey DarlingCo-Founder, GiaRevOps
LinkedIn export contact import
Use this skill when you've downloaded your LinkedIn data export and want your connections, sent invites and DM history in your CRM or contact sheet. Produces upserted contacts plus dated touches, safe to re-run every week. "Import my LinkedIn export", "load my connections into the CRM", "who have I messaged on LinkedIn".
R. Hunter HarrisFounder, Hunter Software ConsultingRevOps
Mail and Messages contact touches
Use this skill on a Mac when your CRM or contact sheet doesn't know who you last emailed or texted. Produces dated touch records (date, contact, channel, direction, email subject) from Apple Mail and Messages, without storing message bodies. "Log my emails and texts to the CRM", "when did I last talk to them", "backfill contact history".
R. Hunter HarrisFounder, Hunter Software ConsultingRevOps
Pipeline by script
Use this skill when a small firm runs its pipeline from its own folder with no CRM and an agent records what happens on each deal. Every movement (a send, a reply, a booking, a decision that changes the next step or whose move it is) goes in through one script command that writes the pipeline row, the activity log line, an archive copy and the rebuilt dashboard together, and a drift check at the start of every agent turn names any row left behind its log line. Produces one Markdown pipeline file (open deals, channels, clients won, closed, and a dated activity log), a generated dashboard whose weekly counts come from event tags, and the commands that keep them in step. Also use for "log that reply", "move the deal", "add this to the pipeline", "close it out", "update the client row", "track pipeline without a CRM", "why is this row out of date".
Paul MunroFounder, AppliedGTM
Operations
Process capture
Use this skill when something the firm does well lives only in one or two people's heads, and those people have become the bottleneck. Produces a written process anyone on the team can run: the real sequence including the steps people skip, each decision with the criteria behind it, the quality bar as checkable items, and which steps still need the senior person. Also use for "write down how we actually do this", "document our process", "build an SOP", "why does everything go through me".
Purvesh RathodFounding Software Engineer, Gia
Finance
Rate increase plan
Use this skill when rates have not moved in a year or more and the firm is carrying clients at numbers it would never quote today. Produces who moves and who does not, what each one goes to, who gets grandfathered and why, the order to tell them in, and the message for each. Also use for "we need to raise rates", "put our prices up", "this client is underpriced", "how do I tell them the retainer is going up".
Bailey DarlingCo-Founder, GiaOperations
Source check before sending
Audits a finished deliverable claim by claim before it goes to a client, and traces a number back to its origin when somebody on the client side says it is wrong. Lists every factual claim in the deck, doc, or sheet, ties each one to a named primary source, and marks the ones that cannot be sourced so they get cut or backed up before the thing ships. Use when the user says "/source-check", "fact check all of this", "fact check yourself", "where did we get [the number]", "how do you know that", "I need to be 100% confident in the source for every finding", "read the sources before quoting any of it", "before this goes to [client]", or when someone on the client side says a figure in a deliverable is wrong. Never sends anything.
Gary MagnoneFractional Operations Leader, HighriseRevOps1
Weekly funnel review
Use this skill on the same day every week to see where new business actually comes from, when the numbers live in five different places and nobody agrees what a qualified call is. Produces one row per week, appended to a running history: traffic and outbound by channel, calls booked against calls held, fit, signed work, and revenue split by segment, with the one thing that changed. Also use for "weekly numbers", "where are leads coming from", "how many calls did we hold", "refresh the funnel".
Bailey DarlingCo-Founder, GiaOperations
Work review
Reviews something a teammate or vendor built for a client (a page on staging or live, a dashboard, a PDF, a report, a page revamp) and writes the feedback note that goes back to them. Opens the real thing first, not a summary of it, checks it against the plan it was built from, splits the read into "the good" and "opportunities" ranked high, medium, and low, keeps it at the strategy level, and frames it so nobody on the team feels graded. Use when the user says "/work-review", "[person] is asking me to review [the thing]", "draft of the new [page]. thoughts?", "what's good, what's not so good, any high priority items to flag", "check out [person]'s updated dashboard", "is this page organized the way we planned", or pastes a teammate's handoff and asks what to say. Never sends anything.
Gary MagnoneFractional Operations Leader, Highrise