[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSGX5M3PWRDN4PXDV2GZH1":3,"skill-same:01M7CSGX5M3PWRDN4PXDV2GZH1":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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSGX5M3PWRDN4PXDV2GZH1","queue-monitoring",null,"Use when an \"enable observability\" card asks for queues, or a worker's queue.backlog \u002F consumer lag signals are unbound - which exporter or direct broker data source reads Kafka, RabbitMQ, NATS and Redis queues, the metric names the recipes expect, and the consumer-side metrics the developer adds","makifbaysal\u002Ftasktrooper","makifbaysal","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F25031940?v=4","01M7CRG3ZCSYZSSEVDMW3DEYC8","Mehmet Akif Baysal","01M7CRG401FJ8YAXH5ER730XYV",122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Fqueue-monitoring\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: queue-monitoring\ncategory: observability\ndescription: Use when an \"enable observability\" card asks for queues, or a worker's queue.backlog \u002F consumer lag signals are unbound - which exporter or direct broker data source reads Kafka, RabbitMQ, NATS and Redis queues, the metric names the recipes expect, and the consumer-side metrics the developer adds\nsource: danielqsj\u002Fkafka_exporter, redpanda-data\u002Fkminion, rabbitmq\u002Frabbitmq-server, nats-io\u002Fprometheus-nats-exporter, oliver006\u002Fredis_exporter docs (Apache-2.0\u002FMIT), adapted\n---\n\n# Queue monitoring\n\nA worker's golden signals are its backlog (messages waiting), its consume rate and its errors. The backlog is read at the broker; the rate and the errors are best emitted by the consumer itself. Decide per broker which path exists before you open a task.\n\n## Read the broker first: no code change at all\n\nTaskTrooper reads three brokers directly as data sources of their own kind — `kafka`, `rabbitmq`, `nats` — and their direct recipes (`kafka-direct`, `rabbitmq-direct`, `nats-direct`) bind a worker's backlog to a consumer group, queue or JetStream consumer. When a person can add that data source (broker address and credentials), nothing has to be built: say so on the card and propose the binding once the source exists.\n\n## Or a Prometheus exporter next to the broker\n\n| Broker | Exporter | What the recipes read |\n|---|---|---|\n| Kafka | `danielqsj\u002Fkafka_exporter` (recipe `kafka-exporter`) | `kafka_consumergroup_lag{consumergroup,topic,partition}`, `kafka_topic_partition_current_offset` |\n| Kafka | `redpanda-data\u002Fkminion` (recipe `kminion`) | `kminion_kafka_consumer_group_topic_lag{group_id,topic_name}` |\n| RabbitMQ | the built-in `rabbitmq_prometheus` plugin, port 15692 (recipe `rabbitmq-prometheus`) | `rabbitmq_queue_messages_ready`, `rabbitmq_queue_messages_unacked` per queue — scrape `\u002Fmetrics\u002Fdetailed?family=queue_coarse_metrics` (or `\u002Fmetrics\u002Fper-object`), since the default `\u002Fmetrics` aggregates queues away |\n| NATS JetStream | `nats-io\u002Fprometheus-nats-exporter` with `-jsz=all` (recipe `nats-exporter`) | the consumer's `num_pending` and ack-pending gauges |\n| Redis lists (Sidekiq, Bull, RQ, custom) | `oliver006\u002Fredis_exporter` with `-check-keys` \u002F `-check-single-keys` naming the queue keys (recipe `redis-exporter-lists`) | `redis_key_size{key=\"queue:default\"}` |\n| AWS SQS \u002F GCP Pub\u002FSub | none needed: CloudWatch `ApproximateNumberOfMessagesVisible` and Cloud Monitoring `subscription\u002Fnum_undelivered_messages` (recipes `aws-sqs`, `gcp-pubsub`) | read through the cloud's own data source |\n\nRunning an exporter is infrastructure: if its deployment lives in this repository (a Helm chart, a docker-compose file, Terraform), it can be the developer's task; otherwise it is a `before_deploy` step for a person, and the exporter's address becomes a Prometheus scrape target.\n\n## In the consumer: what the developer adds\n\n- Counters for messages processed and failed, labelled by queue or topic (OpenTelemetry semantic conventions: `messaging.client.consumed.messages`, and `messaging.process.duration` as a histogram), plus `error.type` on failures.\n- A consumer span per message, continuing the producer's trace context from the message headers (the OpenTelemetry Kafka\u002FAMQP\u002FNATS instrumentations do this) — so a slow job shows the request that enqueued it.\n- Where the broker cannot be read (a managed service without metrics access), the consumer's own lag gauge: the client library's lag metric (Kafka consumers expose `records-lag-max`) exported as a gauge.\n\nAcceptance criteria: \"Given messages wait on queue `orders`, then the backlog series for `orders` is readable from \u003Cdata source> and grows while the worker is stopped\"; \"Given a message fails, then the failed counter for `orders` increases by one.\"\n\n## Then\n\nBind `queue.backlog` (and the worker's other golden signals) with `propose_signal_binding` scoped to this worker's queue or group — never a query summing every queue on the broker — and propose a `rising` alert rule above its normal peak.\n","# Queue monitoring\n\nA worker's golden signals are its backlog (messages waiting), its consume rate and its errors. The backlog is read at the broker; the rate and the errors are best emitted by the consumer itself. Decide per broker which path exists before you open a task.\n\n## Read the broker first: no code change at all\n\nTaskTrooper reads three brokers directly as data sources of their own kind — `kafka`, `rabbitmq`, `nats` — and their direct recipes (`kafka-direct`, `rabbitmq-direct`, `nats-direct`) bind a worker's backlog to a consumer group, queue or JetStream consumer. When a person can add that data source (broker address and credentials), nothing has to be built: say so on the card and propose the binding once the source exists.\n\n## Or a Prometheus exporter next to the broker\n\n| Broker | Exporter | What the recipes read |\n|---|---|---|\n| Kafka | `danielqsj\u002Fkafka_exporter` (recipe `kafka-exporter`) | `kafka_consumergroup_lag{consumergroup,topic,partition}`, `kafka_topic_partition_current_offset` |\n| Kafka | `redpanda-data\u002Fkminion` (recipe `kminion`) | `kminion_kafka_consumer_group_topic_lag{group_id,topic_name}` |\n| RabbitMQ | the built-in `rabbitmq_prometheus` plugin, port 15692 (recipe `rabbitmq-prometheus`) | `rabbitmq_queue_messages_ready`, `rabbitmq_queue_messages_unacked` per queue — scrape `\u002Fmetrics\u002Fdetailed?family=queue_coarse_metrics` (or `\u002Fmetrics\u002Fper-object`), since the default `\u002Fmetrics` aggregates queues away |\n| NATS JetStream | `nats-io\u002Fprometheus-nats-exporter` with `-jsz=all` (recipe `nats-exporter`) | the consumer's `num_pending` and ack-pending gauges |\n| Redis lists (Sidekiq, Bull, RQ, custom) | `oliver006\u002Fredis_exporter` with `-check-keys` \u002F `-check-single-keys` naming the queue keys (recipe `redis-exporter-lists`) | `redis_key_size{key=\"queue:default\"}` |\n| AWS SQS \u002F GCP Pub\u002FSub | none needed: CloudWatch `ApproximateNumberOfMessagesVisible` and Cloud Monitoring `subscription\u002Fnum_undelivered_messages` (recipes `aws-sqs`, `gcp-pubsub`) | read through the cloud's own data source |\n\nRunning an exporter is infrastructure: if its deployment lives in this repository (a Helm chart, a docker-compose file, Terraform), it can be the developer's task; otherwise it is a `before_deploy` step for a person, and the exporter's address becomes a Prometheus scrape target.\n\n## In the consumer: what the developer adds\n\n- Counters for messages processed and failed, labelled by queue or topic (OpenTelemetry semantic conventions: `messaging.client.consumed.messages`, and `messaging.process.duration` as a histogram), plus `error.type` on failures.\n- A consumer span per message, continuing the producer's trace context from the message headers (the OpenTelemetry Kafka\u002FAMQP\u002FNATS instrumentations do this) — so a slow job shows the request that enqueued it.\n- Where the broker cannot be read (a managed service without metrics access), the consumer's own lag gauge: the client library's lag metric (Kafka consumers expose `records-lag-max`) exported as a gauge.\n\nAcceptance criteria: \"Given messages wait on queue `orders`, then the backlog series for `orders` is readable from \u003Cdata source> and grows while the worker is stopped\"; \"Given a message fails, then the failed counter for `orders` increases by one.\"\n\n## Then\n\nBind `queue.backlog` (and the worker's other golden signals) with `propose_signal_binding` scoped to this worker's queue or group — never a query summing every queue on the broker — and propose a `rising` alert rule above its normal peak.\n",{"name":5,"source":24,"category":25,"description":7},"danielqsj\u002Fkafka_exporter, redpanda-data\u002Fkminion, rabbitmq\u002Frabbitmq-server, nats-io\u002Fprometheus-nats-exporter, oliver006\u002Fredis_exporter docs (Apache-2.0\u002FMIT), adapted","observability","main","910394a0b6db9fc8c9a8f36328ec421d3ebd8b38","catalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Fqueue-monitoring",18,"https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper","https:\u002F\u002Ftasktrooper.ai","https:\u002F\u002Fgithub.com\u002Fmakifbaysal","Senior Software Developer","2026-11-15 04:50:29",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add makifbaysal\u002Ftasktrooper --skill queue-monitoring",{"tool":41,"command":42},"bunx","bunx skills add makifbaysal\u002Ftasktrooper --skill queue-monitoring",{"tool":44,"command":45},"pnpm","pnpm dlx skills add makifbaysal\u002Ftasktrooper --skill queue-monitoring","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Frelease-engineer\u002Fskills\u002Fqueue-monitoring\u002FSKILL.md",true,[],[50,56,63,70,77,84],{"skillNo":51,"name":52,"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":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CSVEPQW6J6TD6CS2T5FPNZ","visual-craft","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fvisual-craft\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CSVAQG91ETHQ0HBNZDG5FR","ux-copy","Use when you write any words a user reads in a mockup or a hand-off - content language and voice, buttons, labels, errors, empty states, confirmations, numbers and dates, and the longest-string check","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fux-copy\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CSV6H0J38659NDXHJQ8396","screen-mockup-html","Use when you draw screens as the design task's HTML mockup - ONE canvas document holding every screen and every variant side by side, the sanitizer-safe recipe, phone and wide frames, the states grid, static control states, and the loopback self-check with screenshots at 375, 768 and 1440 attached to the task","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fscreen-mockup-html\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CSV3JFRF3BM3XK52M7YEYR","performance-awareness","How the performance score moves for your role. Use when the score context shows a declining trend, or before handing off work you have not self-checked against every criterion.","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fperformance-awareness\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CSTZDH00YRF5SCT7BRT9QD","design-variants","Use when a screen design needs variants - how many, variants as side-by-side rows on the one canvas, what makes two variants genuinely different, recommending one, how the human's choice is read, and narrowing to the chosen one in revision","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-variants\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CSTV6P3SM3PAE28DB0RF77","design-system-authoring","Use when you derive, change or extend a design system - where tokens live per stack, the DTCG token tree, role-based names for both themes, base vs layer vs drift, the DESIGN.md section order, the inventory format, the contrast check and the lint every proposal returns","https:\u002F\u002Fgithub.com\u002Fmakifbaysal\u002Ftasktrooper\u002Fblob\u002Fmain\u002Fcatalog\u002Fagents\u002Fui-designer\u002Fskills\u002Fdesign-system-authoring\u002FSKILL.md",[],[]]