CtrlK
BlogDocsLog inGet started
Tessl Logo

last30days

Research a topic from the last 30 days on Reddit + X + Web, become an expert, and write copy-paste-ready prompts for the user's target tool.

53

Quality

60%

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

Fix and improve this skill with Tessl

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

Quality

Content

50%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.

The body gives executable, well-sequenced guidance but is undermined by duplicated sections, a script path that does not match the actual bundle, a large unmentioned lib/ support tree, and no validation checkpoints for a batch external-research workflow.

Suggestions

Delete the duplicated options block (lines 98-101) and the duplicated '## How It Works' heading (line 103 or 105), and consolidate 'Output Interpretation' with 'Expected Output Format'.

Fix the script path to match the bundle, e.g. 'python scripts/last30days.py "[TOPIC]" --emit=compact', so the command runs as written.

Add an explicit verification step after the run (e.g. confirm non-empty output, handle API-key/empty-result fallback) to satisfy the batch-operation validation requirement.

DimensionReasoningScore

Conciseness

Noticeable padding: the options list (--quick/--deep/--emit) is duplicated verbatim at lines 36-40 and 98-101, the '## How It Works' heading is duplicated at lines 103 and 105, and 'Output Interpretation' repeats 'Expected Output Format'.

2 / 5

Actionability

Provides a concrete, mostly executable command with flags and example output blocks, but the script path in the body (.github/skills/last30days/scripts/last30days.py) does not match the actual bundle path (scripts/last30days.py), a gap that would break the command as written.

4 / 5

Workflow Clarity

The run -> display -> answer-from-loaded-context -> only-rerun-for-new-topic sequence is clear, but this batch research skill (50-70 Reddit, 40-60 X sources) has no validation/verification checkpoints, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Section structure exists and the script is referenced, but the path is mis-signaled (wrong prefix) and the rich scripts/lib/ support module bundle is never mentioned, leaving navigation only partially clear.

3 / 5

Total

12

/

20

Passed

Description

70%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.

The description conveys a distinctive, multi-action capability but omits any explicit 'when to use it' trigger guidance, which caps its completeness. It is otherwise specific and well-triggered.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants current research, recommendations, or news from the last 30 days across Reddit, X, and the web.'

Replace the vague 'become an expert' with a concrete capability like 'synthesize findings into a report'.

Add a few natural synonyms users say ('news', 'recommendations', 'trending', 'what people are saying') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the Reddit + X + Web research domain and several concrete actions ('Research a topic', 'write copy-paste-ready prompts'), though 'become an expert' is vague filler keeping it below a 5.

4 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good coverage of natural terms ('Reddit', 'X', 'Web', 'last 30 days', 'prompts', 'target tool'), but missing common variations a user might say like 'news', 'recommendations', or 'trending'.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (recent multi-source social/web research plus tailored prompt writing) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
0xRabbidfly/Eric-Cartman
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.