CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ljg-invest

投资分析。给一个项目(公司名、BP、创始人对话记录),写一份深度投资分析报告。不走传统投资分析的路——核心判断只有一个:这个项目是不是一台「秩序创造机器」。Use when user says '投资报告', '投资分析', '分析这个项目', '写投资报告', 'investment report', 'invest analysis', or provides entrepreneur conversation records wanting investment evaluation. Also trigger when user pastes or references meeting notes, pitch decks, or founder interviews and asks for analysis.

Quality

87%

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

90%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.

This is a high-quality instruction-only skill body: an opinionated, dense methodology with a concrete report skeleton, explicit judgment criteria with worked examples, and precise output conventions. The only notable gaps are the absence of an explicit pre-delivery validation step and the fact that all detail lives inline in a single ~110-line file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains concepts Claude already knows (no primer on what a BP is or how finance works). The 地基 definition and the 惯常问法 comparison table are the skill's own non-obvious framework rather than padding, so every token earns its place — matching the 'lean and efficient' top anchor.

5 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: an explicit five-section skeleton with tables, three judgment angles with observable states ('停着、刚起步、已经转起来'), a three-tier verdict to choose from, worked example formulas (亚马逊/特斯拉/Google), the exact output directory and denote naming pattern with a concrete filename example, and six hard generation rules including a banned-words list. Specific examples cover the common cases.

5 / 5

Workflow Clarity

A clear sequence runs 输入 → 报告结构(一至五 + 最后一句)→ 输出(Write 工具、命名、报路径给用户), and grounding rules ('查不到的直接标注', '每个判断带证据') act as checkpoints. It falls short of the top anchor because there is no explicit final validation pass — e.g., re-checking the banned-words list and evidence coverage before delivering the report.

4 / 5

Progressive Disclosure

No bundle files exist and all sections are well-organized with clear headers, and the single-generation-task content legitimately needs to be in context at once. However, at roughly 110 lines it exceeds the under-50-line self-contained exception, and detail-heavy material (e.g., the S 曲线/认知折价 signals, example formulas) could arguably live in a reference file — 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

18

/

20

Passed

Description

78%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.

A strong description with explicit, concrete trigger guidance in both Chinese and English and a clear statement of what the skill produces. Its main weakness is capability specificity: it describes one action (write a deep investment report) rather than enumerating the concrete sub-capabilities, and the framework sentence about 「秩序创造机器」 conveys approach more than capability.

Suggestions

Replace part of the framing sentence ('不走传统投资分析的路——核心判断只有一个…') with a compact enumeration of what the report actually contains, e.g., 飞轮判定、创生公式、S 曲线定位、交换建议, so users see concrete capabilities.

Add missing natural trigger variations such as 尽职调查, 投研报告, due diligence, or '值不值得投', and use 'investment analysis' instead of the less natural 'invest analysis'.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — '给一个项目(公司名、BP、创始人对话记录),写一份深度投资分析报告' — with input types, but does not enumerate several distinct capabilities. It matches 'names domain and 1-2 concrete actions, but not comprehensive' rather than the 'several specific actions' of the level above.

3 / 5

Completeness

It explicitly answers both questions: 'what' via '给一个项目(公司名、BP、创始人对话记录),写一份深度投资分析报告' and 'when' via an explicit "Use when user says '投资报告', '投资分析', ... " clause with concrete trigger phrases plus an additional trigger condition for pasted materials. This matches the top anchor exactly.

5 / 5

Trigger Term Quality

Good natural trigger coverage in both languages ('投资报告', '投资分析', '写投资报告', 'investment report') plus material types (meeting notes, pitch decks, founder interviews). A few natural terms are missing (e.g., 尽职调查/due diligence, 投研, '值不值得投') and 'invest analysis' is slightly unnatural English, keeping it below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The investment-evaluation niche is clear with mostly distinct triggers, but '分析这个项目' ('analyze this project') is fairly generic and could overlap with general analysis or research skills, giving minor conflict risk — matching 'mostly distinct; minor overlap risk' rather than 'minimal conflict risk'.

4 / 5

Total

16

/

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

lijigang/ljg-skills

Path

skills/ljg-invest/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.