CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/ljg-invest/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 well-crafted, highly opinionated instruction skill with a concrete report skeleton, specific generation rules, and a precise output spec. It is consistently strong across dimensions, with only minor room to add an explicit verification checkpoint and tighten a few metaphorical passages.

Suggestions

Add an explicit pre-output verification step (e.g., re-check that every judgment has evidence and that no banned words appear before writing the .org file) to give the workflow a concrete validate→fix checkpoint.

Trim a few of the more elaborate metaphorical sentences in 地基 and the 创生公式 framing so the guidance stays lean while preserving the distinctive 'order-creation machine' lens.

DimensionReasoningScore

Conciseness

Dense and opinionated with no padding of concepts Claude already knows; the philosophical framing ('财富不是钱,是被欲望照亮的秩序') is the skill's own lens and earns its place, though a few metaphorical passages could be trimmed slightly.

4 / 5

Actionability

Provides a concrete five-section report skeleton with fill-in tables, named sub-questions, a banned-word list, and an output naming convention with a worked example; intentionally leaves emphasis judgment to the model rather than being fully prescriptive.

4 / 5

Workflow Clarity

Clear input → five-section structure → output sequence with the 生成规则 acting as quality gates ('查不到的直接标注,不硬撑,不编'), but there is no explicit validate-then-fix feedback loop before writing the file.

4 / 5

Progressive Disclosure

Self-contained single file with no bundle references (none needed), organized under clear headers (地基, 输入, 报告结构, 输出, 生成规则); nothing that should be split out is inlined, though no progressive file structure is leveraged.

4 / 5

Total

16

/

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, well-structured description that clearly answers both 'what' and 'when' with concrete bilingual trigger phrases and a distinctive analytical framing. The only weakness is that it names a single concrete action rather than enumerating several, limiting specificity.

DimensionReasoningScore

Specificity

Names the domain and one concrete action — '写一份深度投资分析报告' with inputs (公司名、BP、创始人对话记录) — but does not list multiple distinct actions, so it is not comprehensive.

3 / 5

Completeness

Explicitly states what it does (write a deep investment analysis report from project materials) and when to use it via a concrete 'Use when...' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural terms in both languages ('投资报告', '投资分析', '写投资报告', 'investment report', 'invest analysis') plus content triggers (meeting notes, pitch decks, founder interviews), though a few common phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche with a distinctive framing ('秩序创造机器') and specific investment triggers; minor overlap risk from the somewhat generic '分析这个项目' trigger.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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