OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action…
Install Rma Failure Analysis
$ npx skills add mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills rma-failure-analysis --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rma-failure-analysis .claude/skills/rma-failure-analysis && 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 "rma-failure-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/rma-failure-analysis into .claude/skills/rma-failure-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rma-failure-analysis", 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/mohitagw15856/pm-claude-skills/tree/main/skills/rma-failure-analysisType 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 mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills rma-failure-analysis --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/rma-failure-analysis .agents/skills/rma-failure-analysis && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "rma-failure-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/rma-failure-analysis into .agents/skills/rma-failure-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rma-failure-analysis", 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 mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills rma-failure-analysis --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/rma-failure-analysis .cursor/skills/rma-failure-analysis && 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 "rma-failure-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/rma-failure-analysis into .cursor/skills/rma-failure-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rma-failure-analysis", 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/mohitagw15856/pm-claude-skills.git --path skills/rma-failure-analysis--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 mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills rma-failure-analysis --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/rma-failure-analysis .gemini/skills/rma-failure-analysis && 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 "rma-failure-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/rma-failure-analysis into .gemini/skills/rma-failure-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rma-failure-analysis", 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 mohitagw15856/pm-claude-skills rma-failure-analysisInstalls 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 mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/rma-failure-analysis .github/skills/rma-failure-analysis && 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 "rma-failure-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/rma-failure-analysis into .github/skills/rma-failure-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rma-failure-analysis", 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 mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills rma-failure-analysis --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/rma-failure-analysis .opencode/skills/rma-failure-analysis && 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 "rma-failure-analysis" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/rma-failure-analysis into .opencode/skills/rma-failure-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rma-failure-analysis", 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.
Facts
- Skill name
rma-failure-analysis- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 699 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action…
- Works in 7 steps: Summary — return rate vs target,… → Triage breakdown — table: bucket, count,… → Verified-failure Pareto — mode, count,… → …
- Asked to analyse RMA data
- SKILL.md covers What This Skill Produces, Required Inputs, Analysis Framework and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Rma Failure Analysis is an agent skill from mohitagw15856/pm-claude-skills. Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action structure, and cost-of-quality framing. Use when asked to analyse RMA data, investigate field returns, run failure analysis on returned units, write an 8D report, or figure out why return rates are climbing. Produces a failure-analysis report with a triage-clean Pareto, 8D actions, and the cost case for fixing each mode.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Root cause analysis. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to analyse RMA data
- Investigate field returns
- Run failure analysis on returned units
- Write an 8D report
Example prompts
- “/rma-failure-analysis”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Summary — return rate vs target, headline modes, the one-paragraph verdict
- Triage breakdown — table: bucket, count, % of returns, % of shipped
- Verified-failure Pareto — mode, count, rate vs shipped, trend, batch correlation
- 8D per top mode — the eight disciplines, with D4 evidence labelled verified/hypothesis
- Cost of quality — per-return cost, annualised per mode, fix ROI table
- Actions — containment (now) and corrective (cut-in) with owners and dates
- Data caveats — denominator gaps, lag effects, unteardown returns
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. 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.
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
Rma Failure Analysis loads about 1.4k tokens when it runs. Until then it costs about 133 tokens; SKILL.md has 699 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.
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 mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 699 words, ~1,373 tokens.
Download SKILL.mdSave it as
.claude/skills/rma-failure-analysis/SKILL.md (or your agent's skills folder).- name
- rma-failure-analysis
- description
- Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action structure, and cost-of-quality framing. Use when asked to analyse RMA data, investigate field returns, run failure analysis on returned units, write an 8D report, or figure out why return rates are climbing. Produces a failure-analysis report with a triage-clean Pareto, 8D actions, and the cost case for fixing each mode.
RMA Failure Analysis Skill
Raw RMA data lies: it mixes buyer's remorse, user error, and shipping damage in with real design and manufacturing defects. This skill turns returns into decisions — triage first so the Pareto is of verified failure modes, run the top modes through 8D discipline (contain now, root-cause properly, correct permanently), and price each mode in cost-of-quality terms so the fix competes for resources on money, not anecdote.
What This Skill Produces
- A triaged breakdown of returns using a standard RMA taxonomy
- A Pareto of verified failure modes with rates against units shipped
- An 8D-structured analysis for each top failure mode
- Cost-of-quality framing: cost per return, per mode, and the fix ROI
- Prioritised corrective actions with owners and cut-in points
Required Inputs
Ask for these if not provided; analyse whatever slice exists, but state the denominator caveats plainly:
- RMA records — return reasons, dates, symptoms, any teardown/FA findings
- Units shipped per period — the denominator; return counts without it are useless
- Product age mix — manufacture date or batch, to separate infant mortality from wear-out
- Cost inputs — per-return logistics, refurb/scrap cost, support cost per case (estimate and label if unknown)
- Known changes — ECOs, factory or component changes that bracket the data in time
Analysis Framework
Step 1 — Triage taxonomy. Bucket every return before any Pareto:
| Bucket | Meaning |
|---|---|
| NTF / CND | No trouble found — unit passes full test; count separately, it's a UX/expectation signal |
| CID | Customer-induced damage (drop, liquid) — a robustness signal, not a defect |
| OBF / DOA | Failed out of box — points at outgoing quality or transit |
| SW-resolvable | Fixed by update/reset — cheapest class to kill |
| Verified HW failure | Real defect, classified by subsystem and failure mode |
| Remorse / non-technical | Returned working — exclude from quality analysis, report separately |
Step 2 — Pareto verified failures only, by failure mode (not symptom — "won't charge" is a symptom; "USB connector solder crack" is a mode). Express each as % of units shipped in the exposed population, with the time window stated.
Step 3 — 8D per top mode (top 3–5 carry most of the cost): D1 team · D2 problem statement with data · D3 containment (screen stock, hold lots, factory rescreen — dated) · D4 root cause via evidence (teardown, cross-section, batch correlation), labelled [verified] or [hypothesis] · D5 corrective action chosen · D6 implementation with cut-in (ECO/date/serial break) · D7 recurrence prevention (test coverage, DFM rule, spec change) · D8 closure criteria (return rate for the mode falls to X by date Y).
Step 4 — Cost of quality. Cost per return = freight + refurb/scrap + support labour + replacement unit margin. Annualise per mode; compare fix cost vs failure cost; note warranty-accrual impact.
Show full SKILL.md (276 more words)Show less
Output Format
RMA failure analysis: [product] — [period]
- Summary — return rate vs target, headline modes, the one-paragraph verdict
- Triage breakdown — table: bucket, count, % of returns, % of shipped
- Verified-failure Pareto — mode, count, rate vs shipped, trend, batch correlation
- 8D per top mode — the eight disciplines, with D4 evidence labelled verified/hypothesis
- Cost of quality — per-return cost, annualised per mode, fix ROI table
- Actions — containment (now) and corrective (cut-in) with owners and dates
- Data caveats — denominator gaps, lag effects, unteardown returns
Quality Checks
- Every rate has a denominator and an exposure window — counts alone never appear
- NTF, CID, and remorse are separated out before the failure Pareto
- Pareto items are failure modes, not symptoms
- Every root cause is labelled
[verified]or[hypothesis]with its evidence - Containment actions are distinct from corrective actions, each dated and owned
- Cost of quality uses stated inputs; estimates are labelled as estimates
Anti-Patterns
- Do not Pareto raw return reasons — triage first, or NTF and remorse will drown the real defects
- Do not report return counts without units shipped and the exposure window
- Do not close an 8D at D5 — a corrective action without cut-in verification and recurrence prevention is a wish
- Do not treat NTF as noise to discard — a high NTF rate is a product or support failure of its own
- Do not root-cause by vote — teardown evidence and batch correlation, or label it a hypothesis
- Do not compare return rates across cohorts with different time-in-field — young cohorts always look better
Example Trigger Phrases
- "Analyse RMA data."
- "Investigate field returns."
- "Run failure analysis on returned units."
- "Write an 8D report."
- "Figure out why return rates are climbing."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/rma-failure-analysis of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Rma Failure Analysis 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 |
|---|---|---|---|---|---|---|
| Rma Failure Analysis this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Review PRapache/shardingsphere | 21k | — | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| Graph-Based Bug Tracingtirth8205/code-review-graph | 32k | 1 repos | ~287 | Automated safety check: Pass | MIT |
Similar skills
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Review PR
apache/shardingsphere
Review Apache ShardingSphere or user-authorized downstream pull requests and PR discussions from public or authorized repository evidence.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
Om Auto Fix Issue
go-musicfox/go-musicfox
Fix or implement a tracker issue end to end from a single command — takes an issue id or a plain problem description (filed first via om-prepare-issue), classifies, then drives the bug autofix chain…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Rma Failure Analysis
What does Rma Failure Analysis do?
Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action…. Rma Failure Analysis is an agent skill from mohitagw15856/pm-claude-skills. Turn field returns into a structured failure-analysis report — RMA triage taxonomy (NTF vs real failures), Pareto by verified failure mode, 8D-style containment→root-cause→corrective-action structure, and cost-of-quality framing.
When should I use Rma Failure Analysis?
Rma Failure Analysis fits situations like: asked to analyse RMA data; investigate field returns; run failure analysis on returned units; write an 8D report.
How do I install Rma Failure Analysis in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a claude-code`. Or copy the skill folder (skills/rma-failure-analysis in mohitagw15856/pm-claude-skills) into .claude/skills/rma-failure-analysis in your project. Claude Code loads it when a task matches its description.
How do I install Rma Failure Analysis in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a codex`. Or copy the skill folder (skills/rma-failure-analysis in mohitagw15856/pm-claude-skills) into .agents/skills/rma-failure-analysis in your project. Codex loads it when a task matches its description.
Can I use Rma Failure Analysis 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 mohitagw15856/pm-claude-skills --skill rma-failure-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rma-failure-analysis, .gemini/skills/rma-failure-analysis, .github/skills/rma-failure-analysis and .opencode/skills/rma-failure-analysis in your project.
What does Rma Failure Analysis need to run?
SKILL.md names no scripts, command-line tools or credentials: Rma Failure Analysis is instructions for the agent only.
Does Rma Failure Analysis 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 Rma Failure Analysis 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 Rma Failure Analysis use?
Rma Failure Analysis 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 Rma Failure Analysis use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Rma Failure Analysis?
Skills that share tags, products or a category with Rma Failure Analysis: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Review PR (apache/shardingsphere, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Rma Failure Analysis?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.