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'.
35
21%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/ai-ml/nlp-text-analyzer/skills/analyzing-text-with-nlp/SKILL.mdQuality
Discovery
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 attempts to specify NLP capabilities but is undermined by internal contradictions (text analysis vs. code/data analysis), an incomplete capability list ('...'), and overly generic trigger terms that would cause frequent false matches. It also uses second/third person inconsistently and includes filler language like 'enables AI assistant to perform' rather than being direct.
Suggestions
Remove the contradictory 'Use when analyzing code or data' clause and replace with specific NLP-focused triggers like 'Use when the user asks for sentiment analysis, keyword extraction, topic modeling, or text summarization'.
Replace overly generic trigger terms ('analyze', 'review', 'examine') with more distinctive phrases like 'sentiment', 'extract keywords', 'topic model', 'text analysis', 'NLP'.
Complete the trailing '...' with the full list of supported capabilities, and remove filler like 'enables AI assistant to perform' in favor of direct action verbs (e.g., 'Performs sentiment analysis, extracts keywords, and models topics from text').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names some specific actions like 'sentiment analysis, keyword extraction, topic modeling' but the description is padded with vague language ('natural language processing and text analysis'), trails off with '...', and conflates text analysis with code/data analysis, reducing clarity. | 2 / 3 |
Completeness | It attempts to answer both 'what' (NLP tasks like sentiment analysis, keyword extraction) and 'when' (trigger phrases), but the 'when' guidance is contradictory—it says 'Use when analyzing code or data' which conflicts with the NLP/text focus, and the capabilities list trails off with '...' leaving it incomplete. | 2 / 3 |
Trigger Term Quality | Includes some trigger terms like 'analyze', 'review', 'examine', 'sentiment analysis', 'keyword extraction', but these are overly generic ('analyze' could match almost anything) and miss natural user phrases like 'summarize text', 'find keywords', 'what is the sentiment', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The description would heavily conflict with other skills due to extremely generic triggers like 'analyze', 'review', 'examine' and the broad scope of 'analyzing code or data', which could match code review tools, data analysis tools, and many other skills. | 1 / 3 |
Total | 7 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill content is almost entirely generic boilerplate with no actionable, concrete, or specific guidance. It never shows how to actually invoke the nlp-text-analyzer plugin, what parameters it accepts, what output formats to expect, or any executable code. Every section reads like a template placeholder rather than a real skill instruction.
Suggestions
Replace the abstract 'How It Works' and 'Examples' sections with actual executable code or tool invocation examples showing specific plugin calls, parameters, and expected output formats (e.g., JSON schema of sentiment analysis results).
Remove all sections that explain concepts Claude already knows (Overview, When to Use, Best Practices about 'be specific') and replace with a concise quick-start showing the exact plugin API or command syntax.
Add concrete validation steps: how to verify the plugin is available, how to check output correctness, and specific error handling with actual error messages and remediation commands.
Provide real resource links or file references instead of generic placeholders like 'Project documentation' and 'Related skills and commands'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive explanation of concepts Claude already knows. Sections like 'Overview', 'How It Works', 'When to Use', 'Best Practices', 'Integration', and 'Prerequisites' are padded with generic filler that adds no actionable value. The content explains what NLP is and how analysis works, which Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, API calls, or executable examples anywhere. The 'Examples' section describes what the skill 'will do' in abstract terms rather than showing actual plugin invocations, parameters, or expected output formats. The 'Instructions' section is entirely generic ('Invoke this skill when trigger conditions are met'). | 1 / 3 |
Workflow Clarity | The workflow steps are vague and generic ('Request Analysis', 'Text Processing', 'Insight Extraction'). No specific commands, validation checkpoints, or error recovery loops are provided. The 'Instructions' section is a placeholder with no real sequencing or concrete steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with many sections that contain little substance. No references to external files, no clear navigation structure, and the 'Resources' section lists generic placeholders ('Project documentation', 'Related skills and commands') with no actual links. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | 9 / 11 Passed | |
- Commit
c8a915c
- 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.