osprey-rule-investigator

skywatch-skills

A Claude Code plugin marketplace for investigating coordinated behaviour on the AT Protocol network, authoring Osprey SML moderation rules, and managing Ozone queues. Built and maintained by Skywatch Blue.

Plugins

Plugin	Version	Purpose
osprey-rules	0.3.0	SML rule authoring orchestrator with specialized subagents
osprey-rule-investigator	0.1.0	Read-only analysis of SML rule projects
skywatch-investigations	0.18.0	Network investigation toolkit (MCP + skills + agents)

Installation

Add the marketplace to your Claude Code settings:

claude install-plugin github:skywatch-bsky/claude-skills

Individual plugins are registered in .claude-plugin/marketplace.json and loaded by Claude Code from the plugins/ directory.

Prerequisites

• Claude Code installed
• uv on PATH (used by MCP server installation and osprey-cli)
• SSH access to GitHub (for git+ssh:// MCP dependencies)
• osprey-rules: local clone of osprey-for-atproto repo
• skywatch-investigations: ClickHouse credentials; optionally Ozone credentials for moderation write tools

---

osprey-rules

Orchestrator plugin for writing, reviewing, and debugging Osprey SML moderation rules. Uses an orchestrator-and-subagents pattern where domain knowledge lives in skills and agents contain only routing logic.

Architecture

The entry point agent (osprey-rule-writer) dispatches specialized subagents based on user intent:

Flow	Trigger	Agents involved
Write	"Write a rule for X"	investigator → planner → impl → reviewer (→ debugger loop)
Validate	"Validate my rules"	investigator → reviewer (→ offer debugger)
Fix	"Fix this error"	investigator → debugger → reviewer (→ debugger loop)
Reference	"What patterns exist?"	Orchestrator loads osprey-sml-reference directly
Review	"Review this rule"	Reviewer in ad-hoc mode

Subagents

• osprey-rule-writer — thin orchestrator, routes intent and manages review-fix loop
• osprey-rule-planner — gathers requirements, produces rule specifications
• osprey-rule-impl — writes SML files from specifications
• osprey-rule-reviewer — three-stage verification gate (osprey-cli, proactive checks, convention review)
• osprey-rule-debugger — fixes reviewer-identified issues

Skills (5)

• planning-osprey-rules — requirements gathering workflow
• authoring-osprey-rules — SML authoring workflow
• reviewing-osprey-rules — three-layer verification methodology
• fixing-osprey-rules — error categories and fix patterns
• osprey-sml-reference — SML type system, 24 labelling pattern templates, naming conventions

Command

• /osprey-validate [path] — runs uv run osprey-cli push-rules --dry-run

Key Design Decisions

• Skills are fat, agents are thin. All SML domain knowledge lives in skills. Agent prompts contain routing logic and constraints only.
• Reviewer is a hard gate. Zero issues across all severities (Critical, Important, Minor) required to pass. Minor issues are not optional.
• Baseline diffing. The reviewer captures pre-existing errors before writing so the review loop only focuses on regressions.
• Max 5 review-fix cycles before escalating to a human.
• Depends on osprey-rule-investigator for project state discovery (Flows 1-3 fail without it).

Environment Variables

Variable	Required	Purpose
OSPREY_RULES_PATH	No	Path to the Osprey rules project directory (contains main.sml). If unset, the agent asks.
OSPREY_REPO_PATH	No	Path to the osprey-for-atproto repository. If unset, the agent asks.

---

osprey-rule-investigator

Read-only analysis agent for Osprey SML rule projects — produces structured text reports covering project structure, labels, models, UDFs, and execution graphs without modifying any files.

Used as a subagent by osprey-rules for project state discovery, but can also be invoked standalone.

What It Reports

• Project structure inventory (files, labels, models)
• UDF discovery (dynamic from Python source, static fallback)
• Execution graph mapping (Import/Require chains, Rule/WhenRules catalogues)
• Confidence level for UDF discovery method used

Inputs

• Rules project path (required)
• osprey-for-atproto repo path (required for dynamic UDF discovery; static fallback used otherwise)

---

skywatch-investigations

Investigation toolkit for AT Protocol network analysis. Three-layer architecture: an MCP server for native tool access, skills that codify investigation methodology, and agents that orchestrate workflows.