swain-content-desk

Automate end-to-end beat reporting workflows into research-backed cards.

1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/peteknowsai/swain-agents --skill swain-content-desk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swain-content-desk
Source: https://github.com/peteknowsai/swain-agents/tree/main/skills/swain-content-desk
Command: npx skills add https://github.com/peteknowsai/swain-agents --skill swain-content-desk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual beat reporting for content desks is time-consuming and error-prone, requiring researchers to collect editorial signals, identify coverage gaps, and produce actionable cards. This Skill streamlines the workflow so teams can produce timely, accurate regional beat cards with minimal friction.

Core Features & Use Cases

  • Automates processing of pending editorial requests and prioritizes topics based on coverage gaps across categories such as weather-tides, fishing-reports, activities-events, maintenance-care, safety-regulations, routes-navigation, and wildlife-nature.
  • Orchestrates research with firecrawl, extracts key data (dates, locations, names), and creates styled, publication-ready cards that can be fulfilled against desk requests.
  • Supports desk updates by pushing new microlocations and marinas when discoveries emerge, and enforces card verification before publishing.

Quick Start

Start by configuring your desk region and running a pending editorial requests query to begin generating beat cards.

Frequently Asked Questions about swain-content-desk

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

FAQPage Schema
How do I automate beat reporting and card creation for regional content desks?

Automate beat reporting by configuring your desk region and querying pending editorial requests to generate research-backed, publication-ready cards. The workflow identifies coverage gaps across regional categories and extracts key data like dates and locations to fulfill editorial requests.

What is the best way to manage editorial requests and coverage gaps for regional topics?

Managing editorial requests involves querying pending items and prioritizing topics based on coverage gaps across categories like weather-tides, fishing-reports, and wildlife-nature. This ensures researchers focus on producing timely, accurate regional beat cards with minimal friction.

How does card verification work before publishing beat reports?

Card verification enforces a validation step before publishing beat reports. The workflow styles and verifies extracted research data, ensuring publication-ready cards meet editorial standards before marking the original desk requests as fulfilled.

Can I push newly discovered microlocations and marinas using the Swain CLI?

Yes, you can push newly discovered microlocations and marinas using the Swain CLI. This desk update capability allows teams to broadcast discoveries and expand regional coverage directly from the automated research workflow.

Do I need firecrawl to perform reconnaissance with vetted sources?

Firecrawl is used to orchestrate research and perform reconnaissance with vetted sources. It extracts key data such as dates, locations, and names, which are then transformed into styled, publication-ready beat cards.

What regional categories are supported for beat reporting workflows?

Supported regional categories include weather-tides, fishing-reports, activities-events, maintenance-care, safety-regulations, routes-navigation, and wildlife-nature. The workflow applies gap analysis and card creation across all these regional desk topics.