CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-search-social-media

搜索社区、社媒、新闻热点、百科趋势、开发者生态和技术讨论时使用。

60

Quality

68%

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 ./skills/sn-search-social-media/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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 real executable scripts, copy-paste commands, and a clear resource-selection table, supported by well-organized one-level-deep bundle references; it loses points mainly to mild rule redundancy and implicit rather than explicit verification checkpoints.

Suggestions

De-duplicate the crypto-ban and credential rules so each is stated once, tightening conciseness toward anchor 3.

Add an explicit verify-before-report checkpoint (e.g., check `success`/`error` fields and cross-source consistency before reporting a trend) to strengthen workflow clarity.

Resolve or clarify the missing `requirements.txt` reference (the dependency install command targets a file not present in the bundle) to avoid a broken bundle reference.

DimensionReasoningScore

Conciseness

The body is mostly lean and well-organized, but the crypto ban and credential rules are restated across 凭证配置, 硬性规则, and 输出约定, adding some redundancy that could be tightened — matching the 'mostly efficient but could be tightened' anchor 2 rather than the every-token-earns-its-place anchor 3.

2 / 3

Actionability

It provides concrete, copy-paste-ready `python3 scripts/...` commands with real flags and example arguments, a scenario→tool resource table, and a concrete output JSON schema, with all referenced scripts being real bundle files — matching the fully-executable anchor 3.

3 / 3

Workflow Clarity

Scenario-based guidance and explicit fallbacks (raise --scan, switch to browser-use on dependency failure, stop on crypto error) give a clear selection flow, but explicit validation/verify-before-report checkpoints are only implicit, matching anchor 2 rather than the explicit-checkpoint anchor 3.

2 / 3

Progressive Disclosure

SKILL.md acts as a well-organized overview (clear sections + resource table) pointing to real one-level-deep bundle scripts in scripts/, with no deeply nested references, matching the clear-overview-with-well-signaled-references anchor 3.

3 / 3

Total

10

/

12

Passed

Description

65%

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 provides strong explicit trigger guidance and natural keywords, but the capability statement relies on a single generic verb ("搜索") rather than enumerating concrete actions, leaving both specificity and completeness at the mid level.

Suggestions

Expand the description to list concrete actions (e.g., fetching pageview trends, searching public repos/issues, scanning Hacker News hot lists) instead of the single generic verb "搜索".

Keep the explicit "时使用" trigger but pair it with a clearer 'what' clause so both purpose and trigger are unambiguous.

Add a scoping cue that distinguishes this from a general web-search skill (e.g., emphasizing free/no-keycode public signal sources) to reduce conflict risk.

DimensionReasoningScore

Specificity

The description names the domain clearly ("社区、社媒、新闻热点、百科趋势、开发者生态和技术讨论") but uses a single generic action verb ("搜索") rather than listing multiple concrete capabilities, matching the 'names domain and some actions' anchor rather than the multi-action anchor 3.

2 / 3

Completeness

It has an explicit 'when' trigger ("...时使用") but the 'what' is only the generic verb "搜索" without concrete listed actions, so it answers 'when' clearly but 'what' only thinly — not the clear both-what-and-when of anchor 3.

2 / 3

Trigger Term Quality

It covers natural terms a user would actually say — "搜索社区", "社媒", "新闻热点", "百科趋势", "技术讨论" — giving good coverage of the search-domain keywords matching the anchor 3 example.

3 / 3

Distinctiveness Conflict Risk

The named source types give it a recognizable niche, but the broad 'search communities/social-media/news' framing could still overlap with a general web-search skill, matching anchor 2 rather than the clearly-distinct-niche anchor 3.

2 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
OpenSenseNova/SenseNova-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.