org-planning
org-planning helps teams develop organizational structures, headcount strategies, and hiring roadmaps by modeling team sizes, reporting relationships, and sequencing critical roles. Use it when planning growth, restructuring teams, optimizing span of control, or determining which positions to hire next based on organizational health benchmarks and budget constraints.
git clone --depth 1 https://github.com/openyak/openyak /tmp/org-planning && cp -r /tmp/org-planning/backend/app/data/plugins/human-resources/skills/org-planning ~/.claude/skills/org-planningSKILL.md
# Org Planning Help plan organizational structure, headcount, and team design. ## Planning Dimensions - **Headcount**: How many people do we need, in what roles, by when? - **Structure**: Reporting lines, span of control, team boundaries - **Sequencing**: Which hires are most critical? What's the right order? - **Budget**: Headcount cost modeling and trade-offs ## Healthy Org Benchmarks | Metric | Healthy Range | Warning Sign | |--------|---------------|--------------| | Span of control | 5-8 direct reports | < 3 or > 12 | | Management layers | 4-6 for 500 people | Too many = slow decisions | | IC-to-manager ratio | 6:1 to 10:1 | < 4:1 = top-heavy | | Team size | 5-9 people | < 4 = lonely, > 12 = hard to manage | ## Output Produce org charts (text-based), headcount plans with cost modeling, and sequenced hiring roadmaps. Flag structural issues like single points of failure or excessive management overhead.
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full ASM JSON, flattened CSV for easy import, and exportable Python code for data engineers. Common triggers include converting instrument files, standardizing lab data, preparing data for upload to LIMS/ELN systems, or generating parser code for production pipelines.
Run nf-core bioinformatics pipelines (rnaseq, sarek, atacseq) on sequencing data. Use when analyzing RNA-seq, WGS/WES, or ATAC-seq data—either local FASTQs or public datasets from GEO/SRA. Triggers on nf-core, Nextflow, FASTQ analysis, variant calling, gene expression, differential expression, GEO reanalysis, GSE/GSM/SRR accessions, or samplesheet creation.
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
Deep learning for single-cell analysis using scvi-tools. This skill should be used when users need (1) data integration and batch correction with scVI/scANVI, (2) ATAC-seq analysis with PeakVI, (3) CITE-seq multi-modal analysis with totalVI, (4) multiome RNA+ATAC analysis with MultiVI, (5) spatial transcriptomics deconvolution with DestVI, (6) label transfer and reference mapping with scANVI/scArches, (7) RNA velocity with veloVI, or (8) any deep learning-based single-cell method. Triggers include mentions of scVI, scANVI, totalVI, PeakVI, MultiVI, DestVI, veloVI, sysVI, scArches, variational autoencoder, VAE, batch correction, data integration, multi-modal, CITE-seq, multiome, reference mapping, latent space.
Performs quality control on single-cell RNA-seq data (.h5ad or .h5 files) using scverse best practices with MAD-based filtering and comprehensive visualizations. Use when users request QC analysis, filtering low-quality cells, assessing data quality, or following scverse/scanpy best practices for single-cell analysis.
Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.
>
>