Total 54,172 skills, Data Processing has 2771 skills
Showing 12 of 2771 skills
How to read and query onchain data — events, The Graph, indexing patterns. Why you cannot just loop through blocks, and what to use instead.
Detect and analyze adverse drug event signals using FDA FAERS data, drug labels, disproportionality analysis (PRR, ROR, IC), and biomedical evidence. Generates quantitative safety signal scores (0-100) with evidence grading. Use for post-market surveillance, pharmacovigilance, drug safety assessment, adverse event investigation, and regulatory decision support.
Process perform on-chain analysis including whale tracking, token flows, and network activity. Use when performing crypto analysis. Trigger with phrases like "analyze crypto", "check blockchain", or "monitor market".
Interpret genetic variants (SNPs) from GWAS studies by aggregating evidence from multiple databases (GWAS Catalog, Open Targets Genetics, ClinVar). Retrieves variant annotations, GWAS trait associations, fine-mapping evidence, locus-to-gene predictions, and clinical significance. Use when asked to interpret a SNP by rsID, find disease associations for a variant, assess clinical significance, or answer questions like "What diseases is rs429358 associated with?" or "Interpret rs7903146".
Reading and writing data with Pandas from/to cloud storage (S3, GCS, Azure) using fsspec and PyArrow filesystems.
Advanced SQL patterns including window functions, CTEs, recursive queries, and optimization techniques.
Patterns for building robust, reproducible genomics analysis pipelines. Covers workflow managers, NGS data processing, variant calling, RNA-seq, and common bioinformatics pitfalls. Use when ", " mentioned.
Parse raw text from an Instagram or TikTok Story insights screenshot and format it into a clean, spreadsheet-ready row with labeled fields. This skill should be used when parsing Story metrics from a screenshot, formatting Story insights for a spreadsheet, extracting metrics from a pasted Story screenshot, cleaning up Story analytics data, converting Story insights text into structured data, turning a Story performance screenshot into a row for the tracker, logging Story metrics into a spreadsheet, normalizing Story screenshot data, pulling numbers from a Story insights paste, organizing Story metrics from creator screenshots, processing a batch of Story screenshots into rows, building a Story metrics tracker from screenshots, or entering Story data from a screenshot into a sheet. For normalizing metrics from multiple sources into a unified table, see metrics-normalization-formatter. For calculating engagement rates and comparing to benchmarks, see engagement-rate-calculator-benchmarker.
This skill should be used when the user needs to perform year-end closing adjustments, review financial statements, compute depreciation, or review their trial balance. Trigger phrases include: "year-end settlement", "year-end closing adjustments", "prepare financial statements", "depreciation", "trial balance", "trial balance sheet", "income statement", "balance sheet", "BS", "PL", "period-end processing", "inventory taking", "accrual of unpaid expenses", "prepayment processing"
Web crawling and scraping with analysis. Use for crawling websites, security scanning, and extracting information from web pages.
Arquiteto de Dados especialista em PostgreSQL, Supabase e modelagem multi-tenant para a plataforma PAPO
Given event_candidates YAML (output from discover-event-surfaces), generates a concrete instrumentation plan for priority-3 (critical) events. Acts as a Software Architect: discovers existing analytics patterns in the codebase, reads the hinted files to determine what variables are in scope, designs minimal chart-useful properties, and identifies the exact insertion point for each tracking call. Outputs a structured JSON trackingPlan. Use this as step 3 of the analytics instrumentation workflow, after discover-event-surfaces. Trigger whenever a user has event_candidates and wants to generate tracking code, asks "instrument these events", "generate tracking plan", "add analytics for these events", "where should I put the tracking calls", or any request to turn event candidates into concrete implementation guidance.