CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-text-with-nlp

Execute this skill enables AI assistant to perform natural language processing and text analysis using the nlp-text-analyzer plugin. it should be used when the user requests analysis of text, including sentiment analysis, keyword extraction, topic modeling, or ... Use when analyzing code or data. Trigger with phrases like 'analyze', 'review', or 'examine'.

39

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

The body is well-sectioned but mostly descriptive filler with no executable guidance, and it fails to connect to the real bundle files (an executable script, error-handling examples, templates, and example inputs) that would make it actionable. Workflows are sequenced but lack validation checkpoints.

Suggestions

Add concrete, executable guidance — at minimum show how to invoke scripts/analyze_text.py with example arguments, or reference it directly instead of vaguely describing 'the plugin processes the text'.

Replace generic filler sections (Output, Resources, Best Practices) with links to the actual bundle files: error_handling_examples.md, analysis_report_template.md, and example_text_inputs.json.

Tighten the workflow with a verification step (e.g., confirm the analysis output is valid JSON / matches the expected schema) rather than the vague 'review the generated output' instruction.

DimensionReasoningScore

Conciseness

The body is reasonably sectioned and does not explain basic concepts Claude already knows, but it is padded with generic filler such as 'The skill produces structured output relevant to the task', a vague Best Practices section, and a Resources list ('Project documentation', 'Related skills and commands') that could be tightened.

2 / 3

Actionability

The guidance is entirely descriptive ('Process the review text using the nlp-text-analyzer plugin', 'Determine the sentiment as positive') with no executable code or commands, and it never references the bundled executable script analyze_text.py that is present.

1 / 3

Workflow Clarity

Steps are listed in 'How It Works' and 'Instructions', giving a recognizable sequence, but they are abstract and lack any validation or verification checkpoints; the Instructions steps ('review the generated output', 'apply modifications as needed') are generic.

2 / 3

Progressive Disclosure

The body has clear section organization and real bundle files exist (analyze_text.py, error_handling_examples.md, analysis_report_template.md, example_text_inputs.json), but the SKILL.md never links to or signals any of them, leaving content that should be referenced (error handling, templates, the script) described vaguely inline instead.

2 / 3

Total

7

/

12

Passed

Description

42%

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 includes explicit trigger guidance and names several NLP capabilities, but suffers from broken grammar, a truncated capability list, and overly generic triggers ('review', 'examine', 'analyzing code or data') that create high conflict risk with unrelated skills.

Suggestions

Fix the broken opening phrasing and complete the truncated 'or ...' capability list so the 'what' side is comprehensive.

Replace generic triggers ('review', 'examine', 'analyzing code or data') with NLP-specific phrasing like 'sentiment analysis', 'extract keywords', or 'topic modeling' to reduce conflict with code-review and data-analysis skills.

Use consistent third-person voice and remove the misleading 'analyzing code or data' clause that does not match a text-analysis skill.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('sentiment analysis, keyword extraction, topic modeling') but the list is truncated with 'or ...' and the grammar is broken ('Execute this skill enables AI assistant'), so it is not comprehensive.

2 / 3

Completeness

It answers both what and when with an explicit 'Use when...' clause and trigger phrases, but the 'what' side is cut off ('or ...') and 'Use when analyzing code or data' is misleading for a text-analysis skill, weakening the otherwise-complete trigger guidance.

2 / 3

Trigger Term Quality

It offers natural verbs ('analyze', 'review', 'examine') a user might say, but coverage is thin — only three generic verbs with no domain nouns like 'text analysis' or 'sentiment' — and 'review'/'examine' are not NLP-specific.

2 / 3

Distinctiveness Conflict Risk

Triggers 'analyze', 'review', 'examine' plus 'Use when analyzing code or data' are very generic and would fire for code review, data analysis, and general inspection tasks, conflicting with many other skills.

1 / 3

Total

7

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-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.