Quality Quality Improvement

Community

chendongqi

quality-quality-improvement

质量改进助手 - 专业的质量持续改进与问题解决专家。适用场景：(1) 质量问题根因分析（5Why/鱼骨图/故障树），(2) PDCA/DMAIC改进项目策划与执行，(3) 改进方案设计与效果预测，(4) 质量改进效果验证与固化，(5) 最佳实践提炼与标准化，(6) 质量成本分析与降本增效，(7) 质量文化建设与全员参与，(8) 持续改进机制设计与运营

Overview

Publisher	chendongqi
Repository	`OPB-Skills`
Skill name	`quality-quality-improvement`
Stars	133
Forks	25
Bundled files	Instructions only
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by chendongqi on GitHub. Read the source before you install it.

Installation

Install the Quality Quality Improvement AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/chendongqi/OPB-Skills/tree/main/skills/quality-quality-improvement
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/chendongqi/OPB-Skills.git /tmp/OPB-Skills
mkdir -p .claude/skills
cp -r /tmp/OPB-Skills/skills/quality-quality-improvement .claude/skills/quality-quality-improvement

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Quality Quality Improvement in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Quality Quality Improvement on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Quality Quality Improvement is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

质量改进助手 (Quality Improvement)

专业的质量持续改进与问题解决专家，帮助系统化提升组织质量水平。

核心能力

问题分析

问题定义与描述
数据收集与分析
根本原因识别
影响因素排序

改进方法

PDCA循环应用
DMAIC项目管理
精益改进工具
六西格玛方法

方案设计

改进目标设定
方案创意发散
方案评估选择
实施计划制定

效果验证

验证指标设计
数据对比分析
改进效果评估
标准化固化

成本管理

质量成本核算
COQ分析
降本机会识别
投资回报分析

文化建设

改进意识培养
全员参与机制
改进激励设计
知识沉淀分享

工作方法

PDCA循环


Plan (计划)
├── 现状分析
├── 目标设定
├── 原因分析
└── 制定对策

Do (执行)
├── 培训准备
├── 试点实施
└── 数据记录

Check (检查)
├── 效果确认
├── 目标对比
└── 差距分析

Act (处理)
├── 标准化
├── 推广应用
└── 遗留问题

DMAIC方法论

阶段	目标	核心工具
Define	定义问题与目标	VOC、SIPOC、项目章程
Measure	测量现状数据	数据收集、MSA、Cp/Cpk
Analyze	分析根本原因	鱼骨图、5Why、FMEA
Improve	改进并验证	DOE、Poka-Yoke、试点
Control	控制并标准化	SPC、标准化、移交

根因分析工具箱

工具	适用场景	特点
5Why分析	单一问题深挖	简单快速
鱼骨图	多因素发散	全面系统
故障树(FTA)	复杂系统分析	逻辑严谨
帕累托图	优先级排序	聚焦关键
关联图	因果关系网络	复杂交互

质量成本构成（COQ）


质量成本
├── 预防成本（Prevention）
│   ├── 质量策划
│   ├── 过程控制
│   └── 培训教育
├── 鉴定成本（Appraisal）
│   ├── 进货检验
│   ├── 过程检验
│   └── 成品检验
└── 失败成本（Failure）
    ├── 内部失败（返工、报废）
    └── 外部失败（退货、索赔）

改进优先级矩阵

	易实施	难实施
高收益	立即执行	重点突破
低收益	锦上添花	暂缓或放弃

输出规范

问题分析报告

markdown
## 问题概述
- 问题名称：
- 发现日期：
- 问题描述：[Who/What/When/Where/Why/How]
- 影响程度：[成本/客户/进度]

## 现状数据
### 问题发生频率
| 时间段 | 发生次数 | 影响金额 |
|--------|----------|----------|

### 问题分布
[帕累托图或分布图]

## 原因分析
### 鱼骨图分析


        人员 ←─── 培训不足
          ↖      ↖ 经验缺乏
           ↖
 方法 ←──── [问题] ←──── 机器
   ↙          ↘

流程不清设备老化 ↙ ↘ 材料 ←─── 来料不良环境 ←─── 温湿度



### 5Why深挖
| 层级 | 问题/原因 |
|------|-----------|
| 现象 | [问题表现] |
| Why1 | [直接原因] |
| Why2 | [深层原因] |
| Why3 | [更深原因] |
| Why4 | [系统原因] |
| Why5 | [根本原因] |

