CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

last30days

Research what people have discussed in the last 30 days across high-signal public platforms. Use when the user asks for `/last30days`, recent trend research, competitive intelligence, market pulse briefs, or engagement-ranked synthesis from Reddit, Hacker News, GitHub, X, YouTube, Polymarket, and similar sources.

68

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-organized single-purpose skill body: concrete platform and engagement guidance, a clear sequenced workflow, and copy-paste example prompts with no wasted tokens. The only refinements would be explicit validation checkpoints (e.g., verifying the 30-day window per source) and slightly more concrete search mechanics per platform.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and assumes Claude's competence: every line gives skill-specific instruction (platforms to search, metrics to capture, de-duplication, ranking, output structure, HTML/ELI5 variants) with no padding and no explanation of concepts Claude already knows. Not a 4 because no section needs trimming.

5 / 5

Actionability

Concrete, specific guidance throughout: named platforms, concrete engagement signals ("upvotes, comments, stars, views, reposts, or prediction odds"), a defined brief structure, and three copy-paste-ready example prompts. It stays below 5 because the actual mechanics of searching each platform and capturing engagement data are left general — a minor gap for an instruction-only skill.

4 / 5

Workflow Clarity

The 8-step workflow is clearly sequenced with implicit quality checkpoints ("De-duplicate repeated stories across platforms", "Rank findings by engagement and relevance, not by editorial placement"). It is not a 5 because there is no explicit validation step, e.g., verifying each source's date falls within the 30-day window before including it.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/, scripts/, or assets/ bundle exists), and the body is well organized into Overview, Workflow, and Example Prompts sections — the simple-skill case the rubric scores at 5.

5 / 5

Total

18

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what-and-when structure, natural trigger phrases, and named platforms. Its main weaknesses are a single umbrella action instead of an enumerated action list, and a couple of broad trigger phrases that slightly increase overlap risk with generic research skills.

Suggestions

Replace the single umbrella action with an enumerated action list, e.g., "Searches Reddit, Hacker News, GitHub, X, YouTube, and Polymarket for the last 30 days, captures engagement metrics, de-duplicates stories, ranks findings by engagement, and synthesizes a brief."

Add common user phrasings as triggers, such as "trending topics", "what people are saying", or "recent discussions", to broaden natural keyword coverage.

Anchor the broad phrases "competitive intelligence" and "recent trend research" more tightly to the 30-day window and engagement ranking to reduce conflict risk with general research skills.

DimensionReasoningScore

Specificity

"Research what people have discussed in the last 30 days across high-signal public platforms" names the domain and 1-2 concrete actions (research discussions, engagement-ranked synthesis), but does not enumerate several distinct actions like the anchor-5 example. It is above a 2 because the domain and action are concrete rather than generic.

3 / 5

Completeness

It clearly answers both questions with concrete trigger phrases: the "what" ("Research what people have discussed in the last 30 days across high-signal public platforms") and an explicit "Use when the user asks for `/last30days`, recent trend research, competitive intelligence, market pulse briefs, or engagement-ranked synthesis...", matching the anchor-5 example structure exactly. Not below 5 because neither half is vague or implied.

5 / 5

Trigger Term Quality

Good keyword coverage: the command "`/last30days`", "recent trend research", "competitive intelligence", "market pulse briefs", "engagement-ranked synthesis", plus six named platforms. A few natural user phrasings are missing (e.g., "trending topics", "what people are saying", "recent discussions"), which keeps it below the comprehensive anchor-5 coverage.

4 / 5

Distinctiveness Conflict Risk

The time-boxed (30 days), engagement-ranked, multi-platform niche with a distinctive command trigger is mostly distinct, but "recent trend research" and "competitive intelligence" are broad enough phrases to create minor overlap risk with general web-research or market-research skills, so it does not reach the minimal-conflict anchor 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

eigent-ai/agent-skills

Path

skills/search-and-research/last30days/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.