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.

52

Quality

57%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/last30days/SKILL.md

The canonical home for this skill is last30days in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

56%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 is highly actionable with a well-sequenced, checkpointed workflow and good code-level separation, but it is heavily padded with repeated ALL-CAPS directives and the SKILL.md itself is a monolithic wall rather than an overview pointing to reference material.

Suggestions

De-duplicate repeated directives — consolidate the "Do NOT output Sources:" and "WAIT for user" reminders into a single stated rule to trim padding.

Move the long output-format/stat-block templates and the query-type WebSearch recipes into a references/ doc (e.g. OUTPUT_FORMATS.md) and link from SKILL.md, turning the body into a lean overview.

Replace the hardcoded ~/.claude/skills/last30days/scripts/ path with a relative reference so the invocation survives installation in other locations.

DimensionReasoningScore

Conciseness

The body is noticeably padded — "CRITICAL: Do NOT output any 'Sources:' lists" is repeated roughly three times, "WAIT" is emphasized multiple times, and ALL-CAPS directives recur — beyond what is needed to convey the workflow.

2 / 5

Actionability

Provides concrete executable guidance: a bash setup snippet, the exact python3 invocation with --emit=compact, per-query-type WebSearch query templates, and copy-paste output-format blocks, with only minor gaps (the hardcoded ~/.claude/skills/ path).

4 / 5

Workflow Clarity

A clear sequence runs from intent parsing through script execution, mode detection, WebSearch, synthesis, summary, and a final "WAIT" gate, with explicit checkpoints ("SELF-CHECK before displaying", a quality checklist) and a validate-then-rewrite feedback loop.

4 / 5

Progressive Disclosure

Code complexity is well separated into scripts/last30days.py plus 16 lib modules, but the SKILL.md body itself is a ~430-line monolithic block of inline instructions with no references/ docs to offload detail, so structure is only partly optimized.

3 / 5

Total

13

/

20

Passed

Description

58%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 concrete capabilities and a recognizable niche, but omits an explicit "when to use" trigger clause and lacks common synonyms users would naturally invoke. Per the rubric's completeness cap, that absence limits the score.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when the user wants recent developments, recommendations, or copy-paste prompts about a topic from the last 30 days."

Include common synonyms users say — "recent", "news", "what's trending", "this month" — alongside "last 30 days" to broaden trigger coverage.

Replace the abstract "become an expert" with a more concrete action like "synthesize what communities are recommending and debating" to sharpen specificity.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Research a topic from the last 30 days", "become an expert", and "write copy-paste-ready prompts for the user's target tool" — though "become an expert" is somewhat abstract, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

It states clearly what the skill does but provides no "Use when..." trigger clause, so per the guidelines the missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant natural terms ("Reddit", "X", "Web", "last 30 days", "prompts") but misses common variations a user would actually say ("recent", "news", "what's trending", "this month"), so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

The "last 30 days on Reddit + X + Web" framing carves a fairly distinct niche with minimal overlap, though "become an expert and write prompts" shares some surface with general research/prompting skills.

4 / 5

Total

14

/

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.