Kit

Skills are reusable pieces of knowledge — procedures, policies, FAQs, or anything your team needs to reference. In Slack, just tell Kit what you want to save:

"Create a skill called closing-checklist with our end-of-day steps: lock the front door, run the register report, and set the alarm."

You can also upload files directly in Slack — PDFs, Word docs, markdown, or even ZIP archives. Kit will read them and create skills automatically.

Via MCP, use the create_skill tool with a name, description, and content. Skills are written in markdown.

By default, skills are visible to everyone. You can scope them to a specific role (e.g. "managers") when creating.

Rules tell Kit's AI agent how to behave — tone, policies, guardrails. Think of them as standing instructions. In Slack:

"Add a rule: always suggest checking the employee handbook before answering HR questions."

Via MCP, use create_rule with the rule content and an optional priority (lower number = higher priority).

Rules can be scoped to specific roles so different teams get different behavior.

Tasks let Kit do things on a schedule — daily summaries, weekly reminders, recurring reports. Just describe when in plain language:

"Every weekday at 9am, post a morning briefing to this channel."
"Every Monday at 8am, remind the team about the weekly standup."
"Tomorrow at 3pm, send me the sales report."

Kit understands natural schedules — no cron syntax needed. You can also create one-time tasks by specifying a date and time.

Kit uses roles to control access. Create roles (e.g. "managers", "kitchen-staff"), assign users, then scope skills, rules, and tasks to those roles.

"Create a role called managers"
"Assign @jane to managers"
"Create a skill called payroll-process scoped to managers"

Anything scoped to "tenant" is visible to everyone. Anything with no scopes is invisible (default deny).

In Slack, just ask a question — Kit automatically searches relevant skills and memories to answer.

"What's our return policy?"
"How do I close out the register?"

Via MCP, use search_skills with a query, or list_skills to browse everything you have access to.

Kit tracks todos for your team. Create them from conversation or ask Kit to find and create them from Slack messages.

"Create a todo to restock the paper towels"
"What todos are overdue?"

Todos support priorities, due dates, assignments, and role scoping.

Admins can configure channels for Kit to search. Kit can then browse and search messages in those channels.

"Look in #general for any action items from today"

Channel access is scoped to roles, so users only see messages from channels they're allowed to access.

Plug in any public iCal (.ics) URL — a Google Calendar share link, a brewery shift schedule, a band tour calendar — and Kit keeps it in sync and answers questions about the events on it.

"Configure a calendar called shifts at https://example.com/shifts.ics"
"Who's working tonight?"
"When is the next festival?"

Calendars are scoped to roles like everything else. Kit re-fetches each feed in the background, so changes show up automatically.

Run scheduling in Square? Connect Square and a Google Calendar (via a service account) on the Integrations page, and Kit mirrors your published shift schedule into a calendar your team already subscribes to — updated automatically every 15 minutes, cancelled shifts removed.

"Sync my Square shifts now"
"When did the shift sync last run?"

Each published shift becomes a calendar event for the assigned team member. Setup and controls are admin-only; then it just runs.

Your site publishes three subscribable calendar feeds — everything, real happenings only, and just the big ones. A chamber of commerce or a city calendar subscribes once and then follows along on its own, and a regular can add your calendar to their phone. Which events land in which comes from the prominence you already set, so there is nothing extra to keep up.

For the places that only take a form, Kit keeps a running list of what is outstanding — ordered by their deadline rather than the event date, with the link and the details ready to paste. A missed reminder drops off instead of piling up, and the moment a calendar agrees to take the feed, that channel stops asking you for anything ever again.

Two clicks on the Events page — this week or next — print the card that stands on your taproom tables: a coloured band per event with the day, the door time, a line or two about it, and the event's own poster. Two identical 4x6in cards to a sheet — cut on the dashed lines and each one slides into a standard 4x6 table frame.

There is nothing to lay out — it is built from the events you already entered, and only from the published, public ones, so a private booking can never turn up on a card in front of customers. Repeating events print the date they land on this week.

Each morning Kit posts the day to a channel — who's on and what's happening, private bookings included, not just the public listings. The people working get mentioned; the per-event detail goes in a thread, so the channel stays one line a day and questions get answered where everyone can see them.

