Daily News Report v3.0 workflow skill. Use this skill when the user needs Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Daily News Report v3.0 workflow skill. Use this skill when the user needs Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-awesome-skills/skills/daily-news-report from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Core Architecture, Configuration Files, Output Template, 1. Title, 2. Title, Error Handling.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
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
Use when the request clearly matches the imported source intent: Scrapes content based on a preset URL list, filters high-quality technical information, and generates daily Markdown reports.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
cache.json
Starts with the smallest copied file that materially changes execution
Supporting context
sources.json
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Determine date (user argument or current date)
Read sources.json for source configurations
Read cache.json for historical data
Create output directory NewsReport/
Check if a partial report exists for today (append mode)
Worker A: Tier1 Batch A (HN, HuggingFace Papers)
Worker B: Tier1 Batch B (OneUsefulThing, Paul Graham)
Use @daily-news-report-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @daily-news-report-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @daily-news-report-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @daily-news-report-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: SubAgent Call Examples
Using general-purpose Agent
Since custom agents require session restart to be discovered, use general-purpose and inject worker prompts:
Task Call:
subagent_type: general-purpose
model: haiku
prompt: |
You are a stateless execution unit. Only do the assigned task and return structured JSON.
Task: Scrape the following URLs and extract content
URLs:
- https://news.ycombinator.com (Extract Top 10)
- https://huggingface.co/papers (Extract top voted papers)
Output Format:
{
"status": "success" | "partial" | "failed",
"data": [
{
"source_id": "hn",
"title": "...",
"summary": "...",
"key_points": ["...", "...", "..."],
"url": "...",
"keywords": ["...", "..."],
"quality_score": 4
}
],
"errors": [],
"metadata": { "processed": 2, "failed": 0 }
}
Filter Criteria:
- Keep: Cutting-edge Tech/Deep Tech/Productivity/Practical Info
- Exclude: General Science/Marketing Puff/Overly Academic/Job Posts
Return JSON directly, no explanation.
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Quality over Quantity: Low-quality content does not enter the report.
Early Stop: Stop scraping once 20 high-quality items are reached.
Parallel First: SubAgents in the same batch execute in parallel.
Fault Tolerance: Failure of a single source does not affect the whole process.
Cache Reuse: Avoid re-scraping the same content.
Main Agent Control: All decisions are made by the Main Agent.
Fallback Awareness: Detect sub-agent availability, gracefully degrade if unavailable.
Imported Operating Notes
Imported: Constraints & Principles
Quality over Quantity: Low-quality content does not enter the report.
Early Stop: Stop scraping once 20 high-quality items are reached.
Parallel First: SubAgents in the same batch execute in parallel.
Fault Tolerance: Failure of a single source does not affect the whole process.
Cache Reuse: Avoid re-scraping the same content.
Main Agent Control: All decisions are made by the Main Agent.
Fallback Awareness: Detect sub-agent availability, gracefully degrade if unavailable.
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-awesome-skills/skills/daily-news-report, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Related Skills
@00-andruia-consultant - Use when the work is better handled by that native specialization after this imported skill establishes context.
@00-andruia-consultant-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith - Use when the work is better handled by that native specialization after this imported skill establishes context.
@10-andruia-skill-smith-v2 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
# Daily News Report (YYYY-MM-DD)> Curated from N sources today, containing 20 high-quality items> Generation Time: X min | Version: v3.0>
> **Warning**: Sub-agent 'worker' not detected. Running in generic mode (Serial Execution). Performance might be degraded.
---
#### Imported: 1. Title-**Summary**: 2-4 lines overview
-**Key Points**:
1. Point one
2. Point two
3. Point three
-**Source**: Link
-**Keywords**: `keyword1``keyword2``keyword3`-**Score**: ⭐⭐⭐⭐⭐ (5/5)
---
#### Imported: 2. Title
...
---
*Generated by Daily News Report v3.0**Sources: HN, HuggingFace, OneUsefulThing, ...*
Imported: 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
Imported: Compatibility & Fallback
To ensure usability across different Agent environments, the following checks must be performed:
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.
Serial Execution Mode:
Do not use parallel block.
Main Agent executes scraping tasks for each source sequentially.
Slower, but guarantees basic functionality.
User Alert:
MUST include a clear warning in the generated report header indicating the current degraded mode.
