skywatch-investigating-osprey-rules

To audit an Osprey SML rules project, use this skill to automatically map file dependencies, extract label definitions from configuration files, and validate the overall project structure. It generates a comprehensive report of the project inventory.

UDF discovery dynamically scans the osprey-for-atproto repository to identify and document User-Defined Functions and their signatures. This ensures rule-writing accuracy by validating available functions before they are invoked in your SML rules.

Yes, you can trace complex rule chains and conditional logic triggers within Osprey rules. The skill maps the execution graph to provide a clear summary of rule triggers and their resulting effects across the project.

Yes, you need access to both the project directory and the associated osprey-for-atproto repository. These are required to perform dynamic UDF discovery, validate signatures, and map execution graphs accurately.

The best way to debug complex SML rules engine chains is through automated execution graph mapping. This skill systematically traces conditional logic triggers and file dependencies to identify structural issues and label definitions.

Osprey SML rules may fail to trigger due to incorrect UDF signatures or misconfigured conditional logic. This skill investigates these issues by mapping the execution graph and validating UDF discovery against the repository.