CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-search-code

用于查找代码示例、开源项目、GitHub Issue、技术问答、开发者讨论、HuggingFace 模型/数据集/Space。

64

Quality

75%

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-code/SKILL.md
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.

The body is highly actionable with executable commands and clear per-script guidance, and workflow sequencing includes a sensible failure fallback. Its main weakness is progressive disclosure: it cites bundle files (requirements.txt, .env.example) that do not exist.

Suggestions

Add the missing requirements.txt and .env.example files referenced in the body, or remove the references to avoid broken navigation.

Tighten the 凭证配置 paragraph and 注意 notes to remove minor verbosity without losing the credential-handling guidance.

Consider splitting the long per-script parameter tables into a separate reference file if the skill grows, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Efficient use of arg tables and executable bash examples with no concept over-explanation; only minor wording in the credential-config and 注意 notes could be trimmed, so it sits just below the lean 5 anchor.

4 / 5

Actionability

Each script gets copy-paste-ready bash commands with real flags, defaults, env-var alternatives, and multiple concrete example queries, matching the 'fully executable' anchor.

5 / 5

Workflow Clarity

Clear run sequence with an explicit dependency-failure checkpoint and web-search fallback; read-only search limits the need for stronger validation loops, keeping it just under 5.

4 / 5

Progressive Disclosure

Sections are well-organized and scripts live appropriately in scripts/, but the body references requirements.txt and .env.example that are not present in the bundle, so referenced paths are broken.

3 / 5

Total

16

/

20

Passed

Description

71%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 is specific and distinct, clearly naming the developer-search platforms and content types it covers. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness and slightly limits trigger guidance.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill, e.g. 'Use when the user wants to find code examples, open-source projects, GitHub issues, technical Q&A, developer discussions, or HuggingFace models/datasets/Spaces.'

Include colloquial trigger variants and synonyms (e.g. '搜代码', '找开源库', 'code search') to broaden natural keyword coverage.

Clarify the relationship to general web search so Claude can distinguish this skill from generic search tools.

DimensionReasoningScore

Specificity

Names the developer-search domain and lists six concrete target types across four platforms (代码示例、开源项目、GitHub Issue、技术问答、开发者讨论、HuggingFace 模型/数据集/Space), matching the 'comprehensive coverage' anchor.

5 / 5

Completeness

Provides a clear 'what' (查找六类开发者内容) but no 'Use when...' clause, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Includes natural user terms like '代码示例', '开源项目', 'GitHub Issue', and '技术问答', but lacks common colloquial variants or English synonyms that would push it to a 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to a clear developer-search niche across named platforms with distinct triggers; only minor overlap risk with generic web-search or code-assistant skills.

4 / 5

Total

16

/

20

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.