The toolkit lists what an intern's agent may connect to and the written skills it may follow. Open it from "For students" or "For US businesses", then "The toolkit", or go to /toolkit. The first page says how many connectors and skills there are and how many are approved for client work. Signed in, interns also have "Toolkit" in the course menu, and business owners have "Toolkit" in the dashboard menu.
Without logging in: samples
Without logging in, the connector and skill lists show a few samples each, with a panel that says how many there are in all and "Log in". Every account sees the whole toolkit: interns, free Starter accounts and businesses that have posted a project. No account yet? The panel's "New here?" choices are the login page's.
Search and the filters look through the samples only, and the list says so. Opening a connector or skill that is not a sample, or downloading one of its files, takes you to the login page, and back afterwards. On a sample's page, the lists of workflows and skills linked to it show samples only; "Log in to see every workflow and skill linked to it" is under them.
Connectors and skills
A connector is a system a business already runs, such as its till, calendar or inbox. Its page says how an agent connects (the vendor's own MCP server, its API, a file export or an automation platform), the sign-in it needs, what data it holds and what an agent may do there by default: read only, draft for a person, or write with each change approved.
A skill is a set of instructions an agent follows for one job, such as checking supplier invoices or removing personal details from a message. Each skill has example files, a "Never" list of what it must refuse and a "Hand over" list of what a person checks.
The review status
Every connector and skill shows one of three badges:
- "Approved for client work": an intern may use it for a business, through the gateway.
- "Under review": it is being checked and is not used for client work yet.
- "Not approved": it is not used for client work.
The researcher who wrote the page proposes a status; we review it, and only our review counts.
What "approved" covers
Approval is for a way of connecting, not for a whole product. Near the top of "How an agent connects", each connector page says "Approved route" (for example the owner's own report export, a read-only connection the gateway holds, or the vendor's own automation steps in the owner's account) and "Not approved" (for example shared logins, screen scraping, private endpoints and community MCP servers). An intern uses only the approved route. For systems that hold health, children's, legal or tax records, the approved route is usually a report with the fewest fields the job needs, made by the business's own staff.
The gateway rule
An intern's agent never holds the business's passwords. It sends each request to the gateway with a token the owner issued. Reads run and are logged; anything that changes the business's data or speaks for it waits for the owner's approval. See Tokens for your intern's agent and Approvals and standing permissions.
Browse and filter
- Open "Connectors" or "Skills".
- Type a word in "Search", or leave it empty.
- For connectors, choose a "Category", a "Business type", a "Way in" (such as "Has an official MCP server") or a "Review" status. For skills, choose a "Category", a "Job", a "Business type" or a "Review" status.
- Press "Show". A long list comes in pages of 30; "Clear the filter" brings back the whole list.
On a connector's page
"The facts" lists every field in plain words. "Used in workflows" lists the designs in the workflow library that use the system; each opens its workflow page. A workflow page links each tool back to its connector when there is one.
On a skill's page
The instructions come first, then "The skill folder": every file, with "Download" and "Copy" for each. "Use it in Claude Code" says where to put the folder so Claude Code finds it. The example files hold invented data only.
Related guides
- The workflow library
Designs for the jobs a small business does every week, by business type and by department, each with the agent's steps, the human checks and the data it needs. Pick one and post it as a project.
- Tokens for your intern's agent
Issue a token that lets your intern's agent do only what you tick, send it privately, and revoke it at once if it leaks.
- Approvals and standing permissions
Review each held request and approve or decline it, approve all or some items of a batch request, and give a standing permission so one kind of request runs without asking, up to a daily number, until a date.
Edit suggestions
Spotted something wrong, out of date or missing? Tell us which guide and what you expected to see.
Email hello@aiharnesslabs.com