Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Xrd Pattern Analysis

ASecurity

Powder X-ray diffraction from measurement to meaning — phase ID, lattice parameters, crystallite size, and Rietveld refinement.

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgoreactdatabase

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill xrd-pattern-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Xrd Pattern Analysis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Xrd Pattern Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-xrd-pattern-analysis/badge)](https://www.skillsdirectory.com/skills/aicodedecode-xrd-pattern-analysis)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: xrd-pattern-analysis
description: Powder X-ray diffraction from measurement to meaning — phase ID, lattice parameters, crystallite size, and Rietveld refinement.
category: scientific
---

## Overview

Powder XRD turns a polycrystalline sample into a fingerprint of its crystal
structure. This skill covers the full pipeline: collecting good data,
identifying phases, extracting lattice parameters and crystallite size, and
performing Rietveld refinement — with the data-quality discipline that makes
the difference between a publishable pattern and a pretty picture.

## When to use

- Identifying unknown phases in a synthesis product (search–match against PDF/ICSD databases)
- Tracking lattice parameter shifts from doping, strain, or thermal expansion
- Estimating crystallite size and microstrain from peak broadening
- Quantifying phase mixtures via Rietveld refinement
- Monitoring reactions in situ (variable temperature, gas atmosphere)

## Core concepts

- **Bragg's law (nλ = 2d sinθ):** peak positions encode d-spacings; everything quantitative starts here. A systematic shift means the lattice changed (composition, temperature, stress).
- **Structure factor:** peak intensities encode which atoms sit where — the basis of structure determination and Rietveld refinement.
- **Peak broadening:** three contributors — instrumental, crystallite size (Scherrer: β = Kλ/(L cosθ)), and microstrain (Williamson–Hall separates size from strain by their different θ-dependence).
- **Systematic absences:** missing reflections fingerprint the lattice centering and glide/screw symmetry (e.g., FCC shows only all-even or all-odd hkl).
- **Rietveld refinement:** fits the entire pattern (background, peak shapes, structure model) by least squares; the difference plot, not R_wp alone, judges the fit.
- **Preferred orientation:** plate/needle crystallites align in the holder, distorting intensities — a sample-prep artifact, not a structural feature.

- **Intensity corrections:** Lorentz-polarization correction is mandatory; microabsorption (Brindley) matters when phases differ strongly in absorption — quantitative phase analysis without absorption correction is only approximate.
- **Anisotropic broadening:** plate- or needle-shaped crystallites and directional strain broaden different (hkl) differently — model with anisotropic terms rather than forcing an isotropic size that fits nothing well.
- **Pair distribution function (PDF):** the Fourier transform of total scattering gives real-space atom-pair distances — the structural tool for amorphous and nanoscale materials where Bragg analysis fails.

## Practical workflow

### 1. Collect data worth analyzing

1. Grind to a fine, uniform powder; pack flat without pressing texture into it (back-loading or side-loading holders help).
2. Choose scan range and step: cover at least 10–80° 2θ (Cu Kα) with steps ≤ 1/5 of the narrowest peak width; count long enough that the weakest peak of interest is well above background.
3. Run a standard (e.g., NIST Si or LaB₆) periodically to verify zero shift and instrumental broadening.
4. Note the radiation (Cu Kα vs Mo/Co), slit settings, and sample holder — fluorescence (e.g., Fe/Co samples with Cu radiation) ruins data.

### 2. Phase identification

1. Strip Kα₂ / correct zero shift, then search–match peak positions (positions first, intensities second — texture distorts intensities).
2. Confirm with the full pattern, not just the three strongest lines; check for unindexed peaks (impurities, new phases).
3. For mixtures, identify the major phase first, then hunt residuals.

### 3. Extract numbers

1. **Lattice parameters:** least-squares fit of ≥6 well-resolved peak positions; report with estimated standard deviations.
2. **Crystallite size:** Scherrer on an isolated peak after subtracting instrumental broadening; cross-check with Williamson–Hall for strain contribution.
3. **Phase fractions:** Rietveld with refined scale factors — needs good data and correct structure models for every phase present.

### 4. Rietveld refinement sequence

1. Fit background and scale, then lattice parameters, then peak-shape/profile terms.
2. Refine atomic positions, then occupancies and displacement parameters — in that order, releasing parameters gradually.
3. Inspect the difference curve at every step; a structured residual means the model is wrong, not the data.
4. Report R_wp, R_exp, χ², and the refined parameters with uncertainties; never refine more parameters than the data supports.

### 5. Do a proper quantitative phase analysis

1. Add an internal standard (e.g., 10 wt% corundum) to quantify amorphous content — Rietveld normalizes crystalline phases to 100%, hiding glass.
2. Refine all phases with correct structure models; validate refined weight fractions against known spike compositions.
3. Report refinement uncertainties and cross-check with an independent method (chemical analysis, NMR, or Mössbauer).

### 6. Quick-reference checklist

- [ ] Radiation type and instrument configuration verified in the data header
- [ ] Zero shift / sample displacement corrected (standard or internal Si)
- [ ] Kα₂ stripped or modeled; tube artifacts identified
- [ ] Preferred orientation assessed and addressed in sample prep or model
- [ ] Instrumental broadening subtracted before Scherrer analysis
- [ ] Phase ID confirmed on full pattern, not just strongest lines
- [ ] Rietveld difference plot inspected at every refinement stage
- [ ] Amorphous content quantified with an internal standard where relevant

## Common pitfalls

- **Preferred orientation:** pressing the powder flat aligns plates — intensities lie; re-prep or model it (March–Dollase) rather than believing it.
- **Misidentifying the Kβ or W contamination lines:** know your tube's artifacts before claiming new peaks.
- **Scherrer on strained or textured samples:** broadening has three sources; attributing it all to size is the most common XRD error.
- **Rietveld over-refinement:** refining occupancies and ADPs simultaneously on mediocre data produces precise-looking nonsense.
- **Ignoring amorphous content:** a broad hump under the pattern is real material — quantify it with an internal standard (spiking) if it matters.
- **Wrong wavelength in the software:** a Cu/Mo mixup shifts every d-spacing — verify the instrument configuration in the data file header.
- **Sample-displacement error:** a mispositioned sample shifts peaks systematically — refine the zero shift or use an internal standard (Si) rather than absorbing the error into lattice parameters.
- **Texture modeled as structure:** strong preferred orientation refined through atomic parameters instead of a texture model produces chemically absurd occupancies — model the texture explicitly.

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →