Academy starter folder · Proscris Academy
How Your Agent Uses Tools
Understand file tools, the terminal, connectors, extensions and plugins while keeping your own role simple: describe the outcome and review the evidence.
Your prepared files are ready
Use this start page in your browser before opening the folder in VS Code. You do not have to write code, run a command, connect an account or submit homework.
The lesson pages contain the complete written explanations and guided activities. These downloaded files give you small examples to inspect later. All business names and records here are fictional.
- Extract the ZIP using your normal file manager.
- Open the extracted
proscris-academy-starterfolder in VS Code if you want optional app practice. - Find
courses/how-agents-use-tools. Start with a prepared file below and follow the matching lesson.
A familiar working pattern
- Describe the task. Name one useful result.
- Use the source. Choose relevant information or guidance.
- Review the result. Check what happened.
An illustrated learning model, not a live agent connection. Different tools and supported applications handle the mechanics.
Try one small choice here
The chat says “I will update the note.” What tells you the file actually changed?
Choose an answer to see its explanation. No request is sent and no file is changed.
Prepared examples
- welcome-note.md
- action-map.md
- toolbox-map.md
- terminal-result.md
- environment-card.md
- target-card.md
- action-cards.md
- result-receipts.md
- problem-card.md
- small-task.md
- routine-card.md
Markdown files are readable text. A browser may show or download them; open them in VS Code for a familiar editing view.
Your ten short lessons
- An Answer and an Action Are Different
Recognize whether the assistant is explaining something or using a tool to affect a specific item. - Meet the Tools in the Toolbox
Match a tool to the job and distinguish extensions, plugins, APIs and MCP connections. - The Terminal Is a Place Tools Can Work
Understand the terminal as a text-based work area without typing commands. - Different Computers, Similar Intentions
Recognize that an agent must adapt its method to the actual computer and shell. - Name the Place Where the Action Happens
Identify the file, folder, account or site that a proposed tool action will affect. - Read, Draft, Change or Send
Distinguish gathering information, preparing a draft, changing a record and sending something. - Read the Result Like a Business Receipt
Match the agent’s completion claim to evidence of the actual requested result. - When a Tool Cannot Finish
Treat unavailable tools, denied actions and uncertain results as different situations with clear next steps. - Ask for One Inspectable Action
Describe a small agent-led inspection using a named source, a clear question and a practical boundary. - Keep a Simple Tool-Use Routine
Use a repeatable routine: describe the result, confirm the target, understand the effect and inspect the evidence.
Official help when you need it
Download VS Code from Microsoft. The application is a separate official download; this starter kit contains no installers.