All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- Agent Postmortem CouncilRun a team of postmortem agents that builds the timeline, analyzes causes, drafts corrective actions, and reviews for blamelessness and completeness. Use after an incident when you need a rigorous, blameless writeup and owned action list instead of a hasty narrative that pins it on a person.Votes: 0GitHub stars: 7
- Agent Pricing CommitteeConvene agents to model pricing options, argue them from customer, competitor, and margin angles, and hand a human a decision pack. Use when setting or changing prices and the discussion keeps going in circles.Votes: 0GitHub stars: 7
- Agent Procurement DeskEvaluate vendors with agents that build a comparable requirement matrix, research each option, check security and data terms, and prepare a recommendation for human sign-off. Use when choosing tools or suppliers and comparisons keep drifting on vendor marketing.Votes: 0GitHub stars: 7
- Agent Progressive DisclosureGive agents context in stages, escalating to more capable models or fuller context only when the cheap path proves insufficient. Use when most tasks are easy but a few are hard and cost or latency matters.Votes: 0GitHub stars: 7
- Agent Qa GatePlace a QA agent as the last blocking node before output ships, checking acceptance criteria against executed test evidence with the power to veto. Use when builder agents keep declaring done on work that does not meet its criteria and you need one gate that runs the artifact instead of trusting the claim.Votes: 0GitHub stars: 7
- Agent Quality CouncilHold a consistent standard across everything a company ships, with agents that review against written criteria and escalate disagreements rather than averaging them. Use when quality varies by who happened to do the work.Votes: 0GitHub stars: 7
- Agent Red Team Blue TeamRun attacker and defender agents in a fix-and-re-attack loop so exploitable bugs get found, triaged, fixed, and verified before ship. Use when you want a system probed and hardened by an agent team rather than one pass of review.Votes: 0GitHub stars: 7
- Agent Release TrainRun release agents that draft the changelog, scan risk, verify the candidate, and gate publish behind a go/no-go check. Use when cutting a release and you want the boring parts automated and the risky parts caught before ship.Votes: 0GitHub stars: 7
- Agent Research LabRun a lab of researcher agents that search in parallel, verify sources independently, and synthesize a cited answer. Use when a question needs breadth of sources and every load-bearing claim must trace to evidence.Votes: 0GitHub stars: 7
- Agent Risk RegisterMaintain a living register of business risks with agents that surface new ones, track mitigations, and force stale entries back to a decision. Use when risks are discussed in meetings and then forgotten until they happen.Votes: 0GitHub stars: 7
- Agent Role DefinitionWrite role cards that pin each agent to one charter with declared inputs, outputs, refusal rules, and non-overlapping scope. Use when assembling a multi-agent team and you need every agent to stay in its lane instead of all drifting toward the same work.Votes: 0GitHub stars: 7
- Agent Sales PipelineStaff a pipeline with agents that research accounts, qualify leads against explicit criteria, draft outreach for human sending, and keep the CRM honest. Use when lead flow needs consistent handling and the pipeline record keeps rotting.Votes: 0GitHub stars: 7
- Agent Security Audit TeamRun a security audit as agents that map the attack surface, review each surface in parallel, skeptic-test every finding, and assemble one report. Use when you want a codebase audited by a coordinated agent team instead of a single review pass.Votes: 0GitHub stars: 7
- Agent Specialist RouterRoute each request to the agent best suited to it, with a fallback and an explicit unknown path, instead of one generalist handling everything. Use when tasks vary enough that one prompt serves none of them well.Votes: 0GitHub stars: 7
- Agent Startup SquadRun a lean startup team of agents (builder, marketer, analyst) through one disciplined weekly loop of ship, promote, and measure. Use when you want a small agent team to move a single product metric week over week.Votes: 0GitHub stars: 7
- Agent Status RollupAggregate desk-level state into an honest company view where problems stay visible instead of averaging away. Use when everything is reported green and things are still going wrong.Votes: 0GitHub stars: 7
- Agent Strategy ReviewRun a periodic strategy review with agents that check whether stated goals still match reality, argue the alternatives, and force an explicit continue or change decision. Use when quarterly planning repeats last quarter's plan by default.Votes: 0GitHub stars: 7
- Agent Support DeskRun a team of support agents that triages each ticket, reproduces the problem, drafts a reply, and hands clean escalations to a human. Use when inbound support volume needs consistent handling and a person must approve every customer-facing reply before it goes out.Votes: 0GitHub stars: 7
- Agent Tournament SelectionGenerate several independent attempts, score them against explicit criteria, and select or combine the winner, instead of iterating one attempt. Use when the solution space is wide and the first approach may not be the best.Votes: 0GitHub stars: 7
- Agent Training AcademyTurn internal knowledge into role-based learning paths with agents that build, test, and keep material current as systems change. Use when onboarding is slow because knowledge lives in people rather than in material.Votes: 0GitHub stars: 7
- Agent Vendor OperationsTrack every vendor's cost, renewal, usage, and access with agents that flag waste and surface renewals before they auto-renew. Use when software spend grows quietly and nobody knows what is still in use.Votes: 0GitHub stars: 7
- Agent Work AssignmentMatch work to the agent or person best able to finish it, with explicit capacity limits so nothing is assigned into an already full queue. Use when work is distributed by whoever is nearest rather than by fit and capacity.Votes: 0GitHub stars: 7
- Agent Workload BalancingRedistribute work across desks and workers as load shifts, so one bottleneck does not stall the company while others idle. Use when some desks are overwhelmed and others have nothing queued.Votes: 0GitHub stars: 7
- Virtual Engineering TeamRun a product-engineering squad of agents from spec to shipped change with a PM, an architect, two engineers, a reviewer, and QA. Use when a task is too large for one agent and needs both division of labor and an independent quality gate.Votes: 0GitHub stars: 7
- Dns FundamentalsReason about DNS records, resolution, TTLs, and caching so name changes land predictably instead of mysteriously. Use when configuring a domain, moving a service, or debugging why a hostname resolves to the wrong place.Votes: 0GitHub stars: 7
- Load BalancingDistribute traffic across instances with the right algorithm, health checks, and draining so capacity is used and failures are absorbed. Use when scaling a service horizontally or diagnosing uneven load.Votes: 0GitHub stars: 7
- Tls And CertificatesIssue, install, renew, and debug TLS certificates so connections stay encrypted and trusted without surprise expiry. Use when setting up HTTPS, rotating a certificate, or diagnosing a trust or handshake error.Votes: 0GitHub stars: 7
- Websockets At ScaleRun persistent connections with heartbeats, reconnection, backpressure, and fan-out that survive load and restarts. Use when building realtime features on WebSockets or a similar long-lived transport.Votes: 0GitHub stars: 7
- Delivery TrackingKnow whether a message was accepted, delivered, opened, and acted on, and treat failures as events rather than statistics. Use when messages are assumed delivered and support tickets say otherwise.Votes: 0GitHub stars: 7
- Digest DesignBatch many low-urgency events into one periodic summary that is worth opening, rather than sending each as it happens. Use when individual events are too frequent or too minor to interrupt.Votes: 0GitHub stars: 7
- Email DeliverabilityGet email into the inbox rather than the spam folder, through authentication, reputation, and list hygiene. Use when email is not arriving or engagement suddenly drops.Votes: 0GitHub stars: 7
- In App MessagingDeliver messages inside the product where they are contextual and non-interruptive, using the right surface for each urgency. Use when a message relates to what the user is doing right now.Votes: 0GitHub stars: 7
- Multi Channel OrchestrationCoordinate across push, email, in-app, and SMS so a user gets one message rather than the same thing four times. Use when several channels exist and users receive duplicates.Votes: 0GitHub stars: 7
- Notification BatchingGroup related events so a burst of activity produces one message instead of twenty, with rules that stay predictable. Use when a single action generates many notifications or activity comes in bursts.Votes: 0GitHub stars: 7
- Notification FatigueDetect and reverse the point where users stop reading, by measuring engagement decay and cutting volume before they mute. Use when open rates are falling or mute rates are rising.Votes: 0GitHub stars: 7
- Notification StrategyDecide what deserves a notification, on which channel, and at what urgency, before building any of it. Use when notifications are added per feature and users are starting to mute everything.Votes: 0GitHub stars: 7
- Push Notification PermissionsAsk for push permission at a moment when the value is obvious, and handle denial gracefully, because the prompt only comes once. Use when adding push to a mobile or web product.Votes: 0GitHub stars: 7
- Quiet Hours And TimingSend at times that respect the recipient's local hours and working pattern, deferring anything non-urgent. Use when notifications reach people at night or on weekends.Votes: 0GitHub stars: 7
- Transactional MessagingSend the messages a user is waiting for, such as receipts, resets, and confirmations, with reliability and clarity that marketing messages do not need. Use when building password resets, receipts, or order confirmations.Votes: 0GitHub stars: 7
- Unsubscribe And PreferencesGive users real control over what they receive, with granular options and an honest one-click exit. Use when building preference centres or reducing complaint rates.Votes: 0GitHub stars: 7
- Code Of Conduct EnforcementApply a code of conduct consistently, with a reporting path, proportionate responses, and records, so it protects people rather than decorating the repository. Use when adopting a code of conduct or handling a report.Votes: 0GitHub stars: 7
- Contributor OnboardingLower the cost of a first contribution with a working setup, a clear scope, and a fast review so people come back. Use when a project wants contributors and gets drive-by patches or none.Votes: 0GitHub stars: 7
- Documentation For AdoptionWrite the docs that decide whether someone adopts a project: a truthful readme, a working quickstart, and answers to the first questions. Use when a project is capable but nobody gets past the first ten minutes.Votes: 0GitHub stars: 7
- Forking And VendoringDecide between patching upstream, forking, and vendoring a dependency, and carry the ongoing cost knowingly. Use when a dependency needs a change you cannot get merged, or is unmaintained.Votes: 0GitHub stars: 7
- Issue TriageProcess incoming issues so real problems get found fast and the queue stays honest about what will be worked on. Use when an issue tracker has grown past what anyone reads.Votes: 0GitHub stars: 7
- Maintainer SustainabilityKeep a project alive without burning out its maintainers, through scope limits, shared load, and honest signals about capacity. Use when maintenance feels like an obligation you cannot decline.Votes: 0GitHub stars: 7
- Open Source LicensingChoose a licence, comply with the licences you depend on, and keep attribution correct as a project grows. Use when publishing a project, adding a dependency, or answering whether a licence permits your use.Votes: 0GitHub stars: 7
- Project GovernanceDefine who decides what in a project, how that changes, and how disputes end, before a disagreement forces the question. Use when a project grows past one maintainer or a conflict has no clear resolution path.Votes: 0GitHub stars: 7
- Release ManagementShip releases on a predictable rhythm with versioned changes, tested artifacts, and notes users can act on. Use when releases are ad hoc or users cannot tell what changed.Votes: 0GitHub stars: 7
- Semantic VersioningCommunicate compatibility through version numbers so consumers know what upgrading costs. Use when releasing a library, deciding whether a change is breaking, or setting a dependency range.Votes: 0GitHub stars: 7