[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QPBPD23NYKK5DWF0PD6RXV":3,"skill-same:01M6QPBPD23NYKK5DWF0PD6RXV":77},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":14,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6QPBPD23NYKK5DWF0PD6RXV","vulnerability-scanner",null,"Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist","LOrdEnRYQuE","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F93767164?v=4","01M6QNZGVYDMQTN925B3BDB98Z","LOrdEnRYQuE | Advanced Digital Solutions ","01M6QNZH078JB4S8QJNNQNJPS5",0,"MIT","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fvulnerability-scanner\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"vulnerability","vulnerability scanner","scanner","read","supply","advanced","principles","2025","mapping","chain","attack surface","supply chain","security","grep","Bash","prioritization","analysis","risk","owasp","supply chain security","2026-11-10 10:12:30",false,"---\nname: vulnerability-scanner\ndescription: Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.\nallowed-tools: Read, Glob, Grep, Bash\n---\n\n# Vulnerability Scanner\n\n> Think like an attacker, defend like an expert. 2025 threat landscape awareness.\n\n## ? Runtime Scripts\n\n**Execute for automated validation:**\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| `scripts\u002Fsecurity_scan.py` | Validate security principles applied | `python scripts\u002Fsecurity_scan.py \u003Cproject_path>` |\n\n## ? Reference Files\n\n| File | Purpose |\n|------|---------|\n| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |\n\n---\n\n## 1. Security Expert Mindset\n\n### Core Principles\n\n| Principle | Application |\n|-----------|-------------|\n| **Assume Breach** | Design as if attacker already inside |\n| **Zero Trust** | Never trust, always verify |\n| **Defense in Depth** | Multiple layers, no single point |\n| **Least Privilege** | Minimum required access only |\n| **Fail Secure** | On error, deny access |\n\n### Threat Modeling Questions\n\nBefore scanning, ask:\n1. What are we protecting? (Assets)\n2. Who would attack? (Threat actors)\n3. How would they attack? (Attack vectors)\n4. What's the impact? (Business risk)\n\n---\n\n## 2. OWASP Top 10:2025\n\n### Risk Categories\n\n| Rank | Category | Think About |\n|------|----------|-------------|\n| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |\n| **A02** | Security Misconfiguration | Defaults, headers, exposed services |\n| **A03** | Software Supply Chain ? | Dependencies, CI\u002FCD, build integrity |\n| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |\n| **A05** | Injection | User input → system commands |\n| **A06** | Insecure Design | Flawed architecture |\n| **A07** | Authentication Failures | Session, credential management |\n| **A08** | Integrity Failures | Unsigned updates, tampered data |\n| **A09** | Logging & Alerting | Blind spots, no monitoring |\n| **A10** | Exceptional Conditions ? | Error handling, fail-open states |\n\n### 2025 Key Changes\n\n```\n2021 → 2025 Shifts:\n├── SSRF merged into A01 (Access Control)\n├── A02 elevated (Cloud\u002FContainer configs)\n├── A03 NEW: Supply Chain (major focus)\n├── A10 NEW: Exceptional Conditions\n└── Focus shift: Root causes > Symptoms\n```\n\n---\n\n## 3. Supply Chain Security (A03)\n\n### Attack Surface\n\n| Vector | Risk | Question to Ask |\n|--------|------|-----------------|\n| **Dependencies** | Malicious packages | Do we audit new deps? |\n| **Lock files** | Integrity attacks | Are they committed? |\n| **Build pipeline** | CI\u002FCD compromise | Who can modify? |\n| **Registry** | Typosquatting | Verified sources? |\n\n### Defense Principles\n\n- Verify package integrity (checksums)\n- Pin versions, audit updates\n- Use private registries for critical deps\n- Sign and verify artifacts\n\n---\n\n## 4. Attack Surface Mapping\n\n### What to Map\n\n| Category | Elements |\n|----------|----------|\n| **Entry Points** | APIs, forms, file uploads |\n| **Data Flows** | Input → Process → Output |\n| **Trust Boundaries** | Where auth\u002Fauthz checked |\n| **Assets** | Secrets, PII, business data |\n\n### Prioritization Matrix\n\n```\nRisk = Likelihood × Impact\n\nHigh Impact + High Likelihood → CRITICAL\nHigh Impact + Low Likelihood  → HIGH\nLow Impact + High Likelihood  → MEDIUM\nLow Impact + Low Likelihood   → LOW\n```\n\n---\n\n## 5. Risk Prioritization\n\n### CVSS + Context\n\n| Factor | Weight | Question |\n|--------|--------|----------|\n| **CVSS Score** | Base severity | How severe is the vuln? |\n| **EPSS Score** | Exploit likelihood | Is it being exploited? |\n| **Asset Value** | Business context | What's at risk? |\n| **Exposure** | Attack surface | Internet-facing? |\n\n### Prioritization Decision Tree\n\n```\nIs it actively exploited (EPSS >0.5)?\n├── YES → CRITICAL: Immediate action\n└── NO → Check CVSS\n         ├── CVSS ≥9.0 → HIGH\n         ├── CVSS 7.0-8.9 → Consider asset value\n         └── CVSS \u003C7.0 → Schedule for later\n```\n\n---\n\n## 6. Exceptional Conditions (A10 - New)\n\n### Fail-Open vs Fail-Closed\n\n| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |\n|----------|-----------------|---------------------|\n| Auth error | Allow access | Deny access |\n| Parsing fails | Accept input | Reject input |\n| Timeout | Retry forever | Limit + abort |\n\n### What to Check\n\n- Exception handlers that catch-all and ignore\n- Missing error handling on security operations\n- Race conditions in auth\u002Fauthz\n- Resource exhaustion scenarios\n\n---\n\n## 7. Scanning Methodology\n\n### Phase-Based Approach\n\n```\n1. RECONNAISSANCE\n   └── Understand the target\n       ├── Technology stack\n       ├── Entry points\n       └── Data flows\n\n2. DISCOVERY\n   └── Identify potential issues\n       ├── Configuration review\n       ├── Dependency analysis\n       └── Code pattern search\n\n3. ANALYSIS\n   └── Validate and prioritize\n       ├── False positive elimination\n       ├── Risk scoring\n       └── Attack chain mapping\n\n4. REPORTING\n   └── Actionable findings\n       ├── Clear reproduction steps\n       ├── Business impact\n       └── Remediation guidance\n```\n\n---\n\n## 8. Code Pattern Analysis\n\n### High-Risk Patterns\n\n| Pattern | Risk | Look For |\n|---------|------|----------|\n| **String concat in queries** | Injection | `\"SELECT * FROM \" + user_input` |\n| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |\n| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |\n| **Path manipulation** | Traversal | User input in file paths |\n| **Disabled security** | Various | `verify=False`, `--insecure` |\n\n### Secret Patterns\n\n| Type | Indicators |\n|------|-----------|\n| API Keys | `api_key`, `apikey`, high entropy |\n| Tokens | `token`, `bearer`, `jwt` |\n| Credentials | `password`, `secret`, `key` |\n| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |\n\n---\n\n## 9. Cloud Security Considerations\n\n### Shared Responsibility\n\n| Layer | You Own | Provider Owns |\n|-------|---------|---------------|\n| Data | ✅ | ❌ |\n| Application | ✅ | ❌ |\n| OS\u002FRuntime | Depends | Depends |\n| Infrastructure | ❌ | ✅ |\n\n### Cloud-Specific Checks\n\n- IAM: Least privilege applied?\n- Storage: Public buckets?\n- Network: Security groups tightened?\n- Secrets: Using secrets manager?\n\n---\n\n## 10. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Scan without understanding | Map attack surface first |\n| Alert on every CVE | Prioritize by exploitability + asset |\n| Ignore false positives | Maintain verified baseline |\n| Fix symptoms only | Address root causes |\n| Scan once before deploy | Continuous scanning |\n| Trust third-party deps blindly | Verify integrity, audit code |\n\n---\n\n## 11. Reporting Principles\n\n### Finding Structure\n\nEach finding should answer:\n1. **What?** - Clear vulnerability description\n2. **Where?** - Exact location (file, line, endpoint)\n3. **Why?** - Root cause explanation\n4. **Impact?** - Business consequence\n5. **How to fix?** - Specific remediation\n\n### Severity Classification\n\n| Severity | Criteria |\n|----------|----------|\n| **Critical** | RCE, auth bypass, mass data exposure |\n| **High** | Data exposure, privilege escalation |\n| **Medium** | Limited scope, requires conditions |\n| **Low** | Informational, best practice |\n\n---\n\n> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: \"What would an attacker do with this?\"\n","# Vulnerability Scanner\n\n> Think like an attacker, defend like an expert. 2025 threat landscape awareness.\n\n## ? Runtime Scripts\n\n**Execute for automated validation:**\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| `scripts\u002Fsecurity_scan.py` | Validate security principles applied | `python scripts\u002Fsecurity_scan.py \u003Cproject_path>` |\n\n## ? Reference Files\n\n| File | Purpose |\n|------|---------|\n| [checklists.md](checklists.md) | OWASP Top 10, Auth, API, Data protection checklists |\n\n---\n\n## 1. Security Expert Mindset\n\n### Core Principles\n\n| Principle | Application |\n|-----------|-------------|\n| **Assume Breach** | Design as if attacker already inside |\n| **Zero Trust** | Never trust, always verify |\n| **Defense in Depth** | Multiple layers, no single point |\n| **Least Privilege** | Minimum required access only |\n| **Fail Secure** | On error, deny access |\n\n### Threat Modeling Questions\n\nBefore scanning, ask:\n1. What are we protecting? (Assets)\n2. Who would attack? (Threat actors)\n3. How would they attack? (Attack vectors)\n4. What's the impact? (Business risk)\n\n---\n\n## 2. OWASP Top 10:2025\n\n### Risk Categories\n\n| Rank | Category | Think About |\n|------|----------|-------------|\n| **A01** | Broken Access Control | Who can access what? IDOR, SSRF |\n| **A02** | Security Misconfiguration | Defaults, headers, exposed services |\n| **A03** | Software Supply Chain ? | Dependencies, CI\u002FCD, build integrity |\n| **A04** | Cryptographic Failures | Weak crypto, exposed secrets |\n| **A05** | Injection | User input → system commands |\n| **A06** | Insecure Design | Flawed architecture |\n| **A07** | Authentication Failures | Session, credential management |\n| **A08** | Integrity Failures | Unsigned updates, tampered data |\n| **A09** | Logging & Alerting | Blind spots, no monitoring |\n| **A10** | Exceptional Conditions ? | Error handling, fail-open states |\n\n### 2025 Key Changes\n\n```\n2021 → 2025 Shifts:\n├── SSRF merged into A01 (Access Control)\n├── A02 elevated (Cloud\u002FContainer configs)\n├── A03 NEW: Supply Chain (major focus)\n├── A10 NEW: Exceptional Conditions\n└── Focus shift: Root causes > Symptoms\n```\n\n---\n\n## 3. Supply Chain Security (A03)\n\n### Attack Surface\n\n| Vector | Risk | Question to Ask |\n|--------|------|-----------------|\n| **Dependencies** | Malicious packages | Do we audit new deps? |\n| **Lock files** | Integrity attacks | Are they committed? |\n| **Build pipeline** | CI\u002FCD compromise | Who can modify? |\n| **Registry** | Typosquatting | Verified sources? |\n\n### Defense Principles\n\n- Verify package integrity (checksums)\n- Pin versions, audit updates\n- Use private registries for critical deps\n- Sign and verify artifacts\n\n---\n\n## 4. Attack Surface Mapping\n\n### What to Map\n\n| Category | Elements |\n|----------|----------|\n| **Entry Points** | APIs, forms, file uploads |\n| **Data Flows** | Input → Process → Output |\n| **Trust Boundaries** | Where auth\u002Fauthz checked |\n| **Assets** | Secrets, PII, business data |\n\n### Prioritization Matrix\n\n```\nRisk = Likelihood × Impact\n\nHigh Impact + High Likelihood → CRITICAL\nHigh Impact + Low Likelihood  → HIGH\nLow Impact + High Likelihood  → MEDIUM\nLow Impact + Low Likelihood   → LOW\n```\n\n---\n\n## 5. Risk Prioritization\n\n### CVSS + Context\n\n| Factor | Weight | Question |\n|--------|--------|----------|\n| **CVSS Score** | Base severity | How severe is the vuln? |\n| **EPSS Score** | Exploit likelihood | Is it being exploited? |\n| **Asset Value** | Business context | What's at risk? |\n| **Exposure** | Attack surface | Internet-facing? |\n\n### Prioritization Decision Tree\n\n```\nIs it actively exploited (EPSS >0.5)?\n├── YES → CRITICAL: Immediate action\n└── NO → Check CVSS\n         ├── CVSS ≥9.0 → HIGH\n         ├── CVSS 7.0-8.9 → Consider asset value\n         └── CVSS \u003C7.0 → Schedule for later\n```\n\n---\n\n## 6. Exceptional Conditions (A10 - New)\n\n### Fail-Open vs Fail-Closed\n\n| Scenario | Fail-Open (BAD) | Fail-Closed (GOOD) |\n|----------|-----------------|---------------------|\n| Auth error | Allow access | Deny access |\n| Parsing fails | Accept input | Reject input |\n| Timeout | Retry forever | Limit + abort |\n\n### What to Check\n\n- Exception handlers that catch-all and ignore\n- Missing error handling on security operations\n- Race conditions in auth\u002Fauthz\n- Resource exhaustion scenarios\n\n---\n\n## 7. Scanning Methodology\n\n### Phase-Based Approach\n\n```\n1. RECONNAISSANCE\n   └── Understand the target\n       ├── Technology stack\n       ├── Entry points\n       └── Data flows\n\n2. DISCOVERY\n   └── Identify potential issues\n       ├── Configuration review\n       ├── Dependency analysis\n       └── Code pattern search\n\n3. ANALYSIS\n   └── Validate and prioritize\n       ├── False positive elimination\n       ├── Risk scoring\n       └── Attack chain mapping\n\n4. REPORTING\n   └── Actionable findings\n       ├── Clear reproduction steps\n       ├── Business impact\n       └── Remediation guidance\n```\n\n---\n\n## 8. Code Pattern Analysis\n\n### High-Risk Patterns\n\n| Pattern | Risk | Look For |\n|---------|------|----------|\n| **String concat in queries** | Injection | `\"SELECT * FROM \" + user_input` |\n| **Dynamic code execution** | RCE | `eval()`, `exec()`, `Function()` |\n| **Unsafe deserialization** | RCE | `pickle.loads()`, `unserialize()` |\n| **Path manipulation** | Traversal | User input in file paths |\n| **Disabled security** | Various | `verify=False`, `--insecure` |\n\n### Secret Patterns\n\n| Type | Indicators |\n|------|-----------|\n| API Keys | `api_key`, `apikey`, high entropy |\n| Tokens | `token`, `bearer`, `jwt` |\n| Credentials | `password`, `secret`, `key` |\n| Cloud | `AWS_`, `AZURE_`, `GCP_` prefixes |\n\n---\n\n## 9. Cloud Security Considerations\n\n### Shared Responsibility\n\n| Layer | You Own | Provider Owns |\n|-------|---------|---------------|\n| Data | ✅ | ❌ |\n| Application | ✅ | ❌ |\n| OS\u002FRuntime | Depends | Depends |\n| Infrastructure | ❌ | ✅ |\n\n### Cloud-Specific Checks\n\n- IAM: Least privilege applied?\n- Storage: Public buckets?\n- Network: Security groups tightened?\n- Secrets: Using secrets manager?\n\n---\n\n## 10. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Scan without understanding | Map attack surface first |\n| Alert on every CVE | Prioritize by exploitability + asset |\n| Ignore false positives | Maintain verified baseline |\n| Fix symptoms only | Address root causes |\n| Scan once before deploy | Continuous scanning |\n| Trust third-party deps blindly | Verify integrity, audit code |\n\n---\n\n## 11. Reporting Principles\n\n### Finding Structure\n\nEach finding should answer:\n1. **What?** - Clear vulnerability description\n2. **Where?** - Exact location (file, line, endpoint)\n3. **Why?** - Root cause explanation\n4. **Impact?** - Business consequence\n5. **How to fix?** - Specific remediation\n\n### Severity Classification\n\n| Severity | Criteria |\n|----------|----------|\n| **Critical** | RCE, auth bypass, mass data exposure |\n| **High** | Data exposure, privilege escalation |\n| **Medium** | Limited scope, requires conditions |\n| **Low** | Informational, best practice |\n\n---\n\n> **Remember:** Vulnerability scanning finds issues. Expert thinking prioritizes what matters. Always ask: \"What would an attacker do with this?\"\n",{"name":5,"description":7,"allowed-tools":44},"Read, Glob, Grep, Bash","main","b04f8c98dcf3dfacf4e2aff1eae92616ed12d83d",".agent\u002Fskills\u002Fvulnerability-scanner","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE","2026-04-10 19:41:10",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist --skill vulnerability-scanner",{"tool":57,"command":58},"bunx","bunx skills add LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist --skill vulnerability-scanner",{"tool":60,"command":61},"pnpm","pnpm dlx skills add LOrdEnRYQuE\u002FLRDEnE-Ai-Specialist --skill vulnerability-scanner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fvulnerability-scanner\u002FSKILL.md",true,[65,71],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"checklists.md","REFERENCE","参考文档",2746,"https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fvulnerability-scanner\u002Fchecklists.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Fsecurity_scan.py","SCRIPT","脚本",18170,"https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002F.agent\u002Fskills\u002Fvulnerability-scanner\u002Fscripts\u002Fsecurity_scan.py",[78,105,140,168,174,183],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":39},"01M6QPEC0HA7GF9HY9S3YDF256","WebApp Architect","Plan, build, refactor, debug, and prepare web applications end-to-end. Activate for greenfield builds, feature additions, architecture reviews, and deployment prep.","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fwindsurf\u002F.agents\u002Fskills\u002Fwebapp-architect\u002FSKILL.md",[],[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104],"webapp architect","webapp","architect","web","architecture","prepare","debug","deployment","refactor","applications","plan","repo","build","activate","scan","feature","end","reviews","prep","for",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":121,"publishedAt":39},"01M6QPE68RNE5PWPC2CPK7ZHCZ","SEO Growth Auditor","Perform technical and on-page SEO audits, generate schema markup, and produce prioritized action reports. Activate for site launches, ranking improvements, and metadata fixes.","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fwindsurf\u002F.agents\u002Fskills\u002Fseo-auditor\u002FSKILL.md",[111,116],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[122,123,124,125,104,126,127,128,129,130,131,132,133,134,135,136,137,138,139,98],"seo","seo growth auditor","auditor","growth","fixes","action","reports","ranking","crawl","generate","produce","metadata","audit","schema markup","site","page","technical","schema",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":149,"publishedAt":39},"01M6QPDSN4KMHFS4CTEMN3520Q","GDPR Compliance Copilot","Identify GDPR compliance gaps, map data flows, generate DSAR templates, and prepare privacy policy inputs. Always requires human legal review.","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fwindsurf\u002F.agents\u002Fskills\u002Fgdpr-copilot\u002FSKILL.md",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000037","律师与法务",[142,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167,131],"gdpr compliance","gdpr","compliance","copilot","legal review","report","policy","privacy","flow","templates","dsar","map","human","gap","review","flows","privacy policy","gaps",{"skillNo":169,"name":170,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":39},"01M6QPDR5FMXB4X0960JKCMK80","webapp-architect","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fcursor\u002Fskills\u002Fwebapp-architect\u002FSKILL.md",[],[85,86,87],{"skillNo":175,"name":176,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":181,"publishedAt":39},"01M6QPDM6FZDXXQS2KRJT1YD8P","seo-auditor","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fcursor\u002Fskills\u002Fseo-auditor\u002FSKILL.md",[179,180],{"categoryNo":112,"categoryName":113,"taxonomyType":114,"taxonomyTypeDesc":115},{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},[122,182,124],"seo auditor",{"skillNo":184,"name":185,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":39},"01M6QPDGEH5RE1VEY57YZ1GA1Q","gdpr-copilot","https:\u002F\u002Fgithub.com\u002FLOrdEnRYQuE\u002FLRDEnE-Ai-Specialist\u002Fblob\u002Fmain\u002Fadapters\u002Fcursor\u002Fskills\u002Fgdpr-copilot\u002FSKILL.md",[],[153,151,189],"gdpr copilot"]