[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75MT233ETEW9RPD8DF37BRS":3,"skill-same:01M75MT233ETEW9RPD8DF37BRS":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M75MT233ETEW9RPD8DF37BRS","push-over-polling",null,"Use when designing how one component learns about another's state changes — observability, status propagation, readiness, or event reaction. Prefer server push over client polling; if polling is unavoidable, bound it.","selamy-labs\u002Fagent-skills","selamy-labs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F287832944?v=4","01M75MDKJ0CKAM94KZ7TWQJM5Q","01M75MDKJNP3TATHAW1MX1FWM6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpush-over-polling\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: push-over-polling\ndescription: Use when designing how one component learns about another's state changes — observability, status propagation, readiness, or event reaction. Prefer server push over client polling; if polling is unavoidable, bound it.\n---\n\n# Push Over Polling\n\nWhen component A needs to know about state changes in component B, default to\n**B pushing the change to A**, not **A repeatedly asking B**. A busy poll loop\nboth wastes cycles when nothing changed and lags reality between intervals. Push\ndelivers the change once, when it happens, and goes quiet otherwise.\n\n## Choose push first\n\nPrefer a push mechanism the platform already gives you:\n\n- server-sent events or a long-lived stream for one-way server-to-client updates\n- webhooks or callbacks for cross-service notifications\n- a message bus, queue, or pub\u002Fsub topic for fan-out to many consumers\n- change-data-capture, watch APIs, or a notify\u002Flisten channel from a datastore\n- a blocking\u002Flong-poll endpoint that holds the request open until something\n  changes, instead of a tight retry loop\n\nPush wins on two axes at once: it is cheaper (no traffic while idle) and fresher\n(no interval-sized lag). Reach for it before writing any retry loop.\n\n## When polling is unavoidable\n\nSome sources offer no push and you must poll. That is acceptable only if the\npoll is **bounded**, never a tight loop:\n\n- **Backoff**: grow the interval when nothing changes; reset on a real change.\n- **Jitter**: randomize intervals so many clients do not align into thundering\n  herds.\n- **Conditional requests**: send `If-Modified-Since` \u002F `ETag` (or an equivalent\n  cursor\u002Fversion) so an unchanged source returns cheaply with no payload.\n- **Cursors over rescans**: poll for \"what changed since X\", not \"give me\n  everything so I can diff it\".\n- **A ceiling and a floor**: cap the slowest interval so freshness stays\n  bounded; floor the fastest so you never hammer.\n\n## When polling is actually fine\n\nDo not over-engineer. A simple bounded poll is the right call when the source\ngenuinely has no push, the change rate is low, and a few seconds of lag is\nacceptable — for example a one-shot readiness check with backoff. The target is\n\"bounded and quiet when idle\", not \"push at any cost\".\n\n## Anti-patterns\n\n- a `while true` loop that re-requests with no sleep, no backoff, and no\n  conditional check — burning cycles to mostly re-read unchanged state\n- fixed-interval polling fast enough to be expensive but still too slow to be\n  fresh — the worst of both\n- many clients polling the same source on the same fixed interval (synchronized\n  herd) with no jitter\n- re-fetching and diffing a whole collection every tick instead of asking for a\n  delta\n- adding a poller when the source already exposes a stream, webhook, or watch\n\n## Done means\n\nState changes reach the consumer via push where the source supports it; any\nremaining poll is bounded (backoff + jitter + conditional\u002Fcursored requests with\na capped interval) and is silent when nothing has changed.\n","# Push Over Polling\n\nWhen component A needs to know about state changes in component B, default to\n**B pushing the change to A**, not **A repeatedly asking B**. A busy poll loop\nboth wastes cycles when nothing changed and lags reality between intervals. Push\ndelivers the change once, when it happens, and goes quiet otherwise.\n\n## Choose push first\n\nPrefer a push mechanism the platform already gives you:\n\n- server-sent events or a long-lived stream for one-way server-to-client updates\n- webhooks or callbacks for cross-service notifications\n- a message bus, queue, or pub\u002Fsub topic for fan-out to many consumers\n- change-data-capture, watch APIs, or a notify\u002Flisten channel from a datastore\n- a blocking\u002Flong-poll endpoint that holds the request open until something\n  changes, instead of a tight retry loop\n\nPush wins on two axes at once: it is cheaper (no traffic while idle) and fresher\n(no interval-sized lag). Reach for it before writing any retry loop.\n\n## When polling is unavoidable\n\nSome sources offer no push and you must poll. That is acceptable only if the\npoll is **bounded**, never a tight loop:\n\n- **Backoff**: grow the interval when nothing changes; reset on a real change.\n- **Jitter**: randomize intervals so many clients do not align into thundering\n  herds.\n- **Conditional requests**: send `If-Modified-Since` \u002F `ETag` (or an equivalent\n  cursor\u002Fversion) so an unchanged source returns cheaply with no payload.\n- **Cursors over rescans**: poll for \"what changed since X\", not \"give me\n  everything so I can diff it\".\n- **A ceiling and a floor**: cap the slowest interval so freshness stays\n  bounded; floor the fastest so you never hammer.\n\n## When polling is actually fine\n\nDo not over-engineer. A simple bounded poll is the right call when the source\ngenuinely has no push, the change rate is low, and a few seconds of lag is\nacceptable — for example a one-shot readiness check with backoff. The target is\n\"bounded and quiet when idle\", not \"push at any cost\".\n\n## Anti-patterns\n\n- a `while true` loop that re-requests with no sleep, no backoff, and no\n  conditional check — burning cycles to mostly re-read unchanged state\n- fixed-interval polling fast enough to be expensive but still too slow to be\n  fresh — the worst of both\n- many clients polling the same source on the same fixed interval (synchronized\n  herd) with no jitter\n- re-fetching and diffing a whole collection every tick instead of asking for a\n  delta\n- adding a poller when the source already exposes a stream, webhook, or watch\n\n## Done means\n\nState changes reach the consumer via push where the source supports it; any\nremaining poll is bounded (backoff + jitter + conditional\u002Fcursored requests with\na capped interval) and is silent when nothing has changed.\n",{"name":5,"description":7},"main","54007b08157feb09e5bb9d7ff5ce4ddd21625dbf","skills\u002Fpush-over-polling",3,"https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills","https:\u002F\u002Fselamy.dev","https:\u002F\u002Fgithub.com\u002Fselamy-labs","2026-11-15 03:50:58",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add selamy-labs\u002Fagent-skills --skill push-over-polling",{"tool":37,"command":38},"bunx","bunx skills add selamy-labs\u002Fagent-skills --skill push-over-polling",{"tool":40,"command":41},"pnpm","pnpm dlx skills add selamy-labs\u002Fagent-skills --skill push-over-polling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fpush-over-polling\u002FSKILL.md",true,[],[46,53,60,67,73,80],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M75MY70JMSNFHQX63G90SKZ7","silence-phrase","A seemingly normal skill.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fsilence-phrase\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75MY5PKVKY60M8H2DFTW58C","selamy-bad-skill","This skill has a vendor prefix that should be rejected.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fprefixed-name\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75MY1TKXCH6WYN9ET0W4T02","oversized-description","This is a very long description that contains way too many words and should be rejected by the validator because it exceeds the forty five word limit that is enforced by the naming lint checker which ensures skill descriptions stay concise and readable for humans and machines alike without unnecessary verbosity or padding","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Foversized-description\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75MY0SZ7EKT99NWJEJ8HKS2","missing-frontmatter","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmissing-frontmatter\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75MXYMBREE6D7KRR87YM4DH","malicious-skill","A poisoned skill used only as a negative fixture for the security gate.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fmalicious-skill\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75MXX2B7AC2QSSRRQQXTA0N","leaking-org-name","A skill about something.","https:\u002F\u002Fgithub.com\u002Fselamy-labs\u002Fagent-skills\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fleaking-org-name\u002FSKILL.md",[],[]]