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

Materials Characterization

ASecurity

Choosing and combining characterization techniques — diffraction, microscopy, spectroscopy, and thermal methods — to fully describe a material.

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

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill materials-characterization --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Materials Characterization?

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

Security grade badge for Materials Characterization
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-materials-characterization/badge)](https://www.skillsdirectory.com/skills/aicodedecode-materials-characterization)

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: materials-characterization
description: Choosing and combining characterization techniques — diffraction, microscopy, spectroscopy, and thermal methods — to fully describe a material.
category: scientific
---

## Overview

No single technique fully characterizes a material. This skill is a
decision framework: given a question (phase purity? composition?
microstructure? surface chemistry?), pick the right combination of
diffraction, microscopy, spectroscopy, and thermal/electrical methods,
prepare samples correctly, and interpret results without overclaiming.

## When to use

- A new material is synthesized: prove what it is, how pure it is, and what it looks like
- A device or batch fails: root-cause analysis across structure, composition, and morphology
- Comparing samples: establish which differences are real and which are artifacts
- Writing the characterization section of a paper or report with appropriate claims
- Deciding whether an expensive technique (TEM, synchrotron, APT) is actually needed

## Core concepts

- **Length scales:** XRD probes the average crystal structure (bulk, nm-scale coherence); SEM shows morphology (µm); TEM reaches atomic resolution but on a tiny, possibly unrepresentative volume. Match the technique to the scale of the question.
- **Surface vs bulk:** XPS and Auger see the top ~5–10 nm; XRD and bulk chemical analysis see the whole sample. A "pure" XRD pattern can hide a completely different surface.
- **Detection limits:** XRD misses amorphous phases and <~2–5 wt% minority phases; EDS is semi-quantitative for light elements; always state what a null result actually rules out.
- **Complementary pairs:** structure (XRD) + composition (EDS/ICP) + morphology (SEM) + thermal behavior (TGA/DSC) covers most new materials; spectroscopy (Raman/IR/XPS) adds bonding and surface state.
- **Quantitative vs qualitative:** peak positions are precise; peak intensities in XRD depend on texture, absorption, and instrument geometry — Rietveld refinement is needed for real quantification.

- **Depth profiling:** angle-resolved XPS, SIMS sputter profiles, cross-sectional TEM — when surface and bulk disagree, profile the transition instead of arguing about which measurement is "right".
- **In situ and operando measurement:** observing during heating, biasing, or reaction — ex situ snapshots miss transient states; the working material often differs from the as-made one.
- **Microstructure statistics:** grain-size and particle-size distributions need real counts (n ≥ 300 particles) — report histograms, not single "average" values from a glance.

## Practical workflow

### 1. Start with the cheap, fast, informative trio

1. **Powder XRD:** phase identification against databases (PDF/ICSD); check for peak shifts (doping/strain), broadening (small crystallites — Scherrer), and amorphous humps.
2. **SEM + EDS:** morphology, particle size, elemental mapping; look for inhomogeneity and secondary phases the XRD missed.
3. **TGA/DSC:** thermal stability, decomposition steps, phase transitions, solvent/water content.

### 2. Answer specific questions with targeted tools

| Question | Technique |
|---|---|
| Atomic structure / defects | TEM (HRTEM, STEM-EELS) |
| Surface chemistry / oxidation states | XPS |
| Local bonding / disorder | Raman, solid-state NMR, PDF analysis |
| Trace composition | ICP-MS/OES |
| Porosity / surface area | BET gas sorption |
| Magnetic/electronic state | SQUID/VSM, transport, UV-Vis |

### 3. Sample preparation discipline

1. Grind powders to avoid preferred orientation in XRD; use a zero-background holder for small quantities.
2. For SEM, ensure conductivity (sputter-coat insulators) and avoid charging artifacts misread as features.
3. For TEM, the thinning/preparation can alter the sample — compare with bulk measurements.
4. Store air-sensitive samples properly; an oxidized surface measured by XPS tells you about your handling, not your material.

### 4. Report honestly

1. State instrument, conditions, and calibration for every technique.
2. Distinguish "not detected" (with the technique's limit) from "absent."
3. Show raw data alongside fits (Rietveld, XPS deconvolution) — hidden residuals hide bad models.

### 5. Correlate across techniques (the closure test)

1. Tabulate each technique's answer to the same question (e.g., particle size from XRD, TEM, BET, DLS) — they probe different moments of the distribution and should bracket each other, not match exactly.
2. Investigate systematic disagreements: XRD size << TEM size means polycrystalline aggregates or amorphous shells.
3. Present the multi-technique comparison table in the paper — it is the most convincing characterization figure there is.

### 6. Quick-reference checklist

- [ ] XRD + SEM/EDS + thermal analysis completed as the baseline trio
- [ ] Surface-sensitive (XPS) vs bulk techniques compared, not conflated
- [ ] Detection limits stated for every "not detected" claim
- [ ] Sample preparation documented (grinding, coating, atmosphere)
- [ ] TEM observations backed by bulk statistics, not single images
- [ ] Raw data shown alongside every fit (Rietveld, XPS deconvolution)
- [ ] Instrument, conditions, and calibration recorded per technique
- [ ] Beam-damage checks done for sensitive samples

## Common pitfalls

- **XRD-only characterization:** a clean diffraction pattern does not prove purity — amorphous and minor phases are invisible.
- **EDS as exact composition:** standardless EDS is ±5–10% at best and unreliable for light elements; use ICP or WDS for numbers you will publish.
- **TEM sampling bias:** a beautiful atomic image of one grain says nothing about the other 99.9% of the sample.
- **Overfitting XPS:** every extra peak component needs a physical justification; unconstrained deconvolution can "find" any oxidation state.
- **Ignoring beam damage:** electron and X-ray beams modify sensitive samples (polymers, halides, MOFs) — check for damage with dose series.
- **Forgetting the substrate/contamination:** peaks from the holder, carbon tape, or adsorbed water routinely get published as discoveries.
- **Charging shifts in XPS/SEM:** sample charging shifts binding energies and distorts images — reference XPS to adventitious C 1s (284.8 eV) or use a flood gun; coat insulators for SEM.
- **EDS on rough surfaces:** take-off-angle variations corrupt standardless quantification — use flat, polished regions for any number you will publish.

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 →