> For the complete documentation index, see [llms.txt](https://llm.theparley.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://llm.theparley.org/starting-to-use-it/lunch-and-learn-series/week-4.md).
# Week 4
### Build Your AI Tool + Share & Learn
#### MONDAY — TURNTABLE TEAM
**Part 1: Tool-Building Tutorial (20-25 min)**
* Quick intro to the platform
* How to set up a simple AI assistant with custom instructions
* Demo: building a basic tool from scratch step-by-step
* Overview of tool options and examples
**Part 2: Build & Present (65-70 min)**
*Build Phase (45 min):*
* **Tool options**:
* Leadership briefing generator
* Strategic update assistant
* Multi-document synthesizer
* \[Or propose your own based on your needs]
* Participants actively build their tool using the platform
* Work individually or in pairs
* Instructors circulate to help troubleshoot
* Test tools with real examples
*Share & Learn (20 min):*
* 2-minute demo from each person/pair
* Focus: "What problem does this solve and how would you use it?"
* Group feedback and suggestions
**Reflection**: What will you continue using? What did you learn about AI's capabilities and limits?
#### TUESDAY — BOOMBOX CREW
**Part 1: Tool-Building Tutorial (20-25 min)**
* Platform walkthrough
* Setting up custom AI assistants
* Example: building a simple tool together live
* Review of possible tool types
**Part 2: Build & Present (65-70 min)**
*Build Phase (45 min):*
* **Tool options**:
* Policy simplifier
* Committee briefing generator
* Instruction clarity assistant
* \[Or design your own]
* Participants create their tool on the platform
* Individual or partner work
* Support available throughout
* Practice using tool with actual content
*Share & Learn (20 min):*
* Quick presentations from each participant
* "What does this tool do and why is it useful?"
* Peer feedback and ideas
**Reflection**: Which tools will you actually use? What surprised you about this process?
***
#### WEDNESDAY — LIMEWIRE LEGENDS
**Part 1: Tool-Building Tutorial (20-25 min)**
* Platform introduction
* Creating customized AI assistants
* Live demo of tool creation process
* Examples of effective tools
**Part 2: Build & Present (65-70 min)**
*Build Phase (45 min):*
* **Tool options**:
* Project update assistant
* Automated follow-up generator
* Event communication helper
* \[Or create based on your workflow]
* Participants build and test their tool
* Work individually or with partners
* Help available for technical issues
* Run through real scenarios
*Share & Learn (20 min):*
* Everyone presents their tool briefly
* "Here's the problem it solves and how I'd use it"
* Group discussion and refinement ideas
**Reflection**: What tools will stick? What did you learn about AI integration in daily work?
***
#### THURSDAY — SPOTIFY SQUAD
**Part 1: Tool-Building Tutorial (20-25 min)**
* Getting started with the platform
* How to build a custom AI assistant
* Walkthrough of a sample tool creation
* Ideas for useful tools
**Part 2: Build & Present (65-70 min)**
*Build Phase (45 min):*
* **Tool options**:
* Onboarding assistant
* "Explain this policy simply" tool
* Recurring email helper
* \[Or build something you need]
* Participants create their tool actively
* Individual or partner work
* Guidance available throughout
* Test with real examples
*Share & Learn (20 min):*
* Short presentations from all participants
* "This is what it does and why it helps"
* Feedback and improvement suggestions
**Reflection**: What will you keep using? What have you learned about working with AI?
Pitch Angle:\
“How this tool helps new staff get organized quickly.”
### FRIDAY - OFFICE HOURS
Answer any questions from the different cohorts. Only one hour? Maybe two?
### KEY TAKEAWAYS?
| Turntable Team | BOOMBOX CREW | LIMEWIRE LEGENDS | SPOTIFY SQUAD |
|---|
| | | |
| | | |
| | | |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://llm.theparley.org/starting-to-use-it/lunch-and-learn-series/week-4.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.