"Preview today's shift notice"
"Post today's notice now"

Pick a channel and it works. Pairing people with their Slack accounts is optional — it's what turns a name into a mention.

With Square connected, Kit posts a card each morning with yesterday's takings — and what stood out about them. Every figure carries its comparison: the same weekday over the previous eight weeks, measured against the median so one festival Saturday doesn't quietly raise the bar for months.

A normal day is a single line. When something stands out, the card leads with it — an unusually high or low day, a stretch of hours that ran dead, an item selling well above its usual, or order count and revenue moving in opposite directions. Findings are ranked by how much money moved and capped at three, so it stays readable in a glance.

No prompting, no asking — it arrives on its own, and it says nothing when there's nothing to say.

Drop a one-line <script> tag onto your site (Wix, Squarespace, anywhere that allows custom HTML) and a floating chat bubble appears in the bottom-right. Visitors ask questions; the bot answers from your tenant's skills, rules, memories, and calendar — strictly read-only, no actions.

"Create a widget token for https://example.com"

Kit-internal documentation and any skill wired into a scheduled job are hidden automatically, so only your customer-facing knowledge surfaces. Conversations are saved so your team can later ask Kit "what did people ask this week?" or "did anyone ask about X?" right from Slack.

Give every unattended screen — lobby TV, shop-floor dashboard, taproom menu — a permanent Kit address, and point the machine's browser at it once. After that you change what the screen shows by editing a URL in the console, not by carrying a keyboard over to it.

A taproom tap list follows Untappd, so the wall screen keeps itself current — anything tapped in the last week badges itself as new, and the same list prints as a letter-sized table menu, descriptions and all, without anyone opening a design tool.

A short copy-paste loop on the machine watches its address and reloads the browser when the target changes. Each screen reports in as it polls, so a display that has gone dark shows up on the page instead of going unnoticed for a week.

Connect any IMAP + SMTP mailbox — Gmail (app password), iCloud, Fastmail, self-hosted, etc. — and Kit can read your inbox and draft replies. Credentials go through a one-time URL so the LLM never sees your password.

"Set up my email"
"Any emails from Jim this week?"
"Draft a reply thanking them and proposing Thursday at 1pm"

Every send goes through an approval card — you review and revise the drafted message in the card stack, then swipe to approve. Kit never sends mail directly.

Tell Kit who you want to meet with and when you're available — Kit DMs each participant on Slack, collects their availability in plain language ("Tue or Wed afternoon", "anytime after Thursday"), proposes times back, and confirms once everyone aligns.

"Set up a 30-minute meeting with @alice and @bob next week — Tue/Wed afternoons work for me"

You see an approval card for each drafted DM before it goes out (or flip on auto-approve to skip). When Kit finds a time that works for everyone, you get a confirmation card. If it stalls — bad availability, deadline lapses, no overlap — you get an abandonment card with options to extend or cancel.

Use a vote when you want quorum approval from a named group — board sign-off, partner alignment, "do we all agree on this". Each participant gets a decision card in their stack (no Slack DM); they swipe Approve / Object or tap Abstain, and can long-press to add a private comment.

"Start a vote on the new vendor agreement with the leadership team"

When everyone's resolved or the deadline hits, the organizer gets a digest card showing the tally and verbatim objection reasons. Options: Accept, Reject, Accept-and-share-with-team, Reject-and-announce. Votes are one-shot — if objections land, you decide what to do.

Kit's vault stores shared logins — the brewery's POS account, the band's Squarespace, the booster club's Mailchimp — encrypted in your browser before anything reaches the server. Each entry is scoped to a role, so visibility tracks team membership.

"Save the password for our Squarespace, scoped to managers"
"What's the login for our POS?"
"List my passwords"

The vault is locked behind one shared master password per workspace (the same model as your members-only website). An admin sets it up once and shares it with the team out-of-band; everyone unlocks with the same password. To save a new entry, Kit hands you a one-time URL — you paste the password into a browser form that encrypts it client-side. To use one, Kit returns a one-tap URL that opens the reveal page (you unlock with the shared master password once per session). Kit and the LLM never see plaintext values.

Browse everything you have access to at https://kit.twdata.org/your-slug/web/vault.