pdg-lookup
Skill20 starsChanged 22 days agoMITView on GitHub
Teaches the PDG (Particle Data Group) tool chain for looking up particle properties, measurements, decays, and references from the local PDG SQLite database.
In this repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- citation-triangulationSkill
- claim-groundingSkill
- claude-cli-runnerSkill
- codex-cli-runnerSkill
- deep-literature-reviewSkill
- derivation-verifySkill
- dsh-cli-runnerSkill
- figure-hygieneSkill
- gemini-cli-runnerSkill
- hep-calcSkill
- hep-mcp-usageSkill
- idea-allocationSkill
- idea-generationSkill
- idea-pairwise-matchSkill
- idea-posteriorSkill
- julia-packageSkill
- julia-perfSkill
- kimi-cli-runnerSkill
- literature-graph-builderSkill
- literature-to-packageSkill
- markdown-hygieneSkill
- numerical-reliability-gateSkill
- opencode-cli-runnerSkill
- paper-reviserSkill
- physics-diagramsSkill
- referee-reviewSkill
- research-harnessSkill
- research-integritySkill
- research-teamSkill
- research-writerSkill
- review-swarmSkill
- zotero-importSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
All PDG tools are local-only (no network) and require PDG_DB_PATH to be set.
- Very specific: line 52
Use allow_derived: true to get width derived from lifetime (and vice versa).
- Very specific: line 59
CRITICAL: If the result has kind: "series_options" or stop_here: true, you MUST STOP and present the options to the user.
- Distinctive: line 64
Never skip the series selection step.
- Very specific: line 113
Use pdg_batch (full exposure only) to run multiple PDG lookups in one call.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PDG Lookup Workflow
This skill teaches the correct tool-calling sequence for PDG lookups via the pdg_* MCP tools.
All PDG tools are local-only (no network) and require PDG_DB_PATH to be set.
Tool Chain Overview
pdg_info # Check DB status, see available editions
|
pdg_find_particle # Search by name / MCID / PDG identifier
|
+-- pdg_get_property # Quick: mass, width, lifetime (with uncertainties)
+-- pdg_get_measurements # Detailed: all measurements for a PDG identifier
+-- pdg_get_decays # All decay modes for a particle
+-- pdg_get # Full PDG identifier object (JSON artifact)
|
pdg_find_reference # Find PDG references by DOI / INSPIRE recid / title
pdg_get_reference # Get a specific PDG reference recordStep 1: Check availability
pdg_info {}Returns DB path, edition year, and data directories. If this fails, the user needs to set PDG_DB_PATH.
Step 2: Find the particle
pdg_find_particle { query: "top quark" }
pdg_find_particle { query: "t", mcid: 6 }
pdg_find_particle { pdgid: "S008" }The result includes pdgid values (e.g., "S008" for the top quark) needed for subsequent calls.
Step 3: Get properties or measurements
Quick property lookup
pdg_get_property { pdgid: "S008M", particle: "t" }
pdg_get_property { particle: "W", property: "mass" }
pdg_get_property { particle: "Z", property: "width" }- Use
allow_derived: trueto get width derived from lifetime (and vice versa). - Returns value, uncertainties, unit, and PDG locator.
Detailed measurements (CRITICAL: stop-and-select pattern)
pdg_get_measurements { particle: "t", property: "mass" }CRITICAL: If the result has kind: "series_options" or stop_here: true, you MUST STOP and present the options to the user. Then call again with the specific property_pdgid or data_type from example_next_calls:
pdg_get_measurements { property_pdgid: "S008M" }
pdg_get_measurements { pdgid: "S008M", data_type: "DIRECT MEASUREMENT" }Never skip the series selection step. The result is a JSONL artifact with full measurement details.
Decay modes
pdg_get_decays { particle: "Z" }
pdg_get_decays { pdgid: "S044" }Returns all known decay modes with branching ratios as a JSONL artifact.
Step 4: References
Find references
pdg_find_reference { query: "CKM" }
pdg_find_reference { doi: "10.1103/PhysRevD.110.030001" }
pdg_find_reference { inspire_id: "2830185" }Get a specific reference
pdg_get_reference { document_id: 12345 }Common Workflow Examples
Top quark mass
pdg_find_particle { query: "top quark" }-> get pdgidS008pdg_get_property { particle: "t", property: "mass" }-> quick valuepdg_get_measurements { particle: "t", property: "mass" }-> may returnseries_options- Select the appropriate series ->
pdg_get_measurements { property_pdgid: "S008M" }
Z boson decays
pdg_find_particle { query: "Z boson" }-> get pdgidS044pdg_get_decays { pdgid: "S044" }-> all decay modes with BRs
Higgs measurements
pdg_find_particle { query: "Higgs" }-> pdgidS126pdg_get_measurements { particle: "H", property: "mass" }-> handle series_optionspdg_get_measurements { property_pdgid: "S126M" }-> all mass measurements
CKM review reference
pdg_find_reference { query: "CKM" }-> find document_idpdg_get_reference { document_id: <id> }-> full reference with INSPIRE link
Tips
pdg_get_propertyis fast and returns a single best-fit value. Use it for quick lookups.pdg_get_measurementsreturns the full measurement history. Use it when the user needs individual experiment results.- Particle names are case-insensitive:
"W","w","W boson"all work. - Use
pdg_batch(full exposure only) to run multiple PDG lookups in one call. - Width and lifetime are related: if only one is in the DB, use
allow_derived: trueto get the other.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

