quant-docs

量化交易文档处理 - PDF、DOCX、PPTX 用于交易报告、策略文档、演示文稿

1.18x

Quality

35%

Does it follow best practices?

Impact

88%

1.18x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/quant-docs/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description identifies a specific domain (quantitative trading) and relevant file types, which provides some differentiation. However, it lacks concrete action verbs describing what the skill actually does, and critically missing explicit trigger guidance ('Use when...') that would help Claude know when to select this skill over general document processing skills.

Suggestions

Add a 'Use when...' clause specifying triggers like 'when user mentions trading reports, backtesting results, strategy documentation, or quantitative analysis documents'

Include specific concrete actions such as 'extract trading metrics from reports', 'parse strategy parameters', 'analyze performance summaries', or 'convert trading data presentations'

Add natural language variations users might say: '交易策略', '回测报告', 'quant docs', 'trading analysis', '量化分析文档'

Dimension	Reasoning	Score
Specificity	Names the domain (quantitative trading documents) and file types (PDF, DOCX, PPTX), mentions use cases (trading reports, strategy documents, presentations), but lacks specific concrete actions like 'extract', 'analyze', 'convert', or 'merge'.	2 / 3
Completeness	Describes 'what' at a high level (document processing for trading) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant file format keywords (PDF, DOCX, PPTX) and domain terms (量化交易/quantitative trading, 交易报告/trading reports, 策略文档/strategy documents), but missing common variations and natural phrases users might say when requesting help.	2 / 3
Distinctiveness Conflict Risk	The quantitative trading domain provides some distinctiveness, but 'document processing' for PDF/DOCX/PPTX is generic and could easily overlap with general document handling skills.	2 / 3
	Total	7 / 12 Passed

Implementation

37%

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

This skill provides a reasonable foundation for document processing in quantitative trading contexts with relevant code examples for PDF, DOCX, and PPTX generation. However, it suffers from incomplete code implementations, missing validation workflows, and could be more concise. The scenarios are useful but lack actionable step-by-step guidance with error handling.

Suggestions

Complete all code examples with actual implementations - define parse_trade_data(), calculate win_rate/total_pnl, and remove placeholder comments like '# ... 填充参数表'

Add validation workflows for document generation: verify file creation, check document integrity, handle common errors (missing fonts, invalid data, file permissions)

Split content into separate files: move detailed API examples to EXAMPLES.md, keep SKILL.md as a concise overview with quick-start code

Remove the overview paragraph explaining what the skill does - Claude doesn't need this meta-description

Dimension	Reasoning	Score
Conciseness	The skill contains substantial code examples but includes some unnecessary explanatory text (e.g., '此技能使 Claude 能够处理...' in the overview). The code is mostly efficient but could be tightened - some functions have incomplete implementations (e.g., parse_trade_data is called but not defined, win_rate used without definition).	2 / 3
Actionability	Code examples are provided but several are incomplete or pseudocode-like - parse_trade_data() is undefined, win_rate/total_pnl variables are used without calculation, and some code blocks have '# ... 填充参数表' placeholders. Not fully copy-paste ready.	2 / 3
Workflow Clarity	The scenarios section lists high-level tasks but lacks clear step-by-step workflows with validation checkpoints. No error handling, no validation steps for document generation, and no feedback loops for catching issues in generated documents.	1 / 3
Progressive Disclosure	Content is organized with clear headings and sections, but it's a monolithic document with no references to external files for detailed content. The 400+ lines could benefit from splitting API reference and examples into separate files.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 days ago

Table of Contents

Discovery Implementation Validation

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.