[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73D0FPBSTPQENRHWW48JAPW":3,"skill-same:01M73D0FPBSTPQENRHWW48JAPW":109},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M73D0FPBSTPQENRHWW48JAPW","implementing-proofpoint-email-security-gateway",null,"Deploy and configure Proofpoint Email Protection as a secure email gateway to detect and block phishing, malware, BEC, and spam before messages reach user inboxes.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: implementing-proofpoint-email-security-gateway\ndescription: Deploy and configure Proofpoint Email Protection as a secure email gateway\n  to detect and block phishing, malware, BEC, and spam before messages reach user\n  inboxes.\ndomain: cybersecurity\nsubdomain: phishing-defense\ntags:\n- email-security\n- proofpoint\n- secure-email-gateway\n- phishing\n- anti-spam\n- anti-malware\n- bec\n- email-filtering\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AT-01\n- DE.CM-09\n- RS.CO-02\n- DE.AE-02\nmitre_attack:\n- T1566\n- T1598\n- T1534\n- T1036\n- T1027\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\n---\n# Implementing Proofpoint Email Security Gateway\n\n## Overview\nProofpoint Email Protection is a cloud-native secure email gateway (SEG) that acts as a security checkpoint where all inbound and outbound mail traffic routes through the gateway before reaching user inboxes. It combines signature-based detection for known malware, machine learning algorithms for emerging threats, real-time threat intelligence feeds, URL rewriting with time-of-click sandboxing, and behavioral analysis for BEC detection. Proofpoint processes over 2.8 billion emails daily and blocks over 1 million extortion attempts per day.\n\n\n## When to Use\n\n- When deploying or configuring implementing proofpoint email security gateway capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Proofpoint Email Protection license (PPS on-premises or Proofpoint on Demand cloud)\n- Administrative access to DNS management for MX record changes\n- Microsoft 365 or Google Workspace email environment\n- Understanding of mail flow architecture and SPF\u002FDKIM\u002FDMARC\n- Network firewall rules permitting Proofpoint IP ranges\n\n## Key Concepts\n\n### Deployment Models\n1. **MX-Based Gateway (Traditional SEG)**: All mail routes through Proofpoint via MX record changes; intercepts threats before delivery\n2. **API-Based Integration**: Connects directly to Microsoft 365 or Google Workspace via API; no MX changes required; can be operational within 48 hours\n3. **Hybrid Deployment**: Combines gateway and API for layered protection\n\n### Core Detection Technologies\n- **Impostor Classifier**: ML model detecting BEC\u002Fimpersonation with no malicious URLs or attachments\n- **URL Defense**: Rewrites URLs and performs real-time sandboxing at time of click\n- **Attachment Defense**: Sandboxes suspicious attachments in virtual environments\n- **Nexus Threat Graph**: Cross-customer threat intelligence correlation engine\n- **Supplier Threat Detection**: Identifies compromised vendor email accounts\n\n### Protection Layers\n| Layer | Technology | Threat Type |\n|---|---|---|\n| Connection | IP reputation, rate limiting | Spam botnets |\n| Authentication | SPF, DKIM, DMARC enforcement | Spoofing |\n| Content | ML classifiers, NLP analysis | BEC, phishing |\n| URL | Rewriting + time-of-click sandbox | Credential theft |\n| Attachment | Static + dynamic sandboxing | Malware, ransomware |\n| Post-delivery | TRAP (auto-retraction) | Weaponized after delivery |\n\n## Workflow\n\n### Step 1: Plan Mail Flow Architecture\n- Document current MX records and mail flow path\n- Identify all legitimate sending sources (marketing platforms, CRM, ticketing systems)\n- Map inbound connectors and transport rules in Microsoft 365 or Google Workspace\n- Plan IP allowlisting for Proofpoint egress IPs on receiving infrastructure\n- Configure SPF record to include Proofpoint: `v=spf1 include:spf.protection.outlook.com include:spf-a.proofpoint.com -all`\n\n### Step 2: Configure Proofpoint Policies\n- Create organizational units matching business structure\n- Define inbound mail policies: anti-spam, anti-virus, impostor detection\n- Configure Smart Search quarantine with end-user digest notifications\n- Set up Proofpoint Encryption for sensitive outbound messages\n- Enable Targeted Attack Protection (TAP) for URL and attachment sandboxing\n\n### Step 3: Deploy Email Authentication\n- Configure DKIM signing through Proofpoint for outbound messages\n- Set DMARC policy to monitor mode initially: `v=DMARC1; p=none; rua=mailto:dmarc@company.com`\n- Enable inbound DMARC enforcement to reject spoofed messages\n- Configure anti-spoofing rules for executive impersonation protection\n\n### Step 4: Enable Advanced Threat Protection\n- Activate URL Defense with rewriting enabled for all inbound messages\n- Configure Attachment Defense sandbox policies (safe attachment mode)\n- Enable Threat Response Auto-Pull (TRAP) for post-delivery remediation\n- Set up TAP Dashboard alerts for targeted attack campaigns\n- Configure Supplier Risk monitoring for vendor email compromise\n\n### Step 5: Migrate MX Records\n- Lower MX record TTL to 300 seconds 48 hours before cutover\n- Update MX records to point to Proofpoint: `company-com.mail.protection.proofpoint.com`\n- Configure connector restrictions in Microsoft 365 to accept mail only from Proofpoint IPs\n- Monitor mail flow through Proofpoint Message Trace for 48-72 hours\n- Verify no legitimate mail is being blocked or delayed\n\n### Step 6: Tune and Optimize\n- Review quarantine and false positive\u002Fnegative rates weekly for first month\n- Adjust spam thresholds based on organizational tolerance\n- Add approved senders and safe lists for legitimate bulk mail\n- Configure data loss prevention (DLP) rules for outbound sensitive content\n- Enable email warning banners for external sender identification\n\n## Tools & Resources\n- **Proofpoint TAP Dashboard**: Real-time threat visibility and campaign tracking\n- **Proofpoint TRAP**: Automated post-delivery email retraction\n- **Proofpoint SER (Spam\u002FEnd-user Release)**: Self-service quarantine management\n- **Proofpoint Closed-Loop Email Analysis (CLEAR)**: Phishing report button integration\n- **MX Toolbox**: DNS record verification and mail flow testing\n\n## Validation\n- All inbound email routes through Proofpoint (verify MX records and message headers)\n- TAP Dashboard shows threat detections and blocked campaigns\n- URL Defense rewrites links in test messages and sandboxes at click time\n- Attachment Defense detonates test malware samples in sandbox\n- TRAP successfully retracts test phishing message from inboxes post-delivery\n- False positive rate below 0.1% after initial tuning period\n- DMARC\u002FSPF\u002FDKIM authentication passes for all legitimate outbound mail\n","# Implementing Proofpoint Email Security Gateway\n\n## Overview\nProofpoint Email Protection is a cloud-native secure email gateway (SEG) that acts as a security checkpoint where all inbound and outbound mail traffic routes through the gateway before reaching user inboxes. It combines signature-based detection for known malware, machine learning algorithms for emerging threats, real-time threat intelligence feeds, URL rewriting with time-of-click sandboxing, and behavioral analysis for BEC detection. Proofpoint processes over 2.8 billion emails daily and blocks over 1 million extortion attempts per day.\n\n\n## When to Use\n\n- When deploying or configuring implementing proofpoint email security gateway capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Proofpoint Email Protection license (PPS on-premises or Proofpoint on Demand cloud)\n- Administrative access to DNS management for MX record changes\n- Microsoft 365 or Google Workspace email environment\n- Understanding of mail flow architecture and SPF\u002FDKIM\u002FDMARC\n- Network firewall rules permitting Proofpoint IP ranges\n\n## Key Concepts\n\n### Deployment Models\n1. **MX-Based Gateway (Traditional SEG)**: All mail routes through Proofpoint via MX record changes; intercepts threats before delivery\n2. **API-Based Integration**: Connects directly to Microsoft 365 or Google Workspace via API; no MX changes required; can be operational within 48 hours\n3. **Hybrid Deployment**: Combines gateway and API for layered protection\n\n### Core Detection Technologies\n- **Impostor Classifier**: ML model detecting BEC\u002Fimpersonation with no malicious URLs or attachments\n- **URL Defense**: Rewrites URLs and performs real-time sandboxing at time of click\n- **Attachment Defense**: Sandboxes suspicious attachments in virtual environments\n- **Nexus Threat Graph**: Cross-customer threat intelligence correlation engine\n- **Supplier Threat Detection**: Identifies compromised vendor email accounts\n\n### Protection Layers\n| Layer | Technology | Threat Type |\n|---|---|---|\n| Connection | IP reputation, rate limiting | Spam botnets |\n| Authentication | SPF, DKIM, DMARC enforcement | Spoofing |\n| Content | ML classifiers, NLP analysis | BEC, phishing |\n| URL | Rewriting + time-of-click sandbox | Credential theft |\n| Attachment | Static + dynamic sandboxing | Malware, ransomware |\n| Post-delivery | TRAP (auto-retraction) | Weaponized after delivery |\n\n## Workflow\n\n### Step 1: Plan Mail Flow Architecture\n- Document current MX records and mail flow path\n- Identify all legitimate sending sources (marketing platforms, CRM, ticketing systems)\n- Map inbound connectors and transport rules in Microsoft 365 or Google Workspace\n- Plan IP allowlisting for Proofpoint egress IPs on receiving infrastructure\n- Configure SPF record to include Proofpoint: `v=spf1 include:spf.protection.outlook.com include:spf-a.proofpoint.com -all`\n\n### Step 2: Configure Proofpoint Policies\n- Create organizational units matching business structure\n- Define inbound mail policies: anti-spam, anti-virus, impostor detection\n- Configure Smart Search quarantine with end-user digest notifications\n- Set up Proofpoint Encryption for sensitive outbound messages\n- Enable Targeted Attack Protection (TAP) for URL and attachment sandboxing\n\n### Step 3: Deploy Email Authentication\n- Configure DKIM signing through Proofpoint for outbound messages\n- Set DMARC policy to monitor mode initially: `v=DMARC1; p=none; rua=mailto:dmarc@company.com`\n- Enable inbound DMARC enforcement to reject spoofed messages\n- Configure anti-spoofing rules for executive impersonation protection\n\n### Step 4: Enable Advanced Threat Protection\n- Activate URL Defense with rewriting enabled for all inbound messages\n- Configure Attachment Defense sandbox policies (safe attachment mode)\n- Enable Threat Response Auto-Pull (TRAP) for post-delivery remediation\n- Set up TAP Dashboard alerts for targeted attack campaigns\n- Configure Supplier Risk monitoring for vendor email compromise\n\n### Step 5: Migrate MX Records\n- Lower MX record TTL to 300 seconds 48 hours before cutover\n- Update MX records to point to Proofpoint: `company-com.mail.protection.proofpoint.com`\n- Configure connector restrictions in Microsoft 365 to accept mail only from Proofpoint IPs\n- Monitor mail flow through Proofpoint Message Trace for 48-72 hours\n- Verify no legitimate mail is being blocked or delayed\n\n### Step 6: Tune and Optimize\n- Review quarantine and false positive\u002Fnegative rates weekly for first month\n- Adjust spam thresholds based on organizational tolerance\n- Add approved senders and safe lists for legitimate bulk mail\n- Configure data loss prevention (DLP) rules for outbound sensitive content\n- Enable email warning banners for external sender identification\n\n## Tools & Resources\n- **Proofpoint TAP Dashboard**: Real-time threat visibility and campaign tracking\n- **Proofpoint TRAP**: Automated post-delivery email retraction\n- **Proofpoint SER (Spam\u002FEnd-user Release)**: Self-service quarantine management\n- **Proofpoint Closed-Loop Email Analysis (CLEAR)**: Phishing report button integration\n- **MX Toolbox**: DNS record verification and mail flow testing\n\n## Validation\n- All inbound email routes through Proofpoint (verify MX records and message headers)\n- TAP Dashboard shows threat detections and blocked campaigns\n- URL Defense rewrites links in test messages and sandboxes at click time\n- Attachment Defense detonates test malware samples in sandbox\n- TRAP successfully retracts test phishing message from inboxes post-delivery\n- False positive rate below 0.1% after initial tuning period\n- DMARC\u002FSPF\u002FDKIM authentication passes for all legitimate outbound mail\n",{"name":5,"tags":25,"author":34,"domain":35,"source":36,"license":15,"version":37,"nist_csf":38,"subdomain":43,"description":7,"mitre_attack":44,"source_commit":50},[26,27,28,29,30,31,32,33],"email-security","proofpoint","secure-email-gateway","phishing","anti-spam","anti-malware","bec","email-filtering","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0",[39,40,41,42],"PR.AT-01","DE.CM-09","RS.CO-02","DE.AE-02","phishing-defense",[45,46,47,48,49],"T1566","T1598","T1534","T1036","T1027","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill implementing-proofpoint-email-security-gateway",{"tool":67,"command":68},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill implementing-proofpoint-email-security-gateway",{"tool":70,"command":71},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill implementing-proofpoint-email-security-gateway","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002FSKILL.md",true,[75,81,85,91,95,99,105],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Ftemplate.md","ASSET","资产文件",1739,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Fassets\u002Ftemplate.md",{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fapi-reference.md","REFERENCE","参考文档",5181,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Freferences\u002Fapi-reference.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fstandards.md",1750,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Freferences\u002Fstandards.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fworkflows.md",2727,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Freferences\u002Fworkflows.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",8392,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Fscripts\u002Fagent.py",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fprocess.py",11351,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fimplementing-proofpoint-email-security-gateway\u002Fscripts\u002Fprocess.py",[110,118,125,133,141,149],{"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":114,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":145,"sourceHtmlUrl":146,"categories":147,"keywords":148,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":150,"name":151,"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":152,"categories":153,"keywords":154,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]