CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-analyzer

提示词分析与洞察 - 查看Prompt详情、对比差异、推荐相似提示词、元素库统计

42

Quality

42%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/prompt-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill is well-structured with per-function step sequences, concrete signatures, and error handling for missing data, but it is overlong for a single file, leans on placeholder pseudocode, and duplicates walkthroughs in a separate examples section. Splitting detail into reference files and tightening the duplicated examples would improve it.

Suggestions

Move the per-function markdown templates and the full '使用示例' section into a reference file (e.g. references/examples.md) to reduce the inline token load and improve progressive disclosure.

Replace placeholder/ellipses pseudocode with executable, copy-paste-ready snippets or explicitly mark illustrative fragments as templates to be filled.

Add explicit validation feedback loops (check → fix → retry) to the comparison and recommendation flows, mirroring the empty-data check already present in the detail flow.

DimensionReasoningScore

Conciseness

The body is mostly action-oriented, but it re-explains basic concepts Claude already knows (e.g. what a similarity score threshold means, generic Python grouping boilerplate) and repeats each function across both a per-function walkthrough and a '使用示例' section, so it is efficient in places but could be tightened.

2 / 3

Actionability

It provides concrete function signatures and markdown templates, but the 'code' is largely illustrative pseudocode with placeholders and ellipses ('category = ...', '# ... (执行层已返回)') rather than copy-paste-ready executable logic, placing it at the 'incomplete/pseudocode' anchor.

2 / 3

Workflow Clarity

Each function follows a clear 4-step sequence (识别意图→调用执行层→检查/分析→格式化展示), and error/empty-data checks are present for the detail and statistics flows; however the comparison and recommendation flows lack explicit validation checkpoints or fix-retry feedback loops, so it sits just below the 'explicit validation/feedback' anchor.

2 / 3

Progressive Disclosure

There are no bundle files (references/scripts/assets) and the entire skill is a single ~600-line monolith with all five features fully inline; while sections are well-labeled, the size warrants splitting detailed templates/examples into reference files, so it is organized but monolithic.

2 / 3

Total

8

/

12

Passed

Description

35%

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 lists several concrete functions but reads as a feature menu rather than an invocation guide, omitting any explicit 'Use when...' trigger and natural user phrasings. It is moderately specific and distinct but incomplete on the 'when' dimension.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to inspect, compare, or get recommendations about already-generated Prompts or element-library statistics.'

Include natural user phrasings as trigger terms such as '查看Prompt详情', '对比两个Prompt', '推荐相似提示词', '元素库有哪些类别'.

Use third-person action voice ('Analyzes generated Prompts...') and lead with the core capability rather than a feature bullet list.

DimensionReasoningScore

Specificity

It enumerates concrete sub-functions ('查看Prompt详情、对比差异、推荐相似提示词、元素库统计'), naming several specific actions, but it is essentially a feature label list rather than a full enumeration of capabilities, so it sits below the multi-action 'score 3' anchor.

2 / 3

Completeness

It states what the skill does but provides no 'Use when...' / trigger clause, so per the guideline a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

The description contains only product-style nouns ('详情', '对比差异', '相似提示词', '元素库统计') and no natural phrasings a user would actually say to invoke analysis, offering no keyword variations a user would naturally utter.

1 / 3

Distinctiveness Conflict Risk

The prompt-analysis/element-library niche is reasonably specific, yet without explicit trigger terms the description could still overlap with a sibling prompt-generation skill in the same ecosystem.

2 / 3

Total

7

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (609 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
huangserva/skill-prompt-generator
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.