CtrlK
BlogDocsLog inGet started
Tessl Logo

ljg-relationship

Relationship analyst combining structural diagnostics (5-layer framework) with psychoanalytic depth (transference, unconscious patterns, resistance). Guides users through dialogue to "see" the real structure of their relationship issues. Use when user says "关系分析", "分析关系", "relationship", "人际关系", or describes a specific relationship problem they want to understand.

68

Quality

86%

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

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

This is a well-crafted conversational-analysis skill: a fully specified multi-step workflow with branch handling, copy-paste-ready question scripts, diagnostic signals per layer, ASCII visualization templates, and a concrete org-mode persistence step. Its weaknesses are small — no validation around the file-write step, a few trimmable metaphorical passages, and a single-file layout that could offload templates to a references file.

Suggestions

Add a validation step before the org-file write in step 6 (check that ~/Documents/notes/ exists, create it if not, and confirm the write before reporting the path to the user).

Move the org-mode file template and/or the judgment-path quick-reference diagram to a references/ file to keep SKILL.md as a leaner overview.

Trim a few of the metaphorical asides (e.g., '像一拳打在胃上', '举着手电筒') — they add character but cost tokens without operational value.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's intelligence: no space is spent explaining what transference or org-mode is, and almost every line is operational (question scripts, diagnostic signals, templates). Minor trims are possible — e.g., the tone metaphors ('要像一拳打在胃上', '你只是举着手电筒') and the two closing ASCII diagrams are evocative but could be tightened — placing it at 'efficient with minor instances that could be trimmed' rather than the lean 5 anchor.

4 / 5

Actionability

Guidance is copy-paste ready throughout: exact dialogue questions to ask at each layer ('如果这段关系明天结束,谁的生活被改变得更多?'), a concrete ASCII diagram template, a full org-mode file template, an exact command (`date +%Y%m%dT%H%M%S`), and an exact output path (`~/Documents/notes/{timestamp}--关系分析-{关键词}__relationship.org`). As an instruction-only skill, its guidance covers the common conversational cases comprehensively.

5 / 5

Workflow Clarity

The 0–6 step sequence is explicit, with branching at step 0 (all three user responses handled), explicit trigger conditions for entering the psychoanalytic layer, per-layer feedback ('展示当前诊断图...哪个你觉得不对?' — user reaction treated as data), and a closing quick-reference flowchart. It falls short of 5 because there is no validation on the file-write step (no check that ~/Documents/notes/ exists or that the write succeeded) and no recovery guidance for a stalled mid-session analysis.

4 / 5

Progressive Disclosure

No bundle files exist, so the single SKILL.md carries everything; it is well organized with clear sections (Usage, Instructions, dialogue steps, quick-reference). At ~250 lines it exceeds the under-50-line simple-skill case, and some self-contained material (the org-mode template, the closing decision flowchart) could live in a references file, which is the minor organization gap that keeps it below 5.

4 / 5

Total

17

/

20

Passed

Description

83%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: it states a clear dual-track methodology, uses third person, and provides an explicit 'Use when' clause with natural bilingual trigger phrases covering both command-style invocations and natural-language descriptions of relationship problems. The only gaps are a few missing common synonyms and capability phrasing that summarizes rather than enumerates the full workflow.

Suggestions

Add a few more natural trigger variations (e.g., '感情问题', '人际冲突', 'relationship problem') to broaden natural-language matching.

Enumerate one or two more concrete outputs (e.g., 'produces a relationship structure diagram and writes an org-mode analysis file') to sharpen the what-clause.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — "structural diagnostics (5-layer framework)", "psychoanalytic depth (transference, unconscious patterns, resistance)", and "Guides users through dialogue" — which goes beyond naming the domain. It falls short of the 5 anchor because the concrete actions are capability categories rather than an exhaustive list of what the skill actually does (diagnose, probe layer-by-layer, produce a structural diagram, write an org file).

4 / 5

Completeness

It explicitly answers both what ("Relationship analyst combining structural diagnostics... with psychoanalytic depth... Guides users through dialogue") and when ("Use when user says '关系分析', '分析关系', 'relationship', '人际关系', or describes a specific relationship problem"), matching the top anchor's pattern of clear what + explicit trigger phrases. Neither half is vague.

5 / 5

Trigger Term Quality

Triggers include natural bilingual phrases users would actually say: "关系分析", "分析关系", "relationship", "人际关系", plus the behavioral trigger "describes a specific relationship problem they want to understand". A few natural variations are missing (e.g., "感情", "婚姻", "人际冲突", "relationship problem/advice"), keeping it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche (structural + psychoanalytic relationship analysis) and its bilingual trigger phrases are distinct from typical technical skills, so wrong-skill triggering is unlikely. Minor overlap risk remains with generic counseling/emotional-support skills, which keeps it just below the clear-niche 5 anchor.

4 / 5

Total

17

/

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