# AI Workshop Studio · Prompt library

All sample research material is fictional. Use each prompt with the files named in its lesson.

## 1. Get set up

### Send your first prompt.

I am learning to use AI for everyday work. Today I will turn three fictional notes into a short brief and check it. Explain what a brief is in two plain-language sentences. Do not create the brief yet.

### Keep the conversation going.

Rewrite that explanation for someone who has never written a brief. Use one sentence and avoid jargon.

## 2. Write a useful prompt

### Try a deliberately vague request

Summarize these notes.

### Make your request testable

Using only the three fictional notes I provided, write a brief for the volunteer coordinator. Include: (1) two observations with note IDs, (2) one possible explanation labeled as a hypothesis, and (3) one question to investigate next. Use no more than 150 words. Do not invent quotes, counts, causes or people. If the notes cannot support a claim, say what is missing.

### Revise one weakness

Check every factual claim in your brief against the supplied notes. Identify one weak claim, explain why the evidence is insufficient, and revise it. Keep observations separate from interpretations.

## 3. Work with your files

### Confirm access before asking for analysis

Use only AI Workshop Practice for this task. Tell me which files you can actually read, then quote the first sentence from sample-notes.md. If you cannot access the folder, say so and ask me to attach or paste the files. Do not claim to have read unavailable files.

### Add one preference, then produce the brief

Read workshop-brief.md, sample-notes.md and my-working-preferences.md. Create a draft brief using only those files. Follow my preferences where they fit the task. Show the note ID next to each observation and label hypotheses. Show me the draft before saving or changing any files.

## 4. Create and test a skill

### Create or install it in your tool

Create an instruction-only skill named evidence-brief using the supplied SKILL.md as its starting point. It should turn provided notes into a short, source-linked brief and ask for missing evidence. Keep it scoped to this practice workspace, with no scripts or external connections. Tell me the exact file location and how to find and invoke it in this interface. Do not overwrite an existing skill with the same name.

### Run the missing-input test

Use the evidence-brief skill to summarize the research findings. I have not supplied the notes yet.

## 5. Understand MCPs


## 6. Check and take it with you


## 7. Claude & Codex


## 8. Build an MCP · optional

### Ask the coding tool to implement the brief

Build the local, read-only practice-notes MCP described in mcp-builder-brief.md. Use the current official MCP SDK documentation. Before installing dependencies, explain what each is needed for. Restrict access to the supplied practice-data folder, reject paths outside it including symlink escapes, return source filenames and exact matching passages, and include the acceptance tests from the brief. Do not connect to an account, deploy a server, spend money, or write outside this project. Run the tests and distinguish tested behavior from anything unverified.