password-strength-analyzer
Password Strength Analyzer - Auto-activating skill for Security Fundamentals. Triggers on: password strength analyzer, password strength analyzer Part of the Security Fundamentals skill category.
35
Quality
7%
Does it follow best practices?
Impact
83%
0.95xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/03-security-fundamentals/password-strength-analyzer/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and category but fails to describe what the skill actually does, what actions it performs, or when Claude should select it. The duplicate trigger term suggests incomplete or auto-generated content.
Suggestions
Add specific capabilities: describe what the analyzer does (e.g., 'Evaluates password strength based on length, complexity, common patterns, and dictionary attacks. Provides improvement suggestions.')
Add a 'Use when...' clause with natural trigger terms users would say: 'Use when the user asks to check password strength, evaluate password security, test if a password is strong, or needs help creating secure passwords.'
Include varied trigger terms users naturally use: 'password security', 'check my password', 'is this password safe', 'strong password', 'password requirements'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Password Strength Analyzer') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of analyzing passwords, checking criteria, providing feedback, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate trigger phrase. There is no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'password strength analyzer' repeated twice. This is overly specific jargon - users are more likely to say 'check my password', 'is this password secure', 'password security', or 'how strong is my password'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'password strength' is fairly specific and unlikely to conflict with unrelated skills. However, it could overlap with broader security skills, and the lack of specific capability descriptions makes boundaries unclear. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a hollow template with no actual content about password strength analysis. It lacks any concrete guidance on password criteria (length, complexity, entropy), common password detection, or implementation code. The entire body consists of generic meta-descriptions that could apply to any skill.
Suggestions
Add concrete password strength criteria (minimum length, character classes, entropy thresholds) with specific scoring examples
Include executable code for a password strength analyzer function with clear input/output examples
Add specific checks to implement: common password lists, dictionary words, keyboard patterns, repeated characters
Provide example passwords with their expected strength scores and reasoning
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about password strength analysis. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, algorithms, or specific guidance on how to actually analyze password strength. The content describes what the skill does abstractly but provides zero executable instructions, criteria, or examples. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps for analyzing passwords, no criteria for strength levels, no validation checkpoints. The 'step-by-step guidance' mentioned is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there's no actual content to disclose. No references to detailed materials, no examples, and the structure exists without substance. | 2 / 3 |
Total | 5 / 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
994edc4
- 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.