home / skills / zhanghandong / rust-skills / rust-daily

rust-daily skill

safe

This skill fetches and summarizes Rust daily, weekly, and monthly updates from major sources to keep you informed efficiently.

npx playbooks add skill zhanghandong/rust-skills --skill rust-daily

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.2 KB

---
name: rust-daily
description: |
  CRITICAL: Use for Rust news and daily/weekly/monthly reports. Triggers on:
  rust news, rust daily, rust weekly, TWIR, rust blog,
  Rust 日报, Rust 周报, Rust 新闻, Rust 动态
argument-hint: "[today|week|month]"
context: fork
agent: Explore
---

# Rust Daily Report

Fetch Rust community updates, filtered by time range.

## Data Sources

| Category | Sources |
|----------|---------|
| Ecosystem | Reddit r/rust, This Week in Rust |
| Official | blog.rust-lang.org, Inside Rust |
| Foundation | rustfoundation.org (news, blog, events) |

## Parameters

- `time_range`: day | week | month (default: week)
- `category`: all | ecosystem | official | foundation

## Execution

Read agent file then launch Task:

```
1. Read: ../../agents/rust-daily-reporter.md
2. Task(subagent_type: "general-purpose", run_in_background: false, prompt: <agent content>)
```

## Output Format

```markdown
# Rust {Weekly|Daily|Monthly} Report

**Time Range:** {start} - {end}

## Ecosystem
| Score | Title | Link |

## Official
| Date | Title | Summary |

## Foundation
| Date | Title | Summary |
```

## Validation

- Each source should have at least 1 result, otherwise mark "No updates"
- On fetch failure, retry with alternative tool

Overview

This skill generates Rust community news reports on a daily, weekly, or monthly cadence. It aggregates updates from ecosystem sources, official Rust channels, and the Rust Foundation, then formats them into a concise report ready for distribution. Use it to stay informed or to publish curated summaries.

How this skill works

The skill fetches items from configured sources (Reddit r/rust, This Week in Rust, blog.rust-lang.org, Inside Rust, rustfoundation.org) filtered by the selected time_range and category. It validates that each category returns at least one item, retries with alternate tools on failure, and outputs a structured markdown report with sections for Ecosystem, Official, and Foundation items. Reports include dates, titles, links, and short summaries where available.

When to use it

Daily briefings for immediate Rust ecosystem activity
Weekly summaries for newsletters or team syncs
Monthly digests for community retrospectives
When preparing release notes or community roundups
Before publishing a TWIR-style post

Best practices

Choose the smallest useful time_range to avoid overload (day for fast-moving topics)
Filter by category when you need focused coverage (official vs ecosystem)
Validate links and summaries before public distribution
Use the markdown output as-is for newsletters or convert to HTML for web publishing
If a source returns no items, note "No updates" to keep cadence consistent

Example use cases

Send a daily summary of notable Rust threads and library releases to an engineering team
Compile a weekly TWIR-style newsletter for a community blog
Produce a monthly roundup of Rust Foundation announcements and events
Monitor ecosystem chatter (Reddit, This Week in Rust) for trending topics to address in project planning

FAQ

What time_range options are supported?

Supported values are day, week, and month; the default is week.

What happens if a source has no updates?

The report marks that category as "No updates" to preserve structure and transparency.