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

83%

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.

A thorough, well-sequenced dialogue skill with concrete templates and strong actionability. The main gap is a missing verification step on the final org-file write.

Suggestions

Add an explicit verification step after writing the org file (e.g., confirm the path exists and report it back) to close the workflow-clarity validation gap.

Consider extracting the per-layer guided-question bank into a reference file so the main flow stays leaner, given the body exceeds 200 lines.

Tighten the per-layer probe sections by merging the 'diagnostic signal' notes more compactly to reduce a few minor verbose passages.

DimensionReasoningScore

Conciseness

Lean and free of basic-concept padding; the length is justified by a genuinely multi-layer process, with only minor passages that could be tightened.

4 / 5

Actionability

Highly actionable for an instruction-only skill: verbatim guided questions, explicit diagnostic signals, copy-paste ASCII diagram templates, and an exact file path plus timestamp command for the org write step.

5 / 5

Workflow Clarity

Step 0–6 sequence is clearly ordered with decision branches and feedback loops (user reactions as data, resistance marking), but the file-write step lacks an explicit verification checkpoint.

4 / 5

Progressive Disclosure

A single self-contained file with clear section headers (Usage, Instructions, 对话流程, 判断路径速查) and well-placed inline diagrams; no external references are needed, and structure is good though the file is over 50 lines.

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 well-crafted description that clearly states capability and trigger conditions with concrete, mostly third-person language. Minor room to sharpen trigger synonyms and tighten distinctiveness.

DimensionReasoningScore

Specificity

Names the domain and several concrete frameworks — 'structural diagnostics (5-layer framework)', 'transference, unconscious patterns, resistance', and the action of guiding dialogue to 'see' the real structure — but stops short of exhaustive coverage of actions.

4 / 5

Completeness

Explicitly answers both 'what' (relationship analyst combining structural and psychoanalytic depth) and 'when' via a concrete 'Use when user says …' clause with multiple trigger phrases.

5 / 5

Trigger Term Quality

Good bilingual trigger coverage ('关系分析', '分析关系', 'relationship', '人际关系') plus a behavioral trigger ('describes a specific relationship problem'), though a few natural synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

The structural-plus-psychoanalytic niche is mostly distinct, but the standalone term 'relationship' is broad enough to create minor overlap with general advice skills.

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.

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.