windows-terminal-fix

Scan Windows Terminal settings.json and remove invalid absolute resource paths.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/christseng89/ClaudeMastery --skill windows-terminal-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-terminal-fix
Source: https://github.com/christseng89/ClaudeMastery/tree/main/Skills/fix-terminal
Command: npx skills add https://github.com/christseng89/ClaudeMastery --skill windows-terminal-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Windows Terminal reports missing resources (icons, backgroundImage, etc.) in settings.json. This skill identifies and removes broken references so the startup warnings disappear without affecting other settings.

Core Features & Use Cases

  • Safe cleanup: removes broken absolute paths from profiles and resource fields.
  • Non-destructive edits: deletes invalid fields entirely and preserves valid settings.
  • Use Case: run when Terminal shows "resource not found" warnings after uninstalls or moves of apps like Docker or WSL that affected icons or images.

Quick Start

Use this skill to scan your Windows Terminal settings.json and automatically remove broken resource paths.

Frequently Asked Questions about windows-terminal-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix missing resource warnings in Windows Terminal settings.json?

To fix missing resource warnings in Windows Terminal, you need to scan settings.json and remove broken absolute paths. This automatically deletes invalid icon or backgroundImage references while preserving valid configurations.

What's the best way to clean up broken references in Windows Terminal profiles?

The best way to clean up broken references is to automate the removal of invalid absolute paths from Windows Terminal profiles. This safely deletes missing resource fields entirely without affecting your non-resource settings.

Why does Windows Terminal show resource not found errors after uninstalling software?

Windows Terminal shows resource not found errors because uninstalling software like Docker or WSL removes files referenced by absolute paths in settings.json. Removing these broken references ensures the JSON remains valid and warnings disappear.

Can I safely remove invalid backgroundImage paths from Windows Terminal without losing other settings?

Yes, you can safely remove invalid backgroundImage paths without losing other settings. The cleanup process performs non-destructive edits by targeting only broken resource fields and preserving the rest of your valid JSON.

Does fixing Windows Terminal settings.json require manual JSON editing?

Fixing Windows Terminal settings.json does not require manual JSON editing. Automated scanning identifies broken resource references and removes invalid fields entirely, ensuring the JSON remains valid and startup warnings stop.

When do I need to scan settings.json for broken Windows Terminal references?

You need to scan settings.json for broken Windows Terminal references when the application displays missing resource warnings on startup. This typically happens after moving or uninstalling apps that affected your icon or image paths.