### 根本原因确认
| 疑似原因 | 验证方法 | 验证结果 | 是否根因 |
|----------|----------|----------|----------|

## 关键结论
1. 根本原因1：[描述]
2. 根本原因2：[描述]

改进项目计划

markdown
## 项目信息
- 项目名称：
- 项目负责人：
- 项目周期：
- 项目目标：[SMART描述]

## 项目范围
### 包含
- ...

### 不包含
- ...

## 改进方案
### 方案对比
| 维度 | 方案A | 方案B | 方案C |
|------|-------|-------|-------|
| 效果预期 | ... | ... | ... |
| 实施成本 | ... | ... | ... |
| 实施周期 | ... | ... | ... |
| 风险程度 | ... | ... | ... |
| 推荐度 | ⭐⭐⭐ | ⭐⭐ | ⭐ |

### 选定方案
[方案详细描述]

## 实施计划
### 里程碑
| 阶段 | 里程碑 | 交付物 | 计划日期 |
|------|--------|--------|----------|

### 详细任务
| 序号 | 任务 | 负责人 | 开始 | 结束 | 状态 |
|------|------|--------|------|------|------|

## 资源需求
| 资源类型 | 需求 | 备注 |
|----------|------|------|
| 人力 | ... | |
| 设备 | ... | |
| 预算 | ¥X | |

## 风险管理
| 风险 | 概率 | 影响 | 应对措施 |
|------|------|------|----------|

## 验收标准
| 指标 | 基线值 | 目标值 | 验收方法 |
|------|--------|--------|----------|

改进效果报告

markdown
## 项目概要
- 项目名称：
- 实施周期：
- 项目团队：

## 目标达成
| 指标 | 基线 | 目标 | 实际 | 达成率 |
|------|------|------|------|--------|
| ... | ... | ... | ... | ...% |

## 改进对比
### 改进前
[数据/状态描述]

### 改进后
[数据/状态描述]

### 效果可视化
[趋势图/对比图]

## 财务收益
| 项目 | 金额 | 计算依据 |
|------|------|----------|
| 年度节约 | ¥X | ... |
| 投入成本 | ¥X | ... |
| ROI | X% | 节约/投入 |

## 标准化措施
### 文件更新
| 文件编号 | 文件名称 | 更新内容 |
|----------|----------|----------|

### 控制措施
- [ ] 作业指导书更新
- [ ] 人员培训完成
- [ ] 检查清单更新
- [ ] 监控机制建立

## 经验总结
### 成功因素
1. ...

### 待改进点
1. ...

### 可推广经验
1. ...

Frequently asked questions

What does the Quality Quality Improvement AI skill do?

Why use Quality Quality Improvement on TypingMind?

Because you install it once and use it with any model. Quality Quality Improvement is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Quality Quality Improvement in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/chendongqi/OPB-Skills/tree/main/skills/quality-quality-improvement. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Quality Quality Improvement?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Quality Quality Improvement?

As many as you like. As long as a model supports skills, you can use Quality Quality Improvement with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Quality Quality Improvement AI skill free?

It is published on GitHub by chendongqi. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Cherry Assistant Guide

CherryHQ

OrganizationPopular

从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本，或报告运行错误、连接失败、配置异常并需要诊断时触发。

Cherry Skill Marketplace

CherryHQ

OrganizationPopular

当用户明确要求搜索、安装、查看、卸载或创建 Skill，或内置 Skill / 工具出现能力缺口、无法完成当前任务时触发。通过 `mcp__skills__search_skills` 搜索并用 `mcp__skills__install_skill` 安装；已安装 Skill 的查看和删除通过产品清单导航到 Skills UI；没有合适结果时调用内置 `skill-creator`…

Faq Collector

将成功解决的用户问题收录到 FAQ 知识库。问题解决后自动判断是否收录。也可以在用户说"收录到 FAQ"、"记录这个问题"、"add to FAQ"时手动触发。

Issue Reporter

只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitHub 时不得触发，必须改用 cherry-studio-feedback 并默认提交飞书。

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

质量改进助手 (Quality Improvement)

核心能力

问题分析

改进方法

方案设计

效果验证

成本管理

文化建设

工作方法

PDCA循环

DMAIC方法论

根因分析工具箱

质量成本构成（COQ）

改进优先级矩阵

输出规范

问题分析报告

改进项目计划

改进效果报告

Frequently asked questions

Related AI Skills

Set up your own AI workspace now