Connect your tools

Books matched to this capability.

4books in this track

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure
T14-L02

Brief Your Team From the Shared Drive, Through a Connector

Connect Claude to your team's SharePoint and OneDrive through the Microsoft 365 connector, and turn the current files into a brief a colleague relies on. Scope the question to one site, make every claim name its file and date, check that the recipient can open each source, and switch the connector off when you're done.

Outcome: A brief built through the connector, plus a short note: the site or folder you scoped it to, the list of cited files with their dates, which of them the recipient can open, what you corrected, and how you switched the connector off. It passes when the recipient opens three cited files at random and finds each claim, and no cited file is one they can't open.

Power user14 minLast edited: Sep 23, 2026

L03 · Builder

Who is affectedColleagues depend on something you built
T14-L03

Turn a Connector Brief Into a Routine Colleagues Can Rerun

Make a connector-based brief repeatable: saved instructions with a fixed scope and changing inputs, read-only tools, a test week with known answers, a check that each colleague's run reads the same files, a README and a fallback. The routine reads as whoever runs it, so you test it with each of them.

Outcome: A saved routine (instructions, scope, inputs, output format), a test sheet with a fixed test week and four more cases with expected results, each colleague's run of the test week, and a README with maintainer, deputy and manual fallback; it passes when a colleague runs the routine from the README under their own account, their test-week file list matches yours or every difference is explained, and they produce the week's brief without asking you.

Builder18 minLast edited: Sep 23, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop
T14-L04

Build a Read-Only Connector for a System Your Assistant Can't Reach Yet

When the system your team needs has no connector, build one: a small MCP server with one read-only tool, a key that can only read, the fewest fields the task needs, and six tests including a write attempt that must fail. IT and the system's administrator agree before colleagues connect it.

Outcome: A working read-only connector with its README and a test sheet of six cases; it passes when all six give the expected result, a write attempt through the same key is refused by the system itself, a colleague's run shows only what their own access allows, and the system's administrator has agreed in writing.

Integrator18 minLast edited: Sep 23, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving
T14-L05

Run Your Organisation's Connectors: One List, Per-Person Access, a Log and a Clean Exit

Operate the connectors a department or company relies on: one list of every route from an assistant into a system, per-person access, a log line for every call, a check of third-party connectors before install, a daily test, and a retirement you can prove.

Outcome: A connector list for one department or company team, plus one retirement record: it passes when every connector has what it reaches, whose access, version, log, responsible person, stand-in and stop; two test accounts show different access where they should; and a retired connector can't be called while its former users know the fallback.

Operator19 minLast edited: Sep 23, 2026