rust-daily▌
actionbook/rust-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Version: 2.1.0 | Last Updated: 2025-01-27
Rust Daily Report
Version: 2.1.0 | Last Updated: 2025-01-27
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 Mode Detection
CRITICAL: Check agent file availability first to determine execution mode.
Try to read: ../../agents/rust-daily-reporter.md
Agent Mode (Plugin Install)
When ../../agents/rust-daily-reporter.md exists:
Workflow
1. Read: ../../agents/rust-daily-reporter.md
2. Task(subagent_type: "general-purpose", run_in_background: false, prompt: <agent content>)
3. Wait for result
4. Format and present to user
Inline Mode (Skills-only Install)
When agent file is NOT available, execute each source directly:
1. Reddit r/rust
# Using agent-browser CLI
agent-browser open "https://www.reddit.com/r/rust/hot/"
agent-browser get text ".Post" --limit 10
agent-browser close
Or with WebFetch fallback:
WebFetch("https://www.reddit.com/r/rust/hot/", "Extract top 10 posts with scores and titles")
Parse output into:
| Score | Title | Link |
|---|
2. This Week in Rust
# Check actionbook first
mcp__actionbook__search_actions("this week in rust")
mcp__actionbook__get_action_by_id(<action_id>)
# Then fetch
agent-browser open "https://this-week-in-rust.org/"
agent-browser get text "<selector_from_actionbook>"
agent-browser close
Parse output into:
- Issue #{number} ({date}): highlights
3. Rust Blog (Official)
agent-browser open "https://blog.rust-lang.org/"
agent-browser get text "article" --limit 5
agent-browser close
Or with WebFetch fallback:
WebFetch("https://blog.rust-lang.org/", "Extract latest 5 blog posts with dates and titles")
Parse output into:
| Date | Title | Summary |
|---|
4. Inside Rust
agent-browser open "https://blog.rust-lang.org/inside-rust/"
agent-browser get text "article" --limit 3
agent-browser close
Or with WebFetch fallback:
WebFetch("https://blog.rust-lang.org/inside-rust/", "Extract latest 3 posts with dates and titles")
5. Rust Foundation
# News
agent-browser open "https://rustfoundation.org/media/category/news/"
agent-browser get text "article" --limit 3
agent-browser close
# Blog
agent-browser open "https://rustfoundation.org/media/category/blog/"
agent-browser get text "article" --limit 3
agent-browser close
# Events
agent-browser open "https://rustfoundation.org/events/"
agent-browser get text "article" --limit 3
agent-browser close
Time Filtering
After fetching all sources, filter by time range:
| Range | Filter |
|---|---|
| day | Last 24 hours |
| week | Last 7 days |
| month | Last 30 days |
Combining Results
After fetching all sources, combine into the output format below.
Tool Chain Priority
Both modes use the same tool chain order:
-
actionbook MCP - Check for cached/pre-fetched content first
mcp__actionbook__search_actions("rust news {date}") mcp__actionbook__search_actions("this week in rust") mcp__actionbook__search_actions("rust blog") -
agent-browser CLI - For dynamic web content
agent-browser open "<url>" agent-browser get text "<selector>" agent-browser close -
WebFetch - Fallback if agent-browser unavailable
| Source | Primary Tool | Fallback |
|---|---|---|
| agent-browser | WebFetch | |
| TWIR | actionbook → agent-browser | WebFetch |
| Rust Blog | actionbook → WebFetch | - |
| Foundation | actionbook → WebFetch | - |
DO NOT use:
- Chrome MCP directly
- WebSearch for fetching news pages
Output Format
# Rust {Weekly|Daily|Monthly} Report
**Time Range:** {start} - {end}
## Ecosystem
### Reddit r/rust
| Score | Title | Link |
|-------|-------|------|
| {score} | {title} | [link]({url}) |
### This Week in Rust
- Issue #{number} ({date}): highlights
## Official
| Date | Title | Summary |
|------|-------|---------|
| {date} | {title} | {summary} |
## Foundation
| Date | Title | Summary |
|------|-------|---------|
| {date} | {title} | {summary} |
Validation
- Each source should have at least 1 result, otherwise mark "No updates"
- On fetch failure, retry with alternative tool
- Report reason if all tools fail for a source
Error Handling
| Error | Cause | Solution |
|---|---|---|
| Agent file not found | Skills-only install | Use inline mode |
| agent-browser unavailable | CLI not installed | Use WebFetch |
| Site timeout | Network issues | Retry once, then skip source |
| Empty results | Selector mismatch | Report and use fallback |
How to use rust-daily on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add rust-daily
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches rust-daily from GitHub repository actionbook/rust-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate rust-daily. Access the skill through slash commands (e.g., /rust-daily) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★53 reviews- ★★★★★Anaya Khan· Dec 28, 2024
Registry listing for rust-daily matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Dec 24, 2024
Solid pick for teams standardizing on skills: rust-daily is focused, and the summary matches what you get after install.
- ★★★★★Anaya Abebe· Dec 20, 2024
rust-daily fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Isabella Torres· Dec 8, 2024
Solid pick for teams standardizing on skills: rust-daily is focused, and the summary matches what you get after install.
- ★★★★★Min Ramirez· Dec 8, 2024
rust-daily is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★James Sethi· Nov 27, 2024
We added rust-daily from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Lucas Garcia· Nov 19, 2024
Useful defaults in rust-daily — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Rahul Santra· Nov 15, 2024
We added rust-daily from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Aarav Iyer· Nov 11, 2024
rust-daily has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Nikhil Rao· Oct 18, 2024
rust-daily fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 53