fixing-osprey-rules

Diagnose and fix Osprey SML validation errors with dependency-ordered workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves Osprey SML validation errors and reviewer-identified issues, ensuring rule files are syntactically correct and ready for deployment.

Core Features & Use Cases

  • Error Diagnosis: Provides structured patterns for common issues like type mismatches, import cycles, and undefined variables.
  • Workflow Optimization: Implements a systematic debugging process to handle cascading errors and ensure efficient, one-pass fixes.
  • Use Case: When the osprey-cli reports multiple validation failures during a rule push, use this skill to categorize the errors, identify the root cause, and apply the correct fix pattern to pass the gate.

Quick Start

Use the fixing-osprey-rules skill to analyze the current validation errors and provide a step-by-step plan to resolve them.

Frequently Asked Questions about fixing-osprey-rules

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

FAQPage Schema
How do I fix Osprey SML validation errors reported by osprey-cli?

Resolve Osprey SML validation errors by categorizing syntax, type, or structural issues and applying standardized debugging patterns to ensure rule files pass validation gates.

What causes type mismatches and import cycles in Osprey SML rules?

Type mismatches, import cycles, and undefined variables in Osprey SML rules stem from incorrect rule-writing environments, requiring structured diagnosis to identify root causes before deployment.

What is the best way to handle cascading validation failures during an Osprey rule push?

Handle cascading validation failures during an Osprey rule push by implementing a systematic debugging process that targets dependency-ordered fixing for efficient, one-pass error resolution.

How do I validate Osprey SML files iteratively without deploying broken rules?

Validate Osprey SML files iteratively without deployment by running the osprey-cli with the --dry-run flag to check fixes and ensure syntax correctness before a live push.

Why are my Osprey SML rules not passing the validation gate despite syntax fixes?

Osprey SML rules may fail validation due to unresolved structural issues or hidden import cycles, requiring iterative re-validation to confirm that applied fix patterns fully resolve the errors.