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

Quality Control Plan

ASecurity

Draft a control plan for a process step: what is checked, how often, and what happens on a fail. Use when the user mentions control plan, quality plan, inspection plan, process control plan, or asks for a control plan. Manufacturing and quality skill by Yasir Jilani.

2 stars
0 votes
0 copies
0 views
Added 9/30/2026
ai-agentspythonreactawsgitapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/30/2026

$npx -y skills add SYasJ/claude-business-skills --skill quality-control-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quality Control Plan?

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

Security grade badge for Quality Control Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/syasj-quality-control-plan/badge)](https://www.skillsdirectory.com/skills/syasj-quality-control-plan)

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: quality-control-plan
description: "Draft a control plan for a process step: what is checked, how often, and what happens on a fail. Use when the user mentions control plan, quality plan, inspection plan, process control plan, or asks for a control plan. Manufacturing and quality skill by Yasir Jilani."
license: MIT
compatibility: Agent Skills standard. No network access, extra packages, or credentials required.
metadata:
  author: Yasir Jilani
  version: "1.0.0"
  domain: manufacturing
---

<!-- GENERATED FILE - edits here are overwritten by scripts/generate.py.
     Edit the 'quality-control-plan' entry in source/, then run:
       python3 scripts/generate.py && python3 scripts/validate.py
     See CONTRIBUTING.md. -->

# Quality Control Plan

Draft a control plan for a process step: what is checked, how often, and what happens on a fail.

## When to use this skill

Use this skill when the user:

- control plan
- quality plan
- inspection plan
- process control plan

## When not to use this skill

- The user wants a different domain's specialist skill.
- The task requires a licensed professional to decide, and the user only needs a referral note rather than a draft.
- The request asks you to deceive, evade a control, or hide material facts.

## Professional boundary

Quality and safety procedures are drafts for the site's quality system. Do not bypass a hold, calibration, or safety step.

## Operating boundaries

- Use only information the user provides or files they explicitly ask you to read. Do not invent metrics, laws, citations, prices, credentials, or clinical facts.
- Do not ask for passwords, API keys, tokens, seed phrases, one-time codes, or payment card data.
- Do not send data to an external service, install packages, or add network calls as part of this skill.
- Separate facts, assumptions, and recommendations. If a required input is missing, state the assumption or ask one focused question.
- If the user asks you to deceive a person, evade a control, forge a record, or cause harm, stop. Offer a legitimate alternative.
- Work product that affects money, employment, health, safety, or legal rights is a draft for a qualified human to review before it is used.

## Inputs to collect

- The characteristic
- The method
- The frequency
- The reaction to a fail

## Workflow


### 1. Step 1

Name the characteristic that matters to the customer or the safety rule they cited.
### 2. Step 2

Specify method and frequency they can staff.
### 3. Write the reaction to a fail

stop, sort, or call. A fail with no reaction is a finding.
### 4. Step 4

Identify the owner of the check.
### 5. Step 5

Do not loosen a limit they said is safety-related.
### 6. Step 6

Link the plan to the work instruction rather than creating a second unofficial standard.

## Output

Deliver a **control plan**.

- Purpose of this control plan, in two sentences.
- Facts the user supplied, listed separately from assumptions.
- The work itself, in the structure the workflow names.
- Open questions, risks, and the single next action with an owner.
- What a qualified reviewer still needs to confirm, if the domain is regulated.

## Quality bar

- Every number, date, name, and citation came from the user or is marked as an assumption.
- The artifact can be used without reading this skill again.
- Recommendations are specific enough that someone could accept or reject them.
- Boundaries were respected: no credentials requested, no unsupported professional claim, no deception.

## Example

### Scenario

Gus Moretti, plant manager at Redline Parts in Nisku, needs a control plan by 30 September 2026. A plan checks a safety dimension weekly because daily checks feel expensive.

### Example data

```text
From: Gus Moretti, plant manager
Organization: Redline Parts, Nisku
Date: 14 September 2026
Needed by: 30 September 2026

A plan checks a safety dimension weekly because daily checks feel expensive.

The characteristic: Line 2, recorded 14 September 2026. No supporting file attached
The method: the method in the ask. No second design attached
The frequency: Line 2, recorded 14 September 2026. No supporting file attached
The reaction to a fail: Line 2; Lot 26-0914. Both unassigned as of 14 September 2026
```

### Example outcome

**Control plan**
To: Gus Moretti, plant manager, Redline Parts
Date: 14 September 2026 · Needed by: 30 September 2026

**Decision**
Keeps the safety check at the frequency their rule requires and flags the cost as a separate decision.

**What the file supports**

| Input | Value | Status |
| --- | --- | --- |
| The characteristic | Line 2, recorded 14 September 2026. No supporting file attached | Needs confirmation |
| The method | the method in the ask. No second design attached | Carried into the draft |
| The frequency | Line 2, recorded 14 September 2026. No supporting file attached | Carried into the draft |
| The reaction to a fail | Line 2; Lot 26-0914. Both unassigned as of 14 September 2026 | Needs confirmation |

**How this draft was built**

**1. Name the characteristic that matters to the customer or the safety rule they cited**

**2. Specify method and frequency they can staff**

**3. Write the reaction to a fail**  
stop, sort, or call. A fail with no reaction is a finding.

**4. Identify the owner of the check**

**5. Do not loosen a limit they said is safety-related**

**Deliberately not done**
- A check with no reaction.
- Loosening a safety limit.
- An unstaffed frequency.

**Open items for a human**
- Confirm every row marked *Needs confirmation* above before this leaves draft.
- Anything absent from the file stayed absent. No figure, date, or name was supplied from outside it.

Next: Gus Moretti by 30 September 2026. This is a draft, not a sign-off.

## Anti-patterns

- A check with no reaction
- Loosening a safety limit
- An unstaffed frequency

## Related skills

- `incoming-inspection`
- `work-instruction`

Attribution

SYasJSYasJ
View sourceSee grades on GitHubMore from SYasJ →
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', ...

698431 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 →