Build the Cosmos Explorer project. Use this skill when asked to build, compile, or check the build status of the project.
npx skills add https://github.com/Azure/cosmos-explorer --skill build
Use the following commands to build the Cosmos Explorer project. Choose the appropriate command based on the task.
Run a complete production build (format check → lint → compile → strict compile → webpack prod → copy):
npm run build
Run a CI build that uses webpack dev mode for faster bundling:
npm run build:ci
Run a TypeScript type-check without emitting output:
npm run compile
Run a strict null-checks compile on the subset of files in tsconfig.strict.json:
npm run compile:strict
Run ESLint across all .ts and .tsx files:
npm run lint
Run Prettier to verify formatting without modifying files:
npm run format:check
Before running any build command, check whether npm install needs to be run. Do this by comparing package.json and package-lock.json against the installed node_modules:
node_modules directory exists. If it does not, run npm install.node_modules exists, check whether package.json or package-lock.json have been modified more recently than node_modules. If so, run npm install.# Check if node_modules is missing or outdated
if [ ! -d node_modules ] || [ package.json -nt node_modules ] || [ package-lock.json -nt node_modules ]; then
npm install
fi
On Windows PowerShell:
if (-not (Test-Path node_modules) -or
(Get-Item package.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime -or
(Get-Item package-lock.json).LastWriteTime -gt (Get-Item node_modules).LastWriteTime) {
npm install
}
Always run this check before proceeding with any build command.
npm run build for a full production build.npm run build:ci.npm run compile.npm run compile output.npm run compile:strict output.npm run lint output.npm run format to auto-fix formatting, then retry the build.tsconfig.strict.json so they compile under strict mode.Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take azure/build from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm.
Without those the skill loads but fails at the first command.