Agent skill

Complaint 8d Report

by LeoYeAI in 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.

MITAuto-check passed

Install Complaint 8d Report

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill complaint-8d-report -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills complaint-8d-report --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
complaint-8d-report
GitHub stars
2.2k
Token cost
~4.2k tokens
SKILL.md length
1,357 words
Files
8
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Generates or completes 8D reports (Eight Disciplines) from customer complaint data, with D1–D8 fill-in guidance and a standard template.

  • Works in 4 steps: Ask at the start: "Which customer or… → If the user names a customer → If the user provides a template or… → …
  • Customer complaints
  • SKILL.md covers Customer-specific /…, Charts, diagrams, and…, Workflow (fixed order) and Report template (standard…, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • Customer complaints
  • Quality deviations
  • Defect recurrence prevention

Example prompts

  • “Use the complaint-8d-report skill to generate or completes 8D reports (Eight Disciplines) from customer complaint data, with D1–D8 fill-in guidance…”
  • “/complaint-8d-report”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Ask at the start: "Which customer or report format should we use? If your customer has a specific template (section names, table layout)…
  2. If the user names a customer
  3. If the user provides a template or example (pasted text, list of section titles, or attached document)
  4. Stored format files (optional): In the skill folder, formats/ can contain one file per customer or format (e.g. Customer-A.md…

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    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.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

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.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,357 words, ~4,214 tokens.

Download SKILL.mdSave it as .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.
name
complaint-8d-report
description
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.
triggers
8D report, 8D, write 8D, create 8D report, customer complaint report, quality deviation report, corrective action report, CAR, eight disciplines, root cause…

Customer Complaint 8D Report

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.


Customer-specific / multi-customer formats

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:

  1. Ask at the start: "Which customer or report format should we use? If your customer has a specific template (section names, table layout), paste it or attach it and I’ll match it; otherwise I’ll use the standard template."
  2. If the user names a customer:
    • Check whether a format definition exists under {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.
    • If no stored format exists, use the standard template and say: "Using the standard template. To reuse a custom format next time, you can add a format file under formats/ — see formats/README.md."
  3. If the user provides a template or example (pasted text, list of section titles, or attached document):
    • Extract section titles and table headers (and order). Map standard D1–D8 content into those sections: same logic (team, problem, containment, root cause, permanent actions, implement, prevent recurrence, close), but use the customer’s labels and order. If their format merges or splits disciplines (e.g. "D4–D5: Root cause and corrective actions"), keep one section and include both contents.
    • If their format has extra fields (e.g. "Cost impact", "RMA number"), add those as rows or blocks with placeholders like [To be filled].
  4. Stored format files (optional): In the skill folder, 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.


Charts, diagrams, and attachments (when to use)

WhereCharts / diagramsImages or videoDocuments
D2Optional: defect location sketch, timelineRecommended: defect photos, limit sample, customer evidenceSpec sheet, drawing, limit sample doc ref
D3Optional: containment flowOptional: quarantine area, sorted lotsN/A
D4Recommended: 5-Why tree, fishbone, Pareto, cause–effect matrixOptional: reproduction test photos/video, failure modeProcess doc / FMEA excerpt (before)
D5Optional: before/after data chart, trial summaryRecommended: verification photos or short video (trial, measurement)Trial report, test protocol
D6Optional: Cpk/trend chartOptional: updated work area, gaugeRecommended: revised SOP/spec (cover or excerpt), approval
D7Optional: process change summaryOptional: training photoRecommended: training record, lesson learned doc ref
D8N/AOptional: team/customer sign-off photoRecommended: customer closure confirmation, distribution list
  • Charts/diagrams: When generating the report, prompt the user to add or describe a diagram where the template says "See diagram" or "Attach chart". If the user can provide data (e.g. defect counts by category, 5-Why steps), generate a text or Mermaid-style diagram in Markdown where applicable.
  • Images/video: Use placeholders like [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.
  • Documents: Use placeholders like [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.

Workflow (fixed order)

  1. Determine report format (do this first when the user has multiple customers):
    • Ask: "Which customer or 8D format should we use? You can name a customer (if we have a format file for them), paste your customer’s section titles or template, or use the standard format."
    • If the user names a customer: look for {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.
    • If the user pastes or attaches a template: parse section headings and table headers, then generate the report using that structure and the same D1–D8 content mapping.
    • If no preference: use the "Report template" below (standard).
  2. Gather information: Confirm or collect at least one of the following
    • Complaint/case number
    • Product name, model, batch/lot or production date
    • Customer name, complaint date, receipt date
    • Defect description (symptom, quantity, where found, specification requirement)
    • Responsible department/owner (optional)
  3. Generate report skeleton: Output the full 8D document per the chosen format (standard "Report template" below, or customer-specific structure from step 1). Use [To be filled] or [Fill from context above] for missing items.
  4. Guide by discipline: If the user provided only partial information, add a one-line prompt at the end of the relevant D section: "Suggested addition: …".
  5. Charts and attachments: Where the template calls for a diagram, image, or document, either (a) generate a text/Mermaid diagram from user data when possible, or (b) insert a clear placeholder (e.g. [Attach: defect photo], [See fishbone diagram]) and remind the user to add the file when finalizing the report.
  6. Output format: Deliver copy-pasteable Markdown and suggest saving as 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.

Show full SKILL.md (412 more words)Show less

Report template (standard structure)

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.

markdown
# 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].

Fill-in hints by D (for model reasoning and user prompts)

DKeywordsIf user did not provide, suggest
D1Cross-functional, leader, members, roles"Please provide the 8D team members and leader."
D25W2H, defect, quantity, spec"Please add defect details and quantity/lot information." Suggest: "Attach defect photo(s) and limit sample or spec ref for D2."
D3Quarantine, 100% inspection, stop, recall, due date"Please describe containment actions for stock/shipment/production." Optional: "Attach photo of quarantine/sorted lots if available."
D4Root 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."
D5Permanent actions, verification result"Please list selected permanent actions and verification method." Suggest: "Attach verification photo/video and trial report or test protocol."
D6SOP/spec update, scope, effectiveness"Please state updated documents and implementation scope." Suggest: "Attach revised SOP/spec (cover or excerpt) and approval evidence."
D7Horizontal deployment, process improvement, training"Please describe recurrence prevention and horizontal deployment." Optional: "Attach training record or lesson learned doc ref."
D8Closure, customer confirmation, filing"Please confirm closure date and customer sign-off." Optional: "Attach customer closure confirmation and distribution list."

Output requirements

  1. Language: Match the user (e.g. English for English complaints; add bilingual terms if needed).
  2. Placeholders: Use [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.
  3. Charts/diagrams: When the user gives 5-Why steps, cause categories, or defect counts by category, generate a text diagram (e.g. indented 5-Why, Mermaid flowchart or mindmap if supported) in the report body so the section is self-contained; still mention attaching the formal diagram file if they have one.
  4. Images/video/documents: Keep attachment placeholders explicit; remind the user that images, videos, and document excerpts must be attached when exporting to Word or uploading the final report.
  5. File: Suggest saving the final report as 8D-{case-number}-{date}.md, or to a path specified by the user.
  6. One draft first: Output one complete template fill-in, then update specific sections based on user additions.

References

  • Detailed 8D methodology and tools: {baseDir}/reference.md (if present).
  • Example snippets: {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

Files

SKILL.md and 7 other files in skills/complaint-8d-report of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • README.md
  • _meta.json
  • clawhub.json
  • examples/sample-8d-snippet.md
  • formats/README.md
  • formats/automotive-oem-example.md
  • reference.md

Open the folder on GitHubat commit e5199b5

Compare with similar skills

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.

Complaint 8d Report compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Complaint 8d Report this skillLeoYeAI/openclaw-master-skills2.2k—~4.2kAutomated safety check: PassMIT
Generatealirezarezvani/claude-skills28k1 repos~1.1kAutomated safety check: PassMIT
Fal Generatenexu-io/open-design100k—~306Automated safety check: PassApache-2.0
Video Generationbytedance/deer-flow84k3 repos~1.4kAutomated safety check: PassMIT
Image Generationonyx-dot-app/onyx32k1 repos~1.7kAutomated safety check: PassCustom licence
Structured Image Generationbytedance/deer-flow84k4 repos~2.9kAutomated safety check: PassMIT

Similar skills

  • Generate

    alirezarezvani/claude-skills

    Generate Playwright tests. An agent skill from alirezarezvani/claude-skills.

    28k GitHub starsUsed in 1 repo~1.1k tokens
    Testing & QAAuto-check passed
  • Fal Generate

    nexu-io/open-design

    Generate images and videos using fal.ai AI models. An agent skill from nexu-io/open-design.

    100k GitHub stars~306 tokensUpdated today
    Media & CreativeAuto-check passed
  • Video Generation

    bytedance/deer-flow

    Generates short videos from a structured JSON prompt, optionally guided by a reference image used as the first or last frame.

    84k GitHub starsUsed in 3 repos~1.4k tokens
    Media & CreativeAuto-check passed
  • Image Generation

    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.

    32k GitHub starsUsed in 1 repo~1.7k tokens
    Media & CreativeAuto-check passed
  • Structured Image Generation

    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.

    84k GitHub starsUsed in 4 repos~2.9k tokens
    Media & CreativeAuto-check passed
  • Generate Nanobanana

    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.

    47k GitHub starsUsed in 1 repo~2.8k tokens
    Media & CreativeAuto-check: notes

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    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.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    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.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    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.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    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.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    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.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    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.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Complaint 8d Report

What does Complaint 8d Report do?

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.

When should I use Complaint 8d Report?

Complaint 8d Report fits situations like: customer complaints; quality deviations; defect recurrence prevention.

How do I install Complaint 8d Report in Claude Code?

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.

How do I install Complaint 8d Report in Codex?

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.

Can I use Complaint 8d Report in Cursor, Gemini CLI or GitHub Copilot?

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.

What does Complaint 8d Report need to run?

SKILL.md names no scripts, command-line tools or credentials: Complaint 8d Report is instructions for the agent only.

Does Complaint 8d Report access the network?

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.

Is Complaint 8d Report safe to install?

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.

What licence does Complaint 8d Report use?

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.

How many tokens does Complaint 8d Report use?

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.

What are the alternatives to Complaint 8d Report?

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.

Who maintains Complaint 8d Report?

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.