[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M732M67QS0GA4FN40ME3B1M0":3,"skill-same:01M732M67QS0GA4FN40ME3B1M0":47},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M732M67QS0GA4FN40ME3B1M0","durable-task-queues",null,"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\u002F.claude\u002Fskills\u002Fdurable-task-queues\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: durable-task-queues\ndescription: Durable background job and task queue patterns for AI agent systems. BullMQ Redis-backed queues with concurrency + rate limiting, Inngest event-driven durable functions, Trigger.dev background tasks, dead-letter queue patterns, and job failure diagnostics. Sources: taskforcesh\u002Fbullmq, inngest\u002Finngest, triggerdotdev\u002Ftrigger.dev, OptimalBits\u002Fbull, agenda\u002Fagenda.\norigin: yana-ai — synthesized from taskforcesh\u002Fbullmq, inngest\u002Finngest, triggerdotdev\u002Ftrigger.dev, OptimalBits\u002Fbull, agenda\u002Fagenda\nlicense: Apache-2.0\nversion: 1.0.0\ncompatibility: yana-ai >= 1.3.44\n---\n\n# \u002Fdurable-task-queues\n\n## When to Use\n\n- Agent task takes > 30s — HTTP response timeout risk\n- Work must survive server restart (embedding batch, export, analysis)\n- Fan-out: one event → many parallel sub-tasks\n- \"Why did this job fail last night?\" — need structured job history\n\n## Do NOT use for\n\n- Sub-second operations — queue overhead isn't worth it\n- One-off scripts run manually\n\n---\n\n## Decision: BullMQ vs Inngest vs Trigger.dev\n\n```\nAlready using Redis in infra?\n  YES → BullMQ (battle-tested, mature, full queue primitives)\n  NO  →\n    Want event-driven, serverless-compatible, no extra infra?\n      YES → Inngest (zero infra, SDK only, Vercel\u002FNext.js native)\n      Need long-running background tasks (> 15 min) with retries + logging?\n        YES → Trigger.dev (dashboard, streaming logs, sleep\u002Fwait APIs)\n```\n\n---\n\n## BullMQ (Redis-backed queues)\n\n```typescript\nimport { Queue, Worker, QueueEvents } from 'bullmq'\n\nconst connection = { host: process.env.REDIS_HOST, port: 6379 }\n\n\u002F\u002F Queue — producer side\nconst agentQueue = new Queue('agent-tasks', {\n  connection,\n  defaultJobOptions: {\n    attempts:    3,\n    backoff:     { type: 'exponential', delay: 2000 },  \u002F\u002F 2s, 4s, 8s\n    removeOnComplete: { count: 100 },   \u002F\u002F keep last 100 completed\n    removeOnFail:     { count: 500 },   \u002F\u002F keep last 500 failed for debug\n  },\n})\n\nawait agentQueue.add('run-analysis', { repoUrl, sessionId }, {\n  priority: 1,             \u002F\u002F lower = higher priority (1 = urgent)\n  delay:    0,\n  jobId:    `analysis:${sessionId}`,  \u002F\u002F idempotent ID prevents duplicates\n})\n\n\u002F\u002F Worker — consumer side\nconst worker = new Worker('agent-tasks', async (job) => {\n  job.log(`Starting analysis for ${job.data.repoUrl}`)\n  await job.updateProgress(10)\n\n  const result = await runAgentAnalysis(job.data.repoUrl)\n  await job.updateProgress(100)\n  return result\n\n}, {\n  connection,\n  concurrency:    5,      \u002F\u002F max parallel jobs per worker\n  limiter: {\n    max:          10,     \u002F\u002F rate limit: max 10 jobs\n    duration:     1000,  \u002F\u002F per 1000ms\n  },\n})\n\nworker.on('failed', (job, err) => {\n  logger.error({ jobId: job?.id, err: err.message }, 'job_failed')\n})\n\n\u002F\u002F Rule: always set jobId for idempotency — re-enqueuing same ID is a no-op\n\u002F\u002F Rule: removeOnComplete + removeOnFail required — Redis fills up without them\n\u002F\u002F Rule: job.log() goes to BullMQ job history, visible in BullBoard\n```\n\n```typescript\n\u002F\u002F Dead-letter queue pattern — jobs that exhausted all retries\nconst deadLetterQueue = new Queue('agent-tasks-dlq', { connection })\n\nworker.on('failed', async (job, err) => {\n  if (job && job.attemptsMade >= (job.opts.attempts ?? 1)) {\n    await deadLetterQueue.add('dead', {\n      originalJob:  job.name,\n      data:         job.data,\n      error:        err.message,\n      failedAt:     new Date().toISOString(),\n    })\n  }\n})\n\n\u002F\u002F Rule: DLQ enables manual replay — never silently drop failed jobs\n```\n\n---\n\n## Inngest (event-driven durable functions)\n\n```typescript\nimport { Inngest } from 'inngest'\n\nconst inngest = new Inngest({ id: 'yamtam-agent' })\n\n\u002F\u002F Define a durable function — survives cold starts, serverless-compatible\nexport const processAgentTask = inngest.createFunction(\n  {\n    id:     'process-agent-task',\n    name:   'Process Agent Task',\n    retries: 3,\n    throttle: { limit: 10, period: '1m', key: 'event.data.userId' },\n  },\n  { event: 'agent\u002Ftask.created' },\n\n  async ({ event, step }) => {\n    \u002F\u002F Each step is independently retried — completed steps are skipped on retry\n    const embeddings = await step.run('compute-embeddings', async () => {\n      return computeEmbeddings(event.data.content)\n    })\n\n    const stored = await step.run('store-to-vector-db', async () => {\n      return storeEmbeddings(embeddings, event.data.sessionId)\n    })\n\n    \u002F\u002F Sleep without blocking a thread (Inngest persists state)\n    await step.sleep('wait-for-cooldown', '5s')\n\n    const result = await step.run('run-analysis', async () => {\n      return runAgentAnalysis(event.data.taskId)\n    })\n\n    return { stored, result }\n  }\n)\n```\n\n```typescript\n\u002F\u002F Send event to trigger the function\nawait inngest.send({\n  name: 'agent\u002Ftask.created',\n  data: { taskId: uuid(), userId, content, sessionId },\n})\n\n\u002F\u002F Rule: step.run() = durable checkpoint — data is persisted between steps\n\u002F\u002F Rule: step.sleep() does not consume a thread — safe for minutes\u002Fhours\n\u002F\u002F Rule: throttle.key scopes rate limit per field (e.g., per userId)\n\u002F\u002F Rule: Inngest replays from last successful step on retry — not from start\n```\n\n---\n\n## Trigger.dev (long-running background tasks)\n\n```typescript\nimport { task, schedules, wait } from '@trigger.dev\u002Fsdk\u002Fv3'\n\n\u002F\u002F Long-running task with streaming logs (visible in Trigger.dev dashboard)\nexport const agentResearchTask = task({\n  id:      'agent-research',\n  retry:   { maxAttempts: 3, minTimeoutInMs: 1000, multiplier: 2 },\n  machine: { preset: 'medium-1x' },  \u002F\u002F 1 vCPU \u002F 2GB RAM\n\n  run: async (payload: { topic: string; sessionId: string }) => {\n    console.log(`[research] Starting: ${payload.topic}`)\n\n    const sources = await searchWeb(payload.topic)\n    console.log(`[research] Found ${sources.length} sources`)\n\n    \u002F\u002F wait.for suspends task (not sleeping thread) — supports hours\n    await wait.for({ seconds: 5 })\n\n    const summaries = await Promise.all(\n      sources.map(src => summarizeSource(src))\n    )\n\n    const report = await synthesizeReport(summaries, payload.topic)\n    console.log(`[research] Done — ${report.length} chars`)\n    return { report, sourceCount: sources.length }\n  },\n})\n\n\u002F\u002F Trigger from API route\nimport { tasks } from '@trigger.dev\u002Fsdk\u002Fv3'\n\nconst handle = await tasks.trigger('agent-research', {\n  topic:     'vector database benchmarks 2025',\n  sessionId: req.session.id,\n})\n\n\u002F\u002F Poll or webhook for completion\nconst result = await tasks.poll(handle.id, { intervalMs: 2000 })\n```\n\n---\n\n## Job Failure Diagnostics Pattern\n\n```typescript\n\u002F\u002F Structured failure logging for post-mortem\nworker.on('failed', async (job, err) => {\n  if (!job) return\n\n  const diagnostic = {\n    jobId:      job.id,\n    jobName:    job.name,\n    attempt:    job.attemptsMade,\n    maxAttempts: job.opts.attempts,\n    data:       job.data,             \u002F\u002F scrub PII before logging\n    error:      err.message,\n    stack:      err.stack,\n    startedAt:  new Date(job.processedOn!).toISOString(),\n    failedAt:   new Date().toISOString(),\n    logs:       await job.logs,       \u002F\u002F job.log() entries\n  }\n\n  logger.error(diagnostic, 'job_failure_diagnostic')\n  \u002F\u002F Alert if final attempt\n  if (job.attemptsMade >= (job.opts.attempts ?? 1)) {\n    await alertSlack(`Job ${job.name} exhausted retries: ${err.message}`)\n  }\n})\n\n\u002F\u002F Rule: log job.data in failure diagnostic — can't reproduce without input\n\u002F\u002F Rule: alert only on final attempt — intermediate retries are expected noise\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n```\n❌ BullMQ worker without concurrency limit (Redis connection pool exhausted)\n❌ No removeOnComplete\u002FremoveOnFail (Redis OOM in hours)\n❌ Retry without backoff on rate-limited API (thundering herd on 429)\n❌ jobId missing (duplicate jobs on re-enqueue = duplicate side effects)\n❌ Inngest step.run() not used (whole function re-runs on any step failure)\n❌ DLQ absent (failed jobs silently lost — can't diagnose or replay)\n❌ Trigger.dev task without machine preset (memory default too low for LLM ops)\n❌ Job failure handler logs only error message (missing input data = can't reproduce)\n```\n","# \u002Fdurable-task-queues\n\n## When to Use\n\n- Agent task takes > 30s — HTTP response timeout risk\n- Work must survive server restart (embedding batch, export, analysis)\n- Fan-out: one event → many parallel sub-tasks\n- \"Why did this job fail last night?\" — need structured job history\n\n## Do NOT use for\n\n- Sub-second operations — queue overhead isn't worth it\n- One-off scripts run manually\n\n---\n\n## Decision: BullMQ vs Inngest vs Trigger.dev\n\n```\nAlready using Redis in infra?\n  YES → BullMQ (battle-tested, mature, full queue primitives)\n  NO  →\n    Want event-driven, serverless-compatible, no extra infra?\n      YES → Inngest (zero infra, SDK only, Vercel\u002FNext.js native)\n      Need long-running background tasks (> 15 min) with retries + logging?\n        YES → Trigger.dev (dashboard, streaming logs, sleep\u002Fwait APIs)\n```\n\n---\n\n## BullMQ (Redis-backed queues)\n\n```typescript\nimport { Queue, Worker, QueueEvents } from 'bullmq'\n\nconst connection = { host: process.env.REDIS_HOST, port: 6379 }\n\n\u002F\u002F Queue — producer side\nconst agentQueue = new Queue('agent-tasks', {\n  connection,\n  defaultJobOptions: {\n    attempts:    3,\n    backoff:     { type: 'exponential', delay: 2000 },  \u002F\u002F 2s, 4s, 8s\n    removeOnComplete: { count: 100 },   \u002F\u002F keep last 100 completed\n    removeOnFail:     { count: 500 },   \u002F\u002F keep last 500 failed for debug\n  },\n})\n\nawait agentQueue.add('run-analysis', { repoUrl, sessionId }, {\n  priority: 1,             \u002F\u002F lower = higher priority (1 = urgent)\n  delay:    0,\n  jobId:    `analysis:${sessionId}`,  \u002F\u002F idempotent ID prevents duplicates\n})\n\n\u002F\u002F Worker — consumer side\nconst worker = new Worker('agent-tasks', async (job) => {\n  job.log(`Starting analysis for ${job.data.repoUrl}`)\n  await job.updateProgress(10)\n\n  const result = await runAgentAnalysis(job.data.repoUrl)\n  await job.updateProgress(100)\n  return result\n\n}, {\n  connection,\n  concurrency:    5,      \u002F\u002F max parallel jobs per worker\n  limiter: {\n    max:          10,     \u002F\u002F rate limit: max 10 jobs\n    duration:     1000,  \u002F\u002F per 1000ms\n  },\n})\n\nworker.on('failed', (job, err) => {\n  logger.error({ jobId: job?.id, err: err.message }, 'job_failed')\n})\n\n\u002F\u002F Rule: always set jobId for idempotency — re-enqueuing same ID is a no-op\n\u002F\u002F Rule: removeOnComplete + removeOnFail required — Redis fills up without them\n\u002F\u002F Rule: job.log() goes to BullMQ job history, visible in BullBoard\n```\n\n```typescript\n\u002F\u002F Dead-letter queue pattern — jobs that exhausted all retries\nconst deadLetterQueue = new Queue('agent-tasks-dlq', { connection })\n\nworker.on('failed', async (job, err) => {\n  if (job && job.attemptsMade >= (job.opts.attempts ?? 1)) {\n    await deadLetterQueue.add('dead', {\n      originalJob:  job.name,\n      data:         job.data,\n      error:        err.message,\n      failedAt:     new Date().toISOString(),\n    })\n  }\n})\n\n\u002F\u002F Rule: DLQ enables manual replay — never silently drop failed jobs\n```\n\n---\n\n## Inngest (event-driven durable functions)\n\n```typescript\nimport { Inngest } from 'inngest'\n\nconst inngest = new Inngest({ id: 'yamtam-agent' })\n\n\u002F\u002F Define a durable function — survives cold starts, serverless-compatible\nexport const processAgentTask = inngest.createFunction(\n  {\n    id:     'process-agent-task',\n    name:   'Process Agent Task',\n    retries: 3,\n    throttle: { limit: 10, period: '1m', key: 'event.data.userId' },\n  },\n  { event: 'agent\u002Ftask.created' },\n\n  async ({ event, step }) => {\n    \u002F\u002F Each step is independently retried — completed steps are skipped on retry\n    const embeddings = await step.run('compute-embeddings', async () => {\n      return computeEmbeddings(event.data.content)\n    })\n\n    const stored = await step.run('store-to-vector-db', async () => {\n      return storeEmbeddings(embeddings, event.data.sessionId)\n    })\n\n    \u002F\u002F Sleep without blocking a thread (Inngest persists state)\n    await step.sleep('wait-for-cooldown', '5s')\n\n    const result = await step.run('run-analysis', async () => {\n      return runAgentAnalysis(event.data.taskId)\n    })\n\n    return { stored, result }\n  }\n)\n```\n\n```typescript\n\u002F\u002F Send event to trigger the function\nawait inngest.send({\n  name: 'agent\u002Ftask.created',\n  data: { taskId: uuid(), userId, content, sessionId },\n})\n\n\u002F\u002F Rule: step.run() = durable checkpoint — data is persisted between steps\n\u002F\u002F Rule: step.sleep() does not consume a thread — safe for minutes\u002Fhours\n\u002F\u002F Rule: throttle.key scopes rate limit per field (e.g., per userId)\n\u002F\u002F Rule: Inngest replays from last successful step on retry — not from start\n```\n\n---\n\n## Trigger.dev (long-running background tasks)\n\n```typescript\nimport { task, schedules, wait } from '@trigger.dev\u002Fsdk\u002Fv3'\n\n\u002F\u002F Long-running task with streaming logs (visible in Trigger.dev dashboard)\nexport const agentResearchTask = task({\n  id:      'agent-research',\n  retry:   { maxAttempts: 3, minTimeoutInMs: 1000, multiplier: 2 },\n  machine: { preset: 'medium-1x' },  \u002F\u002F 1 vCPU \u002F 2GB RAM\n\n  run: async (payload: { topic: string; sessionId: string }) => {\n    console.log(`[research] Starting: ${payload.topic}`)\n\n    const sources = await searchWeb(payload.topic)\n    console.log(`[research] Found ${sources.length} sources`)\n\n    \u002F\u002F wait.for suspends task (not sleeping thread) — supports hours\n    await wait.for({ seconds: 5 })\n\n    const summaries = await Promise.all(\n      sources.map(src => summarizeSource(src))\n    )\n\n    const report = await synthesizeReport(summaries, payload.topic)\n    console.log(`[research] Done — ${report.length} chars`)\n    return { report, sourceCount: sources.length }\n  },\n})\n\n\u002F\u002F Trigger from API route\nimport { tasks } from '@trigger.dev\u002Fsdk\u002Fv3'\n\nconst handle = await tasks.trigger('agent-research', {\n  topic:     'vector database benchmarks 2025',\n  sessionId: req.session.id,\n})\n\n\u002F\u002F Poll or webhook for completion\nconst result = await tasks.poll(handle.id, { intervalMs: 2000 })\n```\n\n---\n\n## Job Failure Diagnostics Pattern\n\n```typescript\n\u002F\u002F Structured failure logging for post-mortem\nworker.on('failed', async (job, err) => {\n  if (!job) return\n\n  const diagnostic = {\n    jobId:      job.id,\n    jobName:    job.name,\n    attempt:    job.attemptsMade,\n    maxAttempts: job.opts.attempts,\n    data:       job.data,             \u002F\u002F scrub PII before logging\n    error:      err.message,\n    stack:      err.stack,\n    startedAt:  new Date(job.processedOn!).toISOString(),\n    failedAt:   new Date().toISOString(),\n    logs:       await job.logs,       \u002F\u002F job.log() entries\n  }\n\n  logger.error(diagnostic, 'job_failure_diagnostic')\n  \u002F\u002F Alert if final attempt\n  if (job.attemptsMade >= (job.opts.attempts ?? 1)) {\n    await alertSlack(`Job ${job.name} exhausted retries: ${err.message}`)\n  }\n})\n\n\u002F\u002F Rule: log job.data in failure diagnostic — can't reproduce without input\n\u002F\u002F Rule: alert only on final attempt — intermediate retries are expected noise\n```\n\n---\n\n## Anti-Fake-Pass Checklist\n\n```\n❌ BullMQ worker without concurrency limit (Redis connection pool exhausted)\n❌ No removeOnComplete\u002FremoveOnFail (Redis OOM in hours)\n❌ Retry without backoff on rate-limited API (thundering herd on 429)\n❌ jobId missing (duplicate jobs on re-enqueue = duplicate side effects)\n❌ Inngest step.run() not used (whole function re-runs on any step failure)\n❌ DLQ absent (failed jobs silently lost — can't diagnose or replay)\n❌ Trigger.dev task without machine preset (memory default too low for LLM ops)\n❌ Job failure handler logs only error message (missing input data = can't reproduce)\n```\n",{},"main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa",".claude\u002Fskills\u002Fdurable-task-queues",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":7,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill durable-task-queues",{"tool":39,"command":40},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill durable-task-queues",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill durable-task-queues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdurable-task-queues\u002FSKILL.md",true,[],[48,56,63,71,79,87],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":52,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":18},"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"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":88,"name":89,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]