nf-core

Diagnose and fix issues with running hackathon infrastructure. Use when services are unhealthy, users report problems, OAuth fails, video doesn't work, or maps don't load. Covers SSH access, Docker logs, TLS certificates, and network connectivity troubleshooting.

Deploy complete hackathon infrastructure from scratch including WorkAdventure, LiveKit, Coturn, and Jitsi. Use when setting up for a new event, recovering from accidental destruction, or first-time deployment. Covers pre-flight checks, Terraform bootstrap, map sync, and service verification.

Validate and sync WorkAdventure maps. Use when working with map files, syncing changes, checking for map errors, or setting up interactive zones (Jitsi rooms, silent areas). Covers JSON validation, TypeScript builds, and troubleshooting map loading issues.

Safely tear down hackathon infrastructure. Use when the event is over, doing cleanup, or need to start fresh. Covers Terraform destroy (preferred) and manual AWS cleanup (when state is corrupted). Includes verification steps to ensure complete removal.

Scaffold new DLT pipeline for data ingestion to MotherDuck

Create new Evidence.dev dashboard page with charts and tables

Review an nf-core new pipeline proposal and produce a scored assessment with a draft GitHub comment. Use whenever given a link, issue number, or description from the nf-core/proposals repository, or when asked whether a proposed bioinformatics pipeline should be accepted into nf-core. Triggers on "review this proposal", "should we accept this", "nf-core/proposals#NNN", any github.com/nf-core/proposals link, "is this a good nf-core pipeline?", or any mention of evaluating a pipeline proposal against nf-core criteria. Always invoke this skill rather than doing an ad-hoc review — it handles the research, overlap checking, and structured output.

How to build and modify Slack-app features in this repo (a Python async slack-bolt bot running in Socket Mode). Use this whenever you are touching anything Slack-facing — adding or editing slash commands, events, actions, shortcuts, modals/views, or option providers; formatting or posting messages (Block Kit, mrkdwn, bullets, mentions, threads, ephemeral vs public); resolving why a message won't post or render correctly; or changing the Slack app's scopes/events/manifest. Reach for it even when the user doesn't say "Slack" but is editing files under src/nf_core_bot/ that call `client.*`, `respond`, `ack`, `say`, or `@app.*`, since the formatting and delivery rules here are easy to get subtly wrong.