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.
Overall
score
23%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill password-strength-analyzerActivation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as its only trigger term and fails to describe any concrete capabilities or usage scenarios. The description would be nearly useless in a multi-skill environment where Claude needs to distinguish between options.
Suggestions
Add concrete actions the skill performs, e.g., 'Evaluates password strength by checking length, complexity, common patterns, and dictionary words. Provides security ratings and improvement suggestions.'
Include a 'Use when...' clause with natural trigger phrases like 'Use when users ask to check password strength, evaluate password security, test if a password is strong, or need help creating secure passwords.'
Add varied trigger terms users would naturally say: 'password security', 'check my password', 'is this password safe', 'strong password', 'password requirements', 'secure password'.
| 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, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use-case guidance beyond repeating the skill name). The 'Triggers on' section just duplicates the title. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'password strength analyzer' repeated twice, which is the skill name itself. Missing natural user phrases like 'check my password', 'is this password secure', 'password security', 'strong password', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Password Strength Analyzer' is fairly specific to a niche domain, which provides some distinctiveness. However, the lack of detailed triggers means it could miss relevant queries or conflict with broader security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
7%This skill is essentially an empty template with no actual content about password strength analysis. It contains only meta-descriptions of what a skill should do without any concrete implementation details, code examples, or actionable guidance. The skill fails to teach Claude anything about evaluating password strength.
Suggestions
Add concrete password strength criteria: minimum length, character class requirements, entropy thresholds, and common password blacklist checking
Include executable code example showing a password strength scoring function with specific scoring logic
Provide example inputs and outputs showing weak, medium, and strong passwords with their scores and reasoning
Add specific guidance on detecting common password patterns (keyboard walks, date formats, l33t speak substitutions)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about password strength analysis. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no algorithms, no specific criteria for password strength evaluation, no examples of weak vs strong passwords, no scoring methodology. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. A password strength analyzer should have clear steps for evaluation (length checks, character diversity, dictionary attacks, entropy calculation), but none are present. | 1 / 3 |
Progressive Disclosure | The content is organized into sections with headers, but there's nothing of substance to disclose. No references to detailed documentation or examples that would warrant progressive disclosure. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.