Capture
alirezarezvani/claude-skills
Captures and organizes chaotic brain dumps into a structured, actionable system with zero information loss.
Captures solved problems as categorized documentation with YAML frontmatter for fast lookup.
No licenceAuto-check: notes
Install Troubleshooting Docs
$ npx skills add glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install glittercowboy/plugin-freedom-system troubleshooting-docs --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/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/troubleshooting-docs .claude/skills/troubleshooting-docs && 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 "troubleshooting-docs" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/troubleshooting-docs into .claude/skills/troubleshooting-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-docs", 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/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/troubleshooting-docsType 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 glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install glittercowboy/plugin-freedom-system troubleshooting-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/troubleshooting-docs .agents/skills/troubleshooting-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "troubleshooting-docs" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/troubleshooting-docs into .agents/skills/troubleshooting-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-docs", 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 glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install glittercowboy/plugin-freedom-system troubleshooting-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/troubleshooting-docs .cursor/skills/troubleshooting-docs && 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 "troubleshooting-docs" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/troubleshooting-docs into .cursor/skills/troubleshooting-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-docs", 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/glittercowboy/plugin-freedom-system.git --path .claude/skills/troubleshooting-docs--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 glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install glittercowboy/plugin-freedom-system troubleshooting-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/troubleshooting-docs .gemini/skills/troubleshooting-docs && 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 "troubleshooting-docs" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/troubleshooting-docs into .gemini/skills/troubleshooting-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-docs", 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 glittercowboy/plugin-freedom-system troubleshooting-docsInstalls 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 glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/troubleshooting-docs .github/skills/troubleshooting-docs && 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 "troubleshooting-docs" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/troubleshooting-docs into .github/skills/troubleshooting-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-docs", 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 glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install glittercowboy/plugin-freedom-system troubleshooting-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/glittercowboy/plugin-freedom-system.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/troubleshooting-docs .opencode/skills/troubleshooting-docs && 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 "troubleshooting-docs" agent skill from https://github.com/glittercowboy/plugin-freedom-system/tree/main/.claude/skills/troubleshooting-docs into .opencode/skills/troubleshooting-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-docs", 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
troubleshooting-docs- GitHub stars
- 216
- Token cost
- ~2.3k tokens
- SKILL.md length
- 813 words
- Files
- 6 (incl. references, assets)
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Captures solved problems as categorized documentation with YAML frontmatter for fast lookup.
- Works in 7 steps: Detect Confirmation → Gather Context → Check Existing Docs (Skip if unique… → …
- User confirms solution with phrases like that worked
- SKILL.md covers Overview, 7-Step Process, Decision Menu After Capture and Integration Points, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Troubleshooting Docs is an agent skill from glittercowboy/plugin-freedom-system. Captures solved problems as categorized documentation with YAML frontmatter for fast lookup. Use when user confirms solution with phrases like 'that worked', 'it's fixed', 'working now', or via /doc-fix command.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `assets/critical-pattern-template.md`, `assets/resolution-template.md` and `references/example-walkthrough.md`).
The repository describes itself as: AI-assisted JUCE plugin development system for MacOS by TÂCHES.
When your agent uses it
- User confirms solution with phrases like that worked
- Via /doc-fix command
Example prompts
- “that worked”
- “s fixed”
- “working now”
- “/troubleshooting-docs”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Bash, Grep
Workflow steps
7 steps, taken from the step headings in SKILL.md.
- Detect Confirmation
- Gather Context
- Check Existing Docs (Skip if unique first-time issue)
- Generate Filename
- Validate YAML Schema
- Create Documentation
- Cross-Reference & Pattern Detection
What it can do on your machine
Read from SKILL.md and the folder at commit e965cdd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteBashGrep
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 bash).
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
Troubleshooting Docs loads about 2.3k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 813 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Bash, Grep
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
Without a licence we can't republish the file, so here is its outline and opening line. It has 813 words (~2,289 tokens).
“Purpose: Automatically document solved problems to build searchable institutional knowledge with category-based organization (enum-validated problem types).”
- name
- troubleshooting-docs
- allowed-tools
- Read, Write, Bash, Grep
- preconditions
- Problem has been solved (not in-progress), Solution has been verified working
Files
SKILL.md and 5 other files (references, assets) in .claude/skills/troubleshooting-docs of glittercowboy/plugin-freedom-system.
- SKILL.md
- assets/critical-pattern-template.md
- assets/resolution-template.md
- references/example-walkthrough.md
- references/yaml-schema.md
- schema.yaml
Open the folder on GitHubat commit e965cdd
Compare with similar skills
Troubleshooting Docs 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 |
|---|---|---|---|---|---|---|
| Troubleshooting Docs this skillglittercowboy/plugin-freedom-system | 216 | — | ~2.3k | Automated safety check: Notes | None | |
| Capturealirezarezvani/claude-skills | 28k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Vc Problem Solvingwithkynam/vibecode-pro-max-kit | 1.1k | 2 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Is This A Problemanthropics/claude-for-legal | 9.6k | 2 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Resourceful Problem Solvingswarmclawai/swarmclaw | 688 | — | ~460 | Automated safety check: Pass | MIT | |
| Worked Example To Problem Solving Transition DesignerGarethManning/education-agent-skills | 835 | — | ~6.2k | Automated safety check: Pass | Custom licence |
Similar skills
Vc Problem Solving
withkynam/vibecode-pro-max-kit
Apply systematic problem-solving techniques when stuck. An agent skill from withkynam/vibecode-pro-max-kit.
- Official
Is This A Problem
anthropics/claude-for-legal
Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration.
Resourceful Problem Solving
swarmclawai/swarmclaw
Always-on guidance for solving tasks resourcefully. An agent skill from swarmclawai/swarmclaw.
Worked Example To Problem Solving Transition Designer
GarethManning/education-agent-skills
Design the transition from worked examples to independent problem-solving using expertise-reversal principles.
Startup It Troubleshooting
sickn33/agentic-awesome-skills
Practical IT troubleshooting playbooks for small teams without dedicated IT staff.
More from glittercowboy/plugin-freedom-system
All 15 skills in this repoAesthetic Dreaming
glittercowboy/plugin-freedom-system
Create aesthetic templates without first creating a plugin - capture visual design concepts through adaptive questioning.
Deep Research
glittercowboy/plugin-freedom-system
Multi-agent parallel investigation for complex JUCE problems.
Plugin Ideation
glittercowboy/plugin-freedom-system
Adaptive brainstorming for plugin concepts and improvements when exploring ideas, not implementing.
Plugin Improve
glittercowboy/plugin-freedom-system
Fix bugs, add features to completed plugins. An agent skill from glittercowboy/plugin-freedom-system.
Plugin Lifecycle
glittercowboy/plugin-freedom-system
Manage complete plugin lifecycle - install, uninstall, reset, destroy.
Plugin Packaging
glittercowboy/plugin-freedom-system
Create branded PKG installers for plugin distribution. An agent skill from glittercowboy/plugin-freedom-system.
Questions about Troubleshooting Docs
What does Troubleshooting Docs do?
Captures solved problems as categorized documentation with YAML frontmatter for fast lookup. Troubleshooting Docs is an agent skill from glittercowboy/plugin-freedom-system. Captures solved problems as categorized documentation with YAML frontmatter for fast lookup.
When should I use Troubleshooting Docs?
Troubleshooting Docs fits situations like: user confirms solution with phrases like that worked; via /doc-fix command.
How do I install Troubleshooting Docs in Claude Code?
Run `npx skills add glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a claude-code`. Or copy the skill folder (.claude/skills/troubleshooting-docs in glittercowboy/plugin-freedom-system) into .claude/skills/troubleshooting-docs in your project. Claude Code loads it when a task matches its description.
How do I install Troubleshooting Docs in Codex?
Run `npx skills add glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a codex`. Or copy the skill folder (.claude/skills/troubleshooting-docs in glittercowboy/plugin-freedom-system) into .agents/skills/troubleshooting-docs in your project. Codex loads it when a task matches its description.
Can I use Troubleshooting Docs 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 glittercowboy/plugin-freedom-system --skill troubleshooting-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/troubleshooting-docs, .gemini/skills/troubleshooting-docs, .github/skills/troubleshooting-docs and .opencode/skills/troubleshooting-docs in your project.
What does Troubleshooting Docs need to run?
SKILL.md names no scripts, command-line tools or credentials: Troubleshooting Docs is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Bash, Grep.
Does Troubleshooting Docs 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 Troubleshooting Docs safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Troubleshooting Docs use?
No licence was found for Troubleshooting Docs or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Troubleshooting Docs use?
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Troubleshooting Docs?
Skills that share tags, products or a category with Troubleshooting Docs: Capture (alirezarezvani/claude-skills, 28k stars), Vc Problem Solving (withkynam/vibecode-pro-max-kit, 1.1k stars), Is This A Problem (anthropics/claude-for-legal, 9.6k stars) and Resourceful Problem Solving (swarmclawai/swarmclaw, 688 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Troubleshooting Docs?
glittercowboy (a GitHub user) maintains it in glittercowboy/plugin-freedom-system, which has 216 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on November 19, 2025.
Source: glittercowboy/plugin-freedom-system on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.