feat: add rate-limiting-implementation-guide skill and api-resilience-engineer agent#2215
Open
ArthurAdrianoMM wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
agent
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the rate-limiting-implementation-guide skill and the api-resilience-engineer agent.
429,Retry-After,RateLimit-*headers), with runnable Express+Redis and ASP.NET Core examples.Why
Rate limiting is a standard hardening requirement, and getting it wrong (naive per-instance counters, missing Retry-After, retry storms) causes real outages. No existing skill or agent covers API resilience patterns.
Checklist
npm run skill:validatepasses for the new skill (note: an unrelated pre-existing skillaws-cloudwatch-investigationcurrently fails validation onstaged)npm run buildexecuted to update the README