CtrlK
BlogDocsLog inGet started
Tessl Logo

last30days

Recent community and social trend research over the last 30 days. Use when the brief asks what people are saying now, recent sentiment, community reactions, social proof, launch reaction, trend scan, or last-30-days context.

68

Quality

84%

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

78%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 well-structured, actionable skill body with a clear runtime command, sequenced workflow, and a properly delegated one-level reference. The main room for improvement is trimming the redundant untrusted-evidence guidance and tightening validation around the final report.

Suggestions

Consolidate the duplicated 'untrusted evidence / do not claim source access' guidance: it appears in both Source Coverage Rules and the report's Evidence Note — state it once and reference it.

Specify how <safe-topic-slug> is derived (e.g., lowercase, hyphenate, strip non-alphanumeric) so the save path is reproducible.

Add an explicit validation checkpoint after writing the report (e.g., confirm the Source Coverage table lists every source class and that all [n] citations resolve) before finalizing.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, but the long enumeration of sources to avoid claiming ('Reddit, X/Twitter, YouTube transcripts...') and the untrusted-evidence note appearing in both Source Coverage Rules and the report's Evidence Note are minor instances that could be trimmed. It is not a 5 because of that redundancy, and not a 3 because the writing is largely lean rather than padded.

4 / 5

Actionability

Provides a copy-paste engine command and a concrete Markdown report-contract scaffold with an explicit output path. It is not a 5 because derivation of '<safe-topic-slug>' is unspecified and the synthesis step is described abstractly, and not a 3 because the runnable command and full report template are concrete and executable.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with an engine-failure fallback checkpoint and explicit source-status labeling. It is not a 5 because there is no explicit validate->fix->retry feedback loop after report writing, and not a 3 because the sequence and fallback checkpoint are well defined rather than gap-laden.

4 / 5

Progressive Disclosure

Clear overview body with a well-signaled one-level-deep reference ('load references/save-html-brief.md'), which is a real file, with content appropriately split so the optional HTML flow stays out of the main path. It is not a 4 because the single reference is cleanly signaled and navigation is straightforward.

5 / 5

Total

17

/

20

Passed

Description

90%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: it clearly states both what the skill does and when to use it, with comprehensive, natural trigger terms and a well-defined niche. The only soft spot is specificity, where a single generic verb ('research') carries the action rather than a list of concrete operations.

DimensionReasoningScore

Specificity

Names the domain ('Recent community and social trend research over the last 30 days') and conveys concrete research facets (sentiment, community reactions, trend scan), but the single verb 'research' keeps actions from being comprehensive. It is not a 2 because the domain is well specified and the research scope is concrete, and not a 4 because no multiple distinct action verbs are listed.

3 / 5

Completeness

Explicitly answers both what ('Recent community and social trend research over the last 30 days') and when ('Use when the brief asks...') with concrete trigger phrases. It is not a 4 because the 'when' is fully explicit with named trigger conditions, not merely adequate.

5 / 5

Trigger Term Quality

Comprehensive natural terms ('what people are saying now, recent sentiment, community reactions, social proof, launch reaction, trend scan') plus synonyms ('last 30 days'/'last30days'/'last-30-days context') and Chinese variants in the triggers list. It is not a 4 because coverage of natural phrasings and synonyms is thorough rather than merely good.

5 / 5

Distinctiveness Conflict Risk

Clear niche (last-30-days community/social trend research) with distinct triggers and minimal overlap with general research skills. It is not a 4 because the time-boxed community-sentiment framing makes the niche sharply distinguishable rather than only 'mostly distinct'.

5 / 5

Total

18

/

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
nexu-io/open-design
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.