All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- Pythonic IdiomsApply Python idioms where they cut bookkeeping and clarify intent, and refuse them where the clever form hides control flow. Use when writing loops, resource handling, or unpacking and deciding how idiomatic to make it.Votes: 0GitHub stars: 7
- Collaborative Editing ModelsChoose between operational transformation, CRDTs, and locking for multi-user editing, and understand what each costs. Use when more than one person can edit the same document at the same time.Votes: 0GitHub stars: 7
- Comments And AnnotationsAttach comments to content that keeps changing, so anchors survive edits and threads stay resolvable. Use when adding review, feedback, or discussion to a document or design.Votes: 0GitHub stars: 7
- Conflict Resolution UxPresent merge conflicts to users so they can resolve them confidently, rather than resolving silently and losing work. Use when concurrent edits cannot be merged automatically.Votes: 0GitHub stars: 7
- Live Cursors And SelectionRender other people's cursors and selections so they inform rather than distract, and stay correct as content changes. Use when showing where collaborators are working in a shared document.Votes: 0GitHub stars: 7
- Offline SyncLet clients work disconnected and reconcile changes on reconnect without losing edits or resurrecting deletions. Use when building an application that must work on an unreliable network.Votes: 0GitHub stars: 7
- Optimistic Ui UpdatesApply changes locally before the server confirms, then reconcile or roll back honestly when it does not. Use when latency makes a correct-but-slow interface feel broken.Votes: 0GitHub stars: 7
- Presence And AwarenessShow who is here, where they are, and what they are doing, at a cost that scales and without leaking more than intended. Use when adding cursors, avatars, or typing indicators to a shared surface.Votes: 0GitHub stars: 7
- Realtime Data SyncKeep client state current with server changes using subscriptions, deltas, and resync, without drift or memory growth. Use when a UI must reflect data that other users or systems are changing.Votes: 0GitHub stars: 7
- Realtime PermissionsEnforce and revoke access on live connections so a permission change takes effect immediately rather than at the next page load. Use when shared documents have varying access levels.Votes: 0GitHub stars: 7
- Realtime ScalingScale collaborative sessions across instances with room routing, shared state, and controlled fan-out. Use when one server can no longer hold all active sessions.Votes: 0GitHub stars: 7
- Realtime TestingTest collaborative features against concurrency, reconnection, and ordering rather than only the single-user path. Use when a realtime feature works in development and breaks with real users.Votes: 0GitHub stars: 7
- Version History UxKeep 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.Votes: 0GitHub stars: 7
- Capacity ForecastingPredict 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 you.Votes: 0GitHub stars: 7
- Chaos EngineeringDeliberately inject failures to verify that resilience mechanisms work before a real incident tests them. Use when a system has failover, retries, or redundancy that has never actually been exercised.Votes: 0GitHub stars: 7
- Disaster Recovery TestingVerify that backups restore and failover works by practising it, rather than trusting that the procedure would work. Use when recovery has never been rehearsed end to end.Votes: 0GitHub stars: 7
- Failure Mode AnalysisEnumerate how a system can fail and what each failure does, before building the mitigations. Use when designing a critical system or reviewing one that has surprised you.Votes: 0GitHub stars: 7
- Graceful DegradationDesign systems that lose functionality progressively rather than failing entirely when a dependency is unavailable. Use when one component's failure currently takes down the whole product.Votes: 0GitHub stars: 7
- Incident Severity LevelsClassify incidents consistently so the response, communication, and escalation match the impact. Use when incident response is either overwhelming or too slow.Votes: 0GitHub stars: 7
- Load SheddingReject excess work deliberately under overload so the system serves some requests well instead of failing all of them. Use when traffic spikes cause complete collapse rather than partial service.Votes: 0GitHub stars: 7
- On Call HealthRun an on-call rotation that is sustainable, with alert hygiene, fair distribution, and follow-through on what caused the pages. Use when on-call is dreaded or people are leaving because of it.Votes: 0GitHub stars: 7
- Redundancy DesignAdd redundancy where it removes a single point of failure, understanding what each level protects against and what it costs. Use when designing for availability targets.Votes: 0GitHub stars: 7
- Reliability TradeoffsDecide how much reliability to buy, given that each additional nine costs disproportionately more than the last. Use when reliability investment is being decided without reference to its cost.Votes: 0GitHub stars: 7
- Service Level ObjectivesDefine measurable reliability targets from the user's perspective and use the error budget to decide between shipping and stabilising. Use when reliability is debated without numbers.Votes: 0GitHub stars: 7
- Toil ReductionIdentify repetitive manual operational work and eliminate it, so capacity goes to improvement rather than maintenance. Use when an on-call rotation is consumed by routine intervention.Votes: 0GitHub stars: 7
- Autonomous ResearchBuild and run an autonomous research agent that plans, searches, verifies, and synthesizes reliably, with the safeguards a naive research loop lacks. Use when an AI agent must research a question end to end without a human checking every step.Votes: 0GitHub stars: 7
- Decision JournalsRecord decisions with their context and predictions to enable honest calibration and defeat hindsight bias. Use when making consequential decisions you want to learn from later.Votes: 0GitHub stars: 7
- Deep ResearchRun a thorough multi-source research investigation end to end: plan, search broadly, verify, and synthesize a cited answer. Use when a question needs deep, autonomous research across many sources, not a quick lookup.Votes: 0GitHub stars: 7
- Estimation TechniquesEstimate unknown quantities with Fermi decomposition, reference classes, and honest error bars. Use when you need a number for a decision and no exact figure exists.Votes: 0GitHub stars: 7
- Experiment Design BasicsDesign experiments with controls, randomization, confound awareness, and pre-registered analysis. Use when testing a hypothesis empirically and needing the result to actually mean something.Votes: 0GitHub stars: 7
- Fact CheckingVerify claims before stating them: trace to the source, corroborate independently, and separate fact from inference. Use when accuracy matters, especially before an agent asserts facts, numbers, or quotes.Votes: 0GitHub stars: 7
- First Principles ThinkingReason from fundamental truths by excavating assumptions and rebuilding from constraints, knowing when analogy is faster. Use when stuck in a solution space defined by convention or challenging an inherited assumption.Votes: 0GitHub stars: 7
- Hypothesis Driven WorkFrame work as falsifiable hypotheses, test the cheapest first, and update on evidence rather than defending the plan. Use when facing uncertainty and tempted to build the whole thing before learning anything.Votes: 0GitHub stars: 7
- Literature ReviewSurvey prior work systematically through search strategy, citation chasing, quality assessment, and synthesis. Use when entering a new domain or grounding a decision in what is already known.Votes: 0GitHub stars: 7
- Reading PapersRead research papers efficiently in passes, separating claims from evidence and assessing reproducibility. Use when extracting value from academic papers without reading every one cover to cover.Votes: 0GitHub stars: 7
- Research PlanningScope a research question, decide what evidence would answer it, and plan the search before diving in. Use when starting any research task, so effort goes to the questions that matter instead of wandering.Votes: 0GitHub stars: 7
- Research SynthesisTurn multiple sources into a defensible, source-attributed answer that separates fact from inference. Use when researching a question across documents, articles, or search results.Votes: 0GitHub stars: 7
- Source EvaluationJudge whether a source is credible and relevant: authority, evidence, bias, and recency. Use when deciding whether to trust and cite a source, in any research.Votes: 0GitHub stars: 7
- Tradeoff AnalysisCompare options with explicit weighted criteria, sensitivity checks, and reversibility awareness. Use when facing a consequential choice between alternatives with no obvious winner.Votes: 0GitHub stars: 7
- Web ResearchSearch the web effectively: query construction, iterating on results, and going to primary sources. Use when researching a topic online, especially for an agent gathering current or factual information.Votes: 0GitHub stars: 7
- Automation GuardrailsPut confirmation gates, blast-radius limits, audit trails, and kill switches around automation that can destroy things. Use when building scripts or bots with destructive power.Votes: 0GitHub stars: 7
- Bash RobustnessWrite bash that fails loudly, quotes correctly, cleans up after itself, and passes shellcheck. Use when writing shell scripts that automation or other people will depend on.Votes: 0GitHub stars: 7
- Cli Ux DesignDesign command-line interfaces with predictable flags, honest exit codes, machine-readable modes, and helpful failure text. Use when building CLI tools people other than the author will run.Votes: 0GitHub stars: 7
- Environment ConfigManage script and tool configuration through env vars, dotenv files, and layered precedence without leaking secrets. Use when wiring configuration for CLIs, scripts, and local development.Votes: 0GitHub stars: 7
- Makefile DesignWrite Makefiles with honest dependencies, phony discipline, and self-documenting help, and know when make is the wrong tool. Use when standardizing project task-running or fixing rebuild bugs.Votes: 0GitHub stars: 7
- Powershell EssentialsWrite PowerShell that leans on the object pipeline, handles errors deliberately, and runs cross-platform where needed. Use when automating Windows or writing pwsh scripts for mixed fleets.Votes: 0GitHub stars: 7
- Scheduled JobsRun cron and timer jobs with overlap locks, jitter, missed-run policies, and monitoring for silent absence. Use when scheduling recurring automation or debugging jobs that overlap, pile up, or quietly stop.Votes: 0GitHub stars: 7
- Script IdempotencyWrite 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.Votes: 0GitHub stars: 7
- Shell PortabilityWrite shell that runs across POSIX sh, bash versions, and GNU/BSD userlands, or decide deliberately not to. Use when scripts must run on multiple platforms, containers, or CI images.Votes: 0GitHub stars: 7
- Text ProcessingChoose grep, sed, awk, or jq by job, prefer structured formats, and know when a one-liner should become a script. Use when slicing logs, transforming files, or wrangling command output.Votes: 0GitHub stars: 7