Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Q7046 Fastener Specifications

ASecurity

Validate the purchase description a threaded fastener is to be procured against, and derive the numbers a receiving inspection will check it by. Use when a parts list has to become something a supplier can quote and a buyer can accept: report the fields the description does not state, parse the metric thread designation and take the coarse pitch from the table only when none is stated, read tensile and yield strength out of the property class, compute the tensile stress area and proof load, a...

2 stars
0 votes
0 copies
0 views
Added 9/27/2026
ai-agentspython

Works with

claude code

Security Analysis

A100/100

Scanned 9/27/2026

Install to Claude Code

$npx -y skills add ashfordeOU/aero-agent-skills --skill q7046-fastener-specifications --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Q7046 Fastener Specifications?

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

Security grade badge for Q7046 Fastener Specifications
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ashfordeou-q7046-fastener-specifications/badge)](https://www.skillsdirectory.com/skills/ashfordeou-q7046-fastener-specifications)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: q7046-fastener-specifications
description: "Validate the purchase description a threaded fastener is to be procured against, and derive the numbers a receiving inspection will check it by. Use when a parts list has to become something a supplier can quote and a buyer can accept: report the fields the description does not state, parse the metric thread designation and take the coarse pitch from the table only when none is stated, read tensile and yield strength out of the property class, compute the tensile stress area and proof load, and cross-check the class against the material family and the coating against the class. Trigger: ecss, q-st-70-46-threaded-fasteners, fastener-purchase-description, fastener-property-class-strength, metric-thread-stress-area, fastener-proof-load, fastener-coating-embrittlement-conflict."
license: Apache-2.0
compliance: STANDARDS-REF
standards:
  - id: ecss
    reference-only: true
gated: false
domain: space-systems
pack: space-systems
compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"
metadata:
  domain: space-systems
  subdomain: ecss
  tags: [ecss, q-st-70-46-threaded-fasteners, q7046-fastener-specifications, fastener-purchase-description, fastener-property-class-strength, metric-thread-stress-area, fastener-proof-load, fastener-coating-embrittlement-conflict]
  version: 0.1.0
  author: Aero Agent Skills
---

# ECSS Threaded Fasteners — Specifications (space-systems/ecss/q7046-fastener-specifications)

Use when the task is the specifications clause of ECSS-Q-ST-70-46:
turning a fastener line on a parts list into a purchase description
that fixes the dimensions, the property class and the material, and
that carries the load figures acceptance will be judged against.

## Domain quick reference

- A fastener is bought against a standard and a designation, never
  against a description. The standard reference, the thread designation,
  the length, the property class, the material family, the coating, the
  head type and the locking feature are all buyable; "a small stainless
  cap screw" is not.
- The property class is not a lookup table, it is an encoding. A carbon
  or alloy steel class carries its nominal tensile strength in the first
  figure and ten times the ratio of yield to tensile in the second, so
  12.9 means 1200 MPa with a yield at nine tenths of it. Austenitic
  stainless classes are named the other way and are tabulated.
- The tensile stress area is taken on a diameter reduced by a fixed
  multiple of the pitch, not on the nominal diameter. Using the nominal
  diameter overstates an M6 by roughly a sixth, and every preload and
  margin downstream inherits it.
- Pitch is part of the size. A fine-pitch thread of the same nominal
  diameter has a larger stress area and a different mating part, so a
  designation with no pitch means the coarse pitch and nothing else.
- A diameter the coarse table does not carry has no implied pitch. The
  specification has to state one; assuming the nearest tabulated value
  silently buys a different thread.
- The class and the material have to be the same kind of thing. A
  stainless class on an alloy steel part, or a steel class on titanium,
  is a specification no supplier can satisfy and every supplier will
  interpret.
- The coating and the class interact. An electroplated finish puts
  hydrogen into a high-strength part, and above the risk threshold that
  is a conflict to resolve in the specification rather than a process
  note; cadmium carries its own restriction whatever the class.

## Workflow

1. Check the description against the required field set first and stop
   there if anything is missing; the numeric work on a half-specified
   part produces figures nobody should quote.
2. Parse the thread designation, taking the coarse pitch from the table
   when none is stated and refusing an untabulated diameter that states
   no pitch.
3. Read the tensile and yield strength out of the property class,
   refusing a class whose figures fall outside the encodings.
4. Compute the tensile stress area from diameter and pitch, then the
   proof load from the yield strength and the proof ratio, and report
   the tensile load alongside it.
5. Sanity-check the length against the diameter, then run the
   material-against-class and coating-against-class cross-checks.
6. Report the gaps, the parsed thread, the strengths, the loads and
   every conflict, and call the description buyable only when all three
   lists are empty.

## Pitfalls

- Computing the load on the nominal diameter. It is the single most
  common overstatement in a fastener calculation and it always errs
  towards the unsafe side.
- Leaving the pitch off an untabulated diameter. The part arrives with
  whichever pitch the supplier stocks, and it mates with nothing on the
  drawing.
- Treating the property class as a material. The class fixes the
  strength the part must reach; the material fixes what can reach it,
  and the specification owes both.
- Reading the second figure of a steel class as a yield strength in
  hundreds of MPa. It is a ratio; read that way, 10.9 becomes a
  900 MPa tensile part instead of a 1000 MPa one.
- Specifying an electroplated finish on a high-strength class and
  handling the embrittlement in a process note. The relief bake and its
  test belong in the purchase description, or the part arrives without
  them.
- Computing loads for a description that is still missing fields. The
  numbers look authoritative, get quoted downstream, and change when
  the missing fields are finally filled in.

## Behavior contract (gate 3)

The required-field check, the metric designation parser with its
coarse-pitch table and refusals, the property-class encoding for steel
and the tabulated stainless classes, the tensile stress area, the proof
and tensile loads, the length sanity check and the material and coating
cross-checks are exercised by the gate 3 contract test:
scripts/test_q7046_fastener_specifications.py against
scripts/q7046_fastener_specifications_logic.py (stdlib unittest,
offline). Run:
python3 scripts/test_q7046_fastener_specifications.py

## Compliance

- ECSS standards are freely downloadable (ESA); cite the source and
  paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.

Attribution

ashfordeOUashfordeOU
View sourceMore from ashfordeOU →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 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', ...

694821 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.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, 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.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →