Claude Skills by thedixitjain

'Implement Hootsuite webhook signature validation and event handling. Use when setting up webhook endpoints, implementing signature verification, or handling Hootsuite event notifications securely. Trigger with phrases like \"hootsuite webhook\", \"hootsuite events\", \"hootsuite webhook signature\", \"handle hootsuite events\", \"hootsuite notifications\". '

Use when estimation and analysis are the bottleneck for a Human Resource Management (Wiley \"HRM\") manuscript — fitting HLM/SEM, testing mediation and cross-level moderation, defending aggregation, and qualitative coding rigor. Runs and validates the analysis; it does not design the study (hrm-methods).

Plan and bootstrap server-driven web applications with htmx. Use when choosing htmx versus an SPA framework, setting up htmx in a server-rendered app, designing the first CRUD workflow, explaining the htmx mental model, or deciding how much JavaScript a server-driven feature needs.

Use the htmx JavaScript API for imperative integration in server-rendered apps. Use when calling htmx.ajax, htmx.process, htmx.trigger, htmx.on, htmx.off, htmx.onLoad, htmx.find, htmx.findAll, htmx.closest, htmx.addClass, htmx.removeClass, htmx.toggleClass, htmx.takeClass, configuring htmx.config, logging htmx events, or integrating non-htmx JavaScript with swapped content.

Build and review realtime and near-realtime htmx features. Use when implementing polling, load polling, job status updates, WebSockets, Server-Sent Events, htmx ws or sse extensions, streaming server-rendered fragments, multi-client updates, reconnect behavior, or deciding between polling, SSE, and WebSockets.

Use when building an HTTP val — a web endpoint, API route, webhook receiver, or any val that responds to HTTP requests. Covers the handler signature, Hono usage, the endpoint URL, CORS behavior, redirects, and Val Town-specific limitations.

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

| Sync HubSpot CRM data to a data warehouse (BigQuery, Snowflake, or Postgres) for analytics and reporting. Covers initial backfill of millions of records under the 500K/day rate limit, incremental CDC polling via hs_lastmodifieddate, schema-drift detection with ALTER TABLE generation, association sync for contacts/deals/companies, and idempotent upsert patterns that prevent duplicate rows on retry. Use when building a HubSpot → warehouse pipeline, resyncing after a schema change, debugging d...

| Build and harden HubSpot v3 webhook handlers that survive production: HMAC-SHA256 signature verification, Redis SET NX deduplication, async batch processing with immediate 200 ACK, dead-letter queuing for permanent failures, and event-ordering guards for property-change streams. Use when implementing HubSpot webhooks for the first time, hardening an existing handler against retry storms or duplicate processing, debugging signature verification failures, or designing a reliable event pipelin...

Use this skill when the user wants to build tool/scripts or achieve a task where using data from the Hugging Face API would help. This is especially useful when chaining or combining API calls or the task will be repeated/automated. This Skill creates a reusable script to fetch, enrich or process data.

Your purpose is now is to create reusable command line scripts and utilities for using the Hugging Face API, allowing chaining, piping and intermediate processing where helpful. You can access the API directly, as well as use the hf command line tool.

Use this skill when the user wants to build tool/scripts or achieve a task where using data from the Hugging Face API would help. This is especially useful when chaining or combining API calls or the task will be repeated/automated. This Skill creates a reusable script to fetch, enrich...

Use when executing and reporting the analysis for a Human Relations (HR) manuscript — qualitative coding and data-to-theory construction, critical interpretation, or quantitative estimation and robustness. Makes the evidence-to-theory link transparent; it does not design the study (see humrel-methods).

Hunt for data exfiltration through network traffic analysis, detecting unusual data flows, DNS tunneling, cloud storage uploads, and encrypted channel abuse.

Detect data staging activity before exfiltration by monitoring for archive creation with 7-Zip/RAR, unusual temp folder access, large file consolidation, and staging directory patterns via EDR and process telemetry

Detect DCSync attacks by analyzing Windows Event ID 4662 for unauthorized DS-Replication-Get-Changes requests from non-domain-controller accounts.

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

Use when auditing an ICALP (EATCS) Track A or Track B submission for HotCRP readiness, covering the correct-track submission server, abstract registration before the full-paper deadline, the 15-page extended-abstract page budget with a clearly labelled appendix / full version, lightweight double-blind anonymity, the no-simultaneous-submission rule, and the single annual February AoE cutoff.

Use when responding to ICDT (International Conference on Database Theory) referees — principally the first-cycle Revise-and-resubmit round, where you return a corrected paper that closes each identified proof gap, plus any short author-comment phase, keeping the response anonymous and mapping every referee point to a concrete change in the revised PDF.

Use when preparing the final LIPIcs camera-ready for an accepted ICDT (International Conference on Database Theory) paper — the lipics-v2021 final document, mandatory ACM CCS concepts and keywords, author ORCIDs, de-anonymization, complete proofs and the full-version link, CC-BY licensing, and passing the Dagstuhl/DROPS production checks that mint the DOI.

Use when deciding what counts as evidence for an ICDT (International Conference on Database Theory) result — matching-bound complexity analysis as the primary evidence, worked examples and counterexamples that establish separations, and, only for papers with an algorithmic contribution, a proportional and honestly-scoped experimental evaluation that does not pretend to be the contribution.

Use when positioning an ICDT (International Conference on Database Theory) paper against the database-theory literature — covering the ICDT/PODS lineage, finite model theory and complexity, delta-first positioning against the nearest prior theorem, honest treatment of overlapping bounds, and keeping self-citations anonymous under the since-2024 rule.

Use when reasoning about how an ICDT (International Conference on Database Theory) submission is evaluated, covering the two-submission-cycle model, the first-cycle revision (Accept / Revise / Reject) decision, anonymous review since 2024, the cross-cycle resubmission restriction, proof-correctness scrutiny by a database-theory PC, and how ICDT's process differs from PODS and from the co-located EDBT systems track.

Use when auditing an ICDT (International Conference on Database Theory) regular-paper submission for Microsoft CMT readiness, covering the two-step abstract-then-paper deadline in the correct submission cycle, the lipics-v2021 15-page limit excluding references, the clearly-marked appendix read at the PC's discretion, anonymous submission since 2024, the complete-proofs / full-version expectation, and which submission problems are unfixable after the AoE cutoff.

Use when deciding how to split an ICDT (International Conference on Database Theory) paper between the 15-page lipics-v2021 body and the clearly-marked appendix that referees read at their discretion, given that online/external appendices are not allowed and every proof needed to certify the result must live inside the single submitted PDF.

Use when deciding whether a database-theory project belongs at ICDT (International Conference on Database Theory) or should be routed to PODS, the co-located EDBT systems track, a pure-TCS venue (LICS, ICALP, STACS), or a journal (ACM TODS, LMCS, TheoretiCS), and when distinguishing ICDT from its sibling database-theory flagship PODS by calendar, publisher, and community.

Use when deciding what goes into the 10-page body versus the replication package of an ICSE research-track submission, covering the no-unlimited-appendix page model, anonymized supplementary links and HotCRP uploads, package organization for reviewer navigation, and content-placement rules that protect the review.

Use when positioning an IEEE ICSME submission against the software-maintenance and evolution literature across ICSME, SANER, MSR, ICPC, SCAM, ICSE/FSE, and the SE journals (TSE, EMSE), writing delta-first contrast rather than a citation catalog, keeping self-citations double-anonymous, and handling replication overlap and prior-version eligibility.

'Optimize Ideogram costs through model selection, caching, and usage monitoring. Use when analyzing Ideogram billing, reducing API costs, or implementing budget alerts and usage tracking. Trigger with phrases like \"ideogram cost\", \"ideogram billing\", \"reduce ideogram costs\", \"ideogram pricing\", \"ideogram budget\", \"ideogram credits\". '

'Manage Ideogram generated image assets, metadata tracking, and lifecycle management. Use when implementing image persistence, tracking generation history, or building asset management for Ideogram outputs. Trigger with phrases like \"ideogram data\", \"ideogram images\", \"ideogram asset management\", \"ideogram metadata\", \"ideogram image storage\". '

'Implement team-based access control and credit management for Ideogram. Use when managing multiple teams with separate budgets, enforcing content policies, or implementing API key isolation for enterprise Ideogram usage. Trigger with phrases like \"ideogram RBAC\", \"ideogram enterprise\", \"ideogram teams\", \"ideogram permissions\", \"ideogram multi-tenant\". '

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

'Build event-driven workflows around Ideogram''s synchronous API. Use when implementing async generation queues, batch processing, callback patterns, or image processing pipelines. Trigger with phrases like \"ideogram webhook\", \"ideogram events\", \"ideogram async\", \"ideogram queue\", \"ideogram batch pipeline\". '

Use when assembling the data/code deposit and proof appendix for an International Economic Review (IER) manuscript under its AER-style data availability policy. Covers the deposit, README, data availability statement, and self-contained proofs; it does not write the analysis code.

Use when running and reporting the computational experiments — and assembling the reproducible code/data deposit — for an INFORMS Journal on Computing (IJOC) manuscript. Turns a designed protocol (see ijoc-methods) into defensible, reproducible results; it does not redesign the experiment.

Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.

Use when an IMF Economic Review (IMFER) manuscript's data and code must be packaged for reproducibility — including restricted IMF/central-bank data paths, cross-country source lineage, and a runnable environment. Builds the package; it does not produce the exhibits (imfer-tables-figures) or run the submission preflight (imfer-submission).

Implement API abuse detection using token bucket, sliding window, and adaptive rate limiting algorithms to prevent DDoS, brute force, and credential stuffing attacks.

'Implements API rate limiting and throttling controls using token bucket, sliding window, and fixed window algorithms to protect against brute force attacks, credential stuffing, resource exhaustion, and API abuse. The engineer configures per-user, per-IP, and per-endpoint rate limits using Redis-backed counters, API gateway plugins, or application middleware, and implements proper HTTP 429 responses with Retry-After headers. Activates for requests involving rate limiting implementation, API ...

Implement API schema validation using OpenAPI specifications and JSON Schema to enforce input/output contracts and prevent injection, data exposure, and mass assignment attacks.

Implement API Security Posture Management to continuously discover, classify, and score APIs based on risk while enforcing security policies across the API lifecycle.

Implement API threat protection using Google Apigee policies including JSON/XML threat protection, OAuth 2.0, SpikeArrest, and Advanced API Security for OWASP Top 10 defense.

'Process use when you need to track database changes for compliance and security monitoring. This skill implements audit logging using triggers, application-level logging, CDC, or native logs. Trigger with phrases like \"implement database audit logging\", \"add audit trails\", \"track database changes\", or \"monitor database activity for compliance\". '

'Process use when you need to implement multi-tier caching to improve database performance. This skill sets up Redis, in-memory caching, and CDN layers to reduce database load. Trigger with phrases like \"implement database caching\", \"add Redis cache layer\", \"improve query performance with caching\", or \"reduce database load\". '

'Implements Delinea Secret Server for privileged access management (PAM) including secret vault configuration, role-based access policies, automated password rotation, session recording, and integration with Active Directory and cloud platforms. Activates for requests involving PAM deployment, privileged credential vaulting, secret server administration, or password rotation automation. '

Deploy and configure Wazuh SIEM/XDR for endpoint detection including agent management, custom decoder and rule XML creation, alert querying via the Wazuh REST API, and automated response actions.

'Deploys canary tokens and honeytokens (fake AWS credentials, DNS canaries, document beacons, database records) that trigger alerts when accessed by attackers. Uses the Canarytokens API and custom webhook integrations for breach detection. Use when building deception-based early warning systems for intrusion detection. '

Deploy and query Arkime (formerly Moloch) for full packet capture network traffic analysis. Uses the Arkime API v3 to search sessions, download PCAPs, analyze connection patterns, detect beaconing behavior, and identify suspicious network flows. Monitors DNS queries, HTTP traffic, and TLS certificate anomalies across captured traffic.

Deploy privileged access management for database systems including Oracle, SQL Server, PostgreSQL, and MySQL. Covers session proxy configuration, credential vaulting, query auditing, dynamic credentia

Deploy and configure an OpenTAXII server to share and consume STIX-formatted cyber threat intelligence using the TAXII 2.1 protocol for automated indicator exchange between organizations.