CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ljg-learn

Deep concept anatomist that deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy) and compresses insights into an epiphany. Use when user asks to explain, dissect, or deeply understand a concept, term, or idea. Triggers on '解剖概念', '概念解剖', 'explain concept', 'learn concept', '/ljg-learn'. Produces markdown output.

Quality

89%

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

86%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 lean, tightly structured instruction skill: terse imperatives, an explicit output template, exact file-writing commands, and absolute formatting rules leave little ambiguity. The only minor gaps are the absence of a worked example and small robustness details around the file write (directory existence, write verification).

DimensionReasoningScore

Conciseness

The ~75-line body is dense instruction with zero padding — each of the eight cuts gets a terse directive like "写一个公式或形式化表达 → 公式在哪里失效", and no space is spent explaining concepts Claude already knows. Every token earns its place; not 4 because there is nothing to trim.

5 / 5

Actionability

Guidance is highly concrete: per-cut length limits ("每刀 2-3 句"), an exact output-path pattern ("~/Documents/notes/{timestamp}--概念解剖-{概念名}__concept.md"), an executable command (`date +%Y%m%dT%H%M%S`), a full markdown skeleton, and zero-exception format rules. Not 5 because there is no worked example of a finished report and some directives (e.g., "用一个具体意象呈现") rely on judgment rather than copy-paste-ready specification.

4 / 5

Workflow Clarity

A clear five-stage numbered sequence (定锚 → 八刀 → 内观 → 压缩 → 写入) with an exact output structure and a final "报告路径,完成" step; the single file-write is neither destructive nor batch, so the validation cap doesn't apply. Not 5 because there are minor validation gaps — no mkdir/handling if ~/Documents/notes doesn't exist and no verification that the file was written successfully.

4 / 5

Progressive Disclosure

The skill is a short, self-contained, single-process instruction with no bundle files and no need for external references; the five numbered stage sections plus a template block are well-organized and easy to navigate, matching the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

88%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: third-person, concrete, and complete, with a well-formed 'Use when' clause and explicit bilingual trigger terms. The only weaknesses are slightly generic English triggers (explain/learn concept) that could overlap with ordinary explanation requests and a few missing natural synonyms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "deconstructs any concept through 8 exploration dimensions (history, dialectics, phenomenology, linguistics, formalization, existentialism, aesthetics, meta-philosophy)", "compresses insights into an epiphany", "Produces markdown output" — enumerating the dimensions themselves, which comprehensively covers the skill's behavior. Not 4 because coverage is complete for this task, not just several actions with gaps.

5 / 5

Completeness

Both parts are explicit: what — deconstructing concepts through 8 named dimensions and compressing them into an epiphany in markdown; when — "Use when user asks to explain, dissect, or deeply understand a concept, term, or idea" with concrete trigger phrases listed. This matches the 5 anchor's requirement of a clear what AND when with concrete triggers.

5 / 5

Trigger Term Quality

Explicit triggers include "explain concept", "learn concept", "dissect", the slash command "/ljg-learn", and the Chinese phrases "解剖概念" / "概念解剖", which are natural phrasings. Not 5 because common variations like "what is X", "teach me X", or "深入理解" are absent, leaving a few natural terms uncovered.

4 / 5

Distinctiveness Conflict Risk

The niche (philosophical 8-dimension concept dissection with a dedicated slash command and Chinese triggers) is clear and mostly distinct. Not 5 because "explain concept" / "learn concept" are broad enough to overlap with generic explanation or tutoring skills on routine questions.

4 / 5

Total

18

/

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