Notes: Giving the Brain Hands

Ideas to keep

1. 01Start with the job you want done, then choose a connection that supplies the actions.
2. 02Willow Desk and its 12 comments are fictional practice material.
3. 03Inspect the saved report and designs in their destination apps.

Ideas to keep

1. 01A prompt describes the result you want.
2. 02A Skill supplies a reusable method.
3. 03A tool performs a particular action and returns its result.

Ideas to keep

1. 01An API is the interface a program can use to request supported app operations.
2. 02MCP describes tools and their inputs and results in a common format.
3. 03A connector provides a setup surface. A plugin can package Skills, an MCP server or other helpers.

Ideas to keep

1. 01The directory is one discovery route; the provider may document another.
2. 02A CLI accepts terminal commands that Claude Code can run.
3. 03Deferred tool definitions are available to find. Returned content still takes active context.
4. 04The token figures shown belong to the instructor’s recorded session.

Ideas to keep

1. 01Account sign-in and page access affect what the tool can retrieve.
2. 02Read the returned comments before asking for analysis.
3. 03Troubleshoot connection availability, sign-in, page permission and returned material.

Ideas to keep

1. 01Keep all 12 feedback IDs and the quotations supporting each theme.
2. 02F09 is a possible tray-edge problem to investigate, not proof of a widespread defect.
3. 03Open the saved report in Notion to verify the destination.

Ideas to keep

1. 01Watch prepares captions and selected frames for inspection.
2. 02The recording uses Local, Efficient and None for additional transcription.
3. 03Read the saved sources reference to see what Claude actually inspected.
4. 04The new Skill is used in the same conversation; independent discovery is not tested.

Ideas to keep

1. 01Audience and purpose guide the format and content.
2. 02The recording creates a 5-slide deck and a portrait one-page brief.
3. 03Feedback IDs and quotations support proposed investigations. The final priority remains yours.

Ideas to keep

1. 01The lesson shows a desktop custom connector and a local project MCP.
2. 02The instructor performs authentication himself.
3. 03The recording reaches tool availability, then stops before an account or campaign read.
4. 04Optional account practice requires an actual read and comparison in Ads Manager.

Ideas to keep

1. 01Name the starting material, connected actions and useful result.
2. 02Check the route each provider currently recommends.
3. 03Browser MCP, Browser Use and computer use refer to different approaches.
4. 04Public workflow examples illustrate possibilities; they are not your own completed runs.

Ideas to keep

1. 01Begin with a repeated job you already understand.
2. 02Research the official actions and setup before extending the workflow.
3. 03Inspect the result in the destination app.
4. 04A helper can own one part of a larger job and return useful findings.