All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- Supply Chain DefenseHarden the build pipeline by pinning what runs, generating provenance, and signing artifacts so tampering shows. Use when securing a CI/CD workflow, setting up artifact signing, or reviewing how releases are built and shipped.Votes: 0GitHub stars: 7
- Threat ModelingMap assets, entry points, and STRIDE threats before writing code so defenses land in the design instead of a later patch. Use when starting a feature that handles auth, money, personal data, or external input.Votes: 0GitHub stars: 7
- Tls ConfigurationConfigure transport layer security with modern protocol versions, automated certificate renewal, and strict transport enforcement. Use when standing up HTTPS on a server, terminating TLS at a proxy, or hardening an endpoint that already serves traffic.Votes: 0GitHub stars: 7
- Vulnerability TriageScore incoming vulnerability reports the same way every time, tie each score to a fix deadline, and run disclosure on a predictable clock. Use when a vulnerability report arrives or when standing up a process to handle them.Votes: 0GitHub stars: 7
- Xss DefensePrevent cross-site scripting by encoding output for its exact sink, keeping template autoescaping on, and backing it with a strict Content Security Policy. Use when rendering user-controlled data into HTML, attributes, JavaScript, or URLs.Votes: 0GitHub stars: 7
- Zero Trust BasicsApply zero trust by authenticating and authorizing every request on its own merits and issuing only short-lived, narrowly scoped credentials. Use when designing service-to-service access, internal tooling, or any system that still trusts requests because of where they came from.Votes: 0GitHub stars: 7
- Conditional FormattingUse formatting rules to surface exceptions and patterns automatically, without turning the sheet into a colour chart. Use when readers need to spot outliers or status at a glance.Votes: 0GitHub stars: 7
- Data Validation RulesConstrain what can be entered into a spreadsheet so errors are prevented at input rather than found in analysis. Use when a spreadsheet is filled in by people.Votes: 0GitHub stars: 7
- Excel FormulasWrite formulas that stay correct when rows are added and readable when someone else opens the file. Use when building any calculation in a spreadsheet.Votes: 0GitHub stars: 7
- Financial FunctionsUse present value, rate, and payment functions correctly, with consistent periods and sign conventions. Use when modelling loans, investments, or discounted cash flows.Votes: 0GitHub stars: 7
- Lookup FunctionsJoin data between sheets reliably using modern lookup functions, handling missing matches and duplicates explicitly. Use when combining data from more than one table.Votes: 0GitHub stars: 7
- Pivot TablesSummarise and cross-tabulate large tables quickly with pivots, keeping the source data clean and the refresh reliable. Use when aggregating data by category, period, or dimension.Votes: 0GitHub stars: 7
- Power QueryBuild repeatable data transformations that refresh on demand, replacing manual cleaning steps with a recorded pipeline. Use when the same import and cleaning happens more than once.Votes: 0GitHub stars: 7
- Spreadsheet AutomationAutomate repetitive spreadsheet work with scripts, knowing when the task has outgrown a spreadsheet entirely. Use when the same manual steps are repeated on a schedule.Votes: 0GitHub stars: 7
- Spreadsheet ChartsBuild charts that make the point clearly, choosing the type by the question and removing everything that does not carry meaning. Use when presenting spreadsheet data visually.Votes: 0GitHub stars: 7
- Spreadsheet CollaborationShare workbooks so several people can work without overwriting each other or creating competing versions. Use when more than one person edits the same spreadsheet.Votes: 0GitHub stars: 7
- Spreadsheet Data CleaningTurn messy imported data into a clean flat table, fixing types, whitespace, duplicates, and inconsistent categories. Use before any analysis on data that came from elsewhere.Votes: 0GitHub stars: 7
- Spreadsheet PerformanceDiagnose and fix slow spreadsheets by reducing volatile formulas, whole-column references, and unnecessary recalculation. Use when a workbook takes seconds to respond to an edit.Votes: 0GitHub stars: 7
- Common Table ExpressionsUse CTEs to name intermediate steps so a complex query reads as a sequence rather than a nest, and know when they cost performance. Use when a query has grown into nested subqueries nobody can follow.Votes: 0GitHub stars: 7
- Deduplication QueriesFind and remove duplicate rows deterministically, keeping the record you meant to keep. Use when a table has accumulated duplicates or an import needs a clean unique set.Votes: 0GitHub stars: 7
- Null SemanticsReason about SQL nulls in comparisons, aggregates, joins, and uniqueness so absent values stop producing wrong or missing rows. Use when a query silently drops rows or a NOT IN returns nothing.Votes: 0GitHub stars: 7
- Pivot And UnpivotReshape rows into columns and back, and know when the reshape belongs in SQL rather than in the reporting layer. Use when a report needs periods or categories as columns, or a wide table needs normalising.Votes: 0GitHub stars: 7
- Query ReadabilityWrite SQL other people can review, modify, and trust, with clear structure, meaningful aliases, and stated assumptions. Use when a query will be read again by anyone, including you.Votes: 0GitHub stars: 7
- Recursive QueriesWalk hierarchies and graphs with recursive CTEs, with a termination condition and cycle protection so the query ends. Use when querying trees such as org charts, categories, threads, or dependency graphs.Votes: 0GitHub stars: 7
- Sql AggregationGroup and aggregate correctly, understanding what GROUP BY collapses, how HAVING differs from WHERE, and how nulls and empty groups behave. Use when producing counts, sums, and per-group summaries.Votes: 0GitHub stars: 7
- Sql Date TimeStore, compare, and bucket timestamps with explicit time zones so reports do not drift by a day and ranges do not miss rows. Use when filtering by date, grouping by period, or storing an event time.Votes: 0GitHub stars: 7
- Sql JoinsChoose and write the right join so rows are neither lost nor multiplied, and know why a result set grew. Use when combining tables and the row count or the null columns look wrong.Votes: 0GitHub stars: 7
- Sql Set OperationsCombine result sets with UNION, INTERSECT, and EXCEPT, and know when a join or an exists clause is the better tool. Use when merging or comparing two query results rather than two tables.Votes: 0GitHub stars: 7
- Upsert PatternsInsert or update in one statement without races or lost updates, using the engine's conflict handling rather than check-then-write. Use when writing records that may or may not already exist.Votes: 0GitHub stars: 7
- Window FunctionsUse window functions to rank, compare to neighbours, and compute running totals without collapsing rows or self-joining. Use when you need per-row context such as a rank, a previous value, or a running sum.Votes: 0GitHub stars: 7
- C Memory SafetyWrite C with explicit ownership conventions, bounds discipline, and sanitizers wired into every test run. Use when writing or reviewing C code, or hunting memory corruption.Votes: 0GitHub stars: 7
- Cpp RaiiManage every resource through RAII with the rule of zero, correct smart-pointer selection, and move semantics. Use when writing modern C++ or reviewing code with manual new/delete or leaky error paths.Votes: 0GitHub stars: 7
- Ffi BoundariesDesign foreign-function boundaries with explicit ownership, error translation, and contained panics/exceptions. Use when binding between Rust/Go/Python and C/C++ libraries or exposing your library over a C ABI.Votes: 0GitHub stars: 7
- Go ConcurrencyStructure goroutines with owned lifecycles, context propagation, and channel patterns that cannot leak or race. Use when writing concurrent Go or debugging goroutine leaks and data races.Votes: 0GitHub stars: 7
- Go Project LayoutOrganize Go packages by domain with internal boundaries, consumer-side interfaces, and structure that grows on demand. Use when starting a Go project or refactoring one into clearer packages.Votes: 0GitHub stars: 7
- Rust Error HandlingDesign Rust error types with the thiserror/anyhow split, context chains, and a deliberate panic policy. Use when structuring errors in Rust libraries and applications.Votes: 0GitHub stars: 7
- Rust OwnershipWork with the borrow checker through ownership-first design instead of fighting it with clones and unsafe. Use when writing Rust or resolving borrow-checker errors that feel unwinnable.Votes: 0GitHub stars: 7
- Systems ProfilingProfile native code with perf and flamegraphs, then read cache, syscall, and allocation behavior to find the real bottleneck. Use when optimizing systems software or explaining why fast code is slow.Votes: 0GitHub stars: 7
- Unsafe Code ReviewAudit unsafe blocks by verifying documented invariants, minimizing surface, and testing under sanitizers and Miri. Use when reviewing unsafe Rust, C/C++ interop shims, or any code that bypasses language safety.Votes: 0GitHub stars: 7
- Zero Cost AbstractionsVerify that abstractions actually compile away by inspecting generated code and measuring, and know the costs that remain. Use when writing performance-critical Rust/C++ or judging whether an abstraction is free.Votes: 0GitHub stars: 7
- Api TestingTest an HTTP API at its boundary so status codes, response schemas, error bodies, and auth paths all hold under real requests. Use when adding or reviewing tests for a service that other clients call over HTTP.Votes: 0GitHub stars: 7
- Approval TestingAssert hard-to-specify output by reviewing a human-readable snapshot once, approving it, then failing on any later diff. Use when the correct result is easy to recognize but tedious to write as explicit assertions.Votes: 0GitHub stars: 7
- Assertion LibrariesPick an assertion style and write checks that fail with a message you can diagnose without a debugger. Use when test failures read as "expected true, got false" and you cannot tell what actually broke.Votes: 0GitHub stars: 7
- Bdd ScenariosWrite given-when-then scenarios in domain language so stakeholders can read and confirm the behavior each test protects. Use when drafting acceptance criteria or Gherkin features for a user-facing rule.Votes: 0GitHub stars: 7
- Browser MatrixChoose which browsers, versions, and devices to test from real usage data instead of habit or a vendor's full grid. Use when cross-browser testing time or budget is finite and the matrix needs to reflect who actually visits.Votes: 0GitHub stars: 7
- Chaos TestingInject failures like killed instances and network latency on purpose to verify a system degrades gracefully instead of collapsing. Use when validating the resilience of a distributed system that claims to tolerate faults.Votes: 0GitHub stars: 7
- Concurrency TestingForce the thread interleavings that expose races by using barriers, stress loops, and linearizability checks instead of hoping the scheduler hits them. Use when testing locks, shared state, or lock-free code where a bug appears once in a thousand runs.Votes: 0GitHub stars: 7
- Contract TestingVerify a service boundary with a consumer-driven contract that records the payload the caller actually reads and that both sides check in CI. Use when two services deploy independently and an unannounced response change would silently break the consumer.Votes: 0GitHub stars: 7
- Coverage StrategyRead coverage as a map of untested risk that steers the next test, rather than enforcing a percentage target. Use when deciding what to test next or when a team is tempted to mandate a coverage number.Votes: 0GitHub stars: 7
- Database TestingExercise data-access code, migrations, and transactions against the real database engine so constraints, rollbacks, and schema changes are proven rather than assumed. Use when tests for queries or migrations run on SQLite while production runs Postgres.Votes: 0GitHub stars: 7