CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

news-pulse

公司新闻脉搏:股价异动时快速归因。用 4 个并行 Agent 侦察公司事件/监管政策/行业对手/市场情绪,产出"事件时间线 + 异动主因判断 + 是否触发论文重审"。

Quality

78%

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 ./codex-skills/news-pulse/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 a highly actionable, well-sequenced orchestration workflow with concrete commands, prompt templates, and output specs throughout. Its weaknesses are a fully monolithic structure with no reference files for the agent prompts or report template, and a missing failure-handling loop for the parallel agent fan-out.

Suggestions

Move the four agent task descriptions and the 8-section report template into references/ files (e.g. references/agent-tasks.md, references/report-template.md) and link to them from the body, keeping SKILL.md as a lean orchestration overview.

Add a validation/recovery step after launching the 4 agents: what to do if a report is missing, an agent errors out, or a report lacks the required output format (e.g. re-dispatch that single task before synthesis).

Trim the Codex adapter note and the pre-filled example rows in the attribution tables to tighten token efficiency.

DimensionReasoningScore

Conciseness

Nearly every token is operational (parameter tables, per-agent task specs, a fill-in prompt template, output format spec) with no explanation of concepts Claude already knows. Minor trimming possible in the Codex adapter note and the example rows of the report tables — 'minor instances of over-explanation that could be trimmed' (4), not 5.

4 / 5

Actionability

Fully executable guidance: exact tool invocations (TeamCreate with team_name/agent_type values, 'python3 tools/xueqiu_scraper.py --user-id 1247347556 --keywords {公司名},{股票代码} --output /tmp/dyp-{公司名}.md'), a complete copy-paste prompt template with placeholders, and an exact output path ('reports/{公司名}/{公司名}-news-{YYYYMMDD}.md'). Matches 'fully executable; copy-paste ready'.

5 / 5

Workflow Clarity

Nine clearly numbered steps with explicit sequencing, a mid-flight checkpoint (展示每份报告核心发现、等待全部 4 份到齐后 shutdown), and cleanup. Falls short of 5 because there is no explicit validation/recovery loop for the batch fan-out — no instruction for what to do if an agent fails, times out, or returns a partial report.

4 / 5

Progressive Disclosure

Well-sectioned single file, but all content is inline: the four agent task specs and the full report output template are monolithic, no references/ bundle exists despite cross-references to repo files (investment-team.md, tools/financial_rigor.py, AGENTS.md). Fits 'some structure but could be better organized' (3); not 4 because clearly separable content is inlined with no one-level-deep reference files.

3 / 5

Total

16

/

20

Passed

Description

67%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 clearly conveys what the skill does and its key deliverables, with a distinctive multi-agent attribution niche. Its main weaknesses are thin natural-language trigger coverage and a terse 'when' clause that could name concrete user scenarios. Suggestions:

Suggestions

Add an explicit trigger clause with natural user phrases, e.g. 'Use when a stock 涨/跌 sharply (单日 ±5%、一周 ±10%), after earnings moves, or when a headline needs noise-vs-signal judgment' — this would raise both completeness and trigger_term_quality.

Include common synonyms users would say when invoking: 股价大涨/大跌、为什么跌、异动原因、新闻影响 — currently only 股价异动 and 归因 are present.

State the when-conditions with concrete thresholds in the description itself rather than only in the body's 适用场景 table.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('用 4 个并行 Agent 侦察公司事件/监管政策/行业对手/市场情绪') plus three named outputs ('事件时间线', '异动主因判断', '是否触发论文重审'). Not 5 because the outputs are named but not unpacked; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Has a clear 'what' (4 parallel agents, named deliverables) and an explicit 'when' ('股价异动时'), but the 'when' is a single terse condition without trigger scenarios or a 'Use when...' phrasing. Fits anchor 4: 'when could be more explicit or specific'.

4 / 5

Trigger Term Quality

Contains relevant keywords ('股价异动', '归因', '新闻', '市场情绪') but misses the natural phrases users would actually say such as '大涨/大跌', '为什么跌', or '财报后怎么解读'. Matches the anchor 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

A clear niche (rapid multi-agent news attribution for stock moves) with distinctive terms like 归因 and 论文重审; minor overlap risk with sibling investment-research skills (/investment-team, /earnings-review) referenced in the body.

4 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

xbtlin/ai-berkshire

Path

codex-skills/news-pulse/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.