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

Amey-Thakur

@Amey-Thakur on GitHub →

733 Claude Code skills authored by Amey-Thakur.

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

Assign credit for conversions across touchpoints honestly, knowing what each model hides. Use when deciding where to spend and channels each claim the same conversions.
Buy traffic profitably by measuring against payback and lifetime value rather than cost per click. Use when considering paid channels or when spend is rising without profit.
Handle operations that touch several services where some succeed and some fail, without leaving inconsistent state. Use when a single user action calls multiple systems.
Run alert triage as agents that dedup the storm, rate severity by user impact, match a runbook, and draw a hard human-escalation line.
Answer questions that need several linked lookups by decomposing the query and retrieving in sequence.
Enforce authorization so access is denied by default and every request re-checks that the caller owns the specific resource, closing IDOR gaps.
Direct and supervise a coding agent (Claude Code, Cursor, Antigravity) so it ships correct, verified work.
Use CTEs to name intermediate steps so a complex query reads as a sequence rather than a nest, and know when they cost performance.
Write async C# that never blocks on tasks, flows cancellation everywhere, and uses ValueTask where it pays.
Implementing comprehensive validation rules across database, application, and pipeline layers to ensure data integrity.
Order material so each piece is learnable when it arrives, with prerequisites satisfied and difficulty increasing gradually.
Verify a provider against its consumers' recorded pacts in CI so a breaking API change fails before it ships.
Walk hierarchies and graphs with recursive CTEs, with a termination condition and cycle protection so the query ends.
Write PowerShell that leans on the object pipeline, handles errors deliberately, and runs cross-platform where needed.
Run a JavaScript/TypeScript monorepo with workspaces, task orchestration, and internal package versioning that scales.
Split a model that will not fit on one GPU across devices with tensor, pipeline, and expert parallelism, choosing each split by its communication cost.
Build disaster recovery around RTO/RPO tiers, verified backups, and drills that prove the numbers. Use when writing a DR plan or testing whether the existing one actually works.
Extract text and structure from PDFs, office documents, and scans reliably enough to search, index, or summarise.
Operate as an engineering manager who grows people, protects delivery health, hires deliberately, and shields the team from noise.
Draw system, sequence, and flow diagrams that clarify rather than decorate, at a consistent level of abstraction. Use when explaining a system to people who did not build it.
Operate as a DevOps engineer who owns the delivery pipeline, keeps environments identical, and makes every deploy reversible.
Persist facts about a user across sessions with provenance, correction, and expiry, so an assistant improves rather than accumulating stale assumptions.
Choose an optimiser and its hyperparameters based on the problem rather than habit, and know what each actually does.
Decide where a web app keeps tokens and state by reasoning about the XSS blast radius of each store, not by convenience.
Run external programs without ever building a shell string from untrusted input, using argument arrays that bypass the shell entirely.
Write formulas that stay correct when rows are added and readable when someone else opens the file. Use when building any calculation in a spreadsheet.
Operate as a CTO-level advisor who turns business goals into build-or-buy calls, org design, technology bets, and a named risk posture.
Read research papers efficiently in passes, separating claims from evidence and assessing reproducibility.
Choose threads, processes, or asyncio from workload shape, and use concurrent.futures without deadlocks.
Learn something substantial without a course, by defining the goal, finding the right resources, and building feedback into the process.
Pin every fixed bug with a test that fails before the fix and passes after, kept beside the code it guards.
Handle angry, distressed, or unreasonable customers without escalating the conflict or capitulating on things you cannot give.
Write SQL other people can review, modify, and trust, with clear structure, meaningful aliases, and stated assumptions.
Define who decides what in a project, how that changes, and how disputes end, before a disagreement forces the question.
Run a deprecation from usage telemetry through a hard sunset date, with migration tooling and staged comms, so a system retires without stranding its callers.
Split data before looking at it, respect time and groups, and quarantine the test set so scores mean something.
Write tutorials that take a learner from zero to a working result through tested steps with checkpoints and recovery.
Treat any serialized bytes from outside the program as hostile, parsing them through schema-validated formats instead of native object reconstructors.
Prevent cross-site scripting by encoding output for its exact sink, keeping template autoescaping on, and backing it with a strict Content Security Policy.
Store facts as entities and relationships when questions depend on connections rather than similarity.
Guard a multi-agent team against the structural failures single agents never hit: context lost across handoffs, false agreement, and runaway cost.
Prevent server-side request forgery by constraining where a user-influenced URL can make the server connect.
Run a war room for a live incident with defined roles, a steady cadence, a decision log, and explicit stand-down criteria.
Choose media formats and codecs by compatibility, quality, and licensing, with fallbacks for what the client cannot play. Use when deciding what to store and deliver.
Keep Spring Boot apps explicit with constructor injection, typed configuration, test slices, and restrained magic.
Layer input filtering, output validation, injection defense, and human escalation around LLM features.
Use agents to triage contracts and policies, extract obligations, flag unusual terms, and prepare a lawyer's review rather than replace it.
Publish an npm package that installs and imports cleanly: correct exports map, dual formats, types, and semver.
Send 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.
Decompose firmware into RTOS tasks with deadline-derived priorities, queue-based communication, and priority-inversion defenses.
Apply optimistic updates with correct rollback, conflict handling, and pending cues so mutations feel instant without lying.
Build landing pages with a clear message hierarchy, credible proof, and one decisive call to action, tested where it matters.
Verify that abstractions actually compile away by inspecting generated code and measuring, and know the costs that remain.
Initialise parameters so signal and gradients propagate at usable scale from the first step. Use when a deep network fails to train from the start or diverges immediately.
Match words to their variants and equivalents without collapsing distinctions that matter. Use when searches miss obvious results, or when unrelated results appear because two…
Build API clients with retries, timeouts, pagination, and error surfacing baked in, and test them properly. Use when writing a client for an external or internal API.
Flatten nested conditionals into early returns that handle edge cases up front and keep the main path unindented. Use when logic marches rightward into deep nesting.
Move between API versions or providers without downtime, using parallel running and staged cutover. Use when a provider deprecates a version or you are replacing a service.
Give a coding agent the right files and background at the start of a task, so it works from the real system rather than from assumption.
Give agents context in stages, escalating to more capable models or fuller context only when the cheap path proves insufficient.
Search all 733 skills by Amey-Thakur →