[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B8NS8KQ00SJS0H5TYMTMXG":3,"skill-same:01M7B8NS8KQ00SJS0H5TYMTMXG":93},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7B8NS8KQ00SJS0H5TYMTMXG","ac-message-queues",null,"The middleware layer that decouples producers from consumers: broker topologies and what a direct, fanout, or topic exchange actually routes, delivery guarantees from at-most-once through to effectively-once, acknowledgement and redelivery when a consumer dies mid-message, poison messages and the dead-letter path, priority and fair dispatch, queue backpressure and bounded buffers, competing consumers and ordering under scale-out, and the written queue record. It explains how a queue behaves and where it fails; it never recommends a broker. Use when asking \"message queue\", \"dead letter queue\", \"poison message\", \"ack and redeliver\", \"competing consumers\", \"fanout exchange\", \"topic routing\", \"work queue\", \"priority queue\", \"why did this message arrive twice\", \"prefetch\". Not for event-driven design between your own services (ac-event-driven-architecture), not for webhook delivery to endpoints you do not own (ac-webhook-and-async-delivery), not for durable workflows and sagas (ac-durable-execution).","jiayaoqijia\u002Fcryptoskill","jiayaoqijia","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1453879?v=4","01M6GMYTX7Q7S504VC6E756ENR","YQ","01M6GMYV1QKJ1CC75MTTGT9PR0",81,"MIT","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ac-message-queues\ndescription: \"The middleware layer that decouples producers from consumers: broker topologies and what a direct, fanout, or topic exchange actually routes, delivery guarantees from at-most-once through to effectively-once, acknowledgement and redelivery when a consumer dies mid-message, poison messages and the dead-letter path, priority and fair dispatch, queue backpressure and bounded buffers, competing consumers and ordering under scale-out, and the written queue record. It explains how a queue behaves and where it fails; it never recommends a broker. Use when asking \\\"message queue\\\", \\\"dead letter queue\\\", \\\"poison message\\\", \\\"ack and redeliver\\\", \\\"competing consumers\\\", \\\"fanout exchange\\\", \\\"topic routing\\\", \\\"work queue\\\", \\\"priority queue\\\", \\\"why did this message arrive twice\\\", \\\"prefetch\\\". Not for event-driven design between your own services (ac-event-driven-architecture), not for webhook delivery to endpoints you do not own (ac-webhook-and-async-delivery), not for durable workflows and sagas (ac-durable-execution).\"\nlicense: MIT\nmetadata:\n  domain: software-engineering\nstatus: seedling\n---\n\n# Message queues\n\n## Overview\n\nA queue takes a message from a producer who does not want to wait and gives it to a consumer who may not exist yet. That simple contract hides the decisions that decide whether a system works: what the broker promises about delivery, what happens when a consumer accepts and dies, where an unreadable message goes, and who receives the next one when several consumers compete.\n\nThis skill covers the middleware mechanics: routing topologies and what each exchange type matches, the delivery-guarantee ladder and the acknowledgement machinery that produces each rung, the poison-message path that stops one bad message from wedging a worker, priority and prefetch and fair dispatch, and the bounded-buffer question of what a queue does when consumers cannot keep up. The architectural choice to use events belongs to another skill; this one is about operating the pipe.\n\nPrimary sources: \u003Chttps:\u002F\u002Fwww.rabbitmq.com\u002Ftutorials\u002Ftutorial-one-python> and \u003Chttps:\u002F\u002Fkafka.apache.org\u002Fdocumentation\u002F>.\n\n## When to use\n\n- Choosing or reading a broker, exchange, or queue topology.\n- Deciding the acknowledgement and redelivery model for a consumer.\n- Handling a poison message or designing the dead-letter path.\n- Diagnosing duplicate delivery, lost delivery, or wedged workers.\n- Sizing prefetch, priority, and competing consumers under load.\n\n## When NOT to use\n\n- For event-driven architecture between your own services (use ac-event-driven-architecture).\n- For delivering to endpoints you do not control (use ac-webhook-and-async-delivery).\n- For durable workflows and compensation (use ac-durable-execution).\n\n## Subskill Index\n\n| Leaf | Domain segment | Scope (one line) |\n|---|---|---|\n| `subskills\u002Frouting-topologies.md` | `software-engineering\u002Frouting-topologies` | Direct, fanout, topic, and headers exchanges, and what each route matches. |\n| `subskills\u002Fdelivery-guarantees.md` | `software-engineering\u002Fdelivery-guarantees` | The ladder from at-most-once to effectively-once, and its cost at each rung. |\n| `subskills\u002Fack-and-redelivery.md` | `software-engineering\u002Fack-and-redelivery` | Acknowledgement windows, the death-during-processing case, and redelivery. |\n| `subskills\u002Fpoison-and-dead-letter.md` | `software-engineering\u002Fpoison-and-dead-letter` | The unreadable message, retry limits, and the dead-letter path with its reasons. |\n| `subskills\u002Fpriority-and-dispatch.md` | `software-engineering\u002Fpriority-and-dispatch` | Priority queues, prefetch, and the fairness they quietly decide. |\n| `subskills\u002Fqueue-backpressure.md` | `software-engineering\u002Fqueue-backpressure` | Bounded buffers, what to reject, and where the excess is allowed to go. |\n| `subskills\u002Fqueue-record.md` | `software-engineering\u002Fqueue-record` | The written record of guarantees, limits, and inspection points. |\n\n## Status and honest limits\n\nA queue's behaviour is a product of its configuration: identical topologies redeliver differently, drop differently, and order differently across brokers and flags. The guarantees described here are the shape of the machinery, not the settings of any one broker, and each claim must be read against the deployment's own documentation. Nothing here recommends a broker, and no queue makes a consumer idempotent — that obligation lands on the consumer regardless of what the pipe promises.\n","# Message queues\n\n## Overview\n\nA queue takes a message from a producer who does not want to wait and gives it to a consumer who may not exist yet. That simple contract hides the decisions that decide whether a system works: what the broker promises about delivery, what happens when a consumer accepts and dies, where an unreadable message goes, and who receives the next one when several consumers compete.\n\nThis skill covers the middleware mechanics: routing topologies and what each exchange type matches, the delivery-guarantee ladder and the acknowledgement machinery that produces each rung, the poison-message path that stops one bad message from wedging a worker, priority and prefetch and fair dispatch, and the bounded-buffer question of what a queue does when consumers cannot keep up. The architectural choice to use events belongs to another skill; this one is about operating the pipe.\n\nPrimary sources: \u003Chttps:\u002F\u002Fwww.rabbitmq.com\u002Ftutorials\u002Ftutorial-one-python> and \u003Chttps:\u002F\u002Fkafka.apache.org\u002Fdocumentation\u002F>.\n\n## When to use\n\n- Choosing or reading a broker, exchange, or queue topology.\n- Deciding the acknowledgement and redelivery model for a consumer.\n- Handling a poison message or designing the dead-letter path.\n- Diagnosing duplicate delivery, lost delivery, or wedged workers.\n- Sizing prefetch, priority, and competing consumers under load.\n\n## When NOT to use\n\n- For event-driven architecture between your own services (use ac-event-driven-architecture).\n- For delivering to endpoints you do not control (use ac-webhook-and-async-delivery).\n- For durable workflows and compensation (use ac-durable-execution).\n\n## Subskill Index\n\n| Leaf | Domain segment | Scope (one line) |\n|---|---|---|\n| `subskills\u002Frouting-topologies.md` | `software-engineering\u002Frouting-topologies` | Direct, fanout, topic, and headers exchanges, and what each route matches. |\n| `subskills\u002Fdelivery-guarantees.md` | `software-engineering\u002Fdelivery-guarantees` | The ladder from at-most-once to effectively-once, and its cost at each rung. |\n| `subskills\u002Fack-and-redelivery.md` | `software-engineering\u002Fack-and-redelivery` | Acknowledgement windows, the death-during-processing case, and redelivery. |\n| `subskills\u002Fpoison-and-dead-letter.md` | `software-engineering\u002Fpoison-and-dead-letter` | The unreadable message, retry limits, and the dead-letter path with its reasons. |\n| `subskills\u002Fpriority-and-dispatch.md` | `software-engineering\u002Fpriority-and-dispatch` | Priority queues, prefetch, and the fairness they quietly decide. |\n| `subskills\u002Fqueue-backpressure.md` | `software-engineering\u002Fqueue-backpressure` | Bounded buffers, what to reject, and where the excess is allowed to go. |\n| `subskills\u002Fqueue-record.md` | `software-engineering\u002Fqueue-record` | The written record of guarantees, limits, and inspection points. |\n\n## Status and honest limits\n\nA queue's behaviour is a product of its configuration: identical topologies redeliver differently, drop differently, and order differently across brokers and flags. The guarantees described here are the shape of the machinery, not the settings of any one broker, and each claim must be read against the deployment's own documentation. Nothing here recommends a broker, and no queue makes a consumer idempotent — that obligation lands on the consumer regardless of what the pipe promises.\n",{"name":5,"status":25,"license":15,"metadata":26,"description":7},"seedling",{"domain":27},"software-engineering","main","4aff87e77e63c1886a978b82902814d015f55a4f","skills\u002Fexchanges\u002Fanoscranel-ac-message-queues",17,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia","https:\u002F\u002Feth2030.com","Hardcore infra. Building @alt-research and applied cryptography.","2026-11-15 02:28:10",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add jiayaoqijia\u002Fcryptoskill --skill ac-message-queues",{"tool":43,"command":44},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill ac-message-queues",{"tool":46,"command":47},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill ac-message-queues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002FSKILL.md",true,[51,55,61,65,69,73,77,81,85,89],{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE","许可证",1068,{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"SOURCE.md","REFERENCE","参考文档",373,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002FSOURCE.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"subskills\u002Fack-and-redelivery.md",3204,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002Fsubskills\u002Fack-and-redelivery.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"subskills\u002Fdelivery-guarantees.md",3151,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002Fsubskills\u002Fdelivery-guarantees.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"subskills\u002Fpoison-and-dead-letter.md",3188,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002Fsubskills\u002Fpoison-and-dead-letter.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"subskills\u002Fpriority-and-dispatch.md",3111,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002Fsubskills\u002Fpriority-and-dispatch.md",{"path":78,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":79,"sourceHtmlUrl":80},"subskills\u002Fqueue-backpressure.md",3026,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002Fsubskills\u002Fqueue-backpressure.md",{"path":82,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":83,"sourceHtmlUrl":84},"subskills\u002Fqueue-record.md",3156,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002Fsubskills\u002Fqueue-record.md",{"path":86,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":87,"sourceHtmlUrl":88},"subskills\u002Frouting-topologies.md",3164,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002Fsubskills\u002Frouting-topologies.md",{"path":90,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":91,"sourceHtmlUrl":92},"TRUST.auto.yaml",2217,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-message-queues\u002FTRUST.auto.yaml",[94,102,110,118,126,134],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"01M7DTKCERMV0RNX3HZJP4CZ26","troves","Deposit and withdraw from Troves DeFi yield vault strategies on Starknet. View available strategies, check positions, and manage vault deposits. Use this skill when the user mentions Troves, vault, yield vault, DeFi vault, strategy, yield farming, vault deposit, vault withdraw, earning yield through vaults, passive yield strategies, or wants to deposit into or withdraw from a yield strategy — even if they don't say \"Troves\" explicitly.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-troves\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-troves\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":20},"01M7DTK6CJSMGC8KCQHGNYFZBD","trade","Swap tokens on Starknet via Fibrous DEX aggregator. Supports per-provider selection (avnu, ekubo, or auto to race all). Use this skill when the user wants to swap, exchange, trade, convert, buy, or sell one token for another on Starknet. Also use when the user asks about token prices, exchange rates, DEX routing, best swap route, or wants to check how much they would receive for a given amount — even if they don't explicitly say \"swap\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-trade\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-trade\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":20},"01M7DTJZ6A0X4PAW3Y8W4J9K64","staking","Stake, unstake, claim, and compound rewards for STRK, WBTC, tBTC, SolvBTC, and LBTC on Starknet. View validators, pools, and staking positions. Use this skill when the user mentions staking, delegating, validators, staking pools, rewards, compounding, unstaking, earning yield, passive income on crypto, or wants to earn on their STRK or BTC tokens — even if they don't say \"stake\" explicitly.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-staking\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-staking\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":20},"01M7DTJSDZJKCDMW7GHRF4BRH5","send","Send STRK, ETH, or any ERC-20 token to a Starknet address. Supports simulation (dry-run) before execution. Use this skill when the user wants to send, transfer, pay, tip, or move tokens to another wallet address on Starknet. Also trigger when the user mentions sending funds to someone, making a payment, transferring assets, or moving crypto to a specific address — even if they just say \"pay 10 STRK to 0x...\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-send\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-send\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":20},"01M7DTJG1E480D51ZQ7WKDQ26K","portfolio","View a comprehensive DeFi portfolio dashboard and optimize portfolio allocation via automated rebalancing. Use this skill when the user wants an overview, summary, dashboard, total value, net worth, portfolio rebalancing, target allocation, or wants to see all their DeFi positions across Starknet at once. Also trigger when the user asks \"what do I have\", \"show me everything\", \"how much am I worth\", \"my positions\", \"my investments\", \"rebalance my portfolio\", \"I want 50% ETH\", \"optimize my holdings\", or any request for a holistic view of their Starknet holdings — even if they don't explicitly say \"portfolio\".","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-portfolio\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-portfolio\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":138,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":20},"01M7DTJ7M8TE9R2N36HFBZDGVD","multi-swap","Execute multiple token swaps in a single Starknet transaction via Fibrous (default). Supports per-provider selection (avnu, ekubo, or auto to race all). Supports 2-3 swap pairs bundled into one multicall. Use this skill when the user wants to swap multiple token pairs at once, do batch swaps, execute several trades simultaneously, perform parallel swaps, or do bulk trading in one transaction. Also trigger when the user mentions \"two swaps\", \"three swaps\", \"swap X and Y at the same time\", or wants to convert multiple tokens in a single call.","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-multi-swap\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fmcp-servers\u002Fahmetenesdur-multi-swap\u002FSKILL.md",[],[]]