last30days-skill Guide: Install and Use the GitHub Trending AI Agent Skill

Last updated: 2026-06-10

Learn what mvanhorn/last30days-skill is, why it is trending on GitHub, how to install it for Claude Code, Codex, Cursor, and Gemini CLI, and when developers should use it.

Quick answer

Best for: last30days-skill is an early-trending AI agent skill for researching recent signals across social, developer, market, and web sources before turning them into a grounded brief.
Start here: Treat last30days-skill as a current-signal research assistant, not a final source of truth.
Main workflow: Pick one narrow topic, such as a GitHub Trending repository or a new AI coding tool.
Common mistake: Some sources need external accounts, local tools, or API keys before the full source mix is available.

Summary

last30days-skill is an early-trending AI agent skill for researching recent signals across social, developer, market, and web sources before turning them into a grounded brief.

Key takeaways

Treat last30days-skill as a current-signal research assistant, not a final source of truth.
Install it through Claude Code marketplace or the agent-skills CLI depending on your host.
Use it when recent community signals matter more than older evergreen documentation.

Why last30days-skill is getting attention

GitHub Trending currently shows mvanhorn/last30days-skill among active trending repositories.
A local Google Trends export showed the exact query rising from 0 before 2026-06-05 to 100 on 2026-06-09.
The topic fits developer interest in Claude Code, Codex, Cursor, Gemini CLI, and portable agent skills.

How to install it

For Claude Code, use the marketplace flow shown in the repository README.
For Codex, Cursor, Copilot, Gemini CLI, and other agent-skill hosts, use the agent-skills CLI install path.
Keep one install method active per machine to avoid duplicate command entries.

When it is useful

Use it before writing a trend brief, tool comparison, launch analysis, or recent-community research note.
Use it before a meeting when you need a quick picture of what a person, company, or product did recently.
Use it for developer-tool discovery when GitHub issues, Reddit threads, Hacker News, and release notes all matter.

Limits to keep in mind

Some sources need external accounts, local tools, or API keys before the full source mix is available.
GitHub Trending is a short-term discovery signal, so long-term adoption is not guaranteed.
Always verify important claims against primary sources before publishing or making product decisions.

Detailed Notes

Additional implementation notes and source-backed context.

Quick install commands

Use the repository README as the source of truth, because install paths can change as the skill and supported hosts evolve.

For Claude Code, the README shows this marketplace path:

/plugin marketplace add mvanhorn/last30days-skill
/plugin install last30days

For Codex, Cursor, Copilot, Gemini CLI, and other compatible agent-skill hosts, the README shows this CLI path:

npx skills add mvanhorn/last30days-skill -g

The -g flag installs the skill globally for your user. If you only want it in one project, review the current README before changing the install scope.

Why this is a trend worth testing

The current evidence is promising but still early. GitHub Trending is a developer discovery signal, and the local Google Trends export showed a fast move from zero interest to peak relative interest over a few days. That is enough to justify one practical guide, but not enough to justify a full content cluster yet.

The useful angle is not “this tool is the future.” The useful angle is narrower: developers searching for last30days-skill install, last30days-skill codex, or last30days-skill claude code need a plain-English guide that explains what it does, how to install it, and when to verify its output.

Practical use cases

Research a fast-moving GitHub repository before writing a short guide.
Compare recent community reaction around two developer tools.
Prepare for a meeting with recent signals about a person, company, or product.
Collect Reddit, Hacker News, GitHub, and web signals before drafting a content brief.
Build a first-pass timeline of what changed in the last month.

Verification checklist

Before you publish or act on a last30days-skill result:

Confirm install commands against the current repository README.
Check product facts against official docs, release notes, or source repositories.
Separate community reactions from confirmed project behavior.
Avoid quoting social posts unless you have the original URL and context.
Keep a short note of which sources were enabled in your run.

Comparison Table

Practical tradeoffs for this topic page, focused on workflow decisions.

Need	last30days-skill	Standard web search
Recent community signal	Designed to collect recent social, developer, market, and web signals into one brief	Useful for indexed pages, but may miss comments, transcripts, and fast-moving threads
Setup effort	Needs a compatible host and may need keys or browser sessions for optional sources	Works immediately in a browser
Publishing confidence	Good for discovery and synthesis, then requires verification	Good for finding primary pages and official docs

Practical Workflow

Use last30days-skill for a trend research brief

1Pick one narrow topic, such as a GitHub Trending repository or a new AI coding tool.
2Run last30days-skill in the host where you installed it.
3Separate community reactions from primary facts.
4Verify product claims against the repository README, docs, release notes, or official pages.
5Turn the result into a concise brief with install steps, use cases, limitations, and related tools.

Step-by-Step Example

A concrete execution example you can adapt to your own workflow.

Example: Research a GitHub Trending AI agent tool

A developer wants to decide whether a fast-moving AI agent repository deserves a short guide.

1.Use last30days-skill to collect recent GitHub, Reddit, Hacker News, and web signals.
2.Check whether the project has an install path, active README, and a clear user task.
3.Score the topic by trend signal, audience fit, search intent, and content risk.
4.Publish one lightweight guide only if the topic has a practical workflow users can follow.

Expected outcome: The page captures early long-tail search demand without overinvesting in a short-lived trend.

FAQ

Answers based on current implementation intent and source-backed workflow guidance.

What is last30days-skill?

last30days-skill is an AI agent skill from mvanhorn that researches recent signals across sources such as Reddit, X, YouTube, Hacker News, Polymarket, GitHub, and the web, then synthesizes them into a brief.

How do I install last30days-skill in Claude Code?

The repository README recommends adding the Claude Code marketplace plugin with /plugin marketplace add mvanhorn/last30days-skill, then installing the last30days plugin.

Can I use last30days-skill with Codex or Cursor?

Yes. The README lists the agent-skills CLI path for Codex, Cursor, Copilot, Gemini CLI, and other compatible hosts: npx skills add mvanhorn/last30days-skill -g.

Is last30days-skill free to use?

The repository says several sources work without configuration, but some optional sources require accounts, local tools, or API keys. Check the current README before assuming a source is available in your setup.

Is last30days-skill good for search-focused content research?

It can help find recent community signals and angles, but it should not replace primary-source verification, search result review, or Google Search Console data.

How is last30days-skill different from Google Search?

Google Search is strongest for indexed web pages and primary source discovery. last30days-skill is designed to combine recent social, developer, market, transcript, and web signals into an agent-generated brief.

Related Tools and Pages

Internal links used to keep crawl depth low and connect execution-focused workflows.

Related tools

Sources

Primary references used for topic evidence and workflow framing.

GitHub • community-signal • 2026-06-10

Turn the brief into publishable notes

Use the Markdown Previewer to clean up a research brief before converting it into a guide, comparison, or template.

Open Markdown Previewer