daily-run-check
Tests the daily scraping and email delivery pipeline. Use this to verify automation health without triggering live emails.
Install
mkdir -p .claude/skills/daily-run-check && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18822" && unzip -o skill.zip -d .claude/skills/daily-run-check && rm skill.zipInstalls to .claude/skills/daily-run-check
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Verify the daily scrape, file-output, and email pipeline after a change. Use for end-to-end offline checks, scheduler-safe behavior, and generated-file contract verification.Key capabilities
- →Verify daily scrape pipeline
- →Check file-output pipeline
- →Validate email pipeline
- →Perform end-to-end offline checks
- →Ensure scheduler-safe behavior
- →Verify generated-file contracts
How it works
The skill performs checks on CLI flow, config/env validation, generated files, and the email path. It runs integration and unit tests to verify the daily automation pipeline.
Inputs & outputs
When to use daily-run-check
- →Verify scrape pipeline after fixes
- →Test CLI configuration flows
- →Run end-to-end integration tests
- →Validate generated file contracts
About this skill
Daily Run Check
Read AGENTS.md first, then inspect the touched path in src/scrape_n_email/ and the matching tests.
Use this skill when the goal is to confirm the daily automation still works after a code or site-change fix.
Bias
- Prefer the narrowest offline validation that covers the touched code.
- Use
python -m scrape_n_email --skip-emailor mocks before anything live. - Keep generated outputs in temp paths or disposable directories.
- Do not send real SMTP traffic unless the maintainer explicitly asks.
Common Checks
- CLI flow:
src/scrape_n_email/cli.py - Config/env validation:
src/scrape_n_email/config.py - Generated files:
src/scrape_n_email/csv.py, scraper modules - Email path:
src/scrape_n_email/mailer.py - End-to-end coverage:
tests/integration/test_pipeline.py
Verify Before Declaring Done
ruff check src/ tests/
ruff format --check src/ tests/
mypy src/scrape_n_email
pytest tests/integration/test_pipeline.py -q
pytest tests/unit/test_cli.py tests/unit/test_mailer.py -q
When not to use it
- →When the user explicitly asks to send real SMTP traffic
- →When the goal is not to confirm daily automation functionality
Limitations
- →Prefers the narrowest offline validation
- →Uses `python -m scrape_n_email --skip-email` or mocks before anything live
- →Keeps generated outputs in temp paths or disposable directories
How it compares
This skill provides a systematic way to verify the entire daily automation pipeline after changes, ensuring all components function correctly and adhere to contracts, unlike isolated testing of individual components.
Compared to similar skills
daily-run-check side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| daily-run-check (this skill) | 0 | 18d | Review | Intermediate |
| dev | 2 | 5mo | Review | Advanced |
| examples-auto-run | 2 | 2mo | Review | Intermediate |
| lora-manager-e2e | 1 | 5mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by cgfixit
View all by cgfixit →You might also like
dev
atopile
LLM-focused workflow for working in this repo: compile Zig, run the orchestrated test runner, consume test-report.json/html artifacts, and discover/debug ConfigFlags.
examples-auto-run
openai
Run python examples in auto mode with logging, rerun helpers, and background control.
lora-manager-e2e
willmiao
End-to-end testing and validation for LoRa Manager features. Use when performing automated E2E validation of LoRa Manager standalone mode, including starting/restarting the server, using Chrome DevTools MCP to interact with the web UI at http://127.0.0.1:8188/loras, and verifying frontend-to-backend functionality. Covers workflow validation, UI interaction testing, and integration testing between the standalone Python backend and the browser frontend.
migrate
alirezarezvani
Migrate from Cypress or Selenium to Playwright. Use when user mentions "cypress", "selenium", "migrate tests", "convert tests", "switch to playwright", "move from cypress", or "replace selenium".
mobile-use-setup
minitap-ai
Interactive setup wizard for Minitap mobile-use SDK. USE WHEN user wants to set up mobile automation, configure mobile-use SDK, connect iOS or Android devices, or create a new mobile testing project.
create-environments
PrimeIntellect-ai
Create or migrate verifiers environments for the Prime Lab ecosystem. Use when asked to build a new environment from scratch, port an eval or benchmark from papers or other libraries, start from an environment on the Hub, or convert existing tasks into a package that exposes load_environment and installs cleanly with prime env install.