visor-agent-dev

Develop visor AI assistants with YAML tests, validation, mocks, and trace debugging.

23|2|Updated Sep 4, 2025
One-click install
npx skills add https://github.com/probelabs/visor --skill visor-agent-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visor-agent-dev
Source: https://github.com/probelabs/visor/tree/main/.claude/skills/visor-agent-dev
Command: npx skills add https://github.com/probelabs/visor --skill visor-agent-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides developers through a safe, end-to-end development loop for visor AI assistants, from skill creation to debugging.

Core Features & Use Cases

  • Structured development workflow: write YAML tests first, validate configurations, iterate with mocks, and gradually graduate to real providers with traces.
  • Safety and governance: enforces safety rules, trace-based debugging, and best practices for modifying assistant configurations.
  • Reusable developer playbook: documentation and workflows for creating new skills, workflows, checks, or updating assistant.yaml.

Quick Start

Write YAML tests first, then validate and iterate with mocks using visor validate and visor test.

Frequently Asked Questions about visor-agent-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test AI assistant configurations before deploying to production?

Testing AI assistant configurations safely involves writing YAML tests first, validating configurations, and iterating with mocks before graduating to real providers. This structured workflow enforces safety guardrails and trace-based debugging throughout the development loop.

What is trace-based debugging for AI assistant development?

Trace-based debugging for AI assistant development is a mechanism that uses execution traces to validate safety rules and diagnose issues when modifying assistant configurations. It enables iterative testing by graduating configurations from mocked environments to real providers.

Can I validate YAML test files and assistant configurations locally?

Yes, YAML test files and assistant configurations can be validated locally using the visor validate command. This allows developers to check configurations, run tests with mocks using visor test, and ensure safety rules are enforced before production.

What's the best way to extend AI assistants with new skills and workflows?

The best way to extend AI assistants with new skills and workflows is following a structured end-to-end development loop. This approach requires writing YAML tests first, validating configurations, iterating with mocks, and using trace debugging to graduate changes safely.

Why does my AI assistant configuration fail validation checks?

AI assistant configuration validation fails when safety rules are violated or configurations lack required elements. Using trace-based debugging and running visor validate helps identify specific issues in the YAML test files before graduating to real providers.