CtrlK
BlogDocsLog inGet started
Tessl Logo

sn-deep-research

用于用户请求深度研究、系统性研究、竞品分析、方案对比、趋势分析或事实核查时。**遇到以下任一情况就主动使用本 skill,不要自行搜几条就回答**:①用户出现触发词:深度研究 / 深度调研 / 深入研究 / 全面研究 / 系统研究 / 调研 / 调查 / 尽调 / 行业研究 / 市场研究 / 竞品分析 / 政策研究 / 技术研究 / 趋势研究 / 事实核查 / 写一份研究报告 / 调研报告 / 深度报告 / research / deep research;②请求需要跨多来源取证、多维度对比、交叉验证才能给出可靠结论;③用户要求产出报告、白皮书、行业分析或尽调文档;④话题涉及最新政策/市场/产品/价格/法规,需要系统核查。无核验要求的简单常识问答不使用。模糊或宽泛的"研究/了解一下 X"也优先触发。仅不用于:一句话摘要、已给定单一来源的整理、纯文字润色改写。

71

Quality

87%

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

88%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 highly actionable, well-sequenced orchestration skill with concrete payload contracts, validation gates, and explicit failure-routing feedback loops. Its only notable gaps are minor conciseness repetition and bundle references whose target files are not all present.

Suggestions

Consolidate the repeated payload header pattern ('先读取 {plugin_role_dir}/<role>.md 并严格遵守.') via a single documented convention reference to trim length.

Ensure all referenced role .md and schema .md files are included in the bundle so the one-level-deep references resolve for every payload.

DimensionReasoningScore

Conciseness

Dense, directive controller prose that assumes Claude's intelligence and avoids explaining basic concepts; every section is operational. Not a 5 only because the 550-line body, while justified by 3 modes and 10 stages, has minor repetition across mode pipelines and payload templates that could be tightened.

4 / 5

Actionability

Provides copy-paste-ready payload contracts with exact field names, absolute path templates, concrete bash commands (e.g., the progress_event.py and launch_workbench.py invocations), and explicit output file targets covering the common per-stage cases.

5 / 5

Workflow Clarity

Three mode pipelines are explicitly sequenced with per-stage validation gates (validation_ok:true, validator scripts), and §4.4 gives a complete failure/retry table with routing, retry limits, and feedback loops for evidence, planning, and stitching — a textbook validate→fix→retry loop for a batch research operation.

5 / 5

Progressive Disclosure

Clear §1→§6 reading map with one-level-deep references to role files, schemas, and validator scripts; the referenced validator scripts exist in ./scripts/. Not a 5 because the role .md and schema .md files referenced in payloads are not present in the provided bundle, so the split is signaled but not fully verifiable.

4 / 5

Total

18

/

20

Passed

Description

86%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 trigger-rich description with comprehensive natural keywords and explicit exclusions that give it a clear, low-conflict niche. Its main weakness is that the 'what does this skill do' capability is implied rather than stated concretely.

Suggestions

Open with a concrete capability statement (e.g., 'Orchestrates multi-agent deep research to produce verified reports') before the trigger list so the 'what' is as explicit as the 'when'.

Tighten the four numbered trigger conditions, which partially overlap with the trigger-word list, to reduce redundancy.

DimensionReasoningScore

Specificity

Lists several specific trigger scenarios (深度研究、系统性研究、竞品分析、方案对比、趋势分析、事实核查) plus four explicit numbered trigger conditions and concrete exclusions, but the core 'what' (multi-agent research orchestration) is implied rather than enumerated as concrete actions.

4 / 5

Completeness

Has an exceptionally explicit and thorough 'when' (trigger words, four conditions, and exclusions) but the 'what' is only weakly implied via the trigger context rather than stating the orchestration capability directly; not a 5 because 'what' lacks a concrete capability statement.

4 / 5

Trigger Term Quality

Comprehensive coverage of natural terms including Chinese synonyms (研究/调研/调查/尽调/行业研究), scenario phrases, and English equivalents (research/deep research) that users would naturally say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (deep multi-source research requiring cross-verification) with explicit exclusions (简单常识问答不使用, 一句话摘要, 纯文字润色) that sharply minimize conflict with general Q&A or summarization skills.

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

skill_md_line_count

SKILL.md is long (553 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.