scraper-nightly

Retrieve latest nightly scraper run metrics from GitHub Artifacts or local files.

Updated May 25, 2024
One-click install
npx skills add https://github.com/gioe/laughtrack --skill scraper-nightly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scraper-nightly
Source: https://github.com/gioe/laughtrack/tree/main/.agents/skills/scraper-nightly
Command: npx skills add https://github.com/gioe/laughtrack --skill scraper-nightly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill surfaces the most recent nightly scraper run metrics by pulling the latest GitHub Actions artifact or reading local metrics files, enabling rapid health checks.

Core Features & Use Cases

  • Nightly metrics surface: identify the latest run, its outcome, and timing.
  • Fallback reliability: gracefully switch to local metrics when artifacts are unavailable or authentication is limited.
  • Use Case: quickly generate a concise status report for on-call dashboards or team standups.

Quick Start

Trigger a nightly metrics render by reviewing the latest GitHub Actions artifact or the local metrics file.

Frequently Asked Questions about scraper-nightly

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

FAQPage Schema
How do I get a quick health snapshot of recent nightly scraper runs?

Nightly scraper metrics can be surfaced by pulling the latest GitHub Actions artifact or reading local metrics files. This provides a quick health snapshot across recent runs for on-call dashboards or team standups.

What happens to nightly metrics reporting if GitHub Artifacts are unavailable?

When GitHub Artifacts are unavailable or authentication is limited, reporting gracefully falls back to reading local metrics files. This ensures you still get a health snapshot even without artifact access.

Do I need gh CLI access to report on nightly scraper metrics?

Yes, gh CLI access is required to pull the latest metrics artifacts from GitHub Actions. If authentication is unavailable, the skill falls back to local metrics files so you can still generate the report.

What is the best way to surface scraper metrics for an on-call dashboard?

The best way to surface scraper metrics for an on-call dashboard is to identify the latest GitHub Actions artifact or local metrics file. This renders a concise status report covering run outcomes and timing.

Where are the scraper metrics artifacts located for nightly reporting?

Scraper metrics artifacts for nightly reporting are located under the apps/scraper/metrics directory. The skill accesses this path via gh CLI to extract the latest run data.