onboarding
The onboarding skill generates a structured checklist and timeline for integrating a new employee into an organization. Use it when a new hire has a confirmed start date to create pre-arrival setup tasks, a detailed first-day schedule, week-one activities, and 30/60/90-day milestone goals tailored to the specific role and team.
git clone --depth 1 https://github.com/openyak/openyak /tmp/onboarding && cp -r /tmp/onboarding/backend/app/data/plugins/human-resources/skills/onboarding ~/.claude/skills/onboardingSKILL.md
# /onboarding > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Generate a comprehensive onboarding plan for a new team member. ## Usage ``` /onboarding $ARGUMENTS ``` ## What I Need From You - **New hire name**: Who's starting? - **Role**: What position? - **Team**: Which team are they joining? - **Start date**: When do they start? - **Manager**: Who's their manager? ## Output ```markdown ## Onboarding Plan: [Name] — [Role] **Start Date:** [Date] | **Team:** [Team] | **Manager:** [Manager] ### Pre-Start (Before Day 1) - [ ] Send welcome email with start date, time, and logistics - [ ] Set up accounts: email, Slack, [tools for role] - [ ] Order equipment (laptop, monitor, peripherals) - [ ] Add to team calendar and recurring meetings - [ ] Assign onboarding buddy: [Suggested person] - [ ] Prepare desk / remote setup instructions ### Day 1 | Time | Activity | With | |------|----------|------| | 9:00 | Welcome and orientation | Manager | | 10:00 | IT setup and tool walkthrough | IT / Buddy | | 11:00 | Team introductions | Team | | 12:00 | Welcome lunch | Manager + Team | | 1:30 | Company overview and values | Manager | | 3:00 | Role expectations and 30/60/90 plan | Manager | | 4:00 | Free time to explore tools and docs | Self | ### Week 1 - [ ] Complete required compliance training - [ ] Read key documentation: [list for role] - [ ] 1:1 with each team member - [ ] Shadow key meetings - [ ] First small task or project assigned - [ ] End-of-week check-in with manager ### 30-Day Goals 1. [Goal aligned to role] 2. [Goal aligned to role] 3. [Goal aligned to role] ### 60-Day Goals 1. [Goal] 2. [Goal] ### 90-Day Goals 1. [Goal] 2. [Goal] ### Key Contacts | Person | Role | For What | |--------|------|----------| | [Manager] | Manager | Day-to-day guidance | | [Buddy] | Onboarding Buddy | Questions, culture, navigation | | [IT Contact] | IT | Tool access, equipment | | [HR Contact] | HR | Benefits, policies | ### Tools Access Needed | Tool | Access Level | Requested | |------|-------------|-----------| | [Tool] | [Level] | [ ] | ``` ## If Connectors Available If **~~HRIS** is connected: - Pull new hire details and team org chart - Auto-populate tools access list based on role If **~~knowledge base** is connected: - Link to relevant onboarding docs, team wikis, and runbooks - Pull the team's existing onboarding checklist to customize If **~~calendar** is connected: - Create Day 1 calendar events and Week 1 meeting invites automatically ## Tips 1. **Customize for the role** — An engineer's onboarding looks different from a designer's. 2. **Don't overload Day 1** — Focus on setup and relationships. Deep work starts Week 2. 3. **Assign a buddy** — Having a go-to person who isn't their manager makes a huge difference.
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.
>
>