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.

76

Quality

93%

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

87%Weight 40%Scale 1-3

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

The body is concise, highly actionable, and well-structured for a single-file instruction skill. Its only gap is that fact-verification and exit signals are stated as rules rather than as explicit ordered checkpoints in the writing workflow.

Suggestions

Promote the fact-verification rule ('只用真实信息。查不到的直接标注') into an explicit ordered step within the report-generation sequence, e.g. a '验证' checkpoint before the '换不换' conclusion, to make the validation loop a first-class workflow step rather than a standing rule.

Add a brief inline example of a finished report skeleton (one short filled-in instance of the 一–五 sections) so the abstract table schema becomes a concrete, copy-ready template.

Make the per-assumption exit-signal mechanism explicit as a step: after writing assumptions, attach each to a named '退出信号' field with an example, ensuring the verification feedback loop is unmissable.

DimensionReasoningScore

Conciseness

Lean instruction prose that assumes competence — it never explains what an investment report is, and every line instructs (sections, banned words, naming convention, output tool) without padding.

3 / 3

Actionability

Provides concrete, specific guidance: a five-section schema with named table fields, a banned-word list, a literal file-naming example, and an explicit output tool/path. For an instruction-only skill this is copy-ready and actionable.

3 / 3

Workflow Clarity

The five-section sequence (一–五) plus 最后一句 and 输出/生成规则 is clearly ordered, but verification is present as a standing rule ('查不到的直接标注,不硬撑,不编') rather than as an explicit checkpoint embedded in the sequence.

2 / 3

Progressive Disclosure

A single self-contained file with no bundle references, organized into clearly labeled sections — appropriate for a standalone instruction skill that needs no external files.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, well-triggered in two languages, complete on both what and when, and highly distinctive. It is concise despite covering a rich method.

DimensionReasoningScore

Specificity

Names concrete actions and inputs — '写一份深度投资分析报告' with named inputs (公司名、BP、创始人对话记录) and a distinctive core method ('这个项目是不是一台「秩序创造机器」'), listing multiple specific actions rather than just a domain.

3 / 3

Completeness

Clearly states what it does ('写一份深度投资分析报告') and an explicit 'Use when...' / 'Also trigger when...' clause answering when Claude should use it.

3 / 3

Trigger Term Quality

Natural trigger terms in both Chinese ('投资报告', '投资分析', '分析这个项目', '写投资报告') and English ('investment report', 'invest analysis'), plus situational triggers (pasting meeting notes, pitch decks, founder interviews) a user would actually invoke.

3 / 3

Distinctiveness Conflict Risk

A sharply distinctive investment-analysis niche framed around the 'order-creation-machine' thesis, with triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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