Run any Skill in Manus with one click

lhcb-software-environment

Stars0

Forks0

UpdatedJuly 3, 2026 at 03:04

Select, construct, and verify a current LHCb Run 3 released or development software environment. Use for lb-run, lbexec, lb-dev, platform selection, DaVinci version selection, CVMFS availability, or diagnosing an LHCb application environment. Do not use for generic Python environments or legacy Run 1/2 setup unless the user explicitly requests legacy support.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

MohamedElashri

MohamedElashri/lhcb-marketplace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

3 files

SKILL.md

readonly

name	lhcb-software-environment
description	Select, construct, and verify a current LHCb Run 3 released or development software environment. Use for lb-run, lbexec, lb-dev, platform selection, DaVinci version selection, CVMFS availability, or diagnosing an LHCb application environment. Do not use for generic Python environments or legacy Run 1/2 setup unless the user explicitly requests legacy support.
license	MIT
metadata	{"era":"run3","maintainer":"LHCb Agent Marketplace contributors","last_verified":"2026-07-02","origin":"original","sources":"https://lhcb-starterkit-run3.docs.cern.ch/first-analysis-steps/davinci/; https://lhcb-starterkit-run3.docs.cern.ch/first-analysis-steps/lhcb-dev/"}

LHCb software environment

Select an exact application release and compatible platform from authoritative sample metadata.

Workflow

Confirm this is a Run 3 task. Do not translate Run 1/2 commands silently.
Record the application, exact version, platform, data/MC status, processing stage, and geometry or conditions requirements. Never use latest in a reproducible command.
Use a released environment for normal execution:
```
lb-run [-c <platform>] <Application>/<version> <command>
```
Use lb-dev and the project ./run wrapper only when modifying packages.
If CVMFS is mounted but lb-run is not already on PATH, initialize the environment with source /cvmfs/lhcb.cern.ch/lib/LbEnv.sh.
List releases with lb-run --list <Application> and choose one documented for the sample.
Generate the command with scripts/check_environment.py; use --probe only on a compatible host.
Pass the selected environment to $davinci-run3.

Validation

Confirm lb-run and lbexec resolve in the selected release.
Run lbexec --help or a job --dry-run.
Record the exact version, platform, and command.

Failure handling

If the environment cannot run, provide the exact command and mark execution unverified.
If the sample metadata is incomplete, request it rather than inventing conditions, geometry, processing stage, or polarity.
Do not use private paths, credentials, containers, or site-specific mounts without authorization.

Provenance and scope

Original community guidance based on the public Run 3 Starterkit. It is not official LHCb approval and does not cover legacy setup by default.

Sources:

More from this repository

same repository

analysis-productions

MohamedElashri/lhcb-marketplace

Create, review, render, validate, and locally test modern LHCb Run 3 Analysis Productions using info.yaml, lbexec entrypoints, Bookkeeping inputs, and lb-ap. Use for production job matrices, data or MC input queries, application versions, output registration, local tests, and preservation handoffs. Do not use for direct grid submission, Run 1/2 gaudirun.py productions, dataset discovery alone, or inventing working-group policy.

2026-07-030

davinci-run3

MohamedElashri/lhcb-marketplace

Create, review, run, and troubleshoot modern LHCb Run 3 DaVinci jobs using an options function, YAML data options, PyConf, and lbexec. Use for minimal DaVinci configurations, input-process and conditions setup, line filters, dry runs, and job artifact checks. Do not use for Run 1/2 gaudirun.py or configurable-style jobs, FunTuple variable design alone, data discovery, or grid production submission.

2026-07-030

funtuple

MohamedElashri/lhcb-marketplace

Design, review, and verify modern LHCb Run 3 FunTuple configurations and ROOT ntuple outputs. Use for decay fields, caret placement, ThOr functors, FunctorCollection composition, event variables, tuple naming, branch checks, and output inspection. Do not use for legacy DecayTreeTuple or LoKi TupleTools, general DaVinci environment setup, data discovery, or physics-variable choices without user requirements.

2026-07-030

lhcb-analysis-spec

MohamedElashri/lhcb-marketplace

Create, review, and validate auditable LHCb Run 3 analysis specifications spanning physics objectives, datasets, software, selections, outputs, validation, provenance, open decisions, and preservation. Use for measurement plans, efficiency studies, control studies, analysis handoffs, and readiness reviews. Do not use to invent collaboration policy, approve physics choices, discover datasets by itself, or replace executable DaVinci and production validation.

2026-07-030

lhcb-data-discovery

MohamedElashri/lhcb-marketplace

Find, compare, record, and validate LHCb Run 3 data or simulation datasets using Bookkeeping, LHCbDIRAC, processing metadata, LFNs, and access checks. Use for event types, campaigns, magnet polarity, streams, HLT2 or Sprucing outputs, file manifests, and dataset provenance. Do not use for generic web search, physics-literature discovery, direct production submission, or choosing undocumented sample metadata.

2026-07-030

name	lhcb-software-environment
description	Select, construct, and verify a current LHCb Run 3 released or development software environment. Use for lb-run, lbexec, lb-dev, platform selection, DaVinci version selection, CVMFS availability, or diagnosing an LHCb application environment. Do not use for generic Python environments or legacy Run 1/2 setup unless the user explicitly requests legacy support.
license	MIT
metadata	{"era":"run3","maintainer":"LHCb Agent Marketplace contributors","last_verified":"2026-07-02","origin":"original","sources":"https://lhcb-starterkit-run3.docs.cern.ch/first-analysis-steps/davinci/; https://lhcb-starterkit-run3.docs.cern.ch/first-analysis-steps/lhcb-dev/"}

LHCb software environment

Select an exact application release and compatible platform from authoritative sample metadata.

Workflow

Confirm this is a Run 3 task. Do not translate Run 1/2 commands silently.
Record the application, exact version, platform, data/MC status, processing stage, and geometry or conditions requirements. Never use latest in a reproducible command.
Use a released environment for normal execution:
```
lb-run [-c <platform>] <Application>/<version> <command>
```
Use lb-dev and the project ./run wrapper only when modifying packages.
If CVMFS is mounted but lb-run is not already on PATH, initialize the environment with source /cvmfs/lhcb.cern.ch/lib/LbEnv.sh.
List releases with lb-run --list <Application> and choose one documented for the sample.
Generate the command with scripts/check_environment.py; use --probe only on a compatible host.
Pass the selected environment to $davinci-run3.

Validation

Confirm lb-run and lbexec resolve in the selected release.
Run lbexec --help or a job --dry-run.
Record the exact version, platform, and command.

Failure handling

If the environment cannot run, provide the exact command and mark execution unverified.
If the sample metadata is incomplete, request it rather than inventing conditions, geometry, processing stage, or polarity.
Do not use private paths, credentials, containers, or site-specific mounts without authorization.

Provenance and scope

Original community guidance based on the public Run 3 Starterkit. It is not official LHCb approval and does not cover legacy setup by default.

Sources: