daily-news-report
Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.
By sickn33 · 1,088 installs
npx skills add sickn33/agentic-awesome-skills --skill daily-news-report
Source repository · Upstream listing
Daily News Report v3.0
Architecture Upgrade : Main Agent Orchestration + SubAgent Execution + Browser Scraping + Smart Caching
Core Architecture
Configuration Files
This skill uses the following configuration files:
File Purpose
sources.json Source configuration, priorities, scrape methods
cache.json Cached data, historical stats, deduplication fingerprints
Execution Process Details
Phase 1: Initialization
Phase 2: Dispatch SubAgents
Strategy : Parallel dispatch, batch execution, early stopping mechanism
Phase 3: SubAgent Task Format
Task format received by each SubAgent:
Phase 4: Main Agent Monitoring & Feedback
Main Agent Responsibilities:
Phase 5: Evaluation & Filtering
Phase 6: Browser Scraping (MCP Chrome DevTools)
For pages requiring JS rendering, use a headless browser:
Phase 7: Generate Report
Phase 8: Update Cache
SubAgent Call Examples
Using general purpose Agent
Since custom agents require session restart to be discovered, use general purpose and inject worker prompts:
Using worker Agent (Requires session restart)
Output Template
Constraints & Principles
1. Quality over Quantity : Low quality content does not enter the report.
2. Early Stop : Stop scraping once 20 high quality items are reached.
3. Parallel First : SubAgents in the same batch execute in parallel.
4. Fault Tolerance : Failure of a single source does not affect the whole process.
5. Cache Reuse : Avoid re scraping the same content.
6. Main Agent Control : All decisions are made by the Main Agent.
7. Fallback Awareness : Detect sub agent availability, gracefully degrade if unavailable.
Expected Performance
Scenario Expected Time Note
Optimal ~2 mins Tier1 sufficient, no browser needed
Normal ~3 4 mins Requires Tier2 supplement
Browser Needed ~5 6 mins Includes JS rendered pages
Error Handling
Error Type Handling
SubAgent Timeout Log error, continue to next
Source 403/404 Mark disabled, update sources.json
Extraction Failed Return raw content, Main Agent decides
Browser Crash Skip source, log entry
Compatibility & Fallback
To ensure usability across different Agent environments, the following checks must be performed:
1. Environment Check :
In Phase 1 initialization, attempt to detect if worker sub agent exists.
If not exists (or plugin not installed), automatically switch to Serial Execution Mode .
2. Serial Execution Mode :
Do not use parallel block.
Main Agent executes scraping tasks for each source sequentially.
Slower, but guarantees basic functionality.
3. User Alert :
MUST include a clear warning in the generated report header indicating the current degraded mode.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.