skills.rest
skywatch-bsky
skywatch-bskyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

skywatch-planning-osprey-rules

Standardize requirements gathering and specification for Osprey SML rule development.

6|Updated Feb 21, 2026
Search Tags:#specification#compliance#rule-writing#osprey#skywatch#sml
One-click install
npx skills add https://github.com/skywatch-bsky/skywatch-agent-skills --skill skywatch-planning-osprey-rules
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skywatch-planning-osprey-rules
Source: https://github.com/skywatch-bsky/skywatch-agent-skills/tree/main/polytoken/skills/skywatch-planning-osprey-rules
Command: npx skills add https://github.com/skywatch-bsky/skywatch-agent-skills --skill skywatch-planning-osprey-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents downstream implementation failures by enforcing a rigorous, standardized requirements-gathering process for Osprey SML rules before any code is written.

Core Features & Use Cases

  • Context Validation: Ensures all necessary investigator reports, label tables, and UDF signatures are present before starting.
  • Rule Specification: Generates a structured, plain-text specification covering target behavior, signals, and logic.
  • Use Case: When a user requests a new detection rule, this skill guides the agent to verify label existence and entity types, ensuring the final SML code is valid and ready for production.

Quick Start

Use the skywatch-planning-osprey-rules skill to generate a formal rule specification based on the current investigator report and user request.

Frequently Asked Questions about skywatch-planning-osprey-rules

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

FAQPage Schema
How do I gather requirements for Osprey SML rule development before writing code?▼

Requirements gathering for Osprey SML rules involves validating project context, verifying label configurations, and specifying target entities, event types, and signals to prevent downstream implementation failures.

What is the best way to standardize detection rule specifications for Osprey SML?▼

Standardizing detection rule specifications for Osprey SML requires generating a structured, plain-text specification that defines target behavior, signals, and logic based on validated investigator reports.

Do I need to verify UDF signatures and label tables before creating an Osprey SML rule?▼

Yes, verifying UDF signatures and label tables is a required context validation step before creating an Osprey SML rule, ensuring technical alignment and that the final SML code is valid for production.

How do I ensure technical alignment when generating Osprey SML rule definitions?▼

Ensuring technical alignment when generating Osprey SML rule definitions requires validating existing label configurations and UDF availability, confirming that event types and target entities match the project context.

Why does Osprey SML rule implementation fail without a formal specification phase?▼

Osprey SML rule implementation fails without a formal specification phase because missing context validation and unverified label configurations lead to invalid SML code that is not ready for production.

Related Skills

Explore More Software Engineering Skills→
skywatch-bskyskywatch-bsky
6

planning-osprey-rules

Validate investigator reports and produce structured Osprey SML rule specifications.

Official
Advanced
skywatch-bskyskywatch-bsky
6

skywatch-reviewing-osprey-rules

Validate Osprey SML rules via CLI, logic, and convention checks.

Official
Advanced
skywatch-bskyskywatch-bsky
6

investigating-osprey-rules

Audit Osprey SML rules projects by mapping file structures, UDF signatures, and execution graphs.

Official
Advanced
skywatch-bskyskywatch-bsky
6

osprey-sml-reference

Document Osprey SML rule syntax and best practices for moderation.

Official
Advanced