Token导航 LogoToken导航

Agent Skill · 研究检索

pfmea(pfmea 搜索)

pfmea 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

pfmea 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 52,984。

总安装 541周安装 23GitHub Stars 1下载 190核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:pfmea(pfmea 搜索)
来源仓库:https://github.com/robdtaylor/personal-ai-infrastructure
仓库路径:skills/pfmea
安装命令:
npx skills add https://github.com/robdtaylor/personal-ai-infrastructure --skill Pfmea
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/robdtaylor/personal-ai-infrastructure --skill Pfmea

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。pfmea 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合在关键词搜索、任务场景或来源线索下快速定位候选结果。可结合仓库、安装命令和 README 核验具体用法。安装前建议确认权限范围和维护状态及是否触发联网或文件操作。注意避免误执行命令或越权访问敏感数据。

来源仓库内路径:skills/pfmea

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/robdtaylor/personal-ai-infrastructure --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

pfmea 怎么安装?

在终端执行 npx skills add https://github.com/robdtaylor/personal-ai-infrastructure --skill Pfmea。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

pfmea 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

pfmea 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

pfmea 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

pfmea 用的人多吗?

公开数据是累计安装 541 次,近一周安装 23 次,下载 190 次,GitHub 1 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

pfmea 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
pfmea

pfmea 搜索 · 本页

5411只读MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Process FMEA (PFMEA)

When to Activate This Skill

  • "Create a PFMEA for [process]"
  • "What are the failure modes for [operation]?"
  • "Calculate RPN for [risk scenario]"
  • "Rate severity/occurrence/detection for [failure]"
  • "Identify process risks"
  • "FMEA analysis for [part/process]"

AIAG-VDA 7-Step Methodology

Step 1: Planning and Preparation

  • Define scope and boundaries
  • Identify team members (cross-functional)
  • Gather documentation (process flow, control plan, drawings)
  • Review lessons learned from similar processes

Step 2: Structure Analysis

  • Define process steps from process flow diagram
  • Create process tree (System > Sub-system > Process Element)
  • Identify interfaces between steps
  • Link to product characteristics

Step 3: Function Analysis

  • Define function of each process step
  • Identify product/process requirements
  • Link to customer/engineering specifications
  • Document special characteristics (CC/SC)

Step 4: Failure Analysis

  • Identify failure modes (how can step fail to perform function?)
  • Determine failure effects (consequences to customer/next operation)
  • Identify failure causes (why would failure mode occur?)
  • Chain: Cause → Failure Mode → Effect

Step 5: Risk Analysis

  • Rate Severity (S) of effects: 1-10
  • Rate Occurrence (O) of causes: 1-10
  • Rate Detection (D) of controls: 1-10
  • Calculate Action Priority (AP) or RPN

Step 6: Optimization

  • Prioritize high-risk items
  • Develop countermeasures (hierarchy: Eliminate > Substitute > Engineer > Admin > Detect)
  • Assign responsibility and target dates
  • Re-rate after countermeasures

Step 7: Results Documentation

  • Document all analysis
  • Track countermeasure completion
  • Update Control Plan linkage
  • Archive for lessons learned

Rating Scales (MNMUK Standard)

Severity (S) - Effect on Customer/Process

RatingCriteriaMNMUK Examples
10Affects safety without warningBrake component failure, no containment possible
9Affects safety with warningSafety critical dimension OOS, detectable at assembly
8Product inoperable, 100% scrapPart cannot be reworked, total loss
7Product operable but degraded, customer dissatisfiedPerformance below spec, customer complaint
6Product operable, comfort/convenience affectedCosmetic defect, minor fit issue
550% of product may need reworkSignificant rework required
4Product requires sorting/reworkSorting operation needed
3Minor rework at stationIn-station repair possible
2Slight inconvenienceMinor adjustment
1No effectNo discernible impact

Occurrence (O) - Likelihood of Cause

RatingFailure RateCpk EquivalentMNMUK Examples
10Very high: ≥100/1000<0.33New process, no controls
9High: 50/1000≥0.33Known problem process
8High: 20/1000≥0.51Similar process had failures
7Moderately high: 10/1000≥0.67Occasional failures observed
6Moderate: 2/1000≥0.83Infrequent failures
5Moderately low: 0.5/1000≥1.00Controlled process, some failures
4Low: 0.1/1000≥1.17Well-controlled process
3Very low: 0.01/1000≥1.33Capable and controlled
2Remote: 0.001/1000≥1.50Proven design and controls
1Nearly impossible: ≤0.001/1000≥1.67Failure eliminated by design

Detection (D) - Ability to Detect Before Customer

RatingDetection CapabilityMNMUK Examples
10No detection possibleNo inspection, no opportunity to detect
9Unlikely to detectRandom sampling only, infrequent
8Low: Visual inspection by operator100% visual check, variable attention
7Very low: Double visual inspectionTwo operators check
6Low: Charting/SPCControl charts, trend monitoring
5Moderate: Attribute gagingGo/No-go gaging
4Moderately high: Variable gagingMeasurement with limit checking
3High: Automated in-process testAutomatic measurement, alarm
2Very high: Error-proofingPoka-yoke prevents defect production
1Almost certain: Error-proofing prevents causeDesign makes failure impossible

