The AI reference
All 130 tools your AI can call on your office, read from the tools themselves, so this page is always current. Call start first, once a session, and pass its run_id on every call. Anything that emails, charges, publishes or changes what a person sees waits for your yes.
• For your AI
How the office works
- Yes cards: the owner taps yes in the office or on their phone; it then happens once. Busywork runs at once.
- Their three switches (Settings): pause automations, website offline, pause new bookings and sales. Only they flip them; when one is on, say so plainly and never work around it.
- Plans (Starter, Business, Growth) differ only in room; the trial is 15 days.
- The office may have a built-in chat, a small taster. Real work runs in their own Claude, ChatGPT or Claude Code, via this door. Bigger work: job_card.
- AATAM's method and links: read_tool guide, when a moment needs it. Real distress or danger: no tools, only care and real help (112 in Europe).
• Websites
Building a website
What any AI can build on a Company of One site, how, and the real limits. The steps are in the skill build-a-landing-page (its references page-craft.md and own-code.md) and run-my-website.
What you can build
- Pages and whole sites, in the brand's look: a new page with build-a-landing-page, the rest of the site with run-my-website, a small app of plain pages with build-an-app. deploy_site makes a private preview and answers its version; going live is propose site_publish { site, version } for exactly that version, then the owner's yes. deploy_site(read: true) lists the site's versions, pages and files; deploy_site(undo: true) brings back the version that was live before, as a new version, live after the same yes.
- A blog, a gallery, a directory, any list (content collections): define the collection with records_put (module collections; the owner says yes to a new or changed one), write its entries with records_put (module col-<name>, at once; only _status: ready shows), and two site files, _collections/<name>/entry.html and _collections/<name>/list.html. Placeholders: {{field}}, {{field|markdown}} (in text only), {{#field}}…{{/field}}, {{^field}}…{{/field}}; a value goes only in a page's text or a quoted attribute, an address only https, mailto or a path starting /, never in a script, a style or an on* attribute. Every deploy_site makes the public pages (/<name>/<entry>/, the list, categories, tags and a feed for a blog). read: "members" makes no pages: signed-in members read it from the site's own address, only those who bought its product when it has one. A form named in co1-app.json form_collections turns each visitor's send into a waiting entry; it shows only once you mark it ready and the owner says yes to the version. A field with format: "media" holds a media library piece: a picture is copied into the version, a film plays by a signed link.
- Site search on every site: each version carries its own search index; "search": true in page.json puts the box in the header.
- Your own code: any code on public pages, the industry way (site-wide head and footer, or a code block on one page), inline code included: trackers, widgets, embeds, 3D scenes. The yes card shows what code a version adds. Trackers wait for the visitor's yes (skill tracking, our cookie banner first).
- Members and sign-in live on the site's own locked members address: only the site's own files run there (no inline code, no scripts from other hosts), and it calls only the site's /api/v1 or a host the site allows. Card numbers are typed only on the secure payment page, never on the site.
- Never on any page: password, card, bank or one-time-code fields; a page that sends visitors to another site as it opens; a newsletter box ticked in advance; text shaped like a key in the site's files; code that mines cryptocurrency or comes from hosts known for malware. deploy_site refuses each and says what to change.
- Outside services: co1-app.json allowedHosts lists exact https addresses by kind (connect, form, img, media, frame, script, style, font; up to 20 each). On public pages any https host works; in the members area they count for pictures, films, fonts, frames, forms and calls, never for scripts or styles.
- Pictures and films from the media library: deploy_site(media: [{ path, asset_id }]) puts a picture's web-sized copy into the version. Films and sound stay in the media library and play from there: a product's or a lesson's film in the member area, a collection's film by a signed link.
- Forms, bookings, money and members through the site's own addresses below, each named with its permission in co1-app.json permissions.
- Moving in: skill move-in rebuilds the old site page by page with the same addresses, and co1-app.json redirects (up to 10,000) send each old address that must change to its new page. Their own domain: skill connect-my-domain (the owner adds it on their own screen). Tracking: skill tracking.
- Who builds it: building and changing pages is heavy work for the owner's own AI (Claude, ChatGPT or Claude Code). The office's built-in chat hands deploy_site and adopt_look to their own AI and does the small everyday edits; only a job from a job card that may deploy (on AI credits, after the owner's yes on its plan) runs them in the office.
What a page can call
Every site answers these on its own address (GET /api/v1 lists them live). A page uses only the ones its co1-app.json permissions name (up to 10 of: forms.submit, signups.create, classes.read, classes.book, courses.read, courses.enrol, checkout.create, checkout.withdraw, members.sign_in, content.read_own). Everything under /api/v1/members/ answers only on the members address.
| Call | Permission | What it does |
|---|---|---|
GET /api/v1 | none | This list. |
GET /api/v1/health | none | Is the gate up. |
POST /api/v1/forms/{form} | forms.submit | A form declared in co1-app.json; the person goes into People. A plain HTML form works (no key needed); want books a class or course (classes.book / courses.enrol). |
POST /api/v1/signups | signups.create | Sign up for an offer. Needs an Idempotency-Key. |
GET /api/v1/classes | classes.read | Upcoming classes with places left. |
POST /api/v1/classes/{id}/bookings | classes.book | Book a class. Needs an Idempotency-Key. |
GET /api/v1/courses | courses.read | Open courses. |
POST /api/v1/courses/{id}/enrolments | courses.enrol | Join a course. Needs an Idempotency-Key. |
GET /api/v1/calls | classes.read | The owner's open 1:1 times from now on. |
POST /api/v1/calls/{slot}/bookings | classes.book | Book one 1:1 time (a paid one answers where to pay). Needs an Idempotency-Key. |
POST /api/v1/calls/{slot}/confirm | classes.book | Back from paying for a 1:1 time: booked once it is paid. |
POST /api/v1/checkout/sessions | checkout.create | Where to pay for one product (then set location to the url). Needs an Idempotency-Key. |
POST /api/v1/withdrawals | checkout.withdraw | The EU withdrawal button, step one: the buyer gets an email with the confirm step. Needs an Idempotency-Key. |
POST /api/v1/members/sign-in | members.sign_in | Email a 6-digit sign-in code. |
POST /api/v1/members/verify | members.sign_in | Sign in with the code; sets the __Host-co1m cookie on this site. |
GET /api/v1/members/me | members.sign_in | Who is signed in and their bookings. |
POST /api/v1/members/sign-out | members.sign_in | Sign out on this device. |
GET /api/v1/members/me/content | content.read_own | What this member bought; nothing else. |
GET /api/v1/members/me/courses/{product} | content.read_own | A course this member bought: its ready lessons in order. |
POST /api/v1/members/me/courses/{product}/progress | content.read_own | Mark one lesson of a bought course done (or not); the course's progress back. |
POST /api/v1/members/me/links | content.read_own | A signed link to one paid film or download, for 2 hours. |
GET /api/v1/members/me/data | members.sign_in | The member's own data, to them only. |
POST /api/v1/members/me/billing | members.sign_in | The member's own Stripe page for their card, invoices and plan (then set location to the url). |
GET /api/v1/members/me/plan | members.sign_in | The member's own plans: each name, where it stands and when it renews or ends (none for one-off buyers). |
GET /api/v1/members/me/collections | content.read_own | The members-only collections this member may open in the live version (a product's only to its owners): each name and title. |
GET /api/v1/members/me/collections/{collection} | content.read_own | A members-only collection's entries in the live version (a collection for a product's owners: only to them). |
GET /api/v1/members/me/collections/{collection}/media/{id} | content.read_own | A signed link (2 hours) to one film in a members-only collection's entry. |
GET /api/v1/collections/{collection}/media/{id} | none | A signed link (2 hours) to one film on a public collection's page in the live version. |
POST /api/v1/members/me/erase | members.sign_in | Ask the company to erase this member (the owner says yes). Needs an Idempotency-Key. |
The real limits
- With the plan: pages, files, MB, forms, fields a form, products sold and collection pages a site, on every plan, are in the capability map below (Website and forms, Blog, gallery, any list, Selling). deploy_site(read: true) answers the company's own files, MB, pages, forms and products sold.
- The same on every plan: 50 collections a company, 5,000 entries a collection, 60 fields an entry, a collection's schema up to 18 KB, a members-only collection's ready entries up to 2 MB in a version; co1-app.json up to 10 permissions, 20 hosts a kind and 10,000 redirects.
- More room: a bigger plan, room in Billing where an add-on is shown, and a site's sizes are lifted on request. Need more? Email hello@companyofone.eu and we'll lift it. Tell the owner exactly that, with the number they reached.
• Capability map
Everything your office can do
Each job, why it is good, its room on every plan and the way past it. Read from the code, so it is always current.
Website and forms: own code, members area locked; Undo; private preview. agency-grade from their brand and six designed looks; their own code, trackers and 3D work, while members and sign-in stay on a locked address; the same addresses when they move in; a private preview before anything goes live, and every version can be undone.
deploy_site, people, page_edit · skills: build-a-landing-page, run-my-website, move-in, tracking
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| live sites | 1 | 1 | 3 | 10 | a bigger plan; +1 live site (Billing) |
| pages a site | 100 | 500 | 1,000 | 2,000 | a bigger plan; lifted on request |
| files a site | 2,000 | 5,000 | 10,000 | 20,000 | a bigger plan; lifted on request |
| MB a site | 250 | 500 | 1,024 | 2,048 | a bigger plan; lifted on request |
| MB a file | 25 | 25 | 25 | 25 | lifted on request |
| forms a site | 10 | 20 | 50 | 100 | a bigger plan; lifted on request |
| fields a form | 20 | 30 | 50 | 50 | a bigger plan; lifted on request |
Past it: a bigger plan or more room in Billing (+1 live site); sizes lifted on request; films and big photo sets in the media library.
Blog, gallery, any list: public or members-only, visitor entries, search. content collections: one design, many pages, as WordPress and Squarespace do, with categories, tags, a feed and search; members-only lists behind a product; nothing shows before the owner's yes.
records_put, deploy_site
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| collection pages a site | 100 | 500 | 2,000 | 5,000 | a bigger plan |
Past it: a bigger plan; until then, mark fewer entries ready, or keep long lists members-only.
Client portal, member area: built in: members sign in by emailed code. no extra app: members sign in on their site, and access is given or taken away on a yes.
deploy_site, member_access
Selling: Buy buttons, payment links, memberships; card and iDEAL. a pay link in one step, memberships and payment plans, paid into their own account.
payment_link, connector_call · skills: set-up-payments, sell-a-membership
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| things a site sells | 20 | 50 | 200 | 500 | a bigger plan; lifted on request |
Past it: a bigger plan, or we lift it on request.
Courses: lessons, films, progress. lessons with films, and each student's progress.
records_put, course_progress · skills: install-a-module
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| GB of streaming a month | 5 | 50 | 300 | 1,000 | a bigger plan; +100 GB video storage and +300 GB streaming (Billing) |
Past it: a bigger plan or more room in Billing (+100 GB video).
Classes and 1:1 calls: Classes and 1:1 calls. seats, a waiting list and class reminders, which keep going even while automations are paused.
records_put, booking_attendance · skills: add-a-class
People and email: custom fields, {{key}} in emails. every person's card with their emails, bookings and payments in one place.
people, thread, email_person, file_email, email_domain, domain
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| emails a day | 20 | 5,000 | 25,000 | 100,000 | a bigger plan |
Past it: a plan (Go live), then a bigger plan, for more a day; for many people, the newsletter or a sequence.
Newsletters, group emails: opted-in people only. their own look, sent from their own address, to opted-in people only.
propose · skills: newsletter
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| contacts you can email | 0 | 1,000 | 5,000 | 20,000 | a bigger plan; +5,000 contacts and +25,000 emails (Billing) |
| emails a month | 600 | 5,000 | 25,000 | 100,000 | a bigger plan; +5,000 contacts and +25,000 emails (Billing) |
Past it: a bigger plan or more room in Billing (+5,000 contacts).
Automations, email sequences: 15 ready-made ones to switch on. ready-made, each started on the owner's yes; one switch pauses them all.
automations, automation_enrol · skills: build-an-automation
Quotes, invoices, payments: refunds, receipts again. quotes the client accepts with one tap; invoices sent and reminded on the owner's yes; refunds back to the card they paid with.
invoice, invoices, quote, quotes, payments
Posts: Posts. one post card for every network, scheduled, each on the owner's yes.
propose, channel_connect_link
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| social accounts | 0 | 2 | 6 | 10 | a bigger plan; +1 social account (Billing) |
| posts a day | 0 | 10 | 25 | 50 | a bigger plan |
| X posts with a link a month | 0 | 10 | 30 | 100 | a bigger plan; +50 X posts with a link (Billing) |
Past it: a bigger plan or more room in Billing (+1 social account, +50 X posts).
Change your branding: brand.json feeds site, emails, invoices; then rebrand. one brand file feeds the site, emails and invoices, so a change shows everywhere.
looks, adopt_look, propose, deploy_site
Films and pictures: the media library, upload and share links, content plan and results. every file kept with its versions and reviewed on the phone; clients send files to a link with no account; share links expire by themselves.
publish_asset, list_assets, review_help, audit_metadata, get_asset, get_assets, update_asset, update_notes, archive_asset, restore_asset, list_deleted, list_jobs, job_status, fetch_original, record_spend, group_carousel, create_drop_link, list_drop_links, revoke_drop_link, list_submissions, get_submission, claim_submission, fetch_submission, update_submission, release_submission, finish_submission, create_share_link, list_share_links, revoke_share_link, content, results, record_post, record_packaging, channel_status, list_posts, start_work, update_work, finish_work, list_work
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| MB of media storage | 1 GB | 10 GB | 100 GB | 300 GB | a bigger plan; +100 GB video storage and +300 GB streaming (Billing) |
| film encodes a month | 5 | 200 | 200 | 200 | a plan (Go live) |
| film minutes (trial) | 2 | no limit | no limit | no limit | a plan (Go live) |
Past it: a bigger plan or more room in Billing (+100 GB video); on the trial, a plan lifts film minutes and encodes.
Make films and sound: cloud studio, one JSON or Motion JSON piece; film ready yes, then a post card. finished edits and sound with no software on their computer.
studio_job, studio_status, film_ready, propose, list_formats, list_looks, list_agent_music, record_feedback, list_feedback, absorb_feedback, link_feedback_result, ask_owner, submit_edit, get_edit, watch_edit, list_edits, add_edit_note, select_score
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| film minutes (trial) | 2 | no limit | no limit | no limit | a plan (Go live) |
Past it: a plan (Go live) for full-length films.
Own email, language, plan, connections: Own email, language, plan, connections. emails from their own address; the office in six languages; their own accounts connect in one tap, and every write through them waits for a yes.
email_domain, company_language, billing, connectors, connector_tools, connector_read, connector_call, secrets, channel_connect_link, status
Your domain with us: read only: the owner moves it. their whole domain looked after: the site, email sending and subdomains.
domain
Tasks, notes, files and records: the core list. everything is on the board and in the folder, so the next session picks up where this one stopped.
status, start, tasks, new_task, pick_up, log, done, wait, read, write, records_list, records_get, records_put, tools_for, read_tool, use_tool, records_delete, entries_put, task_edit
| Room | Free trial | Starter | Business | Growth | More room |
|---|---|---|---|---|---|
| seats in the office | 1 | 1 | 2 | 5 | a bigger plan; +1 seat (Billing) |
| people (trial) | 200 | no limit | no limit | no limit | a plan (Go live) |
| open tasks (trial) | 300 | no limit | no limit | no limit | a plan (Go live) |
Past it: a bigger plan or more room in Billing (+1 seat); on the trial, a plan lifts people and tasks.
Search, AI call log, owner settings: Search, AI call log, owner settings. one search across people, tasks, files and media; every AI call kept as a count; every setting the owner keeps for themselves explained with its link.
search, ai_calls, settings, memory, remember, recall, coach, guide, job_card, parts, open_part
Remember the owner: only while they switched it on (You › What your AI remembers). every chat starts where the last one ended: how they like to work, who they are, their goals and what happened lately, as short notes they can see, change or delete.
memory, remember
Her coach: Her coach. next steps, check-in, review.
coach, now, moment, move, programme, programme_start, immersive, review, today, waiting, made, office_read, office_do
Help and support: the guide first; still stuck, it's on us. an answer from the guide with its link, and a person when it is about money or the account.
help, report_problem
• Every process
114 step-by-step skills
management
add-a-view: Adds a view to one department of the dashboard (a list, a board, a calendar, a grid of posters, an inbox, numbers or a timeline) by writing one small view file, so what the owner wants to see shows up with no new code. Use when the owner asks "show my bookings as a calendar", "add a view of my suppliers", "I want to see X on Operations", or taps "+ view" on a department. Not for a new tool (build-an-app) or what customers receive (change-a-template).bring-my-business: Brings what a running business already has into the company, one kind at a time, through the paths that already exist: people as a people import, past invoices as an invoice import, files and films into the media library, offers into the offers page, students, bookings, posts and open jobs as records or tasks, and the tools that hold live data (payments, bookings, email, social) connected rather than copied. Converts whatever export the owner has, shows a sample, and asks one yes per batch. Use when the owner says "bring my business in", "import my clients", "move my stuff over", "here is my export", "I have a spreadsheet of students", during set-up path B (steps B5 and B6), or when a file of past data arrives. Not for planning the whole move (move-in).coach: How you talk with the owner: the answer first, one small next step, honest encouragement and help in hard moments. Use when you reply to the owner in a chat (read it once a session, before your first reply), when the morning brief writes today's move or the Friday scorecard writes how you showed up, or when the owner says they are stuck, tired, overwhelmed, scared to send or publish, worried about money, facing an upset client, or "I can't do this". Not for the brief (morning-brief) or the week's plan (weekly-plan).company-manager: The role every session without a task starts in: reads the central brain and the whole board, decides which department and skill the owner's request belongs to, makes that task with its skill, then does it now or leaves it for the department; answers questions about the company from the board, the scorecard, the numbers and the outputs across every department. Use when a session starts with no task, the owner just says what they want ("can you...", "where are we with...", "I need..."), or they tap "What do you need?" or "Talk it through". Not for work a department skill already covers: route it there.customer-research: Finds real demand for what the company sells or could sell, from public conversations, reviews, forums and complaints, and maps the competitors, using the AI app's own web search or deep research; writes a short demand map with real quotes and their links into the company folder, which spot-the-offer and weekly-content then use as questions to the owner. Use when the owner asks "what do people actually want", "research my market", "who else does this", "what are people complaining about", or before spotting a new offer. Not for choosing the offer (spot-the-offer) or where to find clients (find-avenues).design-system: Builds and keeps the company's own design system from its brand: colours for light and dark, one type scale, space, corners, icons, the core pieces (buttons, cards, forms, tables, navigation, hero, pricing, footer, email and invoice layouts), picture and motion rules and do and don't, with a one-page live preview, all proposed for one yes. Use when setup's look step is open, the owner says "make it look like us", "here is my logo", "change our colours", "update my invoice look", "our brand", "our pages look generic", or another skill finds no look to follow. Not for one page or picture (high-end-design, make-a-graphic).email-assistant: Handles an email that came in to the company's own address (hello@), the way its kind needs, ending in one real deliverable for the owner's yes or a filed record. Use when a task was made from an email that came in (job email-assistant, a task whose log says "An email came in"), when start shows emails that came in, or the owner says "deal with my email", "what came in" or "answer hello@". Not for the owner's own Gmail or Outlook (check-inbox).follow-my-path: The owner's weekly coach on their path: says where they are (the week, what is done, the next milestone), marks milestones reached from what the company already counts, and turns this week's one to three steps into tasks, each said as what it gives them. Use when start has a path block and the week's plan is being made (weekly-plan calls it first), when the owner says "where am I on my path", "what's my next step", "am I on track", or after a milestone (a first offer live, a first payment). Not for choosing or changing the path (start-a-path) or the whole week's plan across departments (weekly-plan).grill-me: Interviews the owner by voice, one short spoken question at a time, each with a recommended answer, saves every answer straight away to brain/interviews/ (with the key decisions and the why behind them), and at the end sends each change to its one owner: the direction through update-direction, rules/ as proposals, department pages written. Use when a "Teach your company" task comes up (job grill-me), a setup step called interview, or the owner says "interview me about X", "grill me", "talk it through", "continue my interview" or "grill me again about X". Not for one change to the direction (update-direction) or goals (set-goals).high-end-design: How everything you design (pages, emails, invoices, posts, graphics) looks like a top studio made it: start from one of the six looks, match the owner's reference, avoid design slop and check the phone and desktop pictures before the owner sees it. Use when you build or change anything people will see, with the work's own skill, or when the owner says "make it look better", "it looks generic", "like this site", "update my invoice look", "change our brand" or "our colours". Not for the brand's design system itself (design-system).make-it-yours: Makes a department the owner just turned on theirs, from the centre (their direction, voice, offers and look): reads the kit's standard page, views, templates and emails for that department, writes the page and views in the owner's words and proposes the templates and emails, together on one task for one answer, never over anything they already changed, and ends with the department's page working. Use when a department's setup step "yours" is open (its setup job), right after a department is turned on, or when the owner says "make Marketing ours", "this page doesn't sound like us". Not for setting up the whole company (set-up-my-business).morning-brief: Writes the owner's morning brief from the board, about ten lines that take 30 seconds to read: what needs them, what moved, and the one thing that matters today. Use when the weekday "Morning brief" task comes up (job morning-brief), or the owner asks for a brief, "what's happening" or "what needs me today". Not for the week's plan (weekly-plan) or the Friday scorecard (weekly-review).move-in: Moves a running business in, the staged way: day one it connects what they already have and starts working here, then brings their contacts over, then rebuilds their website fresh in Co1 page by page to match the old one (look, words, structure, the same addresses, redirects where one must change), with forms, bookings and payments on our own modules, and moves the domain last, when they are happy. Use when the owner says "I already have a business", "move my business in", "here is my website", "move my site from Squarespace", "move my newsletter over", "can we switch now?", or when set-up's `Stage:` line says running. Not for a business starting from scratch (start-a-path) or a one-off import of contacts or invoices with no move planned (bring-my-business).next-90-days: Looks back on the last 90 days with the owner, then drafts the next 90: one to three outcomes with dates and a number each, the milestones each department takes toward them, the routines that carry it, and what is dropped on purpose; keeps her living plan (plans/90-days.md) and the quarter's review (such as reviews/2027-Q1.md), with the new outcomes proposed into direction.md. Use when a period ends or its outcome dates have passed, or the owner says "plan the next quarter", "what's next for the business" or "set new goals". Not for this week (weekly-plan) or one change to direction (update-direction).prepare-a-decision: Turns a call only the owner can make into a one-screen decision card: the question, the date it is needed by, two or three real options with what each costs and brings, a clear recommendation, what is in it for the owner, and what happens on a yes. Use when a task asks the owner to choose (a price, a new offer, a client, a date, a tool, what to drop), when work is stuck waiting on a choice, or the owner says "help me decide" or "what should I do about X". Not for work that needs no choice from the owner.roi-card: Keeps the owner's ROI card, management/roi.json, which the dashboard shows: for each piece of work the AI now does, the hours a week it took before and after, since when, and the week and year totals, always marked as the owner's own estimate. Use when a routine or process was just automated (after automate-a-routine), at the end of a month, or when the owner asks "how much time am I saving", "is this worth it" or "update my ROI card". Not for the weekly scorecard (weekly-review).set-goals: Walks the owner through setting each department's top three goals, department by department: what the department is building towards, the number the company counts to measure it, the target and the date, in the owner's own words, then proposes each department's goals.md for a yes. Never invents a goal. Use when the Management setup step "goals" is open (job setup:management:goals), when a goals file still says "Set at setup with your manager", or when the owner says "set my goals", "what are we aiming for", "change Marketing's goals". Not for the next 90 days of outcomes (next-90-days).set-up-my-business: Guides a first-time owner (or someone bringing a business they already run) through setting up their company, one small step at a time, from what is really in the company: the AI does the setup and the owner only answers and says yes. First the direction and the voice, then their own page and first post to look at, then goals, accounts, the first week and their own ways of working. Done steps are skipped and nothing is asked twice. Use when the owner says "set up my business", "start here", "help me get going", "bring my business in", when a new company has just been made, or when the dashboard's Start here step is tapped. Not for moving a running business in (move-in) or choosing a path (start-a-path).sort-the-inbox: Hands each note the owner added as "Not sure" to the department it belongs to, in the owner's own words, splitting notes that hold several things and asking one question when a note is unclear. Use when Management has open tasks that are raw notes from the owner (typed or spoken on the phone), or the owner says "sort my notes" or "file this". Not for the owner's email (check-inbox).spot-the-offer: Finds the offer that AI now makes possible for this owner, drawn out of them: candidates built only from offers, wishes and strengths they named and what their clients really ask for, scored together, one recommended, checked by a second look, shaped into rules/offers.md with a first small test, all for the owner's yes. Use when the owner asks "what should I sell next", "find my offer", "new offer ideas", when direction.md has an outcome like "choose the next offer". Not when the owner already knows the offer and its price: then grill-me's "What we sell" branch writes it.start-a-path: Helps the owner choose the path that fits how they want to be paid (creator and personal brand first; more paths come), then sets up its starter kit in one go, for one yes: the skills, the website pages in their look, the content lists and the ready films, plus the weekly steps and milestones up to the first payment. Use when the set-up step "path" is open, when the owner says "what should I do to get paid", "pick a path", "set up the starter kit", "I want to grow a personal brand", or when start has no path block and the owner asks where to begin. Not for the weekly check on a path already chosen (follow-my-path) or moving a running business in step by step (move-in).update-direction: Turns something the owner said (a note, a decision, a correction, an answer in an interview) into a change to direction.md, the central brain every department reads first, proposed as a before and after for the owner's yes. Use when the owner says "change our direction", "we don't do X any more", "new goal for this quarter", "add this to the direction", when a note or a decision card changes who we serve, what we sell, why us, this period's outcomes or what we never do, or when an outcome's date has passed. Not for a whole new period (next-90-days).weekly-plan: Drafts this week's plan on Monday: one suggested focus tied to the direction, the few tasks in play, what each department will produce, and what waits until later, with a task for the owner to choose the focus. Use when the Monday "Weekly plan" task comes up (job weekly-plan), or the owner says "plan the week", "what should I focus on this week" or "what's in play". Not for the Friday scorecard (weekly-review) or the daily brief (morning-brief).weekly-review: Writes the weekly scorecard: for each department, what was done, what was missed and why, measured against its outputs and this week's plan, plus the one change to make next week. Use when the Friday "Weekly scorecard" task comes up (job weekly-review), or the owner asks "how did the week go", "what did we get done" or "what slipped". Not for next week's plan (weekly-plan) or the ROI card (roi-card).your-account: Answers the owner's questions about their own Company of One account, from what the office knows (the plan and trial line `start` gives), and hands them the one screen where they act themselves: picking a plan (Go live), two-step sign-in and signing out everywhere, exporting everything, erasing the company, and the list of what their AI did. Never does those owner-only actions itself. Use when the owner asks "how long is my trial", "how do I keep going", "is my plan paid", "why is my office read-only", "turn on two-step", "sign me out everywhere", "export everything", "erase my company", "what did my AI do", "disconnect my AI", "let support look". Not for more room on the plan (add-more-room).
marketing
build-a-landing-page: Builds the company's pages people see (a landing page for an offer, a Classes page, a Course page) in the owner's own look and words, with real proof, a sign-up form and a payment or booking link when there is one; shows it as pictures first, then puts it online on the company's website after their yes. Use when the owner says "build my landing page", "I need a page for this offer", "redo my website's front page", when the Start here step asks for a draft page, or when an offer, its classes or its course change and the page must follow. Not for changing the rest of the site (run-my-website).build-an-automation: Builds one automation as a single JSON file in rules/automations/ that runs by itself after the owner's one yes, from scratch or from one of the 15 ready-made sequences (references/ready-made.md: reminders, no-show, review ask, win-back, welcomes, payment care). Something that happens starts it (a sign-up, a purchase, a membership change, a tag, a booking, a lesson done, or a start by hand), and it does steps in order (wait, email, tag, start or stop another automation, a note to the owner, a task, an if). Use when the owner says "after someone buys the course, send lesson 1 now and lesson 2 two days later", "welcome everyone who signs up", "when a payment fails, remind them", "tag people who book a call", or when a task asks for an automation or a sequence. Not for one email to everyone now (newsletter) or new words in an existing email (change-a-template).build-your-showreel: Turns the owner's best past edits into a showreel and a set of work pages: three to six edits picked with them from the media library, each with what it was for and what it changed, saved as draft entries for the website, and one short showreel film made in the studio from the kit's piece. Use when the owner says "help me show my work", "make my showreel", "build my portfolio", when a path step names it, or before reaching out to clients when the edits collection is still empty. Not for editing a new film (video-edit, reel) or posting it (weekly-content).build-your-sound-portfolio: Turns the owner's best sound work (soundscapes, sound for other people's films, podcast sound, music beds) into a portfolio people can listen to: three to six pieces picked with them from the media library, each with what it was for and what it changed, saved as draft entries for the website, and one short teaser film made in the studio from the kit's piece. Use when the owner says "help me show my sound work", "build my sound portfolio", "make a teaser of my soundscape", when a path step names it, or before reaching out to clients when the sounds collection is still empty. Not for designing a new sound piece itself or posting the teaser (weekly-content).carousel: Makes a swipeable carousel (7 to 10 slides, 4:5) from one idea, in the company's brand and voice: the words first, as a ladder that pulls people to the last slide, then the slides built and checked at full size, published to the media library and proposed as one post per channel. Use when the week's plan asks for a carousel, the owner says "make a carousel", "turn this into slides" or "a swipe post", or a task names job carousel. Not for one picture (make-a-graphic) or a single text post (write-a-post).change-a-template: Changes what the company's customers receive, in one place: an email's words or frame, the invoice layout, a page, from the owner's request and the centre (direction, voice, design system, brand.json), proposed as the new template file with a before and after preview for one yes. What the preview shows is exactly what is sent. Never changes the company's details without the owner's own words. Use when the owner taps "Change with your AI" on "What your customer gets", or says "make the invoice look like us", "the welcome email sounds stiff", "check my welcome email", "put our logo on the emails", "change the booking confirmation", or when an offer's dates change and the welcome email must follow. Not for a new email sequence (build-an-automation) or the company's whole look (design-system).content-results: Writes Marketing's one-screen weekly result: what went out against the plan, the real numbers each piece got, what worked and why (marked as a guess), what failed, and three moves for next week, so the next week of content builds on what worked. Use when the Monday "What worked last week" task arrives (job content-results), or when the owner asks "what worked?", "how did the posts do?" or "what should we post more of?". Not for planning next week's posts (weekly-content).content-review: Gives a fresh, friendly-viewer verdict on a piece of content at one step (brief, script, beat plan, collage, sound or final), and turns the owner's verdict in the Review tab into a written fix to the skill that made it (logged before and after). Use when a production skill reaches a gate and needs a reviewer who did not make the piece, when the owner says "review this", "check this film before I see it", or when the owner has given a verdict or notes on a film, reel, short or carousel and the lesson should go into the skill. Not for making the piece (the production skills) or approving it: only the owner approves.documentary-edit: Makes a finished story documentary or long explainer film (16:9, as long as the story needs) from a brief: plan, script (an internal draft), beat plan, a word-timed edit built from the documentary starter, one true fact on screen, sound, a reviewed render, published to the media library for the owner's verdict. Use when the owner asks for a documentary, a YouTube film that tells a real story, an explainer "like" a top channel, or when youtube-film hands over a story film to build. Not for a short vertical film (short-film), Shorts cut from a finished film (documentary-shorts) or an offer explainer (explainer-film).documentary-shorts: Cuts a finished film into vertical Shorts (as many as the cut list names, three by default) (9:16, about 25 to 40 seconds each) that each stand alone for a stranger, recomposed for the phone with the Short starter (hook on top, the film's scenes rebuilt for 9:16, word captions and a moving end card), checked, and published to the media library next to the film for the owner's verdict. Use when shorts-from-film hands over the cut list to build, or the owner asks to re-cut Shorts already planned. Not for titles, times and posting the Shorts (shorts-from-film) or a new short film (short-film).explainer-film: Makes a motion explainer for an offer, a product or a course (16:9, about 30 seconds to 5 minutes) with the explainer starter: one relatable person moving through real moments of their week, the offer appearing where it fits their life, one continuous world with a camera that never cuts, every move keyed to the spoken words, checked as a collage and published to the media library on its task. Use when the owner wants an explainer for an offer, a launch film, a course trailer, "a film that shows what we do", or when youtube-film hands over an explainer to build. Not for a film from one recording (reel), a short story film (short-film) or graphics on a talking video (motion-inserts).film-script: Writes the brief and the spoken script for one film (a YouTube film, a launch film or a short film) in the owner's voice, with a first 10 seconds that makes a stranger stay, one message, one ask and a source under every fact. The script is an internal draft: written and logged, never proposed; the owner's yes comes on the finished film. Use when a film needs its words before anything is made, when youtube-film or short-film reaches its script step, or when the owner says "write the script", "plan the film" or "what should the film say". Not for building the film (the production skills, youtube-film) or a single post (write-a-post).find-your-voice: Finds how the owner really sounds, from their own writing and a few short questions, and turns it into the company's voice page (three words, what we say and never say, real example lines, the language), proposed as a change to rules/voice.md. Use when the Marketing setup step "voice" is open (job setup:marketing:voice), when `rules/voice.md` still says "To fill in", or when the owner says "this does not sound like me" or "set up my voice". Not for writing a post (write-a-post) or the company's look (design-system).make-a-graphic: Makes one designed still picture in the company's own look (a post picture, a quote card, a cover, a film thumbnail, the still slides of a carousel), built from a starter with the design system and checked before it goes to the media library for review. Use when a post needs a picture, when carousel needs still slides, when package-a-film needs thumbnails, or when the owner says "make a graphic", "a quote card", "a cover for this" or "a thumbnail". Not for a whole carousel (carousel) or moving pictures (motion-carousel, reel).motion-carousel: Builds a swipe carousel where every slide is a short looping video whose motion acts out its idea (4:5, about seven slides of six seconds), from approved slide words, with the moving carousel starter: one precise situation on the cover, a map, the moment, what it costs, the turn about two thirds in, one small step, an honest invitation; checked as a collage and published to the media library as one carousel on its task. Use when the carousel skill hands over slides that should move, or the owner asks for "a moving carousel", "animated slides" or "a carousel people want to swipe". Not for still slides (carousel, make-a-graphic) or a film (short-film, reel).motion-inserts: Adds animated graphic inserts to an existing talking video at the exact moments a picture earns its place (a number, a list of three or more, a process, a contrast), with every number researched and sourced, one design brief per insert in the company's look, built from the motion inserts starter, checked as a collage and published to the media library on its task. Use when the owner says "add graphics to this video", "animate the numbers in my talk", "which moments need a visual", or when video-edit or youtube-film needs inserts on a recording. Not for editing the talking video itself (video-edit) or a film from one memo (reel).music-video: Turns a song the company owns into a music or lyric video that never stops moving and is locked to the music (every sung word on screen when it is sung, every shot changing on a bar, things pulsing on the beat, one through-line in every shot), built from the music video starter, with three look stills (you pick one and go on; the owner can swap it with a note), checked as a collage and published to the media library on its task. Use when the owner sends a song or jingle and says "make a music video", "lyric video", "animate this song", or when youtube-film hands over a song. Not for a film from a spoken recording (reel, video-edit).newsletter: Writes the company's newsletter issue in the owner's voice, built from the period's best posts and news, with a subject people open, one useful thing to try, short news and one ask, shown as the email will arrive and sent to everyone who agreed to get it after the owner's yes. Use when the newsletter is due (the Marketing page says how often), when the owner says "write the newsletter", "draft this month's email" or "send something to the list", or a task names job newsletter. Not for a single post (write-a-post) or an email sent automatically after a sign-up (build-an-automation).package-a-film: Makes a finished film clickable: three genuinely different title and thumbnail pairs, each thumbnail made and put in the media library, recorded as the film's packaging for the owner to pick, plus the YouTube description with chapters, credits and one ask. Use when youtube-film reaches its packaging step, when a film in the media library has no title options yet, or when the owner says "give me titles", "make the thumbnail" or "package this film". Not for making the film itself (youtube-film, documentary-edit) or one picture for a post (make-a-graphic).reel: Turns one recording from the owner (a voice memo or a short talking video) into a 30 to 60 second vertical motion reel, built from the reel starter: the recording kept exactly as it is, a beat plan keyed to the spoken words, something moving every 2 to 3 seconds, captions, checked as a collage by a fresh reviewer, rendered and published to the media library on its task. Use when the owner sends a voice memo or clip and says "make a reel from this", "animate this recording", or when short-film hands over a recording to build. Not for a long talking video (video-edit) or a scripted film (short-film, explainer-film).reply-to-comments: Drafts short replies, in the owner's voice, to comments and direct messages on the company's posts, each sent only after the owner's yes and never posted automatically. Use when the owner pastes comments or DMs, says "answer the comments", "reply to my DMs", or the connected social scheduler shows comments waiting. Not for a new post (write-a-post) or a complaint that needs putting right (handle-a-complaint).run-my-website: Runs the company's whole website on Company of One from the chat: adds, changes, renames or removes a page, keeps the menu right, puts the forms in (sign-up, newsletter, contact, booking, buying, member sign-in), reads the site back, and puts each change live after the owner's yes, with Undo. Use when the owner says "add an about page", "change the contact page", "take that page down", "what's on my site?", "undo that", or any change to a page that is already online on Company of One. Not for a new landing page for one offer (build-a-landing-page).short-film: Makes one new short vertical film (30 to 60 seconds) from an idea or from a recording the owner already has: a script whose first second hooks, the owner's own voice or face, motion that acts out the moment, captions, a fresh viewer's check, then posts proposed for the reel channels. Use when the week's plan asks for a reel, when the owner says "make a short film" or "a reel about this", or sends a voice memo or phone video to turn into a reel. For clips cut from a longer film, use shorts-from-film. Not for Shorts cut from a finished film (shorts-from-film), a long YouTube film (youtube-film) or an offer explainer (explainer-film).shorts-from-film: Cuts vertical shorts from a finished film (three by default; the cut list's count wins), each standing alone with a hook in the first second, publishes each to the media library linked to its film, and proposes each for YouTube Shorts and Instagram on its own day. Use when youtube-film adds its "Shorts from" task, or when the owner says "make shorts from this film" or "cut this into reels". Not for a new short film (short-film); the cutting itself is documentary-shorts.sort-media: Gives every older media piece that has no project, series or department one of each, written as one list on the task and then applied (internal tidying, no yes needed), so the To sort album empties and every piece sits in its album. Use when the owner taps "Sort them" on Media's To sort album, or asks to sort, tidy or organise older media. Not for new pieces or removing media.structure-your-knowledge: Turns what the owner already knows into a tidy set of private notes, grouped by topic (stories, how-tos, opinions, questions people ask, results), so every post, newsletter issue, call and first product starts from their own material instead of a blank page. Use when the owner says "help me organise what I know", "what could I write about", "structure my knowledge", when a path step names it, or before the first newsletter issue when the knowledge notes are still empty. Not for writing the post or the newsletter issue itself (write-a-post, newsletter).tracking: Adds the owner's tracking to their Company of One website, the Kajabi way, by pasting the code into the site's head, footer or a page's code block. That covers Google Analytics 4, Google Tag Manager, the Meta pixel and other pixels (TikTok, Pinterest, LinkedIn), lead events from the thank-you pages and purchase events from the buyers' thank-you page. Our own cookie banner goes first, so nothing loads before the visitor's yes (EU law). Use when the owner says "add Google Analytics", "put my Facebook pixel on", "track sales from my ads", "add Tag Manager", "we need a cookie banner", or a moved site had tracking before. Not for building pages (build-a-landing-page, run-my-website).video-edit: Edits a talking video or voice recording from the owner into a polished film (16:9 or 9:16) with the talking video starter: the owner's own words and natural pace kept, dead air trimmed, the framing changing at sentence ends, full-frame explainer scenes cut in on the key points, captions, an even sound, checked as a collage by a fresh reviewer and published to the media library on its task. Use when the owner sends a talking video, a video call or a long voice recording and says "edit this", "make this look good", or when youtube-film or short-film hands over a recording to edit. Not for graphics on top of a talk only (motion-inserts) or a 30 to 60 second reel from a memo (reel).weekly-content: Turns one idea into a week of marketing in the owner's voice: a short week plan, the week's posts each written for its own channel and proposed with its exact time, and a task for the week's carousel and one for its short film (unless the Marketing page sets another week shape). Use when the Monday "Weekly content" task arrives (job weekly-content), or when the owner says "make content from this idea", "plan next week's posts" or "I need posts for next week". Not for a single post (write-a-post), a newsletter (newsletter) or last week's numbers (content-results).write-a-post: Writes one post for one channel (LinkedIn, Instagram, Facebook, X or Threads, or the text that goes with a reel) in the owner's voice, opening on a moment the customer knows and ending with one ask, then proposes it with its exact time. Use when the owner asks for a single post ("write a LinkedIn post about this", "a post for Thursday"), when weekly-content writes each post of the week, or when a carousel or film needs its caption. Not for a week of posts (weekly-content), comment replies (reply-to-comments) or a carousel (carousel).youtube-film: Takes one film idea all the way to a YouTube post waiting for the owner's yes: brief and script (an internal draft, no yes needed), the owner's voice, the film made by the production skill that fits from the company's approved film kit and reviewed at each gate, published to the media library, packaged with three titles and thumbnails, then proposed with the title the owner picked. Use when the owner adds a film idea to Marketing, says "make a YouTube film about this", asks for a launch film or an explainer, or a task names job youtube-film. Not for a short vertical film (short-film) or only titles and thumbnails for a finished film (package-a-film).
money
add-more-room: Helps the owner get more room on their Company of One plan (more contacts and emails, social accounts, video, seats, sites) or pay yearly instead of monthly, by explaining the choices with their prices and handing them their plan page, where they see the price and say yes. Use when a limit card says "add more or wait", a notice says a limit is at 80% or 100%, or the owner says "I need more contacts", "add a seat", "another site", "upgrade my plan", "pay yearly" or "what does my plan include". Not for plans the company sells (sell-a-membership).draft-invoice: Drafts a correct invoice for work that was done (the right client, the items and price as agreed, the next number, the due date from the payment terms, how to pay exactly as the owner set it) and proposes sending it for the owner's yes. Use when a piece of work is delivered or a Money task says "Invoice Anna", or the owner says "invoice Anna" or "bill them for". Not for a late invoice (invoice-reminder) or a quote (send-a-quote).file-receipt: Files the receipts, bills and payouts the owner adds (a photo, a PDF, a typed or forwarded note) as tidy lines with date, supplier, what, category, amount and VAT, and asks about anything it cannot read. Use when the scheduled Friday task arrives (job file-receipt), or the owner says "file this receipt", "here's a bill" or "file my receipts". Not for the bank statement (month-end-check).invoice-reminder: Finds invoices that are open past their due date plus the owner's waiting days, and drafts one short, kind reminder for each, proposed as an email for the owner's yes. Use when the scheduled Monday task arrives (job invoice-reminder), or the owner says "chase my invoices", "who hasn't paid" or "send a reminder to Anna". Not for a new invoice (draft-invoice).make-a-discount-code: Makes a discount code buyers type on the company's own checkout page (its Buy buttons, payment links and join links), after the owner's yes; lists the codes and how often each was used; and stops one. Use when the owner says "make a discount code", "a coupon for my launch", "20% off for my newsletter", "stop that code" or "which codes are running". Not for a lower price on one invoice (draft-invoice).money-in-a-minute: Writes the owner's money card from the company's own records: paid in and out this month, what clients owe and what the owner owes, what is late, how many months the money lasts, and the one thing to do next. Use when the scheduled Monday task arrives (job money-in-a-minute), or the owner asks "how's my money?", "what's open?", "how long does my money last?" or "money in a minute". Not for closing the month (month-end-check).month-end-check: Closes the month: matches the bank statement the owner downloaded against the receipts and invoices, marks things paid only with a matching bank line (an invoice through `invoice(action: "paid", number, paid_on, run_id)`), lists missing receipts and unknown payments as short questions, hands late invoices to reminders, and writes a month summary (and at quarter end, a tidy list for the accountant). Use when a new month starts, the owner drops a bank statement, or says "check my books", "close the month" or "get it ready for my accountant". Not for a quick look at the money (money-in-a-minute).pay-back: Pays a buyer back through Stripe after the owner's yes (all of a payment or part of it), for a buyer who withdrew within their 14 days or a refund the owner decides on, and walks the owner through a dispute or a payout that failed, which are their own steps in Stripe. Use when a "Pay back …: a buyer withdrew" task arrives (job pay-back), an "Answer the dispute" or "Fix your bank details in Stripe" task arrives, or the owner says "refund Anna", "give them their money back" or "pay back her order". Not for a complaint before a refund is decided (handle-a-complaint).sell-a-membership: Sets up a plan people pay for every month or year (a membership, a retainer, course access) in the company's own Stripe, with its join link, the page where members manage their card or cancel, and access that follows payment; and drafts a friendly note when a member's payment fails. Use when the owner says "I want to sell a membership", "set up a monthly plan", "a retainer for my clients", "paid access to my course", "how many members do I have", or when a "Payment failed" task arrives (job sell-a-membership). Not for a one-off sale (set-up-payments).set-up-payments: Sets up card payments with Stripe for the company, step by step and safely: explains what Stripe is for, has the owner connect Stripe on their set-up page (no keys, ever), makes a first payment link in test mode shown to the owner before anything is live, adds Stripe to the systems list, and checks that a test payment reaches Money; also makes the product a Buy button on the company's own page sells. Use when the owner says "I want to take payments", "set up Stripe", "how do people pay me online", or when the Money setup step for payments is open. Not for a monthly plan (sell-a-membership).
operations
add-a-class: Puts a class on the company's class calendar (the Class booking module): its name, day, time, place and number of places, as a record the Classes view shows and book-a-class books into. Use when the owner says "add a class", "put the Tuesday yoga class on the calendar", "we have a new workshop date", or lists the term's classes. Not for booking a person in (book-a-class).book-a-class: Books a person into a class when they did not book themselves (an email request filed by check-inbox, the owner's "book her in"); a seat that comes free goes to the first person waiting by itself (the company's server, with their email), so this skill never moves the waiting list: checks the places, records the booking or a waiting-list place the same safe way the Classes page does, and proposes a short confirmation for the owner's yes (a booking made by hand has no automatic email). Bookings made on the Classes page are instant and confirmed at once by the company's server, with no yes; this skill never redoes or re-confirms them. Use when a booking request arrives by email or note, or when the owner says "book her in". Not for adding a class (add-a-class) or cancelling (cancel-a-booking).cancel-a-booking: Cancels a person's place in a class (the Class booking module): frees their seat, recounts the places left (the first person waiting then gets the place by themselves, with their email), and proposes a short note to the person for the owner's yes. Safe to repeat. Use when someone replies to their confirmation to cancel (an email filed by check-inbox), or the owner says "cancel her booking", "she can't come on Tuesday". Not for booking someone in (book-a-class).client-handout: Turns the owner's notes from a session, workshop or piece of work into a one-page handout for that client, in the owner's voice, proposed to send the same day. Use when the owner adds notes after working with a client, or says "make a handout for Anna" or "send them the notes". Not for a weekly update (weekly-client-update) or the welcome after a yes (onboard-a-client).client-terms: Writes the company's standard client terms (what is included, payment, cancelling and moving dates, what the client provides, who owns what) in rules/terms.md, from the owner's own answers, as one page for the owner's yes. Use when proposals or bookings need terms the folder does not hold, draft-proposal or onboard-a-client asks for them, or the owner says "write my terms", "what is my cancellation policy" or "update my payment terms"; not legal advice, and not the invoice's how-to-pay lines (money/payment-terms.md). Not for one client's proposal (draft-proposal).delivery-checklist: Makes the before, on-the-day and after checklist for one piece of work, with a date and an owner on every line, and keeps the lessons for next time. Use when a piece of work is booked or coming up, prepare-the-work asks for a checklist, or the owner says "make a checklist for the March workshop". Not for the whole week (prepare-the-work) or how the work is done in general (write-a-process).onboard-a-client: Welcomes a client who said yes to paid work with one warm email of what happens next, and sets up their client file and every next step on the board. Use when a proposal is accepted, a booking for one-to-one or team work comes in, or the owner says "onboard Anna" or "they said yes". Not for a newsletter or course sign-up (welcome-a-sign-up).plan-your-craft-tool: Writes the one-page plan for the owner's own craft tool: the one job it does in their way of working, what goes in and comes out, what stays theirs, and checks they can see, so one AI can build it, a second can check it and the owner can approve it. Use when the owner wants their own tool for their work, says "I keep doing the same prep every time" or "plan my craft tool", or the Operations setup asks for the craft tool. Not for building the tool (build-an-app) or writing down a process (write-a-process).prepare-the-work: Prepares every piece of the week's work around the owner's craft (what it needs, by when, drafts made) and shows the owner only what is theirs to do. Use when the scheduled Monday task arrives (job prepare-the-work), or the owner says "prepare this week" or "what do I need for next week". Not for one piece's checklist (delivery-checklist).write-a-process: Turns how the owner actually does a recurring piece of work into a short page of steps anyone can follow, with who does each step and what done looks like. Use when the owner explains how they do something, says "write down how I do this" or "make this a process", or a setup step asks how the work is delivered. Not for a checklist for one booked piece of work (delivery-checklist).
sales
bring-in-bookings: Brings the calls people booked on the owner's own Cal.com onto the board: each new booking becomes a person card and a call task (prepared by discovery-call-prep), a moved call moves its task, a cancelled call closes it. Sends nothing to anyone. Use when its weekday routine runs, when the owner says "check my bookings", "did anyone book a call", or right after Cal.com was connected. Not for preparing the call itself (discovery-call-prep).build-a-funnel: Sets up a simple funnel for one offer with the owner, from the tools the company already has: the landing page, the sign-up with its welcome email, a short series of two to four emails in the owner's voice that runs on one yes, then the offer with its Stripe payment link. Each part is a proposal for the owner's yes; nothing new is built. Use when the owner says "set up a funnel", "I want people who sign up to hear from me and then buy", "an email series for my offer", or when the Start here path suggests one. Not for checking on a funnel that already runs (run-the-funnel).call-summary: Turns the owner's notes or a transcript of a sales call into a short write-up, a thank-you email with the agreed next steps for the owner's yes, and a task for every promise we made. Use when the owner shares call notes or a transcript, or says "write up my call with Anna"; not for preparing a call that has not happened yet (discovery-call-prep).discovery-call-prep: Writes a one-page call brief for the owner before a first call with someone who might buy: who they are, what they asked, what the call is for, five questions, the offer that may fit, likely worries and the next step to suggest. Use when there is a "Prepare the call with Anna" task, or the owner says "prep me for my call with Anna"; not for writing up a call that already happened (call-summary).draft-proposal: Writes a one-page proposal (what changes for the client, what we do, how it runs, the price from the company's own offers, the next step) and a short cover email, for the owner to check and send with one yes. Use when someone asks for a quote, a team or custom offer, a call ended with a promised proposal, or the owner says "draft a proposal for Anna"; not for a first reply to a simple question (reply-to-enquiry).find-avenues: Finds where the next clients could come from: five or six real avenues scored with the owner, and the best two turned into small tests on the board. Use when the owner asks "where do I find more clients?", the list of who is waiting is thin, or a period outcome needs more sign-ups; not for choosing what to sell (spot-the-offer) or writing posts (Marketing).follow-up: Writes a gentle follow-up to someone who had a reply or a proposal and went quiet, on the day it is due, and keeps the list of who is waiting in sales/waiting.md. Use when a dated "Follow up with Anna" task is due, or for the scheduled "Who is waiting" task (job follow-up); not for a first reply (reply-to-enquiry) or an answer that holds a worry or a "not now" (handle-an-objection).handle-an-objection: Answers a person who is interested but holding back, by finding the real worry and writing an honest, calm reply in the owner's voice for the owner's yes, and keeps what worked in sales/objections.md. Use when an enquiry, a follow-up answer or a call write-up holds pushback such as "too expensive", "not now", "I need to think" or "I have to ask my partner", or the owner asks "what do I say to this?"; not for complaints from clients who already bought (handle-a-complaint).reach-out: Writes one warm, personal note to someone the owner already knows (a past client, a referral partner, a lead who went quiet long ago), with one small ask, as an email for the owner's yes. Use when a task says "reach out to Anna", when find-avenues makes a task to contact a past client or partner, or the owner says "write to my old clients", "ask Anna for an introduction" or "check in with Anna"; not for a first reply to an enquiry (reply-to-enquiry), a nudge after a recent reply or proposal (follow-up) or a newsletter (newsletter).reply-to-enquiry: Writes the first reply to someone who asked about the company's work, in the owner's voice, as an email for the owner's yes, and plans the follow-ups. Use when a Sales task holds a new enquiry or a contact form message from someone who has not bought yet, or the owner says "answer this enquiry" or "reply to Anna"; not for someone who went quiet after a reply (follow-up), pushback on price or timing (handle-an-objection), a new sign-up (welcome-a-sign-up) or a client who already bought (Service).run-the-funnel: Checks on each funnel whose email series runs by itself after the owner's one yes: adds a new sign-up for a funnel without an offer once, marks someone who asked to stop, and tells the owner who got which email. Company of One sends each email on its day; this skill never proposes one per person or per day. Use when its weekday routine runs, when a new sign-up for a funnel's offer comes in, or when the owner says "who is in my funnel", "how is my funnel doing". Not for setting up a funnel (build-a-funnel).send-a-quote: Turns an agreed price into a quote the client accepts with one tap (lines, VAT, valid until), sends it after the owner's yes, and when it is accepted hands over the invoice draft, or the first payment of a plan for a recurring one. Use when a client is ready for a firm price ("send me a quote", "what would it cost exactly"), a proposal was agreed and needs a quote to accept, or the owner says "send Anna a quote"; not for writing the proposal itself (draft-proposal).
service
add-a-lesson: Adds a lesson to the company's simple course (the Simple course module): its number, title and the lesson itself (the text, or the link to the video or page), as a record the Lessons view shows and send-next-lessons sends. Use when the owner says "add a lesson", "here is lesson 3", "put this video in the course", or pastes a lesson. Not for sending lessons (send-next-lessons).answer-questions: Answers clients' and sign-ups' questions the same day, kindly and correctly, from the company's reply templates and files, with each answer proposed as an email for the owner's yes. Use when a Service task holds a question, or for the scheduled weekday task (job answer-questions); not for a complaint or an unhappy client (handle-a-complaint), a question about buying from someone who is not yet a client (reply-to-enquiry), or writing the templates themselves (turn-questions-into-answers).check-inbox: Turns the owner's new email into board work, through the owner's own Gmail or Outlook connector: sorts each message (enquiry, client question, invoice or receipt, booking, newsletter, ignore), files the ones that matter on the person's card, makes or reuses the Sales, Service or Money task, leaves short reply drafts in the owner's own threads, moves stages, plans nudges for quiet people, copies the calendar into Operations' upcoming list, and ends with one line for the owner. Use when the scheduled inbox run is due (job check-inbox) or the owner says "check my inbox now"; not for answering a question already on the board (answer-questions) or writing a first reply to an enquiry already filed (reply-to-enquiry).enrol-a-sign-up: Enrols a new sign-up in the company's simple course (the Simple course module): records the learner, and proposes their first lesson by email for the owner's yes. Use when a sign-up for the course offer arrives ("New sign-up: Anna" for the course), or when the owner says "enrol her in the course". Not for the next lessons (send-next-lessons).handle-a-complaint: Handles an unhappy client the same day: finds what went wrong from the facts, writes a calm, honest reply in the owner's voice that owns our part and says what happens next, brings any refund or exception to the owner as a clear choice, and passes the lesson to the department that can fix it. Use when a client is unhappy, something went wrong, or a message holds a complaint, a refund request or anger, or the owner says "help me answer this complaint"; not for an ordinary question (answer-questions) or a prospect's doubts before buying (handle-an-objection).privacy-request: Prepares the answer when someone asks what the company holds about them, asks to correct it, or asks to be forgotten: gathers everything held about that person, drafts a plain reply for the owner's yes, and hands any deleting to the owner in the app. Use when a person asks "what do you have on me", "send me my data", "correct my details", "delete me" or "forget me", or the owner says "someone asked for their data"; never deletes anything itself. Not for a question about the privacy page itself (answer-questions).send-next-lessons: Sends each learner in the company's simple course (the Simple course module) their next lesson when it is due: finds who is due, proposes one email per lesson for the owner's yes (one copy per learner), and moves each learner on. Use when the weekly course run is due, or when the owner says "send the next lessons". Not for a new learner's first lesson (enrol-a-sign-up).shape-your-course: Turns what the owner already teaches into a course plan people can finish: one clear promise, who it is for, three to six lessons in order (each one step the student can do afterwards), and one free lesson for the website, saved as private draft notes. Use when the owner says "help me make a course", "what would my course be", "shape my course", when a path step names it, or before the first lesson is added and the course plan is still empty. Not for adding the lesson itself (add-a-lesson) or selling the course (set-up-payments, sell-a-membership).testimonial-request: Asks a happy client, at the right moment, for a few words about what changed for them, in the owner's voice and with an easy choice about how their words may be shared, then saves their answer word for word with that permission in service/testimonials.md. Use when the owner names a happy client, the Service page's moment for asking has come (for example two weeks after a workshop), or the owner says "ask for a testimonial"; not for writing marketing posts with the words (Marketing) or for a client who is unhappy (handle-a-complaint).turn-questions-into-answers: Turns the questions people keep asking into ready reply templates in service/templates/ (each with the ways people ask it, a short answer in the owner's voice, the files it rests on, and when not to use it), so the next answer takes a minute. Use when service/repeated.md lists questions without a template, the owner says "make templates from our questions" or "write our FAQ", or for the Service setup step that asks for the first three answers; not for answering one person now (answer-questions).weekly-client-update: Writes a short weekly update for each client the company works with now (what happened this week, what comes next, anything needed from them), from the facts on the board and in the folder, each proposed as its own email for the owner's yes. Use when the scheduled Friday task is due (job weekly-client-update), or the owner says "send the client updates" or "write Anna's update"; not for a reply to a client's question (answer-questions) or a problem (handle-a-complaint).welcome-a-sign-up: Makes every new sign-up feel welcomed by a person: for each new sign-up adds the personal touch the Service page asks for, turns a question in their message into a task and tells the owner who joined. Use when there is a "New sign-up: Anna" task; not for the welcome email's own words (change-a-template) or a question on its own (answer-questions).
systems
automate-a-routine: Turns a task the owner repeats into a scheduled output that runs on its own: picks the routine with the owner, makes sure a skill does it well, runs it once now on a real example, and writes the new line in the department page's Outputs (job, cadence, label), written and logged, so the system creates the task on time every period. Use when the owner says "do this every week", "automate X", "take this off my plate", "schedule this", when the same kind of task was done three times. Not for an email sequence to people (build-an-automation).backup-ai: Makes sure a second AI app can take over the company's work when the first is down, slow or out of budget: helps the owner choose and connect it, proves it with a handoff test on a real task with no explaining, records the tested date in rules/yes.md for the owner's yes, and says how to switch safely. Use when the setup step "backup-ai" comes up, the backup test is older than 90 days, the owner asks "what if my AI is down", "set up a backup AI" or "switch to the other AI", or the main AI stopped working mid-task. Not for the weekly health check (health-check).build-a-module: Builds a new module for the company on the module standard (MODULES.md): from the owner's brief to a plan on the task, then its views, skills, role and systems row written and logged (templates and connectors proposed), its first records, and its checks, with no new app code. Use when the owner taps "Extend your business" on Software, or says "I need class booking", "build me a course platform", "make a calendar for bookings", "can the company do X for my clients", or when a task asks for a new piece of software for the company. Not for a ready module (install-a-module) or one view (add-a-view).build-an-app: Gives the owner the app they ask for on their own website, using what the office already runs. First it checks what is built (a members area or client portal is the member area: members sign in with an emailed code, see what they bought, watch their lessons and get their receipts by email), and sets that up. Anything else becomes a small app of plain pages on the site, online as a preview, live after the owner's yes. Use when the owner says "build me an app", "I need a members area", "a client portal", "a small tool for my customers", or when a job needs its own pages on the website. Not for a ready module (install-a-module) or the owner's own domain (connect-my-domain).connect-a-system: Adds one system the company uses (a website, a sign-up form, an email sender, a channel, payments, a booking tool, a module) to the systems list in systems.md, with its address, where it is hosted, the department that owns it and how sign-ups come in, after the owner's yes. Use when the owner says "add my website", "we use Calendly for bookings", "connect Calendly", or when another skill needs a system that is not on the list. Not for the website on the owner's domain (connect-my-domain).connect-my-domain: Puts the company's website or an app at the owner's own domain or a subdomain (example.com, shop.example.com): the owner adds the domain on their own screen, copies the few lines it shows to where their domain is kept, and Check says when it is live over https. Use when the owner says "use my own domain", "put my page at example.com", "connect my domain", "make shop.example.com", or when Start here's page-online step needs an address. Not for email from the owner's own address (set-up-email-domain).engineering-standard: The one way this company builds and changes software, so any AI (in a chat or a coding tool) makes it simple, safe to repeat and proven. Use when you build or change anything for the business (an app, a site, a landing page, a module, an automation, an import, a connector, a change to stored data), or when you check such work before it goes live. Not for words or looks alone (high-end-design).get-help: Answers the owner's questions about Company of One itself (connecting the AI, the yes, sign-in, their data, billing) from the published help pages, and hands anything about money, refunds, account access or data to a person. Use when the owner asks how the office works, says something is not working, asks for help or support, or asks about a charge, a refund, their account or their data. Not for the owner's plan and its screens (your-account).health-check: The weekly health check of the company's system: stuck tasks, scheduled outputs that did not happen, connections missing on the department pages, routines that failed, an untested backup AI, and any key or password that ended up in a file; writes a short note and raises one task per problem. Use when the Sunday "Health check" task comes up (job health-check), or the owner says "check the system", "is everything running" or "something seems stuck". Not for the safety card (safety-review).install-a-module: Installs a ready module pack (Class booking, Simple course) into the company as one kit update: checks what it needs, asks for the pack in modules.json so the whole pack (its views, skills, role and systems row) arrives as one update for the owner's yes, then writes its first records and sets up its regular work. Use when the owner says "add class booking", "install the course module", "I want the simple course", or when a task asks to install a module. Not for building a new module (build-a-module).make-a-skill: Writes a new business skill the same way every skill here is written (front matter, Outcome, Read first, Steps, Quality bar, Needs a yes, Anti-patterns, Example, Done when), from how the owner really does the work, tests it on a real example, and writes it as its own skill file (logged, live for the next task); also folds an owner's correction into an existing skill as a small written fix, logged before and after. Use when work came back three times with no skill for it, no skill fits a task and the work will return, the owner says "make this a skill", "teach the AI to do X my way" or "always do it like this", or the owner corrected an output and the fix should stick. Not for a routine that runs on a schedule (automate-a-routine).safety-review: Checks that the company is safe to leave running: the five safety rules hold in practice, spend caps and the paid-tools budget are set and written down, no routine or skill sends, posts or pays without a yes, no key sits in a file, and the backup AI is tested; writes a one-screen safety card and raises a task for each gap. Use when routines are about to run unattended, after a new routine, skill or tool, once a month, or the owner asks "is it safe", "what can my AI do without me" or "set my spend limits". Not for the weekly health check (health-check).second-look: Gives a piece of work a fresh, independent check before it reaches the owner or goes live (safety rule 5): reads it as a newcomer against the skill that made it, the direction, the facts in the folder, the craft bar in rules/quality.md and the company's own look and voice, and writes a short pass or fail with at most three must-fix points the maker fixes before proposing. Use when a task says "second look" or "check this", before any outward piece (a page, an app screen, an offer, a big email, an invoice layout, a document, a post) is proposed for the owner's yes or goes live, when another skill asks for a second look, or the owner asks "is this really done?". Not for a content piece's viewer review (content-review).set-up-email-domain: Sets up email from the company's own domain, step by step: the AI starts it with one call, the owner adds a few lines where their domain is kept, it turns ready by itself, and the company's emails go out from the owner's own address. Use when the owner says "send email from my own address", "set up my email domain", "my emails go to spam", or when the Start here email step is open. Not for the website on the owner's domain (connect-my-domain).
• Always listed
Every AI app gets these at once, in this order.
• The helpers
They open an area's tools when the work needs them.
• Area
media
films, carousels and pictures in the media library. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
edits
edits, looks, formats, music, scores and the owner's notes on media. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
drops
upload links, people's uploads and share links. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
channel
the content pipeline, results and the YouTube channel. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
work
showing long media work in the hub. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
connections
connected services, secrets and the company's language. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
online
your website: pages, forms, sign-ups, the member area, selling, classes and calls, going live; its look; payment links; course progress; giving or taking away member access. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
inbox
filing an email on a person's card. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
records
deleting a module record. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
money
quotes and payments. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
automations
what each automation is doing, and starting a person by hand. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
studio
making films and sound in the cloud studio (Video Desk, Immersive Desk). Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
office
search, the AI call log, her settings, and opening parts of her office. Open it with tools_for, then call a tool with read_tool or use_tool.
• Area
road
her next step, her taps, coaching moments, her programme, immersives, her review, what waits for her yes, what was made, and her office as her phone reads it. Open it with tools_for, then call a tool with read_tool or use_tool.
• Errors
When a call is refused
The answer reads code: sentence. The sentence always says what to do next.
| Code | What it means |
|---|---|
invalid | The input isn't right. The sentence names the field and the fix; nothing was done. Fix it and call again. |
not_found | No such thing in this company (a task, file, person, record). Check the number or name, or list first. |
not_allowed | Not without another step: the owner's yes, your own task held with pick_up, or a setting the owner turns on. The sentence says which. |
taken | Someone else holds it (another AI on that task). Pick another task. |
stale | It changed since you read it. Read it again and use the new version. |
failed | On our side or a service's, never your input. Try again in a minute; if it keeps failing, call report_problem. |