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

Amey-Thakur

@Amey-Thakur on GitHub →

733 Claude Code skills authored by Amey-Thakur.

updated 2026-11-15 · showing 121–180 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.

Predict when current capacity will be exhausted and plan the increase before it becomes an incident. Use when growth is steady enough to plan for or when scaling events surprise…
Use present value, rate, and payment functions correctly, with consistent periods and sign conventions. Use when modelling loans, investments, or discounted cash flows.
Defer expensive work until the moment it is actually needed, so startup stays fast and unused paths cost nothing.
Understand what the kernel does for your process, so system-level behaviour such as scheduling, file descriptors, and signals stops being mysterious.
Improve RAG answer quality by reranking retrieved candidates so the most relevant chunks reach the model.
Decide what you are, who for, and against what alternative, then say it in words customers use. Use when nobody can explain the product in one sentence or the same product is…
Price SaaS around a value metric with tier design, seat-vs-usage decisions, and low-risk price testing. Use when setting or revisiting software pricing and packaging.
Expose data through MCP resources with stable URIs, useful listings, and sizes that fit a context window. Use when an agent needs to read data rather than perform an action.
Operate as an ML engineer who takes a research model to reliable production behind eval gates and keeps it healthy across its lifecycle.
Share workbooks so several people can work without overwriting each other or creating competing versions. Use when more than one person edits the same spreadsheet.
Store time-series data with retention downsampling, compression, out-of-order handling, and the right store choice.
Reason about SQL nulls in comparisons, aggregates, joins, and uniqueness so absent values stop producing wrong or missing rows.
Run one-on-ones the report owns, splitting career growth from status, with notes that compound. Use when establishing 1:1 practice as a manager or getting more from 1:1s as a…
Follow up on unanswered emails effectively: the right timing, adding value, and knowing when to stop.
Model warehouse tables with explicit grain, conformed dimensions, and deliberate SCD handling. Use when designing analytics schemas or fixing double-counted metrics and unjoinable…
Model NoSQL data from access patterns first, with single-table and denormalization discipline. Use when designing for a document or key-value store, or when a relational mindset…
Pick an assertion style and write checks that fail with a message you can diagnose without a debugger.
Choose embedding models and chunking by evaluating retrieval on your own corpus, not by leaderboard rank.
Manage agent sessions including initialization, handoffs, revival (seance), and persistent identity for Polecats and Crew agents.
Assess and control what third-party services do with personal data you send them, before and after integration. Use when adding a vendor, SDK, or API that will receive user data.
Operate as a product manager who picks the right problem, writes the spec, makes the tradeoff calls, and owns the launch outcome.
Batch many low-urgency events into one periodic summary that is worth opening, rather than sending each as it happens.
Scale collaborative sessions across instances with room routing, shared state, and controlled fan-out. Use when one server can no longer hold all active sessions.
Produce signed software bills of materials from real artifacts and consume them to answer "are we affected" fast.
Operate as a performance engineer who sets budgets, gates regressions in CI, and runs profiling as a service other teams rely on.
Diagnose layout, stacking, and overflow bugs by isolating the failing rule with devtools instead of guessing.
Keep git history atomic, bisectable, and readable with curated commits and disciplined force-push. Use when commits are messy, history is hard to navigate, or bisect and blame…
Quantize a trained model to INT8 or INT4 for inference, calibrate the ranges, and gate the release on a measured quality regression.
Tell correlation from causation and avoid the confounding, selection, and reverse-causation traps. Use when data shows a relationship and someone is about to claim one thing…
Halve the search space repeatedly across code, data, time, and configuration until a single change isolates the failure.
Narrow union types safely with guards, discriminated unions, and exhaustiveness checks. Use when working with values that could be several types, or when the compiler will not let…
Use server-initiated model calls and user prompts responsibly, so a server can ask for reasoning or input without seizing control.
Bootstrap a Node.js backend with ESM, typed config, graceful shutdown, and structured logging from the start.
Keep your service healthy when a dependency is slow or failing, through timeouts, retries, circuit breakers, and fallbacks. Use when an external call sits in a request path.
Reason about how model performance improves with parameters, data, and compute, to allocate a training budget sensibly.
Make a working local environment reachable in minutes from a clean machine, and keep it close to production.
Produce a short honest briefing across every desk on a fixed cadence, surfacing decisions needed rather than activity performed.
Turn an empty result set into a useful next step instead of a dead end, and treat the query as a signal worth acting on. Use when searches return nothing and users leave.
Make immutability the default so aliasing bugs turn into compile errors or no-ops instead of action at a distance.
Handle errors in JavaScript and TypeScript with proper Error subclasses, cause chains, and a policy for async and unhandled failures.
Decide rollback versus fix-forward, handle migrations safely, and rehearse rollbacks so they work under pressure.
Verify changes against real traffic without risking users, using canaries, shadow traffic, and feature gates with automatic rollback.
Know whether a message was accepted, delivered, opened, and acted on, and treat failures as events rather than statistics.
Idiomatic Rust error handling design for libraries and applications: thiserror vs anyhow boundary decisions, error hierarchy design, context chain propagation, HTTP handler error…
Reduce overfitting with weight decay, dropout, augmentation, and early stopping, choosing by why the model is overfitting.
Design the empty, loading, error, and edge states that most designs skip but users constantly hit. Use when designing any screen that can be empty, loading, or fail, which is…
Design foreign-function boundaries with explicit ownership, error translation, and contained panics/exceptions.
Design authentication whose credentials cannot be relayed to a look-alike site, using origin-bound passkeys and hardware keys over phishable codes.
Tie every claim in a generated answer to the retrieved passage that supports it, so users can verify and unsupported claims are visible.
Keep and present document history so users can see what changed, who changed it, and restore safely. Use when edits are shared or when accidental loss must be recoverable.
Run the daily operating rhythm with agents that sweep every system each morning, surface what needs a decision, and keep nothing waiting silently.
Cut LLM cost and latency with caching, model tiering, prompt diet, batching, and streaming UX. Use when the inference bill or response time needs engineering down.
Use Tailwind-style utilities with discipline, extracting components at the right threshold and keeping class lists readable.
Decide whether asyncio pays off, keep the event loop unblocked, and structure concurrency with TaskGroup and disciplined cancellation.
Place data across the GPU memory tiers so a kernel is limited by math rather than by repeated trips to HBM.
Run continuous compliance with agents that map controls to evidence, collect it on a schedule, and flag drift before an audit finds it.
Use window functions to rank, compare to neighbours, and compute running totals without collapsing rows or self-joining.
Direct an agent through a refactor in verifiable steps with tests as the safety net, rather than one large rewrite. Use when restructuring code with agent assistance.
Test localisation readiness with generated pseudo-translations that expand, accent, and bracket text, before any real translation exists.
Extract the lesson from a mistake by examining the reasoning that produced it, rather than only the outcome. Use after something goes wrong, personally or as a team.
Search all 733 skills by Amey-Thakur →