ljg-writes

写作引擎。把一个观点写成可理解、可迁移、经得住反例的 1000-1500 字中文文章。USE WHEN 写文章 OR 优化思想内容 OR 展开观点 OR 改写成逻辑递进的中文。NOT FOR 普通摘要、事实查询或结构风洞（用 ljg-structure）。

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ljg-writes/SKILL.md

Quality

Content

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

A tightly written, well-sectioned instruction skill with concrete output tooling, but it is held back by a missing referenced workflow file (Workflows/WriteEssay.md), mild repetition of the transfer/validation theme, and abstract rather than executable core-process guidance.

Suggestions

Provide the referenced Workflows/WriteEssay.md (or inline its key steps) so the main writing workflow is not routed to a file absent from the bundle.

Consolidate the reader-reconstructs-the-relationship / transfer-and-counterexample point into one place; it currently appears in 成文契约, 最高法则, and Gotchas.

Turn the conceptual 解码→建模→案例映射→迁移验收 sequence into a concrete, ordered checklist with explicit pass/fail checkpoints to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean with no basic-concept padding, but the reader-must-reconstruct-the-relationship / transfer-and-counterexample idea is restated three times (成文契约 final paragraph, 最高法则 second question, Gotchas fourth bullet), so it could be tightened.	2 / 3
Actionability	The 输出约束 section is copy-paste ready (date commands, filename pattern, org header, org-lint read-back), but the core ideation process (解码→建模→案例映射→迁移验收) stays principled/abstract and is routed to an external file rather than given as executable steps.	2 / 3
Workflow Clarity	A recognizable sequence, an explicit reader-acceptance checklist, and an output validation loop are present, but the main writing workflow is delegated to Workflows/WriteEssay.md and is not shown as a crisp validated step list in the body itself.	2 / 3
Progressive Disclosure	The body is well organized into clear sections and the single external reference is clearly signaled in a routing table, but the referenced Workflows/WriteEssay.md is not present in the bundle, so the one-level-deep reference points to a missing file.	2 / 3
	Total	8 / 12 Passed

Description

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

A strong, well-scoped description: explicit what/when triggers, natural user keywords, and a clear NOT-FOR boundary against a sibling skill. The only soft spot is that the listed writing actions are somewhat abstract and overlapping rather than crisply distinct.

Dimension	Reasoning	Score
Specificity	Names the domain and several actions (写成文章, 优化思想内容, 展开观点, 改写) with a concrete output spec (1000-1500 字中文文章), but the verbs overlap and stay more abstract than the 'extract/fill/merge' concreteness of anchor 3.	2 / 3
Completeness	Explicitly states what ('把一个观点写成可理解、可迁移、经得住反例的 1000-1500 字中文文章') and when ('USE WHEN …'), plus a NOT FOR clause, satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	'USE WHEN 写文章 OR 优化思想内容 OR 展开观点 OR 改写成逻辑递进的中文' uses natural phrasings a user would actually say, with good coverage of variations; not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	The 'NOT FOR 普通摘要、事实查询或结构风洞（用 ljg-structure）' clause carves out a clear niche and explicitly disambiguates from a sibling skill, making wrong-skill triggering unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: lijigang/ljg-skills
Path: skills/ljg-writes/SKILL.md
Commit: 0e78094

Reviewed: 9 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.