[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B948EVZCHVJCY2DP4V2GJG":3,"skill-same:01M7B948EVZCHVJCY2DP4V2GJG":97},{"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},"01M7B948EVZCHVJCY2DP4V2GJG","ac-single-request-value",null,"Maximum value from every request to a metered or rate-limited model API: batching sub-questions into one planned request, packing context so one round trip answers many needs, when a clarifying question earns its round trip, pre-reading so the request arrives prepared, multi-part outputs in one call, degrading rather than retrying, and the per-request ledger. It treats requests per answer as the cost metric; it never recommends a provider. Use when asking \"per request limits\", \"RPM\", \"RPD\", \"free tier\", \"how do I ask more in one prompt\", \"batch sub-questions\", \"maximize each API call\", \"request budget\", \"pack my questions into one prompt\". Not for prompt wording and instruction design (ac-prompt-engineer), not for the HTTP mechanics of calling model APIs (ac-llm-api-integration), not for cloud cost attribution of infrastructure (ac-cost-aware-engineering).","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-single-request-value\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ac-single-request-value\ndescription: \"Maximum value from every request to a metered or rate-limited model API: batching sub-questions into one planned request, packing context so one round trip answers many needs, when a clarifying question earns its round trip, pre-reading so the request arrives prepared, multi-part outputs in one call, degrading rather than retrying, and the per-request ledger. It treats requests per answer as the cost metric; it never recommends a provider. Use when asking \\\"per request limits\\\", \\\"RPM\\\", \\\"RPD\\\", \\\"free tier\\\", \\\"how do I ask more in one prompt\\\", \\\"batch sub-questions\\\", \\\"maximize each API call\\\", \\\"request budget\\\", \\\"pack my questions into one prompt\\\". Not for prompt wording and instruction design (ac-prompt-engineer), not for the HTTP mechanics of calling model APIs (ac-llm-api-integration), not for cloud cost attribution of infrastructure (ac-cost-aware-engineering).\"\nlicense: MIT\nmetadata:\n  domain: prompt-engineering\nstatus: seedling\n---\n\n# Single-request value\n\n## Overview\n\nWhen an API prices or meters per request — a cap of so many requests per minute, a free daily allowance, or a pay-per-call tariff — the unit of economy is no longer the token or the dollar but the request itself. A wasteful question is not one word too long; it is a round trip too many. Ten sub-questions asked in ten separate calls burn ten requests; under a cap they multiply cost and can stall mid-sequence — work done, answers withheld.\n\nThis skill is the craft of treating every request as precious. Its centre is the packing decision — what belongs in one request —, and outward to the habits around it: preparing before calling, structuring one response into many deliverables, deciding when a clarification earns its round trip, stopping retries, and keeping the ledger that turns limit arithmetic into a measurable discipline.\n\nPrimary sources: \u003Chttps:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fapi\u002Frate-limits> and \u003Chttps:\u002F\u002Fai.google.dev\u002Fgemini-api\u002Fdocs\u002Frate-limits>.\n\n## When to use\n\n- When the provider limits requests per minute or per day, or prices per request.\n- When a free tier's daily allowance is the binding constraint on what can be done.\n- When a work session would otherwise stall mid-sequence after requests run out.\n- When the same content needs several small outputs and one call could carry them all.\n\n## When NOT to use\n\n- For prompt wording, instruction form, and model knob choices (use ac-prompt-engineer).\n- For HTTP mechanics, auth, streaming, and the tool-use loop (use ac-llm-api-integration).\n- For infrastructure cost attribution and unit economics of systems (use ac-cost-aware-engineering).\n\n## Subskill Index\n\n| Leaf | Domain segment | Scope (one line) |\n|---|---|---|\n| `subskills\u002Frequest-economy.md` | `prompt-engineering\u002Frequest-economy` | Reading the limit: requests as the binding currency, and the arithmetic of allowance. |\n| `subskills\u002Fbatching-sub-questions.md` | `prompt-engineering\u002Fbatching-sub-questions` | Asking in one packed request what would otherwise be ten calls. |\n| `subskills\u002Fpacking-and-context.md` | `prompt-engineering\u002Fpacking-and-context` | Loading one request with the evidence, the questions, and the output contract. |\n| `subskills\u002Fsingle-request-multi-output.md` | `prompt-engineering\u002Fsingle-request-multi-output` | One response structured into several deliverables by design, not parsing luck. |\n| `subskills\u002Fclarification-economics.md` | `prompt-engineering\u002Fclarification-economics` | When a clarifying question is worth a round trip, and when a staged-response contract is better. |\n| `subskills\u002Fpreparation-and-caching.md` | `prompt-engineering\u002Fpreparation-and-caching` | Reading local and computing cheaply before spending a request. |\n| `subskills\u002Fno-retry-degradation.md` | `prompt-engineering\u002Fno-retry-degradation` | Answering from the response already received rather than burning a retry. |\n| `subskills\u002Fvalue-record.md` | `prompt-engineering\u002Fvalue-record` | The per-request ledger: what each request was for, what it returned, what remains. |\n\n## Status and honest limits\n\nPacking work into fewer, denser requests trades structure for economy; a packed request demands more careful drafting and its failures are larger, since a malformed multi-part request wastes the whole call rather than one small one. Nothing here recommends a provider or tariff; limit regimes change, and the record should state the allowance and date from the vendor's current published page.\n","# Single-request value\n\n## Overview\n\nWhen an API prices or meters per request — a cap of so many requests per minute, a free daily allowance, or a pay-per-call tariff — the unit of economy is no longer the token or the dollar but the request itself. A wasteful question is not one word too long; it is a round trip too many. Ten sub-questions asked in ten separate calls burn ten requests; under a cap they multiply cost and can stall mid-sequence — work done, answers withheld.\n\nThis skill is the craft of treating every request as precious. Its centre is the packing decision — what belongs in one request —, and outward to the habits around it: preparing before calling, structuring one response into many deliverables, deciding when a clarification earns its round trip, stopping retries, and keeping the ledger that turns limit arithmetic into a measurable discipline.\n\nPrimary sources: \u003Chttps:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fapi\u002Frate-limits> and \u003Chttps:\u002F\u002Fai.google.dev\u002Fgemini-api\u002Fdocs\u002Frate-limits>.\n\n## When to use\n\n- When the provider limits requests per minute or per day, or prices per request.\n- When a free tier's daily allowance is the binding constraint on what can be done.\n- When a work session would otherwise stall mid-sequence after requests run out.\n- When the same content needs several small outputs and one call could carry them all.\n\n## When NOT to use\n\n- For prompt wording, instruction form, and model knob choices (use ac-prompt-engineer).\n- For HTTP mechanics, auth, streaming, and the tool-use loop (use ac-llm-api-integration).\n- For infrastructure cost attribution and unit economics of systems (use ac-cost-aware-engineering).\n\n## Subskill Index\n\n| Leaf | Domain segment | Scope (one line) |\n|---|---|---|\n| `subskills\u002Frequest-economy.md` | `prompt-engineering\u002Frequest-economy` | Reading the limit: requests as the binding currency, and the arithmetic of allowance. |\n| `subskills\u002Fbatching-sub-questions.md` | `prompt-engineering\u002Fbatching-sub-questions` | Asking in one packed request what would otherwise be ten calls. |\n| `subskills\u002Fpacking-and-context.md` | `prompt-engineering\u002Fpacking-and-context` | Loading one request with the evidence, the questions, and the output contract. |\n| `subskills\u002Fsingle-request-multi-output.md` | `prompt-engineering\u002Fsingle-request-multi-output` | One response structured into several deliverables by design, not parsing luck. |\n| `subskills\u002Fclarification-economics.md` | `prompt-engineering\u002Fclarification-economics` | When a clarifying question is worth a round trip, and when a staged-response contract is better. |\n| `subskills\u002Fpreparation-and-caching.md` | `prompt-engineering\u002Fpreparation-and-caching` | Reading local and computing cheaply before spending a request. |\n| `subskills\u002Fno-retry-degradation.md` | `prompt-engineering\u002Fno-retry-degradation` | Answering from the response already received rather than burning a retry. |\n| `subskills\u002Fvalue-record.md` | `prompt-engineering\u002Fvalue-record` | The per-request ledger: what each request was for, what it returned, what remains. |\n\n## Status and honest limits\n\nPacking work into fewer, denser requests trades structure for economy; a packed request demands more careful drafting and its failures are larger, since a malformed multi-part request wastes the whole call rather than one small one. Nothing here recommends a provider or tariff; limit regimes change, and the record should state the allowance and date from the vendor's current published page.\n",{"name":5,"status":25,"license":15,"metadata":26,"description":7},"seedling",{"domain":27},"prompt-engineering","main","4aff87e77e63c1886a978b82902814d015f55a4f","skills\u002Fexchanges\u002Fanoscranel-ac-single-request-value",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-single-request-value",{"tool":43,"command":44},"bunx","bunx skills add jiayaoqijia\u002Fcryptoskill --skill ac-single-request-value",{"tool":46,"command":47},"pnpm","pnpm dlx skills add jiayaoqijia\u002Fcryptoskill --skill ac-single-request-value","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002FSKILL.md",true,[51,55,61,65,69,73,77,81,85,89,93],{"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","参考文档",379,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002FSOURCE.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"subskills\u002Fbatching-sub-questions.md",3409,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Fbatching-sub-questions.md",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"subskills\u002Fclarification-economics.md",3653,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Fclarification-economics.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"subskills\u002Fno-retry-degradation.md",3588,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Fno-retry-degradation.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"subskills\u002Fpacking-and-context.md",3419,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Fpacking-and-context.md",{"path":78,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":79,"sourceHtmlUrl":80},"subskills\u002Fpreparation-and-caching.md",3303,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Fpreparation-and-caching.md",{"path":82,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":83,"sourceHtmlUrl":84},"subskills\u002Frequest-economy.md",3490,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Frequest-economy.md",{"path":86,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":87,"sourceHtmlUrl":88},"subskills\u002Fsingle-request-multi-output.md",3429,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Fsingle-request-multi-output.md",{"path":90,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":91,"sourceHtmlUrl":92},"subskills\u002Fvalue-record.md",3001,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002Fsubskills\u002Fvalue-record.md",{"path":94,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":95,"sourceHtmlUrl":96},"TRUST.auto.yaml",2324,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fexchanges\u002Fanoscranel-ac-single-request-value\u002FTRUST.auto.yaml",[98,106,114,122,130,138],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"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":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"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":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":142,"sourceHtmlUrl":143,"categories":144,"keywords":145,"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",[],[]]