Generate
alirezarezvani/claude-skills
Generate Playwright tests. An agent skill from alirezarezvani/claude-skills.
Generates or completes 8D reports (Eight Disciplines) from customer complaint data, with D1–D8 fill-in guidance and a standard template.
$ npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills complaint-8d-report --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/complaint-8d-report .claude/skills/complaint-8d-report && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "complaint-8d-report" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/complaint-8d-report into .claude/skills/complaint-8d-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "complaint-8d-report", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/complaint-8d-reportType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills complaint-8d-report --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/complaint-8d-report .agents/skills/complaint-8d-report && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "complaint-8d-report" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/complaint-8d-report into .agents/skills/complaint-8d-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "complaint-8d-report", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills complaint-8d-report --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/complaint-8d-report .cursor/skills/complaint-8d-report && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "complaint-8d-report" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/complaint-8d-report into .cursor/skills/complaint-8d-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "complaint-8d-report", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/LeoYeAI/openclaw-master-skills.git --path skills/complaint-8d-report--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills complaint-8d-report --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/complaint-8d-report .gemini/skills/complaint-8d-report && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "complaint-8d-report" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/complaint-8d-report into .gemini/skills/complaint-8d-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "complaint-8d-report", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install LeoYeAI/openclaw-master-skills complaint-8d-reportInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/complaint-8d-report .github/skills/complaint-8d-report && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "complaint-8d-report" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/complaint-8d-report into .github/skills/complaint-8d-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "complaint-8d-report", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills complaint-8d-report --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/complaint-8d-report .opencode/skills/complaint-8d-report && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "complaint-8d-report" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/complaint-8d-report into .opencode/skills/complaint-8d-report/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "complaint-8d-report", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
complaint-8d-reportGenerates or completes 8D reports (Eight Disciplines) from customer complaint data, with D1–D8 fill-in guidance and a standard template.
Complaint 8d Report is an agent skill from LeoYeAI/openclaw-master-skills. Generates or completes 8D reports (Eight Disciplines) from customer complaint data, with D1–D8 fill-in guidance and a standard template. Supports customer-specific formats (one supplier, multiple customers with different 8D layouts). Use for customer complaints, quality deviations, and defect recurrence prevention.
Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files (for example `README.md`, `_meta.json` and `clawhub.json`).
The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Complaint 8d Report loads about 4.2k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 1,357 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,357 words, ~4,214 tokens.
.claude/skills/complaint-8d-report/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.Generates or completes an 8D report from user-provided complaint data (product, symptom, quantity, customer, dates, etc.) and guides step-by-step completion of D1–D8. Supports chart/diagram analysis (e.g. fishbone, 5-Why, Pareto), image/video evidence for verification, and document attachments for specs and revised procedures. Handles customer-specific formats: one supplier may need different 8D layouts for different customers; the skill can use a chosen template or match a user-provided format. Output is structured Markdown suitable for pasting into Word, Excel, or internal systems.
Scenario: A supplier serves multiple customers; each customer requires 8D/CAR in a different format (different section titles, table columns, order of D1–D8, or extra blocks such as "Supplier response date" or "Cost of quality").
How to handle:
{baseDir}/formats/ (e.g. formats/Customer-A.md or formats/automotive-oem.md). If yes, use that file’s section order and headings to build the report.formats/ — see formats/README.md."[To be filled].formats/ can contain one file per customer or format (e.g. Customer-A.md, Customer-B.md). Each file lists the report structure: section titles in order and, if needed, table column headers. The agent then fills content according to this structure. See {baseDir}/formats/README.md and any example in formats/ for the expected format.Mapping rule: The content of 8D (team, 5W2H, containment, root cause, permanent actions, implementation, recurrence prevention, closure) stays the same; only section titles, order, and table/field names change to match the customer template.
| Where | Charts / diagrams | Images or video | Documents |
|---|---|---|---|
| D2 | Optional: defect location sketch, timeline | Recommended: defect photos, limit sample, customer evidence | Spec sheet, drawing, limit sample doc ref |
| D3 | Optional: containment flow | Optional: quarantine area, sorted lots | N/A |
| D4 | Recommended: 5-Why tree, fishbone, Pareto, cause–effect matrix | Optional: reproduction test photos/video, failure mode | Process doc / FMEA excerpt (before) |
| D5 | Optional: before/after data chart, trial summary | Recommended: verification photos or short video (trial, measurement) | Trial report, test protocol |
| D6 | Optional: Cpk/trend chart | Optional: updated work area, gauge | Recommended: revised SOP/spec (cover or excerpt), approval |
| D7 | Optional: process change summary | Optional: training photo | Recommended: training record, lesson learned doc ref |
| D8 | N/A | Optional: team/customer sign-off photo | Recommended: customer closure confirmation, distribution list |
[Attach: defect photo] or [Attach: video – reproduction test]; remind the user to attach files when exporting to Word or to upload to the report system.[Attach: spec rev X] or [Attach: SOP XYZ rev 2 excerpt]; ask for document number and revision when the user mentions a spec or procedure.{baseDir}/formats/<name>.md (normalize to lowercase, hyphens). If found, use that structure; if not, use the standard template and offer to create a format file for next time.[To be filled] or [Fill from context above] for missing items. [Attach: defect photo], [See fishbone diagram]) and remind the user to add the file when finalizing the report. 8D-{case-number}-{date}.md (or the filename style the customer expects). Remind that images, videos, and document excerpts must be attached in Word or the final report system.The template below is the default layout. When a customer-specific format is selected (step 1), use that format’s section order and headings instead; the content for each D remains the same.
# Customer Complaint 8D Report
## Basic information
| Item | Content |
|------|------|
| Complaint/Case No. | |
| Product name/Model | |
| Batch/Lot or production date | |
| Customer name | |
| Complaint date | |
| Receipt date | |
| Defect summary | |
| Report date | |
| Owner/Team leader | |
---
## D1 Form the team (Team)
**Purpose**: Establish a cross-functional team and define roles and contacts.
| Role | Name | Department | Responsibility |
|------|------|------------|-----------------|
| Leader | | | Overall coordination, customer interface |
| Member | | | |
| Member | | | |
**Output**: Team roster, roles, meeting plan.
---
## D2 Problem description (Problem Description)
**Purpose**: Clearly define the problem using 5W2H to support root cause analysis.
- **What**: What is the defect (symptom, defect type)?
- **Where**: Where was it found (customer line/warehouse/field)? Which process or component?
- **When**: When did it occur or get detected? Production date vs complaint date?
- **Who**: Which customer(s), line(s), or batch(es) are affected?
- **Why**: Why did the customer deem it nonconforming (spec, limit sample)?
- **How many**: Defect quantity, lot size, defect rate?
- **How did we know**: How was it discovered (inspection, complaint, return)?
**Problem statement (one sentence)**: [ Fill in ]
**Attachments (D2)**:
- **Images**: [Attach: defect photo(s)], [Attach: limit sample / customer evidence]. Optional: defect location sketch or timeline diagram.
- **Documents**: [Attach: spec or drawing ref: doc no., rev] — or list spec number and revision here.
---
## D3 Interim containment (Interim Containment)
**Purpose**: Prevent further escape or escalation and protect the customer.
- Stock/in-transit: Quarantine, 100% inspection, sorting, hold shipment?
- Shipped product: Recall, replacement, sorting at customer?
- Production floor: Line/batch stop, investigation, identification?
- Responsible department and due date: |
**Action list**:
| No. | Action | Owner | Due date | Verification |
|-----|--------|-------|----------|---------------|
| 1 | | | | |
| 2 | | | | |
**Attachments (D3)** (optional): [Attach: photo of quarantine area / sorted lots] or [Attach: containment flow diagram].
---
## D4 Root cause (Root Cause)
**Purpose**: Identify the true cause (verifiable and controllable), not just symptoms.
- Use at least one tool: 5-Why, fishbone (Ishikawa), FMEA, cause–effect matrix, Why-Why analysis.
- **Direct cause** (symptom level): |
- **Root cause** (controllable/verifiable end cause): |
- **Verification**: Reproduction test, data comparison, process traceability? |
**Analysis diagram**: [Attach or insert: 5-Why tree / fishbone diagram / Pareto or stratification chart]. If user provides steps or categories, generate a text or Mermaid diagram here.
**Root cause statement**: [ One sentence: "Due to … which resulted in …" ]
**Attachments (D4)**:
- **Charts/diagrams**: [See 5-Why / fishbone / Pareto above or attach file].
- **Images/video** (optional): [Attach: reproduction test photo or short video], [Attach: failure mode evidence].
- **Documents** (optional): [Attach: process doc or FMEA excerpt – before state].
---
## D5 Permanent corrective actions – select and verify (Permanent Corrective Actions)
**Purpose**: Choose permanent actions that address the root cause and verify effectiveness.
- Action(s) (may be multiple): |
- Rationale (why this action eliminates the root cause): |
- Verification: Trial run, pilot batch, data comparison, customer confirmation? |
- Verification result: OK/NG with brief data or conclusion. |
| Action ID | Action | Owner | Planned completion | Verification result |
|-----------|--------|-------|--------------------|----------------------|
| PC1 | | | | |
| PC2 | | | | |
**Attachments (D5)**:
- **Charts** (optional): [Attach or insert: before/after data chart, trial summary].
- **Images/video**: [Attach: verification photo or short video – trial run, measurement, OK parts].
- **Documents**: [Attach: trial report or test protocol], [Attach: customer confirmation if applicable].
---
## D6 Implement and validate (Implement & Validate)
**Purpose**: Incorporate actions into formal process/standards and confirm implementation.
- Updated documents: SOP, specification, FMEA, control plan, inspection criteria, etc. |
- Scope: Full line/model/supplier base? |
- Effectiveness: Cpk, defect rate, customer feedback. |
- Evidence: Document number, revision, implementation date. |
**Attachments (D6)**:
- **Charts** (optional): [Attach: Cpk or trend chart after implementation].
- **Images** (optional): [Attach: updated work area, gauge, or process photo].
- **Documents**: [Attach: revised SOP/spec/drawing – cover or key page with rev and date], [Attach: approval or change record].
---
## D7 Prevent recurrence (Prevent Recurrence)
**Purpose**: Avoid recurrence of the same type of issue through system changes.
- Process/system changes: Design review, incoming spec, change management, training? |
- Horizontal deployment: Same product/process/supplier/platform reviewed and addressed? |
- Lessons learned: Captured in FMEA, lesson learned database, training material? |
| Category | Content | Owner |
|----------|---------|-------|
| Process/Standard | | |
| Horizontal deployment | | |
| Training/Sharing | | |
**Attachments (D7)** (optional): [Attach: process change summary diagram], [Attach: training photo]. **Documents**: [Attach: training record or attendance], [Attach: lesson learned doc or FMEA update ref].
---
## D8 Congratulate the team and close (Congratulate & Close)
**Purpose**: Recognize contribution, close the case, and close the loop with the customer.
- Team contribution summary: |
- Customer communication and closure: Complaint closed, customer confirmation, evidence filed. |
- Closure date: |
- Report distribution: Quality, Manufacturing, R&D, Customer (as needed). |
**Attachments (D8)** (optional): [Attach: team/customer sign-off photo]. **Documents**: [Attach: customer closure confirmation or email], [Attach: distribution list or acknowledgment].| D | Keywords | If user did not provide, suggest |
|---|---|---|
| D1 | Cross-functional, leader, members, roles | "Please provide the 8D team members and leader." |
| D2 | 5W2H, defect, quantity, spec | "Please add defect details and quantity/lot information." Suggest: "Attach defect photo(s) and limit sample or spec ref for D2." |
| D3 | Quarantine, 100% inspection, stop, recall, due date | "Please describe containment actions for stock/shipment/production." Optional: "Attach photo of quarantine/sorted lots if available." |
| D4 | Root cause, 5-Why, fishbone, Pareto, verification | "Please provide root cause conclusion or 5-Why/fishbone summary." Suggest: "Add a 5-Why or fishbone diagram; attach reproduction test photo/video if you have it." |
| D5 | Permanent actions, verification result | "Please list selected permanent actions and verification method." Suggest: "Attach verification photo/video and trial report or test protocol." |
| D6 | SOP/spec update, scope, effectiveness | "Please state updated documents and implementation scope." Suggest: "Attach revised SOP/spec (cover or excerpt) and approval evidence." |
| D7 | Horizontal deployment, process improvement, training | "Please describe recurrence prevention and horizontal deployment." Optional: "Attach training record or lesson learned doc ref." |
| D8 | Closure, customer confirmation, filing | "Please confirm closure date and customer sign-off." Optional: "Attach customer closure confirmation and distribution list." |
[To be filled] or [Fill from context above] when information is missing; do not invent names, dates, or quantities. For attachments use [Attach: description] or [See diagram] so the user knows what to add in Word or the report system. 8D-{case-number}-{date}.md, or to a path specified by the user. {baseDir}/reference.md (if present). {baseDir}/examples/ (if present).© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 7 other files in skills/complaint-8d-report of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Complaint 8d Report next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Complaint 8d Report this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.2k | Automated safety check: Pass | MIT | |
| Generatealirezarezvani/claude-skills | 28k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Fal Generatenexu-io/open-design | 100k | — | ~306 | Automated safety check: Pass | Apache-2.0 | |
| Video Generationbytedance/deer-flow | 84k | 3 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Image Generationonyx-dot-app/onyx | 32k | 1 repos | ~1.7k | Automated safety check: Pass | Custom licence | |
| Structured Image Generationbytedance/deer-flow | 84k | 4 repos | ~2.9k | Automated safety check: Pass | MIT |
alirezarezvani/claude-skills
Generate Playwright tests. An agent skill from alirezarezvani/claude-skills.
nexu-io/open-design
Generate images and videos using fal.ai AI models. An agent skill from nexu-io/open-design.
bytedance/deer-flow
Generates short videos from a structured JSON prompt, optionally guided by a reference image used as the first or last frame.
onyx-dot-app/onyx
Generate or edit raster images (photos, illustrations, textures, sprites, mockups, logos, infographics) using the workspace's configured image-generation provider via onyx-cli image.
bytedance/deer-flow
Turns an image request into a structured JSON prompt and runs a bundled Python script to generate the picture, optionally guided by reference images.
sickn33/agentic-awesome-skills
Generate and edit images/video with Google's Gemini media models (Nano Banana 2/Pro, Gemini Omni Flash), with cost-approval gates, reference-image support, and a prompt/output log per call.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Generates or completes 8D reports (Eight Disciplines) from customer complaint data, with D1–D8 fill-in guidance and a standard template. Complaint 8d Report is an agent skill from LeoYeAI/openclaw-master-skills. Generates or completes 8D reports (Eight Disciplines) from customer complaint data, with D1–D8 fill-in guidance and a standard template.
Complaint 8d Report fits situations like: customer complaints; quality deviations; defect recurrence prevention.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a claude-code`. Or copy the skill folder (skills/complaint-8d-report in LeoYeAI/openclaw-master-skills) into .claude/skills/complaint-8d-report in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a codex`. Or copy the skill folder (skills/complaint-8d-report in LeoYeAI/openclaw-master-skills) into .agents/skills/complaint-8d-report in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/complaint-8d-report, .gemini/skills/complaint-8d-report, .github/skills/complaint-8d-report and .opencode/skills/complaint-8d-report in your project.
SKILL.md names no scripts, command-line tools or credentials: Complaint 8d Report is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Complaint 8d Report is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Complaint 8d Report: Generate (alirezarezvani/claude-skills, 28k stars), Fal Generate (nexu-io/open-design, 100k stars), Video Generation (bytedance/deer-flow, 84k stars) and Image Generation (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.