Claude Skills by thedixitjain

Access DeFi data from DexPaprika: token prices, liquidity pools, OHLCV, transactions across 34+ blockchains and 30M+ pools. Free, no API key needed. Install MCP: add https://mcp.dexpaprika.com/sse as SSE server, or install plugin: /plugin marketplace add coinpaprika/claude-marketplace

Automate Dictionary API tasks via Rube MCP (Composio). Always search tools first for current schemas.

Specialized skill for building production-ready Discord bots. Covers Discord.js (JavaScript) and Pycord (Python), gateway intents, slash commands, interactive components, rate limiting, and sharding.

Model, migrate, refresh, and verify PostgreSQL materialized views in Django for expensive report or dashboard queries that can tolerate stale data. Use when ORM/index/query rewrites are not enough, the result is read often, freshness can be bounded, and a Django app needs unmanaged models, RunSQL migrations, refresh commands, or concurrent refresh.

Optimize Django ORM query loading by fixing N+1 queries, duplicate related-object queries, over-fetching, serializer/template query loops, and inappropriate select_related, prefetch_related, only, or defer usage. Use when a Django page, API, admin view, template, serializer, or queryset issues too many queries or loads more model data than needed.

DRF ile Django mimari desenleri, REST API tasarımı, ORM en iyi uygulamaları, caching, signal'ler, middleware ve production-grade Django uygulamaları.

Django架构模式，使用DRF设计REST API，ORM最佳实践，缓存，信号，中间件，以及生产级Django应用程序。

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

Use when adding, changing, testing, or debugging Django Q2 background tasks, scheduled jobs, qcluster workers, Redis broker configuration, or ORM broker fallback in Django projects.

Read and compare Django/PostgreSQL query execution plans using QuerySet.explain(), EXPLAIN, EXPLAIN ANALYZE, scan types, joins, estimates, actual timing, buffers, and row counts. Use when one SQL query dominates Django latency or when an index, ORM rewrite, pagination change, or materialized view needs proof from a query plan.

'Generate django view generator operations. Auto-activating skill for Backend Development. Triggers on: django view generator, django view generator Part of the Backend Development skill category. Use when working with django view generator functionality. Trigger with phrases like \"django view generator\", \"django generator\", \"django\". '

'Handle document data, signatures, and PII in Documenso integrations. Use when managing document lifecycle, handling signed PDFs, or implementing data retention policies. Trigger with phrases like \"documenso data\", \"signed document\", \"document retention\", \"documenso PII\", \"download signed pdf\". '

'Configure Documenso across multiple environments (dev, staging, production). Use when setting up environment-specific configurations, managing API keys, or implementing environment promotion workflows. Trigger with phrases like \"documenso environments\", \"documenso staging\", \"documenso dev setup\", \"multi-environment documenso\". '

'Implement Documenso rate limiting, backoff, and request throttling patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Documenso. Trigger with phrases like \"documenso rate limit\", \"documenso throttling\", \"documenso 429\", \"documenso retry\", \"documenso backoff\". '

'Implement Documenso webhook configuration and event handling. Use when setting up webhook endpoints, handling document events, or implementing real-time notifications for document signing. Trigger with phrases like \"documenso webhook\", \"documenso events\", \"document completed webhook\", \"signing notification\". '

Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.

Expert .NET backend architect specializing in C#, ASP.NET Core, Entity Framework, Dapper, and enterprise application patterns.

Master C#/.NET backend development patterns for building robust APIs, MCP servers, and enterprise applications. Covers async/await, dependency injection, Entity Framework Core, Dapper, configuration, caching, and testing with xUnit. Use when developing .NET backends, reviewing C# code, or designing API architectures.

Master C#/.NET patterns for building production-grade APIs, MCP servers, and enterprise backends with modern best practices (2024/2025).

Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.

Expert in Drizzle ORM for TypeScript — schema design, relational queries, migrations, and serverless database integration. Use when building type-safe database layers with Drizzle.

Use when assembling the data and code replication package for a The Economic Journal (EJ) manuscript to the RES / EJ Data Editor standard (DCAS-endorsed, Zenodo deposit, reproducibility check before final acceptance). Builds the package and README; it does not run the analysis itself.

Use when assembling the data, code, and verification materials for an Economic Policy (EP) manuscript so results are accessible and replicable to the journal's standard. Builds the verification-ready package; it does not invent evidence or citations.

Use when a revise-and-resubmit or referee reports arrive for an Econometrica manuscript and you must write the response letter and plan the revision. Structures the rebuttal and revision; it does not re-derive the theorems (use ecta-theory-model) or rebuild the package (use ecta-replication-package).

Use when assembling the code and data deposit for an Econometrica manuscript under the journal's Data and Code Availability Policy, including reproducible Monte Carlo and (for empirical work) data provenance. Builds and audits the replication package; it does not design the simulations (use ecta-robustness) or format exhibits (use ecta-tables-figures).

Use for the Monte Carlo and numerical-illustration component of an Econometric Theory (ET) paper — designing simulations that show finite-sample behavior tracks the asymptotics, plus any illustrative empirical example. Lighter than empirical journals; the spine stays the theory.

Use to handle reproducibility and the supplementary-material file for an Econometric Theory (ET) paper — ET has no mandatory data/code archive (theory journal); the relevant policy is the voluntary online Supplementary Material for already-reviewed proofs, derivations, and simulation evidence.

Use when designing or auditing The Econometrics Journal (EctJ) Monte Carlo simulations, empirical applications, estimator comparisons, robustness checks, computation, seeds, and applied-value evidence.

