reviewing-osprey-rules

Validate Osprey SML rule sets via CLI dry-runs and logic checks.

6|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/skywatch-bsky/skywatch-agent-skills --skill reviewing-osprey-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-osprey-rules
Source: https://github.com/skywatch-bsky/skywatch-agent-skills/tree/main/claude-skills/plugins/osprey-rules/skills/reviewing-osprey-rules
Command: npx skills add https://github.com/skywatch-bsky/skywatch-agent-skills --skill reviewing-osprey-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires uv, osprey-cli, and includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of maintaining Osprey SML rules by automating the verification process, ensuring that rules are syntactically correct, logically sound, and compliant with project-wide conventions.

Core Features & Use Cases

  • Multi-Layer Verification: Executes a rigorous three-layer check including CLI validation, proactive logic analysis, and convention enforcement.
  • Standardized Reporting: Generates a structured report classifying issues by severity (Critical, Important, Minor) to streamline the debugging process.
  • Use Case: Use this skill during the development lifecycle of Osprey rules to catch type-mixing errors, hardcoded time values, or naming convention violations before they reach production.

Quick Start

Run the reviewing-osprey-rules skill by providing the path to your rules project and the osprey-for-atproto repository to initiate a full validation report.

Frequently Asked Questions about reviewing-osprey-rules

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

FAQPage Schema
How do I validate Osprey SML rules for atproto agents?

Validating Osprey SML rules involves a three-layer process: CLI dry-runs, proactive logic analysis, and convention adherence reviews. This automated verification catches type-mixing errors, hardcoded time values, and naming violations before production deployment.

What is the best way to automate code review for Osprey SML rule sets?

Automated code review for Osprey SML applies CLI validation, logic checks, and convention enforcement to generate a structured severity-classified report. This process identifies type-mixing errors, hardcoded time values, and naming convention violations during the development lifecycle.

How do I check my Osprey SML rules for type-mixing errors and convention violations?

Checking Osprey SML rules for type-mixing errors requires running automated static analysis and convention adherence reviews. This generates a standardized report classifying structural inconsistencies and logic errors by severity to streamline the debugging process.

Do I need osprey-cli and uv installed to validate SML rules?

Yes, you need osprey-cli and uv installed. Validating Osprey SML rules requires access to the osprey-cli tool and the project-specific SML rule directory to perform comprehensive static analysis and execute CLI dry-runs.

How do I run a dry-run validation on my atproto SML rule directory?

Running a dry-run validation on your SML rule directory requires providing the path to your rules project and the osprey-for-atproto repository. This initiates automated CLI dry-runs and static analysis to generate a full validation report.