CtrlK
BlogDocsLog inGet started
Tessl Logo

ljg-teach

用体验而不是定义来教授概念、原理或检验观点:先给与学习者认知水平相称的局面,让其选择,再用公平的意外显化认知缺口,结构化后才命名,并以迁移局面循环复测。USE WHEN 用户调用 '/ljg-teach'、说 '用情境教我'、'别先讲答案'、'通过案例让我学会',或希望通过选择与反馈理解一个概念或观点。NOT FOR 直接定义查询(用 ljg-is/ljg-word)、八维概念解剖(用 ljg-learn)、伴读文本(用 ljg-read)。

75

Quality

94%

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

88%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 highly actionable, well-sequenced methodology skill that gives concrete diagnostic language and three worked examples, with a routing table and feedback loops making the workflow unambiguous. Its only weakness is mild redundancy from restating the cycle across multiple sections.

Suggestions

Reduce redundancy between the ASCII cycle diagram, the Workflow Routing table, and the 体验循环 subsection headers — the diagram and table already encode the sequence, so the subsection intros can reference them rather than restate.

Consider moving the three Examples into a separate references file and signalling it from SKILL.md, which would let progressive_disclosure reach the top anchor while trimming the main body.

Tighten the 理想状态 bullet list, which partially restates outcomes already implied by the 体验循环 stages, to recover token budget.

DimensionReasoningScore

Conciseness

The body is dense and skill-specific with no padding about concepts Claude already knows, but the six-stage cycle is restated across the diagram, the Workflow Routing table, and the 体验循环 subsections, leaving minor redundancy that could be tightened.

4 / 5

Actionability

Concrete, copy-ready guidance throughout — specific diagnostic questions ('你会怎么选?用一句话说理由', '你原来的判断里,哪条默认现在需要改?'), templated phrasings for the structure stage, and three worked examples covering the common cases.

5 / 5

Workflow Clarity

A clear sequenced cycle (局面→选择→意外→结构→命名→迁移) is reinforced by a state-to-next-step Workflow Routing table, with explicit feedback loops (公平性校验, 迁移复测循环, 收束 criteria); not a destructive/batch operation so no validation cap applies.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections (理想状态, 体验循环, 交互节奏, Gotchas, Examples) with easy navigation and no nested references; at ~130 lines it exceeds the under-50-line simple-skill safe harbor, and content stays entirely inline where a couple of sections could optionally be split out.

4 / 5

Total

18

/

20

Passed

Description

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

An exceptionally well-constructed description: it states a concrete multi-step method, supplies natural trigger phrases plus a slash command, and disambiguates against three sibling skills with a NOT FOR clause. Both the what and when are explicit and specific.

DimensionReasoningScore

Specificity

Lists multiple concrete pedagogical moves in sequence — '先给...局面,让其选择,再用公平的意外显化认知缺口,结构化后才命名,并以迁移局面循环复测' — giving comprehensive coverage of the teaching loop rather than vague abstraction.

5 / 5

Completeness

Explicitly answers both what (体验式教学法及其六步循环) and when ('USE WHEN 用户调用...说...') with concrete trigger phrases, matching the anchor-5 pattern.

5 / 5

Trigger Term Quality

Includes natural user phrases ('用情境教我', '别先讲答案', '通过案例让我学会'), a slash command ('/ljg-teach'), and a paraphrased intent, giving comprehensive coverage of natural terms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

A clear niche (体验式教学) is reinforced by an explicit 'NOT FOR' clause routing sibling cases to ljg-is/ljg-word, ljg-learn, and ljg-read, minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.