Templates

Examples

Use these workflow patterns to understand how Skills should declare purpose, permissions, runtime shape, and safe output behavior.

Browser Research Agent

For analysts and operators who need sourced web research. Uses web search/fetch permissions, returns citations, and should avoid secret collection.

For product and support teams answering from documentation. Uses document retrieval, clear source excerpts, and conservative fallback language.

For engineering teams reviewing diffs. Uses repository metadata and should avoid destructive actions unless explicitly approved.

For data teams summarizing tabular or uploaded datasets. Declares storage and retention behavior before processing.

For support queues. Classifies urgency, extracts next steps, and keeps customer-sensitive fields scoped.

For sales operations. Enriches leads with declared web sources and data retention notes.

For finance reviews. Requires careful permission and retention declarations before handling financial documents.

For operations teams coordinating scheduled workflows. Should expose dry-run mode, idempotency, and audit logs.