skywatch-osprey-validate

Validate Osprey SML rules projects with dry-run push commands via osprey-cli.

6|Updated Feb 21, 2026

Search Tags:#automation #validation #atproto #rules-engine #osprey #sml

Ready to run

npx skills add https://github.com/skywatch-bsky/skywatch-agent-skills --skill skywatch-osprey-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skywatch-osprey-validate
Source: https://github.com/skywatch-bsky/skywatch-agent-skills/tree/main/polytoken/skills/skywatch-osprey-validate
Command: npx skills add https://github.com/skywatch-bsky/skywatch-agent-skills --skill skywatch-osprey-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv.

What problem does it solve?

This skill eliminates manual errors when deploying Osprey SML rules by automating the dry-run validation process, ensuring rules are syntactically and logically sound before they are pushed to production.

Core Features & Use Cases

Automated Dry-Run: Executes the osprey-cli push-rules command with the dry-run flag to catch configuration errors early.
Path Resolution: Intelligently locates the rules project and the required osprey-for-atproto repository path.
Use Case: Use this skill when you have modified your SML rules and need to verify them against the current Osprey worker environment without actually deploying changes to the live system.

Quick Start

Run the skywatch-osprey-validate skill to check the rules project located in the current directory.

Frequently Asked Questions about skywatch-osprey-validate

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

FAQPage Schema

How do I validate Osprey SML rules before deploying them?▼

Validating SML rules without deployment involves executing an automated dry-run push command using the osprey-cli tool. This checks syntactical and logical integrity to catch configuration errors early before any production push occurs.

Do I need the osprey-for-atproto repository to test SML rules?▼

Yes, validating SML rules requires local access to the osprey-for-atproto repository. The validation process intelligently resolves paths between your rules project and this repository to execute the dry-run successfully.

Does the Osprey rules engine validation require a specific environment manager?▼

Yes, the Osprey rules engine validation requires the uv environment manager. It utilizes uv to manage dependencies and execute the shell commands necessary for running the osprey-cli dry-run validation process.

What is an SML rules dry-run and when should I use it?▼

An SML rules dry-run is an automated validation process that executes push commands with a dry-run flag to test rule integrity. You should use it when modifying SML rules to verify them against the current environment without affecting production.

Why does my Osprey SML rules validation fail during path resolution?▼

Osprey SML rules validation may fail if the required osprey-for-atproto repository is not accessible locally. The tool intelligently locates this repository path alongside your rules project to execute the dry-run validation correctly.