Catalog
Buffaly skills catalog
Use the skills catalog to understand the capability families Buffaly can discover and activate for user work.
Common skill families
The catalog should help users recognize where common work belongs.
- File and process skills handle inspection, validation, and command execution.
- Session skills preserve plan, scratch, artifacts, and task continuity.
- Wiki, browser, UI, memory, ontology, and service-discovery skills support documentation work, visible route checks, reusable knowledge, and service/action surface inspection.
- Provider, service, and integration skills expose external capabilities through typed boundaries.
How to use the catalog
Start from the task you want Buffaly to perform, then map it to the capability family that owns the work.
Ask Buffaly to show the likely skill family, candidate actions, and validation path before it changes anything important. That keeps discovery user-facing instead of turning into a hidden implementation detail.
- For repeatable instruction workflows, look for prompt skills.
- For typed operations, look for ProtoScript actions, DLL tools, or services.
- When a capability is missing, add the smallest extension that fits the task.
Ask: "Which skill should handle wiki documentation updates?"
Ask: "List the actions for the file system skill before reading files."
Ask: "Find whether there is a typed tool for this before using PowerShell."
When to add a skill
Add a skill when a repeatable family of work needs discoverable actions, prompts, or services.
- Use a prompt skill for repeatable guidance-driven work.
- Use ProtoScript or services when typed action discovery matters.
- Validate new skills by searching, loading, and executing a small example.
- Keep catalog entries organized by the user workflow they support, not merely by implementation folder names.