Loading...
Loading...
Found 4 Skills
Reasoning skill for multi-omics data integration strategy selection. Use when the user asks to integrate transcriptomics with proteomics, combine multi-omic layers, choose between early intermediate or late integration, apply batch correction across omics, handle partial sample overlap, run MOFA+ or iCluster, interpret multi-omic factors, select enrichment methods for multi-omic signatures, or decide how to merge genomics epigenomics transcriptomics proteomics and metabolomics data. Triggers include "multi-omics integration", "combine omics layers", "early vs late fusion", "MOFA+", "iCluster", "batch correction across omics", "partial overlap", "multi-omic enrichment", "kernel integration", "concatenation vs stacking", "SNF", "similarity network fusion", "intermediate integration", "multi-omic factor analysis".
architecture design system planning structure pattern integration features
Analyze and extract relevant patterns, best practices, and usage examples from fetched documentation for implementation guidance.
Decides whether, when and how far a developer product should open into a platform other companies build on - extension points, partner-built integrations, third-party apps, a complement ecosystem - and what that permanently obliges you to. Use whenever someone asks if the product should become a platform, whether to open extension points or an app model to third parties, how to start an integration ecosystem, why nobody builds on the API, whether partners should build the connectors, or how much value complementors must keep - even if they only say "we want an integrations story". Not marketplace operations or API design. Do NOT use for the revenue model - use samber/developer-relations-skills@devtools-business-model.