CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

last30days

Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Failed to scan

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/last30days/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 mature, dense operational contract with best-in-class reference routing and strong validation checkpoints including a pre-present checklist and bounded regeneration loop. Its weakness is repetition and sheer length in the root body, which could be meaningfully tightened by delegating exception detail to the references it already routes to.

Suggestions

Deduplicate instructions stated twice (SKILL_DIR/env retention in Bootstrap and Dispatch; ScrapeCreators Reddit backfill rules in Dispatch and Security) and drop the version number from the H1, keeping it in frontmatter only.

Move each LAW's mode-specific exceptions (comparison, discovery, hiring, agent-mode) into their respective references, leaving one-sentence laws in the root.

Trim the Security & Permissions section to endpoints and consent boundaries, moving credit-spending thresholds and backend lists into a reference file.

DimensionReasoningScore

Conciseness

The body avoids general-concept padding and assumes competence, but it is noticeably repetitive: SKILL_DIR/env-var retention instructions appear nearly verbatim twice, the ScrapeCreators backfill credit rules are stated in both dispatch and the security section, and the laws restate their exceptions multiple times. The version number "v3.39.0" in the H1 is time-sensitive detail that will stale, and much of the output-contract density could be tightened or delegated to references.

3 / 5

Actionability

Concrete guidance dominates: a complete executable first-run gate command (`grep -q "SETUP_COMPLETE=true" ~/.config/last30days/.env ...`), exact flags (`--plan -` with quoted heredoc, `--resolve-save-dir`, `--diagnose --cached --json`, the three `--discover` legs), and precise env-var handling. It falls short of anchor 5 because the primary engine invocation itself lives in the runbook reference rather than the body.

4 / 5

Workflow Clarity

A clear dispatch sequence (bootstrap → reference routing → first-run gate → topic routes → output contract → pre-present self-check) with genuine validation checkpoints: the gate's one-token branch, the 9-item pre-present checklist, the LAW 8 post-synthesis check, and a regenerate-at-most-once feedback loop. Minor gaps remain because step ordering (Steps 0.45–0.75) and mode-specific sequences are delegated to references, so the body alone does not carry the full sequence.

4 / 5

Progressive Disclosure

The routing table is exemplary: 16 condition → required-read → return-point rows, every referenced file (references/runtime.md through references/save-html-brief.md) verified to exist on disk, one level deep with each mode returning to the root for further loads. The body is a true dispatch hub over well-signaled, appropriately split references.

5 / 5

Total

16

/

20

Passed

Description

66%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 specific, third-person description with strong platform-name keyword coverage and a distinct recency niche. Its main weakness is the absence of any explicit "Use when..." trigger clause, plus missing natural synonyms such as Twitter, social media, and sentiment.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for recent public opinion, reactions, or sentiment on any topic from the past month, or mentions Reddit, X/Twitter, YouTube, or TikTok discussion.",

Include common synonyms users would say: "Twitter" alongside "X", plus "social media", "sentiment", "opinions", and "trending".

Name the primary deliverable (a cited, source-attributed research report) so the "what" covers output, not just data collection.

DimensionReasoningScore

Specificity

Concrete actions are named in third person: "Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web" and "Includes a doctor health check to diagnose broken or missing sources". It stops short of anchor 5 because significant body capabilities (cited report synthesis, comparisons, hiring signals, recommendations) are unmentioned, leaving minor coverage gaps.

4 / 5

Completeness

The "what" is clear (research recent community opinion across named sources, plus a doctor health check), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps this dimension at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Platform names ("Reddit", "X", "YouTube", "TikTok", "Hacker News", "GitHub") plus "last 30 days" and "posts and engagement" are terms users naturally say. Not anchor 5 because common synonyms are missing: "Twitter" for X, "social media", "sentiment", "opinions", "trending".

4 / 5

Distinctiveness Conflict Risk

The recency-windowed, multi-platform social-listening niche with a named doctor diagnostic is mostly distinct with clear triggers. "Any topic" and "the web" keep it from anchor 5 by creating minor overlap with generic research/web-search skills.

4 / 5

Total

15

/

20

Passed

Validation

62%

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

Validation — 10 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 missing

Warning

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

10

/

16

Passed

Repository

mvanhorn/last30days-skill

Path

skills/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.