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 a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep.
Install My Failure Museum
$ npx skills add mohitagw15856/pm-claude-skills --skill my-failure-museum -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills my-failure-museum --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/my-failure-museum .claude/skills/my-failure-museum && 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 "my-failure-museum" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/my-failure-museum into .claude/skills/my-failure-museum/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "my-failure-museum", 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/my-failure-museumType 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 my-failure-museum -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills my-failure-museum --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/my-failure-museum .agents/skills/my-failure-museum && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "my-failure-museum" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/my-failure-museum into .agents/skills/my-failure-museum/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "my-failure-museum", 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 my-failure-museum -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills my-failure-museum --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/my-failure-museum .cursor/skills/my-failure-museum && 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 "my-failure-museum" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/my-failure-museum into .cursor/skills/my-failure-museum/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "my-failure-museum", 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/my-failure-museum--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 my-failure-museum -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills my-failure-museum --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/my-failure-museum .gemini/skills/my-failure-museum && 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 "my-failure-museum" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/my-failure-museum into .gemini/skills/my-failure-museum/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "my-failure-museum", 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 my-failure-museumInstalls 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 my-failure-museum -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/my-failure-museum .github/skills/my-failure-museum && 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 "my-failure-museum" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/my-failure-museum into .github/skills/my-failure-museum/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "my-failure-museum", 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 my-failure-museum -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 my-failure-museum --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/my-failure-museum .opencode/skills/my-failure-museum && 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 "my-failure-museum" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/my-failure-museum into .opencode/skills/my-failure-museum/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "my-failure-museum", 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
my-failure-museum- GitHub stars
- 1.4k
- Token cost
- ~965 tokens
- SKILL.md length
- 483 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Turn a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep.
- Works in 5 steps: Examine, don't flagellate. Approach it… → Dig past the surface cause. "I forgot"… → Extract a specific rule. Convert the… → …
- Asked help me learn from this mistake
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Autopsy Without… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
My Failure Museum is an agent skill from mohitagw15856/pm-claude-skills. Turn a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep. Use when asked help me learn from this mistake, I keep making the same error, capture this lesson, or turn this failure into something useful. Produces an honest, blame-free autopsy of what happened, the real root cause (not the surface one), the specific rule or trigger that prevents a repeat, and a one-line entry for your growing 'failure museum' — because…
Its SKILL.md is about 970 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 help me learn from this mistake
- I keep making the same error
- Capture this lesson
- Turn this failure into something useful
Example prompts
- “s what happened and the rule so it doesn”
- “failure museum”
- “/my-failure-museum”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Examine, don't flagellate. Approach it like an investigator, not a judge — blame shuts down learning; curiosity opens it.
- Dig past the surface cause. "I forgot" or "I was busy" is rarely the real cause — find the system or habit underneath ("no reminder…
- Extract a specific rule. Convert the root cause into an actionable rule or trigger ("before saying yes, check the calendar"; "always CC…
- Write the one-liner. Compress it into a single memorable entry for the museum — short enough to actually reread.
- Check the pattern. If this echoes past failures, name the recurring theme — that's the higher-leverage fix.
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
My Failure Museum loads about 965 tokens when it runs. Until then it costs about 150 tokens; SKILL.md has 483 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). 483 words, ~965 tokens.
Download SKILL.mdSave it as
.claude/skills/my-failure-museum/SKILL.md (or your agent's skills folder).- name
- my-failure-museum
- description
- Turn a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep. Use when asked help me learn from this mistake, I keep making the same error, capture this lesson, or turn this failure into something useful. Produces an honest, blame-free autopsy of what happened, the real root cause (not the surface one), the specific rule or trigger that prevents a repeat, and a one-line entry for your growing 'failure museum' — because unexamined mistakes repeat and examined ones compound into wisdom.
My Failure Museum
A mistake you don't examine is one you'll make again; a mistake you turn into a rule never costs you twice. This does the turning: a short, honest, blame-free autopsy of what went wrong, the real root cause underneath the obvious one, and the specific rule or trigger that stops the repeat — captured as a one-line entry for a growing collection. Over time, your failure museum becomes your hardest-won operating manual.
What This Skill Produces
- The honest autopsy — what actually happened, blame-free (self-flagellation teaches nothing; analysis does)
- The real root cause — the underlying reason, not the surface one ("I was busy" → "I don't build in buffer time")
- The prevention rule — a specific, actionable rule or trigger that would have caught it, and will next time
- The one-line museum entry — a compact, keepable lesson to add to your collection
- A pattern check — whether this is a one-off or part of a recurring theme worth a bigger fix
Required Inputs
Ask for these if not provided:
- What happened — the mistake or failure
- The consequence — what it cost
- Your read on why — your first explanation (we'll dig past it)
- Has it happened before — to spot a pattern
Framework: Autopsy Without Blame, Extract The Rule
- Examine, don't flagellate. Approach it like an investigator, not a judge — blame shuts down learning; curiosity opens it.
- Dig past the surface cause. "I forgot" or "I was busy" is rarely the real cause — find the system or habit underneath ("no reminder system," "I over-commit").
- Extract a specific rule. Convert the root cause into an actionable rule or trigger ("before saying yes, check the calendar"; "always CC myself"). Vague resolutions don't work; specific rules do.
- Write the one-liner. Compress it into a single memorable entry for the museum — short enough to actually reread.
- Check the pattern. If this echoes past failures, name the recurring theme — that's the higher-leverage fix.
Show full SKILL.md (165 more words)Show less
Output Format
Failure: [what happened] · cost: [consequence]
Autopsy (blame-free): [what actually happened]. Real root cause: [the underlying system/habit, past the surface]. Prevention rule: [specific, actionable rule or trigger]. 📓 Museum entry (one line): "[compact lesson]." Pattern? [one-off / part of a recurring theme → the bigger fix].
Quality Checks
- The autopsy is honest but blame-free
- It digs past the surface cause to the real one
- The prevention is a specific rule/trigger, not a vague resolution
- It produces a compact, keepable one-line entry
- It checks whether this is part of a pattern
Anti-Patterns
- Self-flagellation dressed as reflection.
- Stopping at the surface cause ("I was careless").
- A vague resolution ("I'll be more careful") instead of a rule.
- Missing the recurring pattern.
Example Trigger Phrases
- "I messed up — help me actually learn from it."
- "I keep making the same mistake. Why, and how do I stop?"
- "Turn this failure into a lesson I'll remember."
- "Do a blame-free post-mortem on my screw-up."
- "Add this to my list of lessons — what's the rule?"
© 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/my-failure-museum of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
My Failure Museum 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 |
|---|---|---|---|---|---|---|
| My Failure Museum this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~965 | 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 My Failure Museum
What does My Failure Museum do?
Turn a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep. My Failure Museum is an agent skill from mohitagw15856/pm-claude-skills. Turn a mistake into a reusable lesson — a short, unsentimental 'here's what happened and the rule so it doesn't happen again' entry you can actually keep.
When should I use My Failure Museum?
My Failure Museum fits situations like: asked help me learn from this mistake; I keep making the same error; capture this lesson; turn this failure into something useful.
How do I install My Failure Museum in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill my-failure-museum -a claude-code`. Or copy the skill folder (skills/my-failure-museum in mohitagw15856/pm-claude-skills) into .claude/skills/my-failure-museum in your project. Claude Code loads it when a task matches its description.
How do I install My Failure Museum in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill my-failure-museum -a codex`. Or copy the skill folder (skills/my-failure-museum in mohitagw15856/pm-claude-skills) into .agents/skills/my-failure-museum in your project. Codex loads it when a task matches its description.
Can I use My Failure Museum 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 my-failure-museum -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/my-failure-museum, .gemini/skills/my-failure-museum, .github/skills/my-failure-museum and .opencode/skills/my-failure-museum in your project.
What does My Failure Museum need to run?
SKILL.md names no scripts, command-line tools or credentials: My Failure Museum is instructions for the agent only.
Does My Failure Museum 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 My Failure Museum 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 My Failure Museum use?
My Failure Museum 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 My Failure Museum use?
About 965 tokens (SKILL.md is roughly 3.9k 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 My Failure Museum?
Skills that share tags, products or a category with My Failure Museum: 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 My Failure Museum?
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.