[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M739WXYB7QEMM5Z1FQZG2FVS":3,"skill-same:01M739WXYB7QEMM5Z1FQZG2FVS":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},"01M739WXYB7QEMM5Z1FQZG2FVS","codebase-onboarding",null,"Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.","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\u002Fcodebase-onboarding\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: codebase-onboarding\ndescription: Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.\norigin: ECC\n---\n\n# Codebase Onboarding\n\nSystematically analyze an unfamiliar codebase and produce a structured onboarding guide. Designed for developers joining a new project or setting up Claude Code in an existing repo for the first time.\n\n## When to Use\n\n- First time opening a project with Claude Code\n- Joining a new team or repository\n- User asks \"help me understand this codebase\"\n- User asks to generate a CLAUDE.md for a project\n- User says \"onboard me\" or \"walk me through this repo\"\n\n## How It Works\n\n### Phase 1: Reconnaissance\n\nGather raw signals about the project without reading every file. Run these checks in parallel:\n\n```\n1. Package manifest detection\n   → package.json, go.mod, Cargo.toml, pyproject.toml, pom.xml, build.gradle,\n     Gemfile, composer.json, mix.exs, pubspec.yaml\n\n2. Framework fingerprinting\n   → next.config.*, nuxt.config.*, angular.json, vite.config.*,\n     django settings, flask app factory, fastapi main, rails config\n\n3. Entry point identification\n   → main.*, index.*, app.*, server.*, cmd\u002F, src\u002Fmain\u002F\n\n4. Directory structure snapshot\n   → Top 2 levels of the directory tree, ignoring node_modules, vendor,\n     .git, dist, build, __pycache__, .next\n\n5. Config and tooling detection\n   → .eslintrc*, .prettierrc*, tsconfig.json, Makefile, Dockerfile,\n     docker-compose*, .github\u002Fworkflows\u002F, .env.example, CI configs\n\n6. Test structure detection\n   → tests\u002F, test\u002F, __tests__\u002F, *_test.go, *.spec.ts, *.test.js,\n     pytest.ini, jest.config.*, vitest.config.*\n```\n\n### Phase 2: Architecture Mapping\n\nFrom the reconnaissance data, identify:\n\n**Tech Stack**\n- Language(s) and version constraints\n- Framework(s) and major libraries\n- Database(s) and ORMs\n- Build tools and bundlers\n- CI\u002FCD platform\n\n**Architecture Pattern**\n- Monolith, monorepo, microservices, or serverless\n- Frontend\u002Fbackend split or full-stack\n- API style: REST, GraphQL, gRPC, tRPC\n\n**Key Directories**\nMap the top-level directories to their purpose:\n\n\u003C!-- Example for a React project — replace with detected directories -->\n```\nsrc\u002Fcomponents\u002F  → React UI components\nsrc\u002Fapi\u002F         → API route handlers\nsrc\u002Flib\u002F         → Shared utilities\nsrc\u002Fdb\u002F          → Database models and migrations\ntests\u002F           → Test suites\nscripts\u002F         → Build and deployment scripts\n```\n\n**Data Flow**\nTrace one request from entry to response:\n- Where does a request enter? (router, handler, controller)\n- How is it validated? (middleware, schemas, guards)\n- Where is business logic? (services, models, use cases)\n- How does it reach the database? (ORM, raw queries, repositories)\n\n### Phase 3: Convention Detection\n\nIdentify patterns the codebase already follows:\n\n**Naming Conventions**\n- File naming: kebab-case, camelCase, PascalCase, snake_case\n- Component\u002Fclass naming patterns\n- Test file naming: `*.test.ts`, `*.spec.ts`, `*_test.go`\n\n**Code Patterns**\n- Error handling style: try\u002Fcatch, Result types, error codes\n- Dependency injection or direct imports\n- State management approach\n- Async patterns: callbacks, promises, async\u002Fawait, channels\n\n**Git Conventions**\n- Branch naming from recent branches\n- Commit message style from recent commits\n- PR workflow (squash, merge, rebase)\n- If the repo has no commits yet or only a shallow history (e.g. `git clone --depth 1`), skip this section and note \"Git history unavailable or too shallow to detect conventions\"\n\n### Phase 4: Generate Onboarding Artifacts\n\nProduce two outputs:\n\n#### Output 1: Onboarding Guide\n\n```markdown\n# Onboarding Guide: [Project Name]\n\n## Overview\n[2-3 sentences: what this project does and who it serves]\n\n## Tech Stack\n\u003C!-- Example for a Next.js project — replace with detected stack -->\n| Layer | Technology | Version |\n|-------|-----------|---------|\n| Language | TypeScript | 5.x |\n| Framework | Next.js | 14.x |\n| Database | PostgreSQL | 16 |\n| ORM | Prisma | 5.x |\n| Testing | Jest + Playwright | - |\n\n## Architecture\n[Diagram or description of how components connect]\n\n## Key Entry Points\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n- **API routes**: `src\u002Fapp\u002Fapi\u002F` — Next.js route handlers\n- **UI pages**: `src\u002Fapp\u002F(dashboard)\u002F` — authenticated pages\n- **Database**: `prisma\u002Fschema.prisma` — data model source of truth\n- **Config**: `next.config.ts` — build and runtime config\n\n## Directory Map\n[Top-level directory → purpose mapping]\n\n## Request Lifecycle\n[Trace one API request from entry to response]\n\n## Conventions\n- [File naming pattern]\n- [Error handling approach]\n- [Testing patterns]\n- [Git workflow]\n\n## Common Tasks\n\u003C!-- Example for a Node.js project — replace with detected commands -->\n- **Run dev server**: `npm run dev`\n- **Run tests**: `npm test`\n- **Run linter**: `npm run lint`\n- **Database migrations**: `npx prisma migrate dev`\n- **Build for production**: `npm run build`\n\n## Where to Look\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n| I want to... | Look at... |\n|--------------|-----------|\n| Add an API endpoint | `src\u002Fapp\u002Fapi\u002F` |\n| Add a UI page | `src\u002Fapp\u002F(dashboard)\u002F` |\n| Add a database table | `prisma\u002Fschema.prisma` |\n| Add a test | `tests\u002F` matching the source path |\n| Change build config | `next.config.ts` |\n```\n\n#### Output 2: Starter CLAUDE.md\n\nGenerate or update a project-specific CLAUDE.md based on detected conventions. If `CLAUDE.md` already exists, read it first and enhance it — preserve existing project-specific instructions and clearly call out what was added or changed.\n\n```markdown\n# Project Instructions\n\n## Tech Stack\n[Detected stack summary]\n\n## Code Style\n- [Detected naming conventions]\n- [Detected patterns to follow]\n\n## Testing\n- Run tests: `[detected test command]`\n- Test pattern: [detected test file convention]\n- Coverage: [if configured, the coverage command]\n\n## Build & Run\n- Dev: `[detected dev command]`\n- Build: `[detected build command]`\n- Lint: `[detected lint command]`\n\n## Project Structure\n[Key directory → purpose map]\n\n## Conventions\n- [Commit style if detectable]\n- [PR workflow if detectable]\n- [Error handling patterns]\n```\n\n## Best Practices\n\n1. **Don't read everything** — reconnaissance should use Glob and Grep, not Read on every file. Read selectively only for ambiguous signals.\n2. **Verify, don't guess** — if a framework is detected from config but the actual code uses something different, trust the code.\n3. **Respect existing CLAUDE.md** — if one already exists, enhance it rather than replacing it. Call out what's new vs existing.\n4. **Stay concise** — the onboarding guide should be scannable in 2 minutes. Details belong in the code, not the guide.\n5. **Flag unknowns** — if a convention can't be confidently detected, say so rather than guessing. \"Could not determine test runner\" is better than a wrong answer.\n\n## Anti-Patterns to Avoid\n\n- Generating a CLAUDE.md that's longer than 100 lines — keep it focused\n- Listing every dependency — highlight only the ones that shape how you write code\n- Describing obvious directory names — `src\u002F` doesn't need an explanation\n- Copying the README — the onboarding guide adds structural insight the README lacks\n\n## Examples\n\n### Example 1: First time in a new repo\n**User**: \"Onboard me to this codebase\"\n**Action**: Run full 4-phase workflow → produce Onboarding Guide + Starter CLAUDE.md\n**Output**: Onboarding Guide printed directly to the conversation, plus a `CLAUDE.md` written to the project root\n\n### Example 2: Generate CLAUDE.md for existing project\n**User**: \"Generate a CLAUDE.md for this project\"\n**Action**: Run Phases 1-3, skip Onboarding Guide, produce only CLAUDE.md\n**Output**: Project-specific `CLAUDE.md` with detected conventions\n\n### Example 3: Enhance existing CLAUDE.md\n**User**: \"Update the CLAUDE.md with current project conventions\"\n**Action**: Read existing CLAUDE.md, run Phases 1-3, merge new findings\n**Output**: Updated `CLAUDE.md` with additions clearly marked\n","# Codebase Onboarding\n\nSystematically analyze an unfamiliar codebase and produce a structured onboarding guide. Designed for developers joining a new project or setting up Claude Code in an existing repo for the first time.\n\n## When to Use\n\n- First time opening a project with Claude Code\n- Joining a new team or repository\n- User asks \"help me understand this codebase\"\n- User asks to generate a CLAUDE.md for a project\n- User says \"onboard me\" or \"walk me through this repo\"\n\n## How It Works\n\n### Phase 1: Reconnaissance\n\nGather raw signals about the project without reading every file. Run these checks in parallel:\n\n```\n1. Package manifest detection\n   → package.json, go.mod, Cargo.toml, pyproject.toml, pom.xml, build.gradle,\n     Gemfile, composer.json, mix.exs, pubspec.yaml\n\n2. Framework fingerprinting\n   → next.config.*, nuxt.config.*, angular.json, vite.config.*,\n     django settings, flask app factory, fastapi main, rails config\n\n3. Entry point identification\n   → main.*, index.*, app.*, server.*, cmd\u002F, src\u002Fmain\u002F\n\n4. Directory structure snapshot\n   → Top 2 levels of the directory tree, ignoring node_modules, vendor,\n     .git, dist, build, __pycache__, .next\n\n5. Config and tooling detection\n   → .eslintrc*, .prettierrc*, tsconfig.json, Makefile, Dockerfile,\n     docker-compose*, .github\u002Fworkflows\u002F, .env.example, CI configs\n\n6. Test structure detection\n   → tests\u002F, test\u002F, __tests__\u002F, *_test.go, *.spec.ts, *.test.js,\n     pytest.ini, jest.config.*, vitest.config.*\n```\n\n### Phase 2: Architecture Mapping\n\nFrom the reconnaissance data, identify:\n\n**Tech Stack**\n- Language(s) and version constraints\n- Framework(s) and major libraries\n- Database(s) and ORMs\n- Build tools and bundlers\n- CI\u002FCD platform\n\n**Architecture Pattern**\n- Monolith, monorepo, microservices, or serverless\n- Frontend\u002Fbackend split or full-stack\n- API style: REST, GraphQL, gRPC, tRPC\n\n**Key Directories**\nMap the top-level directories to their purpose:\n\n\u003C!-- Example for a React project — replace with detected directories -->\n```\nsrc\u002Fcomponents\u002F  → React UI components\nsrc\u002Fapi\u002F         → API route handlers\nsrc\u002Flib\u002F         → Shared utilities\nsrc\u002Fdb\u002F          → Database models and migrations\ntests\u002F           → Test suites\nscripts\u002F         → Build and deployment scripts\n```\n\n**Data Flow**\nTrace one request from entry to response:\n- Where does a request enter? (router, handler, controller)\n- How is it validated? (middleware, schemas, guards)\n- Where is business logic? (services, models, use cases)\n- How does it reach the database? (ORM, raw queries, repositories)\n\n### Phase 3: Convention Detection\n\nIdentify patterns the codebase already follows:\n\n**Naming Conventions**\n- File naming: kebab-case, camelCase, PascalCase, snake_case\n- Component\u002Fclass naming patterns\n- Test file naming: `*.test.ts`, `*.spec.ts`, `*_test.go`\n\n**Code Patterns**\n- Error handling style: try\u002Fcatch, Result types, error codes\n- Dependency injection or direct imports\n- State management approach\n- Async patterns: callbacks, promises, async\u002Fawait, channels\n\n**Git Conventions**\n- Branch naming from recent branches\n- Commit message style from recent commits\n- PR workflow (squash, merge, rebase)\n- If the repo has no commits yet or only a shallow history (e.g. `git clone --depth 1`), skip this section and note \"Git history unavailable or too shallow to detect conventions\"\n\n### Phase 4: Generate Onboarding Artifacts\n\nProduce two outputs:\n\n#### Output 1: Onboarding Guide\n\n```markdown\n# Onboarding Guide: [Project Name]\n\n## Overview\n[2-3 sentences: what this project does and who it serves]\n\n## Tech Stack\n\u003C!-- Example for a Next.js project — replace with detected stack -->\n| Layer | Technology | Version |\n|-------|-----------|---------|\n| Language | TypeScript | 5.x |\n| Framework | Next.js | 14.x |\n| Database | PostgreSQL | 16 |\n| ORM | Prisma | 5.x |\n| Testing | Jest + Playwright | - |\n\n## Architecture\n[Diagram or description of how components connect]\n\n## Key Entry Points\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n- **API routes**: `src\u002Fapp\u002Fapi\u002F` — Next.js route handlers\n- **UI pages**: `src\u002Fapp\u002F(dashboard)\u002F` — authenticated pages\n- **Database**: `prisma\u002Fschema.prisma` — data model source of truth\n- **Config**: `next.config.ts` — build and runtime config\n\n## Directory Map\n[Top-level directory → purpose mapping]\n\n## Request Lifecycle\n[Trace one API request from entry to response]\n\n## Conventions\n- [File naming pattern]\n- [Error handling approach]\n- [Testing patterns]\n- [Git workflow]\n\n## Common Tasks\n\u003C!-- Example for a Node.js project — replace with detected commands -->\n- **Run dev server**: `npm run dev`\n- **Run tests**: `npm test`\n- **Run linter**: `npm run lint`\n- **Database migrations**: `npx prisma migrate dev`\n- **Build for production**: `npm run build`\n\n## Where to Look\n\u003C!-- Example for a Next.js project — replace with detected paths -->\n| I want to... | Look at... |\n|--------------|-----------|\n| Add an API endpoint | `src\u002Fapp\u002Fapi\u002F` |\n| Add a UI page | `src\u002Fapp\u002F(dashboard)\u002F` |\n| Add a database table | `prisma\u002Fschema.prisma` |\n| Add a test | `tests\u002F` matching the source path |\n| Change build config | `next.config.ts` |\n```\n\n#### Output 2: Starter CLAUDE.md\n\nGenerate or update a project-specific CLAUDE.md based on detected conventions. If `CLAUDE.md` already exists, read it first and enhance it — preserve existing project-specific instructions and clearly call out what was added or changed.\n\n```markdown\n# Project Instructions\n\n## Tech Stack\n[Detected stack summary]\n\n## Code Style\n- [Detected naming conventions]\n- [Detected patterns to follow]\n\n## Testing\n- Run tests: `[detected test command]`\n- Test pattern: [detected test file convention]\n- Coverage: [if configured, the coverage command]\n\n## Build & Run\n- Dev: `[detected dev command]`\n- Build: `[detected build command]`\n- Lint: `[detected lint command]`\n\n## Project Structure\n[Key directory → purpose map]\n\n## Conventions\n- [Commit style if detectable]\n- [PR workflow if detectable]\n- [Error handling patterns]\n```\n\n## Best Practices\n\n1. **Don't read everything** — reconnaissance should use Glob and Grep, not Read on every file. Read selectively only for ambiguous signals.\n2. **Verify, don't guess** — if a framework is detected from config but the actual code uses something different, trust the code.\n3. **Respect existing CLAUDE.md** — if one already exists, enhance it rather than replacing it. Call out what's new vs existing.\n4. **Stay concise** — the onboarding guide should be scannable in 2 minutes. Details belong in the code, not the guide.\n5. **Flag unknowns** — if a convention can't be confidently detected, say so rather than guessing. \"Could not determine test runner\" is better than a wrong answer.\n\n## Anti-Patterns to Avoid\n\n- Generating a CLAUDE.md that's longer than 100 lines — keep it focused\n- Listing every dependency — highlight only the ones that shape how you write code\n- Describing obvious directory names — `src\u002F` doesn't need an explanation\n- Copying the README — the onboarding guide adds structural insight the README lacks\n\n## Examples\n\n### Example 1: First time in a new repo\n**User**: \"Onboard me to this codebase\"\n**Action**: Run full 4-phase workflow → produce Onboarding Guide + Starter CLAUDE.md\n**Output**: Onboarding Guide printed directly to the conversation, plus a `CLAUDE.md` written to the project root\n\n### Example 2: Generate CLAUDE.md for existing project\n**User**: \"Generate a CLAUDE.md for this project\"\n**Action**: Run Phases 1-3, skip Onboarding Guide, produce only CLAUDE.md\n**Output**: Project-specific `CLAUDE.md` with detected conventions\n\n### Example 3: Enhance existing CLAUDE.md\n**User**: \"Update the CLAUDE.md with current project conventions\"\n**Action**: Read existing CLAUDE.md, run Phases 1-3, merge new findings\n**Output**: Updated `CLAUDE.md` with additions clearly marked\n",{"name":5,"origin":24,"description":7},"ECC","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fcodebase-onboarding",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 codebase-onboarding",{"tool":41,"command":42},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill codebase-onboarding",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill codebase-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fcodebase-onboarding\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",[],[]]