refactor: reorganize skill numbering, remove obsolete skills, rename shared libs

- Rename: 00→80 claude-settings-optimizer, 88→79 dintel-skill-update,
  92→81 mac-optimizer, 93→82 tui-design-template
- Rename: dintel-shared → _dintel-shared (consistent with _ourdigital-shared)
- Remove: 61-gtm-manager, 62-gtm-guardian (obsolete), 99_archive
- Update all dintel-* skill refs (114 occurrences across 31 files)
- Sync README.md, CLAUDE.md, AGENTS.md with new structure

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-03-23 19:32:44 +09:00
parent ee355479b7
commit 877db1aa0f
115 changed files with 200 additions and 10979 deletions

View File

@@ -0,0 +1,53 @@
---
allowed-tools: Bash(bash *audit_cleanup.sh*), Bash(bash *cleanup_execute.sh*), Bash(du *), Bash(brew *), Bash(npm *), Bash(pip *), Bash(docker *), Bash(rm *)
description: Scan and clean caches, logs, and clutter — shows sizes first, cleans only with consent
---
## Your task
Scan for reclaimable disk space and offer cleanup.
### Step 1 — Run the audit
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_cleanup.sh
```
### Step 2 — Report
Parse JSON output and present as a table sorted by size (largest first):
| Category | Size | Risk | Target |
|---|---|---|---|
Show the total reclaimable space.
### Step 3 — Ask for consent
Ask which categories to clean. Group by risk level (Safe / Moderate / Risky).
### Step 4 — Dry run first
For approved targets, always run dry-run first:
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/cleanup_execute.sh --dry-run <targets>
```
Show the output and ask for final confirmation.
### Step 5 — Execute
Only after explicit confirmation:
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/cleanup_execute.sh --execute <targets>
```
### Safety rules
- Never execute cleanup without explicit user approval
- Always show sizes before deleting anything
- Always run --dry-run before --execute
- Docker cleanup uses `docker system prune`, never direct file deletion
- No sudo by default — if an action needs sudo, state why and ask first

View File

@@ -0,0 +1,60 @@
---
allowed-tools: Bash(bash *audit_*.sh*), Bash(bash *cleanup_execute.sh*), Bash(du *), Bash(df *), Bash(brew *), Bash(npm *), Bash(pip *), Bash(docker *), Bash(cp *)
description: Full macOS system health check — runs all 5 audit modules and presents unified findings
---
## Your task
Run a full macOS system health check using all 5 audit modules. Follow this workflow exactly:
### Step 1 — Run all audits
Run these scripts sequentially, collecting all JSON output:
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_packages.sh
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_environment.sh
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_security.sh
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_cleanup.sh
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_resources.sh
```
If a script exits non-zero, report the error and continue with other modules.
### Step 2 — Parse and report
Parse all JSON lines. Each has: `{"module":"...","severity":"...","finding":"...","action":"...","details":"..."}`
Present findings grouped by severity (critical first, then warning, then info) as markdown tables:
```
### Critical
| Module | Finding | Recommended Action |
|---|---|---|
### Warning
| Module | Finding | Recommended Action |
|---|---|---|
### Info
| Module | Finding | Recommended Action |
|---|---|---|
```
### Step 3 — Ask for consent
STOP and ask: "Which actions would you like me to perform? You can approve by category (e.g., 'update packages and clean caches') or review each item."
### Step 4 — Execute approved actions only
For cleanup actions, always run `--dry-run` first and show what will happen before running `--execute`.
### Safety rules
- Never execute cleanup without explicit user approval
- Always show sizes before deleting anything
- Security module is read-only — present findings and remediation guidance only
- Back up shell configs before modifying: `cp ~/.zshrc ~/.config/mac-optimizer-backups/.zshrc.$(date +%s)`
- Process deny-list: never suggest killing kernel_task, launchd, WindowServer, loginwindow, mds, mds_stores, opendirectoryd, coreaudiod, SystemUIServer, Finder, Dock
- No sudo by default — if an action needs sudo, state why and ask first
- Docker cleanup uses `docker system prune`, never direct file deletion

View File

@@ -0,0 +1,30 @@
---
allowed-tools: Bash(bash *audit_environment.sh*), Bash(echo *), Bash(cp *)
description: Audit shell environment — PATH, symlinks, shell configs, and startup time
---
## Your task
Audit the shell environment on this Mac.
### Step 1 — Run the audit
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_environment.sh
```
### Step 2 — Report
Parse JSON output and present as a severity-ranked markdown table:
| Severity | Finding | Recommended Action | Details |
|---|---|---|---|
### Step 3 — Ask for consent
If there are fixable issues (duplicate PATH entries, broken symlinks, non-existent directories), list them and ask which to fix.
### Safety rules
- Back up shell configs before modifying: `cp ~/.zshrc ~/.config/mac-optimizer-backups/.zshrc.$(date +%s)`
- Present PATH consolidation suggestions but don't auto-modify

View File

@@ -0,0 +1,32 @@
---
allowed-tools: Bash(bash *audit_packages.sh*), Bash(brew *), Bash(npm *), Bash(pip *), Bash(nvm *), Bash(pyenv *)
description: Audit package managers (Homebrew, npm, pip, pyenv) for outdated packages and issues
---
## Your task
Audit all package managers on this Mac.
### Step 1 — Run the audit
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_packages.sh
```
### Step 2 — Report
Parse JSON output and present as a severity-ranked markdown table:
| Severity | Finding | Recommended Action | Details |
|---|---|---|---|
### Step 3 — Ask for consent
List available update actions grouped by risk. Ask which actions to perform.
### Safety notes
- `brew upgrade` is generally safe but can break projects pinned to specific versions
- Global npm packages are version-independent from project dependencies
- pip upgrades can break dependency chains — suggest `--dry-run` first
- Only audit pyenv-managed environments (not system Python)

View File

@@ -0,0 +1,29 @@
---
allowed-tools: Bash(bash *audit_resources.sh*), Bash(ps *), Bash(kill *), Bash(df *)
description: Monitor CPU, memory, disk, battery, and identify resource-hungry processes
---
## Your task
Check system resource usage on this Mac.
### Step 1 — Run the audit
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_resources.sh
```
### Step 2 — Report
Parse JSON output and present as a severity-ranked markdown table:
| Severity | Finding | Recommended Action | Details |
|---|---|---|---|
### Step 3 — Offer actions
If high-resource processes are found, offer to help. But respect the deny-list:
**Never suggest killing**: kernel_task, launchd, WindowServer, loginwindow, mds, mds_stores, opendirectoryd, coreaudiod, SystemUIServer, Finder, Dock
For user processes consuming excessive resources, ask before terminating.

View File

@@ -0,0 +1,25 @@
---
allowed-tools: Bash(bash *audit_security.sh*)
description: Security posture assessment — SIP, Gatekeeper, Firewall, FileVault, SSH, ports
---
## Your task
Run a read-only security posture assessment.
### Step 1 — Run the audit
```bash
bash $CLAUDE_PLUGIN_ROOT/skills/mac-optimizer/scripts/audit_security.sh
```
### Step 2 — Report
Parse JSON output and present as a severity-ranked markdown table:
| Severity | Finding | Recommended Action | Details |
|---|---|---|---|
### Step 3 — Guidance only
The security module is **read-only**. Present findings and remediation guidance. Do NOT attempt to change security settings. Explain how the user can fix issues themselves via System Settings or Terminal commands.