Loading...
Loading...
Found 1,143 Skills
Create, visualize, and analyze lithological and stratigraphic logs for well data. Use when Claude needs to: (1) Create lithology columns from depth intervals, (2) Parse geological descriptions into structured logs, (3) Visualize stratigraphic columns with patterns and colors, (4) Perform well-to-well correlations, (5) Extract statistics like net-to-gross ratios, (6) Define rock type lexicons and legends, (7) Export lithology data to CSV/LAS/JSON.
Linear operators for large-scale inverse problems with matrix-free representations. Use when Claude needs to: (1) Define linear operators for forward/adjoint operations, (2) Solve inverse problems (deconvolution, imaging, tomography), (3) Apply signal processing transforms (FFT, convolution, derivatives), (4) Compose operators for complex workflows, (5) Perform regularized inversion with smoothness or sparsity constraints, (6) Process seismic or image data at scale.
Generates structured test assertions and failure diagnostics for skill packages from a definition and task prompt. Triggers on: "verify this skill", "generate assertions", "surrogate verification", "diagnose skill failure". NOT for code review, use pr-review.
Add a linked resource (external file reference) to a ***plain spec. Use when the user wants to reference a JSON schema, API spec, data file, or other external file from within a functional spec, definition, or implementation requirement.
Add a concept to the ***definitions*** section of a ***plain spec file. Use when the user wants to define a new concept, entity, or domain term in a .plain file.
Answer questions about ArkEnv and help implement environment variable validation. Use when developers: (1) Ask about environment variable validation or typesafety, (2) Want to setup ArkEnv in a project, (3) Need to define or update schemas using ArkType or Standard Schema, (4) Are integrating with Vite, Bun, or other runtimes. Triggers on: 'ArkEnv', 'env validation', 'typesafe env', 'createEnv', 'env.ts', '@arkenv/cli'.
contract-cli Field Configuration Query Skill: Query the field configuration definitions of vendor, legal_entity, and vendor_risk. Triggered when users want to use `contract-cli mdm fields list` to confirm the master data field structure. The bot identity currently only supports vendor/legalEntity.
Rules and guidelines for working with Spring Data JPA in the project. ALWAYS use this skill when adding, removing, or modifying JPA entities, repositories, or projections. Trigger on any request that involves changing entity structure, adding new entities, modifying field annotations, updating database mappings, creating or modifying Spring Data repositories, or defining query projections (interfaces, DTOs).
BI fundamentals with metric definition, KPI calculation, dimensional modeling, dashboard optimization, and data storytelling. 40+ metric examples and calculation patterns.
Design and operate back-office account opening processes from application intake through activation. Use when building account opening automation or improving STP rates, reducing NIGO rejection rates from custodians or clearing firms, defining document requirements for trusts entities IRAs or estate accounts, implementing approval workflows and regulatory holds for complex account types, setting up multi-custodian account opening across Schwab Fidelity or Pershing, designing account numbering titling or classification schemes, troubleshooting account opening failures or processing delays, integrating with custodian or clearing firm submission systems, or benchmarking account opening cycle times and operational efficiency.
Design and operate data quality programs for financial data — golden source architecture, validation rules, data lineage, exception management, profiling, and governance. Use when building validation rules for pricing or client data pipelines, designing a data quality monitoring framework, establishing golden source designations across systems, implementing data lineage for BCBS 239 or MiFID II, investigating reconciliation breaks or billing errors traced to bad data, preparing for regulatory exams on data accuracy, building data quality scorecards, or defining data stewardship roles. Trigger on: data quality, golden source, data lineage, data validation, data profiling, exception management, data governance, BCBS 239, data completeness, data accuracy, validation rules, data anomaly, data stewardship, data quality scorecard.
Design and implement workflow automation with task routing approval chains and SLA monitoring for securities operations. Use when building a new operational workflow for account opening maintenance transfers or corporate actions, implementing task routing logic based on type priority or capacity, designing multi-level approval chains with dollar thresholds and delegation of authority, defining escalation rules for aging work items approaching SLA breach, selecting a workflow engine or BPM platform like Camunda Pega or ServiceNow, modeling an operational process as a state machine with defined transitions, adding audit trail and logging for SEC Rule 17a-3 or FINRA supervisory obligations, migrating from email-and-spreadsheet tracking to a structured workflow system, or measuring cycle time throughput queue depth and rework rate.