206.events Source Discovery

Identify and integrate Seattle-focused event sources into the 206.events calendar engine.

5|Updated May 7, 2024
One-click install
npx skills add https://github.com/prestomation/206events --skill 206-events-source-discovery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 206.events Source Discovery
Source: https://github.com/prestomation/206events/tree/main/skills/source-discovery
Command: npx skills add https://github.com/prestomation/206events --skill 206-events-source-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain the 206.events calendar by identifying, evaluating, and integrating new Seattle-focused event sources after the daily build report, ensuring the calendar stays current with diverse sources.

Core Features & Use Cases

  • Guides end-to-end discovery: reads per-candidate frontmatter, checks for dead sources, searches for new Seattle sources, and performs a quality gate before updating docs and logs.
  • Manages candidate lifecycle: creates and updates docs/source-candidates entries, tracks discovery logs, and prepares PR-ready changes for added sources.
  • Supports a reproducible workflow: enforces a daily discovery rhythm, frontmatter discipline, and structured logging to enable collaboration and audits.

Quick Start

Identify and document at least one Seattle-focused event source following the discovery steps, then open a PR with the updated candidate file and daily log entry.

Frequently Asked Questions about 206.events Source Discovery

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

FAQPage Schema
How do I discover and add new Seattle event sources to a calendar engine?▼

To discover Seattle event sources, identify candidates with public listings, validate their Seattle-centric focus, document them with per-source frontmatter, and submit a PR with updated candidate files and discovery log entries.

What is the workflow for maintaining event source candidates in a community calendar?▼

The event source candidate workflow operates after a daily build report, searching for new sources, checking for dead links, enforcing frontmatter discipline, and preparing PR-ready changes with structured logging for audits.

Does the source discovery process require a pull request to update added sources?▼

Yes, the source discovery process enforces a PR-based workflow for updating added sources, ensuring that all new Seattle-focused event sources are reviewed before integration into the calendar engine.

How do I track the discovery log for daily event source validation?▼

You track the discovery log by creating and updating structured daily log entries alongside the source-candidates documentation, ensuring reproducible validation and collaboration during the event source discovery rhythm.

What quality gate checks are enforced when integrating Seattle event sources?▼

The quality gate validates that candidates are Seattle-centric with public event listings, enforces per-source frontmatter requirements, and checks for dead sources before allowing integration into the calendar.

Can I use this source discovery process for event calendars outside Seattle?▼

No, the source discovery process is specifically designed to validate and integrate Seattle-focused event sources, ensuring the 206.events calendar stays current with local Seattle event listings.