CtrlK
BlogDocsLog inGet started
Tessl Logo

concept-modeler

从模糊的用户需求中提取领域概念——实体、流程和"暗物质"(用户没说的)。基于 DDD(领域驱动设计)方法论。

69

1.23x
Quality

58%

Does it follow best practices?

Impact

80%

1.23x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/concept-modeler/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a specific methodology (DDD) and mentions key concepts like entities and processes, which provides some clarity. However, it lacks explicit trigger guidance ('Use when...'), uses metaphorical language ('暗物质'/dark matter) that may confuse skill selection, and doesn't include enough natural keywords users would actually say when needing this skill.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like '领域建模', 'domain modeling', '需求分析', 'business requirements', or '业务逻辑'

Replace the metaphorical '暗物质' with concrete examples of what implicit requirements look like (e.g., '隐含的业务规则、约束条件')

Include more natural user phrases such as '整理需求', '理解业务', 'extract requirements', or '分析用户故事'

DimensionReasoningScore

Specificity

Names the domain (DDD methodology) and some actions ('提取领域概念——实体、流程和暗物质'), but the actions are somewhat abstract rather than concrete operations. The term '暗物质' (dark matter) is metaphorical rather than specific.

2 / 3

Completeness

Describes what it does (extract domain concepts) but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance should cap completeness at 2, and this has no trigger guidance at all.

1 / 3

Trigger Term Quality

Includes some relevant keywords like 'DDD', '领域驱动设计', '实体', '流程', but missing common variations users might say like 'domain modeling', 'requirements analysis', 'business logic', or Chinese equivalents.

2 / 3

Distinctiveness Conflict Risk

The DDD methodology reference provides some distinctiveness, but '模糊的用户需求' (vague user requirements) is generic and could overlap with general requirements gathering or analysis skills.

2 / 3

Total

7

/

12

Passed

Implementation

85%

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-structured skill for domain concept extraction with strong actionability through concrete examples, checklists, and output schemas. The workflow is clear with explicit validation steps. Main weakness is some verbosity in the form of stylistic flourishes ('老师傅箴言') and emoji decorations that don't add instructional value.

Suggestions

Remove decorative elements like emoji section headers and 'old master sayings' - they consume tokens without adding actionable guidance

Condense the 'Dark Matter Detection' checklist into a more compact format since Claude understands these concepts

DimensionReasoningScore

Conciseness

Content is reasonably efficient but includes some unnecessary flourishes (emoji headers, 'old master sayings') and explanatory text that Claude doesn't need. The core methodology is clear but could be tighter.

2 / 3

Actionability

Provides concrete checklists, specific questions to ask, clear output JSON schema, and executable tool commands. The extraction process has specific examples showing input→output transformations.

3 / 3

Workflow Clarity

Clear three-step sequential process (Noun Hunting → Verb Analysis → Dark Matter Detection) with explicit validation checkpoints (the checklist table) and mandatory deep thinking requirement before execution.

3 / 3

Progressive Disclosure

Well-organized with clear sections, references to external tools and prompts (glossary_gen.py, GLOSSARY_PROMPT.md, ENTITY_EXTRACTION_PROMPT.md), and collaboration context linking to related skills without deep nesting.

3 / 3

Total

11

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
Lingjie-chen/MT5
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.