CtrlK
BlogDocsLog inGet started
Tessl Logo

shadow-account

Shadow Account — 从用户交割单提炼盈利模式(3-5 条人话规则)→ 跨 A股/港股/美股/crypto 多市场回测 → 差值归因 → 8-section PDF 报告。叙事:你的影子,没有情绪噪音。

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 high-quality, token-efficient skill spec: concrete tool calls, well-sequenced workflow with explicit validation/feedback loops, and clean single-file organization. It earns top marks across all content dimensions.

DimensionReasoningScore

Conciseness

Lean and dense — concrete tool calls, field definitions, and templates with no padding or explanation of concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

Provides concrete tool signatures with parameters (extract_shadow_strategy(journal_path=...), run_shadow_backtest(shadow_id=..., journal_path=...)), exact output field names, dialogue templates with placeholders, and a ready-to-inject rule-translation prompt — fully actionable guidance.

3 / 3

Workflow Clarity

Four-step workflow is explicitly sequenced (1-4) with feedback loops: '如果用户说不像,提高 min_support 重跑', '样本不足 profitable roundtrips < 5 → raise', and weasyprint-failure fallback — clear validation checkpoints and error recovery.

3 / 3

Progressive Disclosure

Single self-contained file, well-organized into clear sections (触发/工作流/产出解读/对话模板/红线) with no bundle files to navigate; appropriately scoped with no nested references.

3 / 3

Total

12

/

12

Passed

Description

67%

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 is specific and distinct, but it is missing an explicit 'Use when...' trigger clause and contains marketing-flavored fluff rather than natural user-facing trigger terms. Adding a concrete trigger phrase and dropping the tagline would raise trigger_term_quality and completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to extract/validate their own trading patterns, backtest their playbook, or see how much more they could have earned.'

Replace '叙事:你的影子,没有情绪噪音。' with natural keywords users would actually say (e.g. '交割单分析, 策略提炼, 打法回测, 多市场回测').

Keep the concrete action list but ensure at least one common variation per capability (e.g. 'trade journal' alongside '交割单').

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '提炼盈利模式(3-5 条人话规则)', '跨 A股/港股/美股/crypto 多市场回测', '差值归因', '8-section PDF 报告' — matching the multi-action anchor.

3 / 3

Completeness

Clearly answers 'what does this do' but provides no explicit 'Use when...' / when-to-trigger clause; per guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Contains relevant domain terms a user might say ('交割单', '盈利模式', '回测'), but lacks common natural variations and is padded with marketing fluff ('叙事:你的影子,没有情绪噪音').

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (shadow-account backtesting from a personal trade journal with delta attribution) with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

10

/

12

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
HKUDS/Vibe-Trading
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.