Action Priority (AIAG-VDA Approach)

Instead of or in addition to RPN, use Action Priority:

PriorityCriteriaAction Required
HIGHS=9-10 (any O, D) OR S=7-8 with O≥4 AND D≥4Immediate action required
MEDIUMS=5-8 with O≥4 OR D≥4Action recommended
LOWAll othersMonitor and document

RPN Thresholds (MNMUK Standard)

RPN RangePriorityRequired Action
≥120CriticalImmediate countermeasure, cannot ship without action
80-119HighCountermeasure required before PPAP
40-79MediumCountermeasure recommended
<40LowMonitor, no immediate action

Note: Any Severity ≥8 requires action regardless of RPN.

Countermeasure Hierarchy

When addressing failure modes, apply controls in this priority order:

  1. Eliminate - Design out the failure mode entirely
  2. Substitute - Replace with less hazardous process/material
  3. Engineer - Install physical safeguards, poka-yoke
  4. Admin - Procedures, training, work instructions
  5. Detect - Inspection, testing, monitoring

Special Characteristics

Critical Characteristics (CC)

  • Safety or regulatory impact
  • Marked with shield symbol or (CC)
  • Requires enhanced controls
  • Mandatory documentation

Significant Characteristics (SC)

  • Fit, function, or durability impact
  • Marked with diamond or (SC)
  • Requires appropriate controls
  • SPC typically required

Output Format Requirements

CRITICAL: Every PFMEA response MUST be complete. Never truncate or cut off mid-entry. Every failure mode listed MUST have:

  • All causes fully documented
  • S/O/D ratings for EVERY cause row
  • RPN calculated for EVERY row
  • Current controls listed
  • Recommended actions specified
  • After-action ratings included

If the full PFMEA would be very long, reduce the NUMBER of failure modes covered, but each one included MUST be 100% complete. Do not start a failure mode entry you cannot finish.

Output Format

When generating PFMEA content:

# PFMEA: [Part/Process Name]
**Part Number**: [P/N]
**Process**: [Description]
**FMEA Number**: PFMEA-[DEPT]-[SEQ]
**Revision**: [Rev] | **Date**: [YYYY-MM-DD]
**Team**: [Names/Roles]

## Process Step: [Step Name]

### Failure Mode 1: [Description]
**Function**: [What the step should do]
**Effect**: [What happens if it fails]
**Cause**: [Why it would fail]

| S | O | D | RPN | AP |
|---|---|---|-----|-----|
| X | X | X | XXX | H/M/L |

**Current Controls**:
- Prevention: [Current prevention measures]
- Detection: [Current detection measures]

**Recommended Actions**:
- [ ] [Action description] - Owner: [Name] - Due: [Date]

**After Action**:
| S | O | D | RPN | AP |
|---|---|---|-----|-----|
| X | X | X | XXX | H/M/L |

Department-Specific Guidance

Machine Shop

  • Common failure modes: Dimensional OOS, surface finish, tool wear
  • Focus on: Fixturing, program parameters, tool life management
  • Key controls: First piece inspection, SPC, gage R&R

Damper Assembly

  • Common failure modes: Leak, incorrect torque, missing component
  • Focus on: Seal integrity, fastener torque, component presence
  • Key controls: Leak test, torque verification, poka-yoke

LVA (Low Volume Assembly)

  • Common failure modes: Wrong component, incorrect orientation, damage
  • Focus on: Part identification, assembly sequence, handling
  • Key controls: Visual verification, traveler documentation

FML (Final Manufacturing Line)

  • Common failure modes: Test failure, labeling error, packaging damage
  • Focus on: Final test parameters, traceability, packaging
  • Key controls: Automated test, barcode verification, packaging audit

Integration with Related Skills

ControlPlan

PFMEA feeds directly into Control Plan:

  • High S/O items require enhanced inspection
  • Detection controls become Control Plan methods
  • Special characteristics flow to Control Plan

Load: read ~/.claude/skills/Controlplan/SKILL.md

AutomotiveManufacturing

Work instructions should reflect PFMEA findings:

  • High-risk steps highlighted
  • Operator controls documented
  • Quality checkpoints specified

Load: read ~/.claude/skills/Automotivemanufacturing/SKILL.md

A3criticalthinking

When PFMEA reveals issues:

  • Use 5 Whys for root cause analysis
  • Fishbone diagram for cause identification
  • A3 format for countermeasure planning

Load: read ~/.claude/skills/A3criticalthinking/SKILL.md

Supplementary Resources

For detailed guidance: read ~/.claude/skills/Pfmea/CLAUDE.md

For templates: ls ~/.claude/skills/Pfmea/templates/

For rating scales: read ~/.claude/skills/Pfmea/reference/rating-scales.md

For common failure modes: read ~/.claude/skills/Pfmea/reference/common-failure-modes.md

平台分布

Claude Code

30.44%
按下载量换算58

windsurf

21.75%
按下载量换算41

trae

17.59%
按下载量换算33

OpenCode

13.23%
按下载量换算25

Cursor

7.27%
按下载量换算14

Codex

3.64%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills