Skills
Turn a working process into a skill
Capture a repeatable procedure with clear inputs and checks, then test it on another example before wider use.
A skill is a reusable set of instructions for a particular kind of work. It can tell Proto when to use a procedure, which inputs to request, how to produce the result, and what to check before finishing.
Build a skill after completing the task successfully at least once. The useful material is the procedure that worked, including the exceptions and review steps you discovered.
Ask Proto to capture the process
Save this supplier-quote comparison process as a skill. It should take the current requirements and two or more quotes, compare cost and delivery on the same basis, cite each difference, and flag missing evidence. It should create a new report and leave the input files unchanged.
Review the saved instructions. Replace details that belonged only to the first run, such as a supplier name or date, with inputs for future runs. Keep stable business rules explicit: the currency basis, approved calculation, or required review step.
Inspect and manage skills
The Skills settings show installed skills and a Refresh skills control. You can inspect a skill’s contents and choose whether it is enabled for new chats. The Open skills folder control opens the folder used for personal skills.
Changes to the default enabled state apply to new chats. If a running task is already using a skill, tell Proto about the change and verify the instructions used on the next run.
A simple skill file
For a hand-authored skill, use a folder containing SKILL.md. A workspace skill can live at .proto/skills/quote-comparison/SKILL.md; a global personal skill belongs under ~/.proto/skills/.
---
name: quote-comparison
description: Compare supplier quotes against a requirements document and prepare an evidence-based decision table.
---
1. Identify the requirements document and the quotes to compare.
2. Normalize currency, quantities, delivery basis, and tax treatment.
3. Cite the source for each material difference.
4. Mark missing or conflicting information explicitly.
5. Save a new comparison report and leave source files unchanged.
6. Check the report against the original quotes before finishing.
Supporting templates and reference documents can live beside the skill. Keep references relevant and avoid embedding passwords, API keys, or one customer’s private records in a reusable package.
Test it on a different example
Start a new task, name the skill, and provide another set of inputs. Include an exception, such as a quote without a delivery date. Check that the skill reports the missing information instead of filling it in.
A skill describes a process. It does not create access to a provider, remove approval requirements, or guarantee that an external service is available. Keep those prerequisites visible in the instructions so future users know what they need.