Claude Code Skills·Claude Skills·The open SKILL.md registry for Claude
ClaudSkills › Authors › Amey-Thakur › Page 4

Amey-Thakur

@Amey-Thakur on GitHub →

733 Claude Code skills authored by Amey-Thakur.

updated 2026-11-15 · showing 181–240 of 733 by quality score

Average Pro QualityScore: 64.1/100

For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.

Debug a live system without making the incident worse by staying read-only first, gating changes behind flags, and testing on mirrored traffic.
Decide how much reliability to buy, given that each additional nine costs disproportionately more than the last.
Profile native code with perf and flamegraphs, then read cache, syscall, and allocation behavior to find the real bottleneck.
Comprehensive guide to load balancing algorithms, health checks, and high-availability patterns.
Write onboarding docs that get a new contributor to a verified working setup and a first contribution fast.
Read a diff for security by tracing attacker-controlled input to dangerous operations and checking every trust boundary it crosses.
Detect input, prediction, and performance drift with reference windows and act through retrain or rollback triggers.
Lay out VPCs, subnets, private connectivity, and DNS so services reach each other privately and the internet only on purpose.
Build self-serve documentation that answers questions before they become tickets, organised by what people search for. Use when the same questions arrive repeatedly.
Talk about competitors accurately and fairly in a way that helps buyers decide, without claims you cannot support.
Group and aggregate correctly, understanding what GROUP BY collapses, how HAVING differs from WHERE, and how nulls and empty groups behave.
Triage lint rules so bug-catchers are errors, style is left to the formatter, and every suppression carries a reason.
Operate as a growth engineer who moves a funnel metric through instrumented, fast experiments and refuses to win with dark patterns.
Design sign-in so credentials are hashed with a slow algorithm, guessing is rate limited, and sessions rotate on login to defeat fixation.
Organize writing so the reader is carried from point to point without friction: logical order, transitions, and signposting.
Speed up a CPU-bound hot path by fixing its algorithm and memory access first, then applying micro-optimization only where the profiler still points.
Paginate large result sets so page cost stays constant by using keyset (cursor) pagination instead of OFFSET, with a stable, encoded cursor.
Issue, install, renew, and debug TLS certificates so connections stay encrypted and trusted without surprise expiry.
Choose the level of abstraction a platform exposes so it hides complexity without hiding what teams need to control.
Choose between operational transformation, CRDTs, and locking for multi-user editing, and understand what each costs.
Determine, apply, and record sales tax or VAT correctly by jurisdiction, product type, and customer status.
Decide whether to refactor code in place or rewrite it from scratch using risk math, not frustration. Use when a component feels beyond repair and someone proposes starting over.
Manage the timing of money in and out so the business can pay what it owes when it is due. Use when growing fast, when payment terms are long, or whenever runway is under a year.
Format code on the current branch using Biome. Use when asked to format, lint, or clean up code before committing or creating a PR.
Explain something to someone with no background, without condescension and without jargon that quietly requires prior knowledge.
Assign a role to shape expertise, register, and priorities, without pretending it grants knowledge the model lacks.
Isolate render failures behind boundaries with useful fallbacks, retry, and reporting so one broken component does not blank the app.
Manage specificity with layers, :where, and low-specificity selectors so overrides stay predictable. Use when styles fight each other, !important spreads, or you are setting…
Place assertions where invariants are established or must hold: constructors, public boundaries, and loop bodies.
Decide what an AI system forgets and when, through expiry, decay, and explicit deletion, so memory stays current and lawful.
Build and ship a small site that loads fast, reads well, and can be updated, choosing the simplest stack that fits.
Lay out the network for distributed training so collectives run on the fastest link that spans them, using NVLink, InfiniBand, and topology-aware placement.
Write scripts whose reruns are always safe through check-then-act steps, atomic writes, and dry-run modes. Use when automation may run twice, die halfway, or need a safe retry.
Reconstruct what happened from the artifacts a dead incident left behind: logs, metrics, dumps, and a timeline, when there is no live system left to poke.
Turn on and migrate to TypeScript's strict flags incrementally so the compiler catches real bugs. Use when configuring TypeScript strictness or tightening a loose codebase without…
Understand unfamiliar code quickly by tracing real execution paths rather than reading files in order.
Prepare and conduct a negotiation around interests and alternatives rather than positions, so agreements are better and hold.
Match provider settlements against your own records so every charge, fee, refund, and payout is accounted for.
Read a stack trace to find the cause frame instead of stopping at the symptom on top. Use when an exception, panic, or error dump lands and you need to locate the line that is…
Help users design effective organizational structures. Use when someone is thinking about team structure, deciding between functional vs.
Apply complexity analysis where input size actually makes it decide performance, and ignore it where constant factors dominate.
Keep client state current with server changes using subscriptions, deltas, and resync, without drift or memory growth.
Cut startup latency by deferring heavy imports, precompiling ahead of time, and pruning the dependency tree that loads before first useful work.
Run repeatable delivery reliably by finding the constraint, reducing variability, and measuring flow rather than utilisation.
Let clients work disconnected and reconcile changes on reconnect without losing edits or resurrecting deletions.
Judge whether a sample represents the population and spot the selection, survivorship, and response biases that invalidate conclusions.
Work with the borrow checker through ownership-first design instead of fighting it with clones and unsafe.
Run competitive analysis as agents that tear down assigned competitors on one template, enforce sourcing rules, and synthesize implications for your product.
Pick an environment manager, pin dependencies with a lockfile, and produce reproducible installs that never touch system Python.
Convene several reviewer agents with fixed distinct lenses, correctness, security, cost, and simplicity, then synthesize their verdicts into one.
Capturing and streaming database changes in real-time using Debezium, Kafka, and event-driven patterns for data synchronization.
Scan commit history and CI for leaked credentials and rotate on every hit, because a pushed secret is already compromised.
Decide where in a prompt to put documents, history, and instructions, given that models attend unevenly across a long context.
Build a custom-property token system with primitive and semantic tiers that supports runtime theme switching.
Make payment operations safe to retry so a network timeout never charges a customer twice. Use when calling a payment API, processing webhooks, or building any money-moving…
Choose between flexbox and grid by content shape and build layouts that survive real content. Use when structuring a page or component layout, or fixing overflow and alignment…
Build a mobile app where the local database is the source of truth, the UI reads and writes it directly, and a background sync engine reconciles with the server.
Script repository operations reliably, respecting rate limits, pagination, and permissions. Use when managing repositories at scale or building tooling around the platform.
Decide between managed services and self-hosting with honest TCO, lock-in assessment, and exit paths.
Judge a canary release against a concurrent baseline using pre-set metric gates, automatic rollback, and statistically honest windows.
Search all 733 skills by Amey-Thakur →