CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

quality-screen

AI Berkshire skill: 去劣筛选:7条指标快速排除非一流公司. Source: skills/quality-screen.md.

Quality

69%

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/quality-screen/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 strong, dense instruction-only skill: exact thresholds, well-structured exemption rules with concrete case examples, an explicit batch workflow with sanity checkpoints, and a complete output template. Main gaps are the missing data cross-check/verification loop and inline meta-harness content that slightly inflates the token budget.

Suggestions

Add an explicit verification step between data collection and screening, e.g. 'For each company, cross-check at least two sources for ROE and FCF before judging; if sources disagree by >10%, flag ⚠️ and state both values.'

Give one or two concrete example WebSearch queries in the data-collection step (e.g. "腾讯 10年 ROE 历史") so the parallel agents fetch consistently.

Move the Codex adapter note out of SKILL.md (or compress it to 2-3 lines) so the body leads with the screening workflow.

DimensionReasoningScore

Conciseness

The body is efficient: thresholds live in compact tables ("10年平均ROE | < 8%"), exemption logic is 3-4 lines each, and it never explains concepts Claude already knows. It is not a 5 because the 'Codex adapter note' section is meta-harness guidance unrelated to the screening task and some case commentary ("典型案例:美团/亚马逊/Costco") could be trimmed.

4 / 5

Actionability

Guidance is highly concrete and executable for an instruction-only skill: exact thresholds and time windows per metric ("5年累计FCF为负", "OCF/净利润 5年均值 < 0.7"), per-metric data-collection specs, a data-source priority order ("公司年报 > 券商研报 > 财经数据平台"), and a copy-paste output markdown template. It is not a 5 because the data-gathering step gives no concrete example WebSearch queries or tool invocations.

4 / 5

Workflow Clarity

A clear four-step sequence (parse input → parallel data collection → per-metric check → templated output) with real checkpoints for a batch operation: the company list is surfaced for confirmation, boundary cases get ⚠️ with values, and missing data is labeled "数据不足" rather than pass/fail. It is not a 5 because there is no explicit verify/re-check loop for cross-checking fetched financial figures (the cross-check rule only appears indirectly via the AGENTS.md reference).

4 / 5

Progressive Disclosure

The skill has no bundle files (no references/, scripts/, assets/), and its single-file structure is well organized with clear section headers, so content placement is mostly appropriate. It is not a 5 because it exceeds 50 lines with everything inline — the output template and the Codex adapter note in particular sit in SKILL.md rather than being split or referenced out.

4 / 5

Total

16

/

20

Passed

Description

48%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 communicates a clear niche and a single-screen 'what', but it is too thin: no trigger guidance, no named indicators, and no synonyms. It would rarely be selected by a user typing natural screening-related phrases, and the meta 'Source:' line wastes the trigger budget.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to screen companies/stocks for quality, mentions 排雷, 选股, 去劣, ROE, or wants to filter an industry/index/theme stock list before deeper research."

Name 2-3 of the concrete indicators (10年平均ROE≥8%, 5年累计自由现金流为正, 利息覆盖≥2倍) to raise specificity and keyword coverage at once.

Remove meta text ("AI Berkshire skill:", "Source: skills/quality-screen.md.") from the description; it adds no trigger value and dilutes the token budget.

DimensionReasoningScore

Specificity

The description names the domain ("去劣筛选" / "一流公司" — excluding non-first-class listed companies) and a single generic action ("7条指标快速排除非一流公司"), but never names any of the 7 indicators or concrete screening actions. This matches the anchor 'Names the domain but actions are minimal or generic' ("Processes PDF files"); it is not a 3 because no 1-2 concrete actions are actually enumerated.

2 / 5

Completeness

There is a reasonably clear 'what' (screen out non-first-class companies via 7 indicators) but no 'Use when...' clause or equivalent trigger guidance anywhere, so completeness is capped at 3 per the rubric guideline. It is not a 2 because the 'what' is stated clearly, not vaguely.

3 / 5

Trigger Term Quality

Some relevant natural keywords are present ("去劣筛选", "指标", "一流公司", "排除"), which fits 'Some relevant keywords but missing common variations or synonyms'. It is not a 4 because users' likely phrasings like 排雷, 选股, ROE, 自由现金流, 财务指标, stock screening are entirely absent.

3 / 5

Distinctiveness Conflict Risk

The niche (Berkshire-style quality screening of listed companies) is mostly distinct with only minor overlap risk against other financial-analysis skills. It is not a 5 because the meta prefixes "AI Berkshire skill:" and "Source: skills/quality-screen.md." add noise rather than distinct triggers, and the description alone does not sharply separate it from general company-research skills.

4 / 5

Total

12

/

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/quality-screen/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.