Waf Rule Creator - Auto-activating skill for Security Advanced. Triggers on: waf rule creator, waf rule creator Part of the Security Advanced skill category.
35
3%
Does it follow best practices?
Impact
94%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/waf-rule-creator/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 extremely weak, essentially just restating the skill name without providing any meaningful information about capabilities, use cases, or trigger conditions. It reads like auto-generated boilerplate rather than a crafted description. It would be nearly impossible for Claude to make an informed decision about when to select this skill over others.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates and configures Web Application Firewall (WAF) rules including IP blocking, rate limiting, SQL injection prevention, and XSS protection rules.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about creating WAF rules, configuring web application firewall policies, blocking malicious traffic, or setting up security rules for web applications.'
Include relevant platform or format details if applicable (e.g., AWS WAF, Cloudflare, ModSecurity) to improve distinctiveness and help Claude match the skill to the right context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions. It only states the skill name 'Waf Rule Creator' and mentions it's part of 'Security Advanced' but never describes what it actually does (e.g., create WAF rules, configure firewall policies, block IP ranges). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause with meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'waf rule creator' repeated twice. It lacks natural user language like 'web application firewall', 'firewall rules', 'block traffic', 'security rules', 'WAF policy', or 'rate limiting'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'WAF' is somewhat niche and specific to web application firewalls, which provides some distinctiveness. However, the lack of detail about what kind of WAF rules or platforms it supports means it could overlap with other security-related skills. | 2 / 3 |
Total | 5 / 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 is an empty placeholder with no substantive content. It contains only generic boilerplate text that repeats the phrase 'waf rule creator' without providing any actual guidance on WAF rule creation—no rule syntax (ModSecurity, AWS WAF JSON, Cloudflare expressions), no examples, no workflows, and no actionable instructions of any kind.
Suggestions
Add concrete, executable WAF rule examples for at least one platform (e.g., ModSecurity rules, AWS WAF JSON rule statements, or Cloudflare WAF expressions) with specific patterns for common attack types like SQLi, XSS, and path traversal.
Define a clear workflow for creating and validating WAF rules: identify threat → write rule → test against benign and malicious payloads → deploy with monitoring → tune false positives.
Include specific rule syntax references and link to detailed files for different WAF platforms (e.g., MODSECURITY_RULES.md, AWS_WAF.md) to enable progressive disclosure.
Remove all generic boilerplate ('This skill provides automated assistance...') and replace with actionable content that assumes Claude's existing knowledge of HTTP, web security, and regex.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'waf rule creator' excessively, and provides zero domain-specific information about actually creating WAF rules. | 1 / 3 |
Actionability | There are no concrete instructions, code examples, rule syntax, or executable guidance whatsoever. The skill describes what it claims to do rather than providing any actual WAF rule creation guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no validation checkpoints, no rule testing procedures, and no sequence for creating or deploying WAF rules. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to rule syntax documentation, example rulesets, or any supporting files. | 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 | |
3e83543
Table of Contents
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.