Cancel anytime before day 7 and you pay nothing. We e-mail you 2 days before the trial ends.
How it works
1Use your own AI. Claude, ChatGPT or Gemini on any plan, free ones too. Claude Code and Cursor work as well.
2Load the skill. One click with the KMS connector (Library plan), or paste the file you buy.
3Write your goal. Your AI becomes this specialist and guides you step by step.
Example
You: We find defects too late and our SAP QM is barely used. Help me build inspection into goods receipt and production.
AI: Hartmut returns an inspection-plan and lot design, the QM trigger points in procurement and production, the results-recording and usage-decision flow, the notification...
Trademarks of their respective owners. KissMySkills is not affiliated with or endorsed by them.
Ask it something hard.
📎 hartmut-sap-qm-consultant.skillLOADED ✓
We find defects too late and our SAP QM is barely used. Help me build inspection into goods receipt and production.
CLAUDE · WITH THIS SKILLHartmut returns an inspection-plan and lot design, the QM trigger points in procurement and production, the results-recording and usage-decision flow, the notification process for defects, and the master data setup, with the MM and PP integration flagged for Priya and Farah.
Or have every skill inside your AI.
0:16 · no sound
Questions before you buy? A person answers, usually the same day: hello@kissmyskills.com
// the file itself
Read it before you buy it.
The first lines of the file your AI will read, exactly as delivered. Nothing rewritten for the page.
Use the name Once the file is loaded, talk to it by name: “Serge, check this page.” That is what the name is for. It also keeps several skills apart in one chat.
// the skill your AI runs on
You are Hartmut, a Senior SAP QM Consultant who designs inspection plans, sampling procedures and the usage decisions that post stock. You have been activated to help the user get inspection lots created and results recorded.
Drop Hartmut into Claude and get a Senior SAP Quality Management Consultant who designs inspection plans that catch the right defects without drowning inspectors in samples, wires QM into procurement and production so lots get created and stock gets blocked automatically, and configures usage decisions so good stock moves and bad stock does not. Hartmut works the way a strong quality team works: characteristics and plans first, then the inspection-type config that triggers lots, then the notification and certificate loop, so quality is a controlled process and not a spreadsheet next to the line. Hartmut covers the QM module end to end: quality planning (master inspection characteristics, catalogs and selected sets, sampling procedures and schemes, inspection plans and material specifications, dynamic modification rules), inspection processing (inspection lots by origin, results recording, sample calculation, defects recording, usage decisions, quality levels), quality notifications (customer complaint Q1, complaint against vendor Q2, internal problem Q3, the CAPA/8D corrective-action loop), quality certificates (certificate profiles, characteristic origins, incoming and outgoing certificates), QM in logistics (QM in procurement with quality info records and technical delivery terms, QM in production, QM in sales), batch management interplay and the Q-inspection stock, and the configuration behind inspection types, control keys, and material QM view settings. Hartmut never jumps straight to config. He works in this order and states his assumptions out loud: 1. Understand what quality risk we are controlling. What can go wrong, at which point in the process, what does an escape cost, and who decides pass/fail? The inspection design follows the risk, not a template - a pharma active ingredient and a packaging carton do not get the same plan. 2. Define the characteristics and catalogs first. Master inspection characteristics (quantitative with tolerances, or qualitative against a selected set), catalogs and code groups for defects and usage decisions. These are the reusable vocabulary; everything downstream references them, so they come first. 3. Design the inspection plan and sampling. Inspection plan with operations and characteristics, the sampling procedure (100%, fixed, statistical to an AQL scheme) and dynamic modification so good history relaxes inspection and bad history tightens it. He sizes the sample to the risk, not to habit. 4. Turn on the right inspection types. The inspection type in the material QM view is what actually creates a lot (01 goods receipt from purchasing, 03 in-process, 04 goods receipt from production, 08 stock transfer, 09 recurring, 89 manual...). Hartmut confirms the inspection type, control key, and posting-to-inspection-stock setting, because "no lot was created" is almost always a missing or wrong inspection type. 5. Close the results and usage-decision loop. Results recording against characteristics, defect recording into a notification, and a usage decision that posts stock (to unrestricted, blocked, or scrap) and updates the quality level. The UD is where quality control becomes a stock movement. 6. Wire the notifications and certificates. Complaints and internal problems flow through quality notifications with tasks and the corrective-action loop; certificates are produced from certificate profiles for outgoing deliveries and checked on incoming goods. He designs those, not leaves them manual. 7. Prove it and integrate it. Hartmut writes the test script and names the MM/PP/PM/SD/batch handshakes (a GR that must create a 01 lot, a production order confirmation that must create an 04 lot, a delivery that must carry a certificate), and marks anything the customer must supply rather than inventing tolerances or material numbers. · Quality planning: master inspection characteristics (quantitative/qualitative, tolerances, control indicators), catalogs and code groups, selected sets, inspection plans and material specifications, inspection points, and reference operation sets. · Sampling: sampling procedures and sampling schemes, AQL and statistical sampling, 100% and fixed sampling, dynamic modification rules and inspection stages, sample-size calculation. · Inspection lots: inspection types by origin (01, 03, 04, 05, 08, 09, 89 and others), lot creation triggers, inspection stock (Q-stock), quality levels, and the control key. · Results and usage decisions: results recording (characteristic and summarized), defects recording, valuation, usage decisions and UD codes, stock postings from the UD, and follow-up actions.
SKILL.md · 65 lines · instant download
// what's inside
What's inside this skill
Inspection lots, plans, and characteristics
Quality notifications and usage decisions
QM in procurement and production (MM/PP integration)
Quality certificates and batch management
Manufacturers on SAP that record quality after the fact and want inspection built into the process.
// two ways to get it
Use it inside your AI, or download it once.
Library plan
This skill and 2,500+ others, inside your chat
$12/mocancel anytime, or $99 a year
All 2,500+ skills, prompt packs and agents, loaded the moment you ask
Nothing to download or paste: connect once in Claude, ChatGPT, Claude Code or Cursor
New skills every week and 10 catalog files a month to download
Download after checkout and paste it into any AI chat
One file, no updates, no connector
30-day money-back guarantee
Already on Library or Both? This one is included, no need to buy the file.
// ask your assistant
Or let your AI set up this skill for you.
Go to kissmyskills.com/pages/connector and set up the "SAP QM Consultant AI Skill - Hartmut" skill (handle: hartmut-sap-qm-consultant) for me
Paste it into Claude, ChatGPT, Claude Code, Cursor or Codex. Your AI walks you through connecting KissMySkills (about 3 minutes, 7-day free trial) and loads the skill. What your AI will read →
What you're actually buying
Drop Hartmut into Claude and get a senior SAP Quality Management consultant who builds inspection into your processes so quality is controlled, not just recorded after the fact.
Hartmut configures SAP Quality Management: inspection lots and inspection plans, quality notifications, results recording and usage decisions, quality certificates, batch management with QM, and QM in procurement and production, integrated with MM and PP. He designs where inspection triggers in the process so defects are caught at goods receipt or in production, not discovered by the customer, and he keeps the master data maintainable.
What you get
→Inspection lots, plans, and characteristics
→Quality notifications and usage decisions
→QM in procurement and production (MM/PP integration)
→Quality certificates and batch management
📄 hartmut-sap-qm-consultant.skillUnder 2 min installWorks with Claude, ChatGPT & any AI chat
How to install
Download the .skill package, open Claude, paste SKILL.md into your Project Instructions or system prompt, describe your requirement, and Hartmut builds the answer. Includes a full worked example so you see exactly what you get.
// how to install
Under 2 minutes
Four steps. Any AI chat.
01
Download the file
After checkout, the download link lands in your inbox. Save the .skill file: Claude takes it as it is.
02
Open your AI chat
Any AI chat you already use: Claude, ChatGPT, Gemini, Grok, Copilot or another.
03
Add it to your AI
Claude: turn on code execution in Settings → Capabilities, then Customize → Skills → + → Create skill → Upload a skill and pick the .skill file. ChatGPT, Gemini and others: open the .skill file like a .zip archive and paste SKILL.md into custom instructions or Project instructions.
04
Start working
Your AI is now configured as a specialist. Ask it anything inside its domain.
No technical knowledge required.
2,500+skills, prompts and agents in the marketplace
Configure SAP QM: set up inspection plans and lots, wire QM into procurement and production, and design the results and decision flow. Load it once into Claude Projects and you get a configured SAP QM Consultant without re-explaining context at the start of every session. Validate every change in a sandbox or quality system against your org's real Customizing, data, and release, and follow your transport and change-control process before moving anything to production.
How do I install this skill file?+
Download the .skill package (it contains SKILL.md), then, in Claude, turn on code execution in Settings → Capabilities and add it under Customize → Skills → + → Create skill → Upload a skill (in ChatGPT, Gemini or another AI, open it as a .zip and paste SKILL.md into Project instructions or custom instructions), add your own context and start your first session. Works with Claude, ChatGPT, or any AI chat that accepts system prompts.
Which AI tools does this skill work with?+
Works with Claude (recommended), ChatGPT, Gemini, Perplexity and Copilot, and any AI chat that accepts system prompts. Claude Projects gives the best results.
How is this different from using Claude without the Hartmut skill?+
Without a skill file your AI starts every session as a general assistant. With Hartmut loaded it applies SAP QM Consultant methodology from the first message, with consistent quality every time. Validate every change in a sandbox or quality system against your org's real Customizing, data, and release, and follow your transport and change-control process before moving anything to production.
Ready to give your AI a specialist?
This one and 2,500+ others, inside Claude, ChatGPT, Claude Code, Codex or Cursor. Cancel anytime.