[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73E53J1TBAVCKCC5CG7NHN4":3,"skill-same:01M73E53J1TBAVCKCC5CG7NHN4":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73E53J1TBAVCKCC5CG7NHN4","opensource-pipeline",null,"Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '\u002Fopensource', 'open source this', 'make this public', 'prepare for open source'.","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\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fopensource-pipeline\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: opensource-pipeline\ndescription: \"Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '\u002Fopensource', 'open source this', 'make this public', 'prepare for open source'.\"\norigin: ECC\n---\n\n# Open-Source Pipeline Skill\n\nSafely open-source any project through a 3-stage pipeline: **Fork** (strip secrets) → **Sanitize** (verify clean) → **Package** (CLAUDE.md + setup.sh + README).\n\n## When to Activate\n\n- User says \"open source this project\" or \"make this public\"\n- User wants to prepare a private repo for public release\n- User needs to strip secrets before pushing to GitHub\n- User invokes `\u002Fopensource fork`, `\u002Fopensource verify`, or `\u002Fopensource package`\n\n## Commands\n\n| Command | Action |\n|---------|--------|\n| `\u002Fopensource fork PROJECT` | Full pipeline: fork + sanitize + package |\n| `\u002Fopensource verify PROJECT` | Run sanitizer on existing repo |\n| `\u002Fopensource package PROJECT` | Generate CLAUDE.md + setup.sh + README |\n| `\u002Fopensource list` | Show all staged projects |\n| `\u002Fopensource status PROJECT` | Show reports for a staged project |\n\n## Protocol\n\n### \u002Fopensource fork PROJECT\n\n**Full pipeline — the main workflow.**\n\n#### Step 1: Gather Parameters\n\nResolve the project path. If PROJECT contains `\u002F`, treat as a path (absolute or relative). Otherwise check: current working directory, `$HOME\u002FPROJECT`, then ask the user.\n\n```\nSOURCE_PATH=\"\u003Cresolved absolute path>\"\nSTAGING_PATH=\"$HOME\u002Fopensource-staging\u002F${PROJECT_NAME}\"\n```\n\nAsk the user:\n1. \"Which project?\" (if not found)\n2. \"License? (MIT \u002F Apache-2.0 \u002F GPL-3.0 \u002F BSD-3-Clause)\"\n3. \"GitHub org or username?\" (default: detect via `gh api user -q .login`)\n4. \"GitHub repo name?\" (default: project name)\n5. \"Description for README?\" (analyze project for suggestion)\n\n#### Step 2: Create Staging Directory\n\n```bash\nmkdir -p $HOME\u002Fopensource-staging\u002F\n```\n\n#### Step 3: Run Forker Agent\n\nSpawn the `opensource-forker` agent:\n\n```\nAgent(\n  description=\"Fork {PROJECT} for open-source\",\n  subagent_type=\"opensource-forker\",\n  prompt=\"\"\"\nFork project for open-source release.\n\nSource: {SOURCE_PATH}\nTarget: {STAGING_PATH}\nLicense: {chosen_license}\n\nFollow the full forking protocol:\n1. Copy files (exclude .git, node_modules, __pycache__, .venv)\n2. Strip all secrets and credentials\n3. Replace internal references with placeholders\n4. Generate .env.example\n5. Clean git history\n6. Generate FORK_REPORT.md in {STAGING_PATH}\u002FFORK_REPORT.md\n\"\"\"\n)\n```\n\nWait for completion. Read `{STAGING_PATH}\u002FFORK_REPORT.md`.\n\n#### Step 4: Run Sanitizer Agent\n\nSpawn the `opensource-sanitizer` agent:\n\n```\nAgent(\n  description=\"Verify {PROJECT} sanitization\",\n  subagent_type=\"opensource-sanitizer\",\n  prompt=\"\"\"\nVerify sanitization of open-source fork.\n\nProject: {STAGING_PATH}\nSource (for reference): {SOURCE_PATH}\n\nRun ALL scan categories:\n1. Secrets scan (CRITICAL)\n2. PII scan (CRITICAL)\n3. Internal references scan (CRITICAL)\n4. Dangerous files check (CRITICAL)\n5. Configuration completeness (WARNING)\n6. Git history audit\n\nGenerate SANITIZATION_REPORT.md inside {STAGING_PATH}\u002F with PASS\u002FFAIL verdict.\n\"\"\"\n)\n```\n\nWait for completion. Read `{STAGING_PATH}\u002FSANITIZATION_REPORT.md`.\n\n**If FAIL:** Show findings to user. Ask: \"Fix these and re-scan, or abort?\"\n- If fix: Apply fixes, re-run sanitizer (maximum 3 retry attempts — after 3 FAILs, present all findings and ask user to fix manually)\n- If abort: Clean up staging directory\n\n**If PASS or PASS WITH WARNINGS:** Continue to Step 5.\n\n#### Step 5: Run Packager Agent\n\nSpawn the `opensource-packager` agent:\n\n```\nAgent(\n  description=\"Package {PROJECT} for open-source\",\n  subagent_type=\"opensource-packager\",\n  prompt=\"\"\"\nGenerate open-source packaging for project.\n\nProject: {STAGING_PATH}\nLicense: {chosen_license}\nProject name: {PROJECT_NAME}\nDescription: {description}\nGitHub repo: {github_repo}\n\nGenerate:\n1. CLAUDE.md (commands, architecture, key files)\n2. setup.sh (one-command bootstrap, make executable)\n3. README.md (or enhance existing)\n4. LICENSE\n5. CONTRIBUTING.md\n6. .github\u002FISSUE_TEMPLATE\u002F (bug_report.md, feature_request.md)\n\"\"\"\n)\n```\n\n#### Step 6: Final Review\n\nPresent to user:\n```\nOpen-Source Fork Ready: {PROJECT_NAME}\n\nLocation: {STAGING_PATH}\nLicense: {license}\nFiles generated:\n  - CLAUDE.md\n  - setup.sh (executable)\n  - README.md\n  - LICENSE\n  - CONTRIBUTING.md\n  - .env.example ({N} variables)\n\nSanitization: {sanitization_verdict}\n\nNext steps:\n  1. Review: cd {STAGING_PATH}\n  2. Create repo: gh repo create {github_org}\u002F{github_repo} --public\n  3. Push: git remote add origin ... && git push -u origin main\n\nProceed with GitHub creation? (yes\u002Fno\u002Freview first)\n```\n\n#### Step 7: GitHub Publish (on user approval)\n\n```bash\ncd \"{STAGING_PATH}\"\ngh repo create \"{github_org}\u002F{github_repo}\" --public --source=. --push --description \"{description}\"\n```\n\n---\n\n### \u002Fopensource verify PROJECT\n\nRun sanitizer independently. Resolve path: if PROJECT contains `\u002F`, treat as a path. Otherwise check `$HOME\u002Fopensource-staging\u002FPROJECT`, then `$HOME\u002FPROJECT`, then current directory.\n\n```\nAgent(\n  subagent_type=\"opensource-sanitizer\",\n  prompt=\"Verify sanitization of: {resolved_path}. Run all 6 scan categories and generate SANITIZATION_REPORT.md.\"\n)\n```\n\n---\n\n### \u002Fopensource package PROJECT\n\nRun packager independently. Ask for \"License?\" and \"Description?\", then:\n\n```\nAgent(\n  subagent_type=\"opensource-packager\",\n  prompt=\"Package: {resolved_path} ...\"\n)\n```\n\n---\n\n### \u002Fopensource list\n\n```bash\nls -d $HOME\u002Fopensource-staging\u002F*\u002F\n```\n\nShow each project with pipeline progress (FORK_REPORT.md, SANITIZATION_REPORT.md, CLAUDE.md presence).\n\n---\n\n### \u002Fopensource status PROJECT\n\n```bash\ncat $HOME\u002Fopensource-staging\u002F${PROJECT}\u002FSANITIZATION_REPORT.md\ncat $HOME\u002Fopensource-staging\u002F${PROJECT}\u002FFORK_REPORT.md\n```\n\n## Staging Layout\n\n```\n$HOME\u002Fopensource-staging\u002F\n  my-project\u002F\n    FORK_REPORT.md           # From forker agent\n    SANITIZATION_REPORT.md   # From sanitizer agent\n    CLAUDE.md                # From packager agent\n    setup.sh                 # From packager agent\n    README.md                # From packager agent\n    .env.example             # From forker agent\n    ...                      # Sanitized project files\n```\n\n## Anti-Patterns\n\n- **Never** push to GitHub without user approval\n- **Never** skip the sanitizer — it is the safety gate\n- **Never** proceed after a sanitizer FAIL without fixing all critical findings\n- **Never** leave `.env`, `*.pem`, or `credentials.json` in the staging directory\n\n## Best Practices\n\n- Always run the full pipeline (fork → sanitize → package) for new releases\n- The staging directory persists until explicitly cleaned up — use it for review\n- Re-run the sanitizer after any manual fixes before publishing\n- Parameterize secrets rather than deleting them — preserve project functionality\n\n## Related Skills\n\nSee `security-review` for secret detection patterns used by the sanitizer.\n","# Open-Source Pipeline Skill\n\nSafely open-source any project through a 3-stage pipeline: **Fork** (strip secrets) → **Sanitize** (verify clean) → **Package** (CLAUDE.md + setup.sh + README).\n\n## When to Activate\n\n- User says \"open source this project\" or \"make this public\"\n- User wants to prepare a private repo for public release\n- User needs to strip secrets before pushing to GitHub\n- User invokes `\u002Fopensource fork`, `\u002Fopensource verify`, or `\u002Fopensource package`\n\n## Commands\n\n| Command | Action |\n|---------|--------|\n| `\u002Fopensource fork PROJECT` | Full pipeline: fork + sanitize + package |\n| `\u002Fopensource verify PROJECT` | Run sanitizer on existing repo |\n| `\u002Fopensource package PROJECT` | Generate CLAUDE.md + setup.sh + README |\n| `\u002Fopensource list` | Show all staged projects |\n| `\u002Fopensource status PROJECT` | Show reports for a staged project |\n\n## Protocol\n\n### \u002Fopensource fork PROJECT\n\n**Full pipeline — the main workflow.**\n\n#### Step 1: Gather Parameters\n\nResolve the project path. If PROJECT contains `\u002F`, treat as a path (absolute or relative). Otherwise check: current working directory, `$HOME\u002FPROJECT`, then ask the user.\n\n```\nSOURCE_PATH=\"\u003Cresolved absolute path>\"\nSTAGING_PATH=\"$HOME\u002Fopensource-staging\u002F${PROJECT_NAME}\"\n```\n\nAsk the user:\n1. \"Which project?\" (if not found)\n2. \"License? (MIT \u002F Apache-2.0 \u002F GPL-3.0 \u002F BSD-3-Clause)\"\n3. \"GitHub org or username?\" (default: detect via `gh api user -q .login`)\n4. \"GitHub repo name?\" (default: project name)\n5. \"Description for README?\" (analyze project for suggestion)\n\n#### Step 2: Create Staging Directory\n\n```bash\nmkdir -p $HOME\u002Fopensource-staging\u002F\n```\n\n#### Step 3: Run Forker Agent\n\nSpawn the `opensource-forker` agent:\n\n```\nAgent(\n  description=\"Fork {PROJECT} for open-source\",\n  subagent_type=\"opensource-forker\",\n  prompt=\"\"\"\nFork project for open-source release.\n\nSource: {SOURCE_PATH}\nTarget: {STAGING_PATH}\nLicense: {chosen_license}\n\nFollow the full forking protocol:\n1. Copy files (exclude .git, node_modules, __pycache__, .venv)\n2. Strip all secrets and credentials\n3. Replace internal references with placeholders\n4. Generate .env.example\n5. Clean git history\n6. Generate FORK_REPORT.md in {STAGING_PATH}\u002FFORK_REPORT.md\n\"\"\"\n)\n```\n\nWait for completion. Read `{STAGING_PATH}\u002FFORK_REPORT.md`.\n\n#### Step 4: Run Sanitizer Agent\n\nSpawn the `opensource-sanitizer` agent:\n\n```\nAgent(\n  description=\"Verify {PROJECT} sanitization\",\n  subagent_type=\"opensource-sanitizer\",\n  prompt=\"\"\"\nVerify sanitization of open-source fork.\n\nProject: {STAGING_PATH}\nSource (for reference): {SOURCE_PATH}\n\nRun ALL scan categories:\n1. Secrets scan (CRITICAL)\n2. PII scan (CRITICAL)\n3. Internal references scan (CRITICAL)\n4. Dangerous files check (CRITICAL)\n5. Configuration completeness (WARNING)\n6. Git history audit\n\nGenerate SANITIZATION_REPORT.md inside {STAGING_PATH}\u002F with PASS\u002FFAIL verdict.\n\"\"\"\n)\n```\n\nWait for completion. Read `{STAGING_PATH}\u002FSANITIZATION_REPORT.md`.\n\n**If FAIL:** Show findings to user. Ask: \"Fix these and re-scan, or abort?\"\n- If fix: Apply fixes, re-run sanitizer (maximum 3 retry attempts — after 3 FAILs, present all findings and ask user to fix manually)\n- If abort: Clean up staging directory\n\n**If PASS or PASS WITH WARNINGS:** Continue to Step 5.\n\n#### Step 5: Run Packager Agent\n\nSpawn the `opensource-packager` agent:\n\n```\nAgent(\n  description=\"Package {PROJECT} for open-source\",\n  subagent_type=\"opensource-packager\",\n  prompt=\"\"\"\nGenerate open-source packaging for project.\n\nProject: {STAGING_PATH}\nLicense: {chosen_license}\nProject name: {PROJECT_NAME}\nDescription: {description}\nGitHub repo: {github_repo}\n\nGenerate:\n1. CLAUDE.md (commands, architecture, key files)\n2. setup.sh (one-command bootstrap, make executable)\n3. README.md (or enhance existing)\n4. LICENSE\n5. CONTRIBUTING.md\n6. .github\u002FISSUE_TEMPLATE\u002F (bug_report.md, feature_request.md)\n\"\"\"\n)\n```\n\n#### Step 6: Final Review\n\nPresent to user:\n```\nOpen-Source Fork Ready: {PROJECT_NAME}\n\nLocation: {STAGING_PATH}\nLicense: {license}\nFiles generated:\n  - CLAUDE.md\n  - setup.sh (executable)\n  - README.md\n  - LICENSE\n  - CONTRIBUTING.md\n  - .env.example ({N} variables)\n\nSanitization: {sanitization_verdict}\n\nNext steps:\n  1. Review: cd {STAGING_PATH}\n  2. Create repo: gh repo create {github_org}\u002F{github_repo} --public\n  3. Push: git remote add origin ... && git push -u origin main\n\nProceed with GitHub creation? (yes\u002Fno\u002Freview first)\n```\n\n#### Step 7: GitHub Publish (on user approval)\n\n```bash\ncd \"{STAGING_PATH}\"\ngh repo create \"{github_org}\u002F{github_repo}\" --public --source=. --push --description \"{description}\"\n```\n\n---\n\n### \u002Fopensource verify PROJECT\n\nRun sanitizer independently. Resolve path: if PROJECT contains `\u002F`, treat as a path. Otherwise check `$HOME\u002Fopensource-staging\u002FPROJECT`, then `$HOME\u002FPROJECT`, then current directory.\n\n```\nAgent(\n  subagent_type=\"opensource-sanitizer\",\n  prompt=\"Verify sanitization of: {resolved_path}. Run all 6 scan categories and generate SANITIZATION_REPORT.md.\"\n)\n```\n\n---\n\n### \u002Fopensource package PROJECT\n\nRun packager independently. Ask for \"License?\" and \"Description?\", then:\n\n```\nAgent(\n  subagent_type=\"opensource-packager\",\n  prompt=\"Package: {resolved_path} ...\"\n)\n```\n\n---\n\n### \u002Fopensource list\n\n```bash\nls -d $HOME\u002Fopensource-staging\u002F*\u002F\n```\n\nShow each project with pipeline progress (FORK_REPORT.md, SANITIZATION_REPORT.md, CLAUDE.md presence).\n\n---\n\n### \u002Fopensource status PROJECT\n\n```bash\ncat $HOME\u002Fopensource-staging\u002F${PROJECT}\u002FSANITIZATION_REPORT.md\ncat $HOME\u002Fopensource-staging\u002F${PROJECT}\u002FFORK_REPORT.md\n```\n\n## Staging Layout\n\n```\n$HOME\u002Fopensource-staging\u002F\n  my-project\u002F\n    FORK_REPORT.md           # From forker agent\n    SANITIZATION_REPORT.md   # From sanitizer agent\n    CLAUDE.md                # From packager agent\n    setup.sh                 # From packager agent\n    README.md                # From packager agent\n    .env.example             # From forker agent\n    ...                      # Sanitized project files\n```\n\n## Anti-Patterns\n\n- **Never** push to GitHub without user approval\n- **Never** skip the sanitizer — it is the safety gate\n- **Never** proceed after a sanitizer FAIL without fixing all critical findings\n- **Never** leave `.env`, `*.pem`, or `credentials.json` in the staging directory\n\n## Best Practices\n\n- Always run the full pipeline (fork → sanitize → package) for new releases\n- The staging directory persists until explicitly cleaned up — use it for review\n- Re-run the sanitizer after any manual fixes before publishing\n- Parameterize secrets rather than deleting them — preserve project functionality\n\n## Related Skills\n\nSee `security-review` for secret detection patterns used by the sanitizer.\n",{"name":5,"origin":24,"description":7},"ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fopensource-pipeline",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill opensource-pipeline",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill opensource-pipeline",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill opensource-pipeline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fopensource-pipeline\u002FSKILL.md",true,[],[50,58,65,73,81,89],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":54,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":77,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"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":90,"name":91,"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":92,"categories":93,"keywords":94,"publishedAt":19},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]