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

Mechanical Testing Basics

ASecurity

Mechanical property measurement — tensile, hardness, fracture, and fatigue testing with proper specimen and data practice.

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

Works with

cli

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill mechanical-testing-basics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mechanical Testing Basics?

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

Security grade badge for Mechanical Testing Basics
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-mechanical-testing-basics/badge)](https://www.skillsdirectory.com/skills/aicodedecode-mechanical-testing-basics)

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: mechanical-testing-basics
description: Mechanical property measurement — tensile, hardness, fracture, and fatigue testing with proper specimen and data practice.
category: scientific
---

## Overview

Mechanical testing converts "this material feels strong" into numbers with
units and uncertainties. This skill covers the core tests — tensile,
hardness, fracture toughness, fatigue, creep — how to prepare specimens,
extract properties from raw data, and avoid the artifacts that make published
strength values irreproducible.

## When to use

- Measuring strength, ductility, stiffness, or toughness of a new material
- Comparing processing routes or heat treatments quantitatively
- Diagnosing failures: was it overload, fatigue, embrittlement, or a defect?
- Qualifying a material against a standard (ASTM/ISO) for an application
- Deciding which test actually answers your question (strength ≠ toughness ≠ hardness)

## Core concepts

- **Stress–strain vocabulary:** engineering vs true stress–strain; Young's modulus E (initial slope); 0.2% offset yield strength; UTS (maximum); elongation and reduction of area (ductility); toughness (area under the curve).
- **Hardness as a proxy:** Vickers/Brinell/Rockwell hardness correlates empirically with strength (Tabor relation) but measures resistance to plastic indentation — not a substitute for tensile data in design.
- **Fracture toughness (K_IC):** resistance to crack propagation, with units MPa√m; the property that determines whether a small flaw causes catastrophic failure. Strength without toughness is brittleness.
- **Fatigue:** S–N curves, endurance limit (steels) vs continuously declining life (aluminum); crack growth follows Paris law da/dN = C(ΔK)^m. Most service failures are fatigue.
- **Size and rate effects:** properties depend on specimen size (grain size vs thickness), strain rate, and temperature — a number without these conditions is incomplete.
- **Weibull statistics:** brittle materials (ceramics, composites) fail from the worst flaw; strength follows a Weibull distribution — report the modulus m, not just a mean.

- **True vs engineering stress–strain:** engineering uses the original area; true uses the instantaneous area — they diverge after necking; Considère's criterion (dσ/dε = σ) marks necking onset.
- **Strain-rate sensitivity:** m = ∂lnσ/∂ln(ε̇) — high m means rate hardening (superplasticity near m ≈ 0.5); strain-rate jump tests measure it without specimen-to-specimen scatter.
- **Notch sensitivity:** elastic stress concentration (K_t) vs actual notch behavior — brittle materials fail near K_t·σ while ductile ones redistribute stress; design with the criterion matching the material.

## Practical workflow

### 1. Choose the test for the question

| Question | Test |
|---|---|
| Stiffness, yield, ductility | Uniaxial tensile (ASTM E8/E8M) |
| Quick strength comparison | Vickers hardness (ASTM E384) |
| Flaw tolerance | Fracture toughness K_IC (ASTM E399/E1820) |
| Cyclic service life | Fatigue S–N or da/dN (ASTM E466/E647) |
| High-temperature service | Creep rupture (ASTM E139) |

### 2. Prepare specimens correctly

1. Machine to the standard geometry with polished gauge sections — surface scratches are crack starters that lower measured ductility.
2. Align the specimen in the grips; bending during a "tensile" test invalidates the result (check with a strain-gauged dummy).
3. Control temperature and strain rate; record both — they are part of the result.
4. Test enough replicates: ≥5 for metals, ≥10–30 for brittle materials (Weibull needs data).

### 3. Extract properties honestly

1. Determine E from the initial linear region with an extensometer — crosshead displacement includes machine compliance.
2. Use the 0.2% offset method for yield; report the method — "yield strength" without it is ambiguous.
3. For fracture toughness, verify plane-strain validity criteria (thickness, crack length) before quoting K_IC.
4. Plot full curves, not just table values; the curve shape diagnoses necking, serrated flow, and premature failure.

### 4. Fractography — read the broken pieces

1. Examine fracture surfaces (SEM): dimples = ductile, cleavage facets = brittle, beach marks/striations = fatigue, intergranular = embrittlement.
2. Find the origin: inclusions, pores, and machining marks locate where failure started.
3. Match the fractography to the test data — a low elongation with dimpled fracture means a defect, not an intrinsically brittle material.

### 5. Run a fracture-toughness test correctly

1. Pre-crack by fatigue — a machined notch is not sharp enough; a real crack is mandatory for valid K_IC.
2. Load per ASTM E399/E1820 and check every validity criterion (P_max/P_Q, thickness, crack length) — invalid tests produce numbers, not toughness values.
3. For ductile materials, use J-integral or CTOD (elastic-plastic fracture mechanics) rather than forcing linear-elastic K_IC.

### 6. Quick-reference checklist

- [ ] Test standard identified (ASTM/ISO) and specimen geometry compliant
- [ ] Strain measured with extensometer/DIC, not crosshead displacement
- [ ] Specimen alignment verified (bending check)
- [ ] Temperature and strain rate recorded as part of the result
- [ ] Replicates: ≥5 for metals, ≥10–30 for brittle materials
- [ ] Yield determined by stated method (0.2% offset)
- [ ] Fracture surfaces examined (fractography) for every failure analysis
- [ ] Full stress–strain curves archived, not just table values

## Common pitfalls

- **Crosshead displacement as strain:** machine compliance inflates apparent elongation; use an extensometer or DIC for modulus and yield.
- **One test, one number:** a single tensile bar proves nothing — scatter is data, report it.
- **Hardness-to-strength conversion abuse:** empirical relations are alloy-family specific; don't convert across material classes.
- **Ignoring the standard:** non-standard specimen geometry makes your numbers incomparable with literature — follow ASTM/ISO or justify the deviation.
- **Testing at the wrong rate/temperature:** quasi-static room-temperature data doesn't predict impact or high-temperature service.
- **Survivorship bias in fatigue:** runouts (unbroken specimens) are data — use proper statistical treatment (staircase method), don't discard them.
- **Grip failures:** stress concentrations at the grips cause breaks outside the gauge section — use proper specimen geometry and alignment; discard grip breaks, don't average them in.
- **Testing composites like metals:** anisotropic materials need directional testing under the appropriate standards — a single "tensile strength" number misleads.

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 →