Skills library
Procedures written and tested by FloConnector, one job each: qualify a lead, chase an invoice, write the weekly update. Install one into your workspace in a click, or download it as a zip. All of them are free to copy and change.
12 skills
Read this before writing, rewriting or reviewing a standard operating procedure, a process document, a work instruction, or any "how we do this here" document meant for someone else to follow.
Read this before writing brand guidelines, capturing an existing brand into a reusable reference, or checking whether a design, document or piece of copy is on brand.
Read this before designing or restyling a web page, app screen, landing page or component, when a visual direction needs choosing, or when someone asks for a specific look such as neobrutalism, glassmorphism, bento or Swiss.
Read this before researching a keyword, deciding what page to write, or producing a content brief for a writer, and before promising that a page can rank.
Read this before following up a quote or estimate that has gone quiet, reviewing outstanding quotes, or deciding whether a quote is still live or should be closed out.
+1Read this before replying to, scoring, routing or recording a new enquiry, and before deciding whether a lead is worth a quote, a call or a polite decline.
+1Read this before reading a profit and loss, explaining a business's monthly results, answering how the business is doing, or preparing a management report from Xero or QuickBooks.
Read this before chasing an unpaid invoice, reviewing aged receivables, drafting a payment reminder, or deciding how hard to push a customer who has not paid.
Read this before running or reviewing a month end close, preparing management accounts, or checking whether a period is ready to be locked in Xero or QuickBooks.
Read this before reconciling a bank account, investigating unreconciled or uncoded transactions, chasing a balance that does not match, or preparing a reconciliation for review in Xero or QuickBooks.
Read this before creating or changing a ServiceM8 form, adding form questions, setting up conditional logic, or preparing the Word document template a completed form renders into.
Read this before creating, updating, scheduling, costing or completing a job in ServiceM8, or before adding anything to a job (contacts, badges, materials, labour, notes, payments).
How it works
Every skill is on its own page in full, files and all, so you can see exactly what your AI will follow before it follows it.
Add to FloConnector puts it in a collection, and every profile carrying that collection has it on its next call. Or download the zip for a client that installs from disk.
Keep updated follows our revisions and records each one in the skill's history. Make my own is a copy you edit freely.
A skill is a short document, in the Agent Skills format, that tells an AI client how to do one job: the steps, the rules, and the references it should read. Your AI loads it when the job comes up and follows it, so the work is done the same way every time.
Add to FloConnector installs the skill into one of your workspace's collections, where every profile carrying that collection can use it at once. Download zip gives you the same skill as a bundle for any client that installs skills from disk.
When you install a skill and choose to keep it updated, FloConnector rewrites your copy whenever we publish a new version, and records the change in that skill's history. Choose make my own instead and the skill is yours from that moment: it never changes unless you change it.
Yes. Every skill here is free to copy, edit, rename and redistribute, with no attribution (they are published under CC0). In FloConnector, install it as your own copy, or make a kept-updated copy editable later in one click.
Not to read or download. Installing in one click and keeping a skill updated need a workspace, and a free one takes a minute to set up.
Request a skill
Tell us the job. We write it, test it against the connector, and publish it here for everyone. Found one that could be better? Say so on the board.
