CtrlK
BlogDocsLog inGet started
Tessl Logo

quality-screen

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

52

Quality

57%

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

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and concise, with clear thresholds, exemptions, and a defined workflow. Its main gaps are the absence of a validation/retry feedback loop for batch screening and no progressive disclosure structure.

Suggestions

Add an explicit validation/retry checkpoint for batch mode, e.g. when data is missing or contradictory, flag it and re-query before scoring, rather than only labeling "数据不足".

Consider moving the detailed output template or the per-indicator methodology into a reference file (e.g. references/output-template.md) to enable progressive disclosure.

For batch mode, add a verification step that cross-checks retrieved financial figures across two sources before applying the exclusion rules.

DimensionReasoningScore

Conciseness

The body is lean and table-driven, assumes Claude's competence, and does not explain concepts Claude already knows; every section earns its place.

3 / 3

Actionability

It gives exact indicator thresholds, explicit exemption conditions, a parallel data-collection procedure, and a copy-ready output template — concrete and executable guidance throughout.

3 / 3

Workflow Clarity

The four-step sequence is clear with status markers and exemption checks, but the batch mode lacks an explicit validate→fix→retry feedback loop, which caps batch-operation workflows at 2.

2 / 3

Progressive Disclosure

Sections are well-organized, but the skill is a single monolithic file with no references or content split, so it is not leveraging progressive disclosure.

2 / 3

Total

10

/

12

Passed

Description

35%

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 conveys the skill's purpose and domain but reads as a label-with-source rather than a trigger-oriented capability statement. It lacks a "Use when..." clause and natural user keywords.

Suggestions

Add an explicit "Use when..." clause stating when Claude should invoke this skill, e.g. "Use when screening listed companies or industries to quickly exclude non-first-class companies."

Include natural trigger terms users would actually say, such as 筛选股票, 排除非一流公司, 选股, or 质量筛选.

Remove the "Source: skills/quality-screen.md." metadata from the description or move it into the body so the description focuses on capability and triggers.

DimensionReasoningScore

Specificity

Names the domain (去劣筛选) and a core action (7条指标排除非一流公司), but it is one composite action rather than multiple distinct concrete actions.

2 / 3

Completeness

States what the skill does, but a "when to use" clause is missing; per guidelines a missing "Use when..." clause caps completeness at 2.

2 / 3

Trigger Term Quality

"去劣筛选" is a domain label rather than natural keywords a user would say, and no "Use when..." trigger phrasing or common user variations are present.

1 / 3

Distinctiveness Conflict Risk

The niche (elimination screening of listed companies) is fairly specific, but without explicit triggers it is distinguishable mainly by topic rather than by distinct trigger terms.

2 / 3

Total

7

/

12

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
xbtlin/ai-berkshire
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.