CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

expert-osbi

开源商业智能(OSBI)专家。从公开信源提取、跟踪和分析商业信息,承接信源情报、竞对动向、公开直播调研及市场/基金/技术研究。原始搜索与内容获取按平台使用文中列出的采集技能和公共 smart-search;潜客探索、互动与联络交 expert-bd,融资推进交 expert-ir。

Quality

77%

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 ./crews/main/skills/expert-osbi/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

An efficient, well-structured hub skill: concise routing tables, concrete tool and path guidance, and explicit verification and delegation rules. The referenced workflow and tool files carry the detailed steps, so validation loops and example invocations are not visible from this file alone.

DimensionReasoningScore

Conciseness

The ~44-line body is lean and dense: routing tables, tool names, storage paths, and operational constraints with zero padding and no explanation of concepts Claude already knows. Every token earns its place, matching anchor 5.

5 / 5

Actionability

Concrete, executable guidance throughout — a task-to-workflow routing table, exact tool names and commands ("douyin-hunter live", "info-record", wrapper "init-db"), and precise storage paths ("osbi/live/<platform>/<日期时间>-<room_id>/"). Not 5 because full command usage is deferred to external tool docs with no example invocations for the common cases.

4 / 5

Workflow Clarity

The opening gives an explicit sequence ("先明确研究问题、对象、范围与交付形式,再取证、提取、交叉核实和分析") and the analysis section sets verification checkpoints (attach sources, record sample scope, explicitly flag unverifiable info). Falls short of 5 because detailed workflow steps and error-recovery loops are deferred to workflow files and no validate→fix→retry loop is stated in the body.

4 / 5

Progressive Disclosure

Well-signaled, one-level-deep references (workflows/*.md links, tools/*/SKILL.md links) keep the body a clean routing overview. Minor gaps: the referenced bundle files are not present to verify, and "browser-guide" plus its nested "references/source-evidence.md" path is referenced by name only without a resolvable link.

4 / 5

Total

17

/

20

Passed

Description

66%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 well-scoped hub description that clearly states capabilities and draws sharp delegation boundaries against sibling experts. Its main weakness is the absence of an explicit "when to use" trigger clause, leaving invocation timing only weakly implied, and keyword coverage is missing a few natural synonyms.

Suggestions

Add an explicit trigger clause equivalent to "Use when..." (e.g., 当用户需要竞对情报、公开直播调研、市场/基金/技术公开信源研究时使用) to raise completeness.

Include natural synonyms users actually say — 尽职调查/尽调、舆情、竞品分析、情报收集 — alongside the existing domain terms to broaden trigger-term coverage.

Clarify that "开源" means public-source OSINT rather than open-source software, to avoid confusion with open-source BI tooling and reduce mis-triggering.

DimensionReasoningScore

Specificity

Lists several concrete actions ("提取、跟踪和分析商业信息") across five named task domains (信源情报、竞对动向、公开直播调研、市场/基金/技术研究), with only minor coverage gaps. It falls short of anchor 5 because the verbs are generic and comprehensiveness rests on domain enumeration rather than a full capability list.

4 / 5

Completeness

The "what" is clear (extract, track, analyze business info from public sources with listed task types), but there is no explicit "Use when..." clause or equivalent trigger guidance — the task enumeration only weakly implies when to invoke it, which caps this at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage ("竞对动向", "公开直播调研", "市场/基金/技术研究", "商业信息") that users would plausibly say, but common synonyms such as 尽职调查/尽调、舆情、竞品分析 are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Explicit routing boundaries ("潜客探索、互动与联络交 expert-bd,融资推进交 expert-ir", platform hunters + smart-search for acquisition) carve a clear niche with minimal conflict risk. Not 5 because 市场/技术/基金研究 is broad enough to overlap with related research skills, and "开源" could be misread as open-source software BI.

4 / 5

Total

15

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 7 missing, 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

TeamWiseFlow/xiaobei

Path

crews/main/skills/expert-osbi/SKILL.md

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.