settings-trim

Clean and optimize permission entries in .claude/settings.local.json.

1|Updated Nov 18, 2023
One-click install
npx skills add https://github.com/CherrySalmon/tyto --skill settings-trim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: settings-trim
Source: https://github.com/CherrySalmon/tyto/tree/main/.claude/skills/settings-trim
Command: npx skills add https://github.com/CherrySalmon/tyto --skill settings-trim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines AI permission configurations by removing redundant, duplicate, or garbled entries in .claude/settings.local.json, ensuring a clean and efficient access control list.

Core Features & Use Cases

  • Redundancy Elimination: Automatically identifies and removes permission entries that are already covered by broader wildcard patterns (e.g., Bash(git push:*) superseding Bash(git push)).
  • Consolidation: Organizes git -C entries to use a standardized wildcard format, simplifying management.
  • Garbage Removal: Filters out entries that appear to be accidental text fragments rather than valid commands.
  • Use Case: After a series of manual permission adjustments, your settings.local.json might contain overlapping or nonsensical entries. This Skill cleans it up, making it easier to audit and manage.

Quick Start

Run the settings-trim skill to clean up the permissions in your local settings file.

Frequently Asked Questions about settings-trim

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

FAQPage Schema
How do I remove duplicate and redundant permissions in settings.local.json?

To remove duplicate permissions in settings.local.json, you need to clean up redundant entries that are already covered by broader wildcard patterns. This process identifies and deletes overlapping access control rules to maintain a streamlined configuration file.

Why does my AI permission configuration contain garbled or nonsensical entries?

AI permission configurations accumulate garbled entries from accidental text fragments generated during manual permission adjustments. Filtering out these invalid command structures ensures the settings file only contains valid and intended access control rules.

What is wildcard subsumption for cleaning up AI settings?

Wildcard subsumption in AI settings is a cleanup rule where specific permission patterns are removed if a broader wildcard already grants that access. This consolidates the access control list by eliminating redundant rules like specific git commands covered by a general git wildcard.

How do I consolidate git -C permission entries in my local settings?

To consolidate git -C permission entries in local settings, you can standardize them into a wildcard format. This simplifies management by grouping similar directory-specific command structures into a unified and readable permission rule.

Can I organize my AI permissions for better readability and maintainability?

You can organize AI permissions for better readability by grouping remaining entries logically after redundancy elimination. This approach structures the settings.local.json file to make future audits and access control management significantly easier.