Use when preparing The Econometrics Journal replication files, README, software versions, data documentation, seeds, proprietary-data exemptions, and OUP Supporting Information package after conditional acceptance or before submission risk review.

Use when designing or auditing EDBT empirical evaluations for database-systems work, covering real workloads and datasets, fair and tuned baselines, honest measurement across realistic scales, reproducible harnesses, and the higher bar of the Experiments & Analysis paper where the measurement itself is the contribution.

Use when positioning an EDBT submission against the data-management literature across SIGMOD, VLDB/PVLDB, ICDE, EDBT, the co-located ICDT, and the database journals (VLDBJ, TODS, TKDE), writing delta-first contrast rather than a citation catalog, and handling the 12-month EDBT resubmission ban, preprints, and prior-version overlap.

Use when deciding what belongs in an EDBT paper body versus its artifact and appendices, covering the per-shape page budget with unlimited references, the rule that decision-critical evidence stays inside the reviewed pages, and how to split a database-systems paper between body and reproducible package.

Use when planning an EDBT project timeline across the multiple-cycle rolling model — choosing a submission cycle, backward-planning through the author-feedback phase and the in-cycle revise-and-resubmit window, and handling the cycle-to-conference roll — for a database-systems paper published open access on OpenProceedings.

Use when assembling the data and code deposit for a European Economic Review (EER) manuscript under Elsevier's mandatory replication policy. Builds a reproducible package and README; it does not run the analysis or write the paper.

Use when running the final pre-submission preflight for the European Economic Review (EER) via Editorial Manager — submission fee, single-anonymized review, Elsevier format and house-style rules, declarations, and the data/replication policy. Final checks; it does not draft content.

Generate D2 database diagrams from Entity Framework Core models. USE FOR: EF Core database diagram, Entity Framework Core ERD, DbContext diagram, C# entity relationship diagram, PostgreSQL schema visualization, generate .d2 file from EF Core entities, Fluent API mapping diagram, migrations-based database diagram, table relationships, owned types, many-to-many join tables, indexes and constraints. DO NOT USE FOR: runtime debugging, database migration execution, schema deployment, SQL performan...

\"Draft email replies for Gonto's Gmail accounts (m@gon.to, gonto@hypergrowthpartners.com).\\ \\ Handles intro acceptances, scheduling intent, thanks/ack, and positive short replies.\\ \\ Use when user asks to draft or reply to an email, or when Gmail webhook triggers\\ \\ arrive for auto-draft classification. Draft-only mode \\u2014 never sends automatically.\"

'Build event-driven APIs with webhooks, Server-Sent Events, and real-time notifications. Use when building event-driven API architectures. Trigger with phrases like \"add webhooks\", \"implement events\", or \"create event-driven API\". '

Validate encryption implementations and cryptographic practices. Use when reviewing data security measures. Trigger with 'check encryption', 'validate crypto', or 'review security keys'.

Audit a dbt project against the Entropy Data reference layout and add anything missing — Open Data Product Specification (ODPS), Open Data Contract Standard (ODCS), OpenLineage transport config, output-port model layout, and the GitHub Actions publish workflow. Trigger when the user asks to integrate a dbt project with Entropy Data, set up Entropy Data publishing, or check whether a dbt project follows the Entropy Data conventions.

List the teams configured in Entropy Data so the user can pick one as the owner (`team.name` in ODPS) of a data product. Useful when bootstrapping a new data product, integrating an existing dbt project, or just exploring who owns what. Trigger when the user asks \"what teams are there\", \"who can own this data product\", \"list teams in Entropy Data\", or when another skill needs to fill in `TEAM_NAME` and the user does not already know it.

'Manage error handler middleware operations. Auto-activating skill for Backend Development. Triggers on: error handler middleware, error handler middleware Part of the Backend Development skill category. Use when working with error handler middleware functionality. Trigger with phrases like \"error handler middleware\", \"error middleware\", \"error\". '

'Manage etag handler operations. Auto-activating skill for API Development. Triggers on: etag handler, etag handler Part of the API Development skill category. Use when working with etag handler functionality. Trigger with phrases like \"etag handler\", \"etag handler\", \"etag\". '

Use when executing or defending the analysis for an Entrepreneurship Theory and Practice (ETP) manuscript — estimation, event-history, SEM, endogeneity, and qualitative coding rigor, with the new-venture inference problems front of mind.

Use when executing and reporting the analysis for a European Sociological Review (ESR) manuscript so it survives expert double-blind review — correct multilevel and longitudinal modeling, honest uncertainty, robustness, and small-macro-N inference on comparative survey or register data. Guides analysis norms; it does not fabricate results.

Use when running the final pre-submission preflight for the European Sociological Review (ESR) via ScholarOne Manuscripts — anonymous-manuscript preparation, word/abstract caps, OUP author-date style, the Data Availability Statement, and replication-package readiness. Final checks; it does not draft content.

Use when preparing the Data Availability Statement and the replication package for a European Sociological Review (ESR) manuscript. ESR requires a Data Availability Statement for every manuscript and (for submissions from 1 January 2025) a replication package for statistical/computational work upon conditional acceptance; qualitative work is exempt. Prepares documentation; it does not over-state or under-state the policy.

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

'Optimize Evernote integration costs and resource usage. Use when managing API quotas, reducing storage usage, or optimizing upload limits. Trigger with phrases like \"evernote cost\", \"evernote quota\", \"evernote limits\", \"evernote upload\". '