Version: 2.1.0 | Last Updated: 2025-01-27
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrust-dailyExecute the skills CLI command in your project's root directory to begin installation:
Fetches rust-daily from actionbook/rust-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate rust-daily. Access via /rust-daily in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
974
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
974
stars
Version: 2.1.0 | Last Updated: 2025-01-27
Fetch Rust community updates, filtered by time range.
| Category | Sources |
|---|---|
| Ecosystem | Reddit r/rust, This Week in Rust |
| Official | blog.rust-lang.org, Inside Rust |
| Foundation | rustfoundation.org (news, blog, events) |
time_range: day | week | month (default: week)category: all | ecosystem | official | foundationCRITICAL: Check agent file availability first to determine execution mode.
Try to read: ../../agents/rust-daily-reporter.md
When ../../agents/rust-daily-reporter.md exists:
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
When agent file is NOT available, execute each source directly:
# 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 |
|---|
# 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:
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 |
|---|
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")
# 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
After fetching all sources, filter by time range:
| Range | Filter |
|---|---|
| day | Last 24 hours |
| week | Last 7 days |
| month | Last 30 days |
After fetching all sources, combine into the output format below.
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:
# 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} |
| 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 |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jwynia/agent-skills
mindrally/skills
github/awesome-copilot
kostja94/marketing-skills
wispbit-ai/skills
mrgoonie/claudekit-skills
Registry listing for rust-daily matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: rust-daily is focused, and the summary matches what you get after install.
rust-daily fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: rust-daily is focused, and the summary matches what you get after install.
rust-daily is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added rust-daily from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in rust-daily — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added rust-daily from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
rust-daily has been reliable in day-to-day use. Documentation quality is above average for community skills.
rust-daily fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 53