[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAAQCWDNDF1SR3MS5T4WHA":3,"skill-same:01M7FAAQCWDNDF1SR3MS5T4WHA":47},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7FAAQCWDNDF1SR3MS5T4WHA","bullmq-specialist",null,"BullMQ expert for Redis-backed job queues, background processing, and reliable async execution in Node.js\u002FTypeScript applications.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fframework\u002Fbullmq-specialist\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: bullmq-specialist\ndescription: BullMQ expert for Redis-backed job queues, background processing,\n  and reliable async execution in Node.js\u002FTypeScript applications.\nrisk: none\nsource: vibeship-spawner-skills (Apache 2.0)\ndate_added: 2026-02-27\n---\n\n# BullMQ Specialist\n\nBullMQ expert for Redis-backed job queues, background processing, and\nreliable async execution in Node.js\u002FTypeScript applications.\n\n## Principles\n\n- Jobs are fire-and-forget from the producer side - let the queue handle delivery\n- Always set explicit job options - defaults rarely match your use case\n- Idempotency is your responsibility - jobs may run more than once\n- Backoff strategies prevent thundering herds - exponential beats linear\n- Dead letter queues are not optional - failed jobs need a home\n- Concurrency limits protect downstream services - start conservative\n- Job data should be small - pass IDs, not payloads\n- Graceful shutdown prevents orphaned jobs - handle SIGTERM properly\n\n## Capabilities\n\n- bullmq-queues\n- job-scheduling\n- delayed-jobs\n- repeatable-jobs\n- job-priorities\n- rate-limiting-jobs\n- job-events\n- worker-patterns\n- flow-producers\n- job-dependencies\n\n## Scope\n\n- redis-infrastructure -> redis-specialist\n- serverless-queues -> upstash-qstash\n- workflow-orchestration -> temporal-craftsman\n- event-sourcing -> event-architect\n- email-delivery -> email-systems\n\n## Tooling\n\n### Core\n\n- bullmq\n- ioredis\n\n### Hosting\n\n- upstash\n- redis-cloud\n- elasticache\n- railway\n\n### Monitoring\n\n- bull-board\n- arena\n- bullmq-pro\n\n### Patterns\n\n- delayed-jobs\n- repeatable-jobs\n- job-flows\n- rate-limiting\n- sandboxed-processors\n\n## Patterns\n\n### Basic Queue Setup\n\nProduction-ready BullMQ queue with proper configuration\n\n**When to use**: Starting any new queue implementation\n\nimport { Queue, Worker, QueueEvents } from 'bullmq';\nimport IORedis from 'ioredis';\n\n\u002F\u002F Shared connection for all queues\nconst connection = new IORedis(process.env.REDIS_URL, {\n  maxRetriesPerRequest: null,  \u002F\u002F Required for BullMQ\n  enableReadyCheck: false,\n});\n\n\u002F\u002F Create queue with sensible defaults\nconst emailQueue = new Queue('emails', {\n  connection,\n  defaultJobOptions: {\n    attempts: 3,\n    backoff: {\n      type: 'exponential',\n      delay: 1000,\n    },\n    removeOnComplete: { count: 1000 },\n    removeOnFail: { count: 5000 },\n  },\n});\n\n\u002F\u002F Worker with concurrency limit\nconst worker = new Worker('emails', async (job) => {\n  await sendEmail(job.data);\n}, {\n  connection,\n  concurrency: 5,\n  limiter: {\n    max: 100,\n    duration: 60000,  \u002F\u002F 100 jobs per minute\n  },\n});\n\n\u002F\u002F Handle events\nworker.on('failed', (job, err) => {\n  console.error(`Job ${job?.id} failed:`, err);\n});\n\n### Delayed and Scheduled Jobs\n\nJobs that run at specific times or after delays\n\n**When to use**: Scheduling future tasks, reminders, or timed actions\n\n\u002F\u002F Delayed job - runs once after delay\nawait queue.add('reminder', { userId: 123 }, {\n  delay: 24 * 60 * 60 * 1000,  \u002F\u002F 24 hours\n});\n\n\u002F\u002F Repeatable job - runs on schedule\nawait queue.add('daily-digest', { type: 'summary' }, {\n  repeat: {\n    pattern: '0 9 * * *',  \u002F\u002F Every day at 9am\n    tz: 'America\u002FNew_York',\n  },\n});\n\n\u002F\u002F Remove repeatable job\nawait queue.removeRepeatable('daily-digest', {\n  pattern: '0 9 * * *',\n  tz: 'America\u002FNew_York',\n});\n\n### Job Flows and Dependencies\n\nComplex multi-step job processing with parent-child relationships\n\n**When to use**: Jobs depend on other jobs completing first\n\nimport { FlowProducer } from 'bullmq';\n\nconst flowProducer = new FlowProducer({ connection });\n\n\u002F\u002F Parent waits for all children to complete\nawait flowProducer.add({\n  name: 'process-order',\n  queueName: 'orders',\n  data: { orderId: 123 },\n  children: [\n    {\n      name: 'validate-inventory',\n      queueName: 'inventory',\n      data: { orderId: 123 },\n    },\n    {\n      name: 'charge-payment',\n      queueName: 'payments',\n      data: { orderId: 123 },\n    },\n    {\n      name: 'notify-warehouse',\n      queueName: 'notifications',\n      data: { orderId: 123 },\n    },\n  ],\n});\n\n### Graceful Shutdown\n\nProperly close workers without losing jobs\n\n**When to use**: Deploying or restarting workers\n\nconst shutdown = async () => {\n  console.log('Shutting down gracefully...');\n\n  \u002F\u002F Stop accepting new jobs\n  await worker.pause();\n\n  \u002F\u002F Wait for current jobs to finish (with timeout)\n  await worker.close();\n\n  \u002F\u002F Close queue connection\n  await queue.close();\n\n  process.exit(0);\n};\n\nprocess.on('SIGTERM', shutdown);\nprocess.on('SIGINT', shutdown);\n\n### Bull Board Dashboard\n\nVisual monitoring for BullMQ queues\n\n**When to use**: Need visibility into queue status and job states\n\nimport { createBullBoard } from '@bull-board\u002Fapi';\nimport { BullMQAdapter } from '@bull-board\u002Fapi\u002FbullMQAdapter';\nimport { ExpressAdapter } from '@bull-board\u002Fexpress';\n\nconst serverAdapter = new ExpressAdapter();\nserverAdapter.setBasePath('\u002Fadmin\u002Fqueues');\n\ncreateBullBoard({\n  queues: [\n    new BullMQAdapter(emailQueue),\n    new BullMQAdapter(orderQueue),\n  ],\n  serverAdapter,\n});\n\napp.use('\u002Fadmin\u002Fqueues', serverAdapter.getRouter());\n\n## Validation Checks\n\n### Redis connection missing maxRetriesPerRequest\n\nSeverity: ERROR\n\nBullMQ requires maxRetriesPerRequest null for proper reconnection handling\n\nMessage: BullMQ queue\u002Fworker created without maxRetriesPerRequest: null on Redis connection. This will cause workers to stop on Redis connection issues.\n\n### No stalled job event handler\n\nSeverity: WARNING\n\nWorkers should handle stalled events to detect crashed workers\n\nMessage: Worker created without 'stalled' event handler. Stalled jobs indicate worker crashes and should be monitored.\n\n### No failed job event handler\n\nSeverity: WARNING\n\nWorkers should handle failed events for monitoring and alerting\n\nMessage: Worker created without 'failed' event handler. Failed jobs should be logged and monitored.\n\n### No graceful shutdown handling\n\nSeverity: WARNING\n\nWorkers should gracefully shut down on SIGTERM\u002FSIGINT\n\nMessage: Worker file without graceful shutdown handling. Jobs may be orphaned on deployment.\n\n### Awaiting queue.add in request handler\n\nSeverity: INFO\n\nQueue additions should be fire-and-forget in request handlers\n\nMessage: Queue.add awaited in request handler. Consider fire-and-forget for faster response.\n\n### Potentially large data in job payload\n\nSeverity: WARNING\n\nJob data should be small - pass IDs not full objects\n\nMessage: Job appears to have large inline data. Pass IDs instead of full objects to keep Redis memory low.\n\n### Job without timeout configuration\n\nSeverity: INFO\n\nJobs should have timeouts to prevent infinite execution\n\nMessage: Job added without explicit timeout. Consider adding timeout to prevent stuck jobs.\n\n### Retry without backoff strategy\n\nSeverity: WARNING\n\nRetries should use exponential backoff to avoid thundering herd\n\nMessage: Job has retry attempts but no backoff strategy. Use exponential backoff to prevent thundering herd.\n\n### Repeatable job without explicit timezone\n\nSeverity: WARNING\n\nRepeatable jobs should specify timezone to avoid DST issues\n\nMessage: Repeatable job without explicit timezone. Will use server local time which can drift with DST.\n\n### Potentially high worker concurrency\n\nSeverity: INFO\n\nHigh concurrency can overwhelm downstream services\n\nMessage: Worker concurrency is high. Ensure downstream services can handle this load (DB connections, API rate limits).\n\n## Collaboration\n\n### Delegation Triggers\n\n- redis infrastructure|redis cluster|memory tuning -> redis-specialist (Queue needs Redis infrastructure)\n- serverless queue|edge queue|no redis -> upstash-qstash (Need queues without managing Redis)\n- complex workflow|saga|compensation|long-running -> temporal-craftsman (Need workflow orchestration beyond simple jobs)\n- event sourcing|CQRS|event streaming -> event-architect (Need event-driven architecture)\n- deploy|kubernetes|scaling|infrastructure -> devops (Queue needs infrastructure)\n- monitor|metrics|alerting|dashboard -> performance-hunter (Queue needs monitoring)\n\n### Email Queue Stack\n\nSkills: bullmq-specialist, email-systems, redis-specialist\n\nWorkflow:\n\n```\n1. Email request received (API)\n2. Job queued with rate limiting (bullmq-specialist)\n3. Worker processes with backoff (bullmq-specialist)\n4. Email sent via provider (email-systems)\n5. Status tracked in Redis (redis-specialist)\n```\n\n### Background Processing Stack\n\nSkills: bullmq-specialist, backend, devops\n\nWorkflow:\n\n```\n1. API receives request (backend)\n2. Long task queued for background (bullmq-specialist)\n3. Worker processes async (bullmq-specialist)\n4. Result stored\u002Fnotified (backend)\n5. Workers scaled per load (devops)\n```\n\n### AI Processing Pipeline\n\nSkills: bullmq-specialist, ai-workflow-automation, performance-hunter\n\nWorkflow:\n\n```\n1. AI task submitted (ai-workflow-automation)\n2. Job flow created with dependencies (bullmq-specialist)\n3. Workers process stages (bullmq-specialist)\n4. Performance monitored (performance-hunter)\n5. Results aggregated (ai-workflow-automation)\n```\n\n### Scheduled Tasks Stack\n\nSkills: bullmq-specialist, backend, redis-specialist\n\nWorkflow:\n\n```\n1. Repeatable jobs defined (bullmq-specialist)\n2. Cron patterns with timezone (bullmq-specialist)\n3. Jobs execute on schedule (bullmq-specialist)\n4. State managed in Redis (redis-specialist)\n5. Results handled (backend)\n```\n\n## Related Skills\n\nWorks well with: `redis-specialist`, `backend`, `nextjs-app-router`, `email-systems`, `ai-workflow-automation`, `performance-hunter`\n\n## When to Use\n- User mentions or implies: bullmq\n- User mentions or implies: bull queue\n- User mentions or implies: redis queue\n- User mentions or implies: background job\n- User mentions or implies: job queue\n- User mentions or implies: delayed job\n- User mentions or implies: repeatable job\n- User mentions or implies: worker process\n- User mentions or implies: job scheduling\n- User mentions or implies: async processing\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# BullMQ Specialist\n\nBullMQ expert for Redis-backed job queues, background processing, and\nreliable async execution in Node.js\u002FTypeScript applications.\n\n## Principles\n\n- Jobs are fire-and-forget from the producer side - let the queue handle delivery\n- Always set explicit job options - defaults rarely match your use case\n- Idempotency is your responsibility - jobs may run more than once\n- Backoff strategies prevent thundering herds - exponential beats linear\n- Dead letter queues are not optional - failed jobs need a home\n- Concurrency limits protect downstream services - start conservative\n- Job data should be small - pass IDs, not payloads\n- Graceful shutdown prevents orphaned jobs - handle SIGTERM properly\n\n## Capabilities\n\n- bullmq-queues\n- job-scheduling\n- delayed-jobs\n- repeatable-jobs\n- job-priorities\n- rate-limiting-jobs\n- job-events\n- worker-patterns\n- flow-producers\n- job-dependencies\n\n## Scope\n\n- redis-infrastructure -> redis-specialist\n- serverless-queues -> upstash-qstash\n- workflow-orchestration -> temporal-craftsman\n- event-sourcing -> event-architect\n- email-delivery -> email-systems\n\n## Tooling\n\n### Core\n\n- bullmq\n- ioredis\n\n### Hosting\n\n- upstash\n- redis-cloud\n- elasticache\n- railway\n\n### Monitoring\n\n- bull-board\n- arena\n- bullmq-pro\n\n### Patterns\n\n- delayed-jobs\n- repeatable-jobs\n- job-flows\n- rate-limiting\n- sandboxed-processors\n\n## Patterns\n\n### Basic Queue Setup\n\nProduction-ready BullMQ queue with proper configuration\n\n**When to use**: Starting any new queue implementation\n\nimport { Queue, Worker, QueueEvents } from 'bullmq';\nimport IORedis from 'ioredis';\n\n\u002F\u002F Shared connection for all queues\nconst connection = new IORedis(process.env.REDIS_URL, {\n  maxRetriesPerRequest: null,  \u002F\u002F Required for BullMQ\n  enableReadyCheck: false,\n});\n\n\u002F\u002F Create queue with sensible defaults\nconst emailQueue = new Queue('emails', {\n  connection,\n  defaultJobOptions: {\n    attempts: 3,\n    backoff: {\n      type: 'exponential',\n      delay: 1000,\n    },\n    removeOnComplete: { count: 1000 },\n    removeOnFail: { count: 5000 },\n  },\n});\n\n\u002F\u002F Worker with concurrency limit\nconst worker = new Worker('emails', async (job) => {\n  await sendEmail(job.data);\n}, {\n  connection,\n  concurrency: 5,\n  limiter: {\n    max: 100,\n    duration: 60000,  \u002F\u002F 100 jobs per minute\n  },\n});\n\n\u002F\u002F Handle events\nworker.on('failed', (job, err) => {\n  console.error(`Job ${job?.id} failed:`, err);\n});\n\n### Delayed and Scheduled Jobs\n\nJobs that run at specific times or after delays\n\n**When to use**: Scheduling future tasks, reminders, or timed actions\n\n\u002F\u002F Delayed job - runs once after delay\nawait queue.add('reminder', { userId: 123 }, {\n  delay: 24 * 60 * 60 * 1000,  \u002F\u002F 24 hours\n});\n\n\u002F\u002F Repeatable job - runs on schedule\nawait queue.add('daily-digest', { type: 'summary' }, {\n  repeat: {\n    pattern: '0 9 * * *',  \u002F\u002F Every day at 9am\n    tz: 'America\u002FNew_York',\n  },\n});\n\n\u002F\u002F Remove repeatable job\nawait queue.removeRepeatable('daily-digest', {\n  pattern: '0 9 * * *',\n  tz: 'America\u002FNew_York',\n});\n\n### Job Flows and Dependencies\n\nComplex multi-step job processing with parent-child relationships\n\n**When to use**: Jobs depend on other jobs completing first\n\nimport { FlowProducer } from 'bullmq';\n\nconst flowProducer = new FlowProducer({ connection });\n\n\u002F\u002F Parent waits for all children to complete\nawait flowProducer.add({\n  name: 'process-order',\n  queueName: 'orders',\n  data: { orderId: 123 },\n  children: [\n    {\n      name: 'validate-inventory',\n      queueName: 'inventory',\n      data: { orderId: 123 },\n    },\n    {\n      name: 'charge-payment',\n      queueName: 'payments',\n      data: { orderId: 123 },\n    },\n    {\n      name: 'notify-warehouse',\n      queueName: 'notifications',\n      data: { orderId: 123 },\n    },\n  ],\n});\n\n### Graceful Shutdown\n\nProperly close workers without losing jobs\n\n**When to use**: Deploying or restarting workers\n\nconst shutdown = async () => {\n  console.log('Shutting down gracefully...');\n\n  \u002F\u002F Stop accepting new jobs\n  await worker.pause();\n\n  \u002F\u002F Wait for current jobs to finish (with timeout)\n  await worker.close();\n\n  \u002F\u002F Close queue connection\n  await queue.close();\n\n  process.exit(0);\n};\n\nprocess.on('SIGTERM', shutdown);\nprocess.on('SIGINT', shutdown);\n\n### Bull Board Dashboard\n\nVisual monitoring for BullMQ queues\n\n**When to use**: Need visibility into queue status and job states\n\nimport { createBullBoard } from '@bull-board\u002Fapi';\nimport { BullMQAdapter } from '@bull-board\u002Fapi\u002FbullMQAdapter';\nimport { ExpressAdapter } from '@bull-board\u002Fexpress';\n\nconst serverAdapter = new ExpressAdapter();\nserverAdapter.setBasePath('\u002Fadmin\u002Fqueues');\n\ncreateBullBoard({\n  queues: [\n    new BullMQAdapter(emailQueue),\n    new BullMQAdapter(orderQueue),\n  ],\n  serverAdapter,\n});\n\napp.use('\u002Fadmin\u002Fqueues', serverAdapter.getRouter());\n\n## Validation Checks\n\n### Redis connection missing maxRetriesPerRequest\n\nSeverity: ERROR\n\nBullMQ requires maxRetriesPerRequest null for proper reconnection handling\n\nMessage: BullMQ queue\u002Fworker created without maxRetriesPerRequest: null on Redis connection. This will cause workers to stop on Redis connection issues.\n\n### No stalled job event handler\n\nSeverity: WARNING\n\nWorkers should handle stalled events to detect crashed workers\n\nMessage: Worker created without 'stalled' event handler. Stalled jobs indicate worker crashes and should be monitored.\n\n### No failed job event handler\n\nSeverity: WARNING\n\nWorkers should handle failed events for monitoring and alerting\n\nMessage: Worker created without 'failed' event handler. Failed jobs should be logged and monitored.\n\n### No graceful shutdown handling\n\nSeverity: WARNING\n\nWorkers should gracefully shut down on SIGTERM\u002FSIGINT\n\nMessage: Worker file without graceful shutdown handling. Jobs may be orphaned on deployment.\n\n### Awaiting queue.add in request handler\n\nSeverity: INFO\n\nQueue additions should be fire-and-forget in request handlers\n\nMessage: Queue.add awaited in request handler. Consider fire-and-forget for faster response.\n\n### Potentially large data in job payload\n\nSeverity: WARNING\n\nJob data should be small - pass IDs not full objects\n\nMessage: Job appears to have large inline data. Pass IDs instead of full objects to keep Redis memory low.\n\n### Job without timeout configuration\n\nSeverity: INFO\n\nJobs should have timeouts to prevent infinite execution\n\nMessage: Job added without explicit timeout. Consider adding timeout to prevent stuck jobs.\n\n### Retry without backoff strategy\n\nSeverity: WARNING\n\nRetries should use exponential backoff to avoid thundering herd\n\nMessage: Job has retry attempts but no backoff strategy. Use exponential backoff to prevent thundering herd.\n\n### Repeatable job without explicit timezone\n\nSeverity: WARNING\n\nRepeatable jobs should specify timezone to avoid DST issues\n\nMessage: Repeatable job without explicit timezone. Will use server local time which can drift with DST.\n\n### Potentially high worker concurrency\n\nSeverity: INFO\n\nHigh concurrency can overwhelm downstream services\n\nMessage: Worker concurrency is high. Ensure downstream services can handle this load (DB connections, API rate limits).\n\n## Collaboration\n\n### Delegation Triggers\n\n- redis infrastructure|redis cluster|memory tuning -> redis-specialist (Queue needs Redis infrastructure)\n- serverless queue|edge queue|no redis -> upstash-qstash (Need queues without managing Redis)\n- complex workflow|saga|compensation|long-running -> temporal-craftsman (Need workflow orchestration beyond simple jobs)\n- event sourcing|CQRS|event streaming -> event-architect (Need event-driven architecture)\n- deploy|kubernetes|scaling|infrastructure -> devops (Queue needs infrastructure)\n- monitor|metrics|alerting|dashboard -> performance-hunter (Queue needs monitoring)\n\n### Email Queue Stack\n\nSkills: bullmq-specialist, email-systems, redis-specialist\n\nWorkflow:\n\n```\n1. Email request received (API)\n2. Job queued with rate limiting (bullmq-specialist)\n3. Worker processes with backoff (bullmq-specialist)\n4. Email sent via provider (email-systems)\n5. Status tracked in Redis (redis-specialist)\n```\n\n### Background Processing Stack\n\nSkills: bullmq-specialist, backend, devops\n\nWorkflow:\n\n```\n1. API receives request (backend)\n2. Long task queued for background (bullmq-specialist)\n3. Worker processes async (bullmq-specialist)\n4. Result stored\u002Fnotified (backend)\n5. Workers scaled per load (devops)\n```\n\n### AI Processing Pipeline\n\nSkills: bullmq-specialist, ai-workflow-automation, performance-hunter\n\nWorkflow:\n\n```\n1. AI task submitted (ai-workflow-automation)\n2. Job flow created with dependencies (bullmq-specialist)\n3. Workers process stages (bullmq-specialist)\n4. Performance monitored (performance-hunter)\n5. Results aggregated (ai-workflow-automation)\n```\n\n### Scheduled Tasks Stack\n\nSkills: bullmq-specialist, backend, redis-specialist\n\nWorkflow:\n\n```\n1. Repeatable jobs defined (bullmq-specialist)\n2. Cron patterns with timezone (bullmq-specialist)\n3. Jobs execute on schedule (bullmq-specialist)\n4. State managed in Redis (redis-specialist)\n5. Results handled (backend)\n```\n\n## Related Skills\n\nWorks well with: `redis-specialist`, `backend`, `nextjs-app-router`, `email-systems`, `ai-workflow-automation`, `performance-hunter`\n\n## When to Use\n- User mentions or implies: bullmq\n- User mentions or implies: bull queue\n- User mentions or implies: redis queue\n- User mentions or implies: background job\n- User mentions or implies: job queue\n- User mentions or implies: delayed job\n- User mentions or implies: repeatable job\n- User mentions or implies: worker process\n- User mentions or implies: job scheduling\n- User mentions or implies: async processing\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"none","vibeship-spawner-skills (Apache 2.0)",1772150400000,"main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fframework\u002Fbullmq-specialist","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bullmq-specialist",{"tool":39,"command":40},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bullmq-specialist",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill bullmq-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fframework\u002Fbullmq-specialist\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]