Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Perf Optimizer

ASecurity

Use when running or debugging the perf-optimizer on Windows.

5 stars
0 votes
0 copies
0 views
Added 10/4/2026
ai-agentspythongoshellbashdebugginggitperformance

Security Analysis

A100/100

Scanned 10/4/2026

$npx -y skills add openamer/openamer --skill perf-optimizer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Perf Optimizer?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Perf Optimizer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/openamer-perf-optimizer/badge)](https://www.skillsdirectory.com/skills/openamer-perf-optimizer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: perf-optimizer
description: >-
  Use when running or debugging the perf-optimizer on Windows.
---

# Perf-Optimizer — KI-Performance-Optimierung

## Beschreibung

Autonomes Performance-Optimierungs-System für OpenAmer auf Windows (Git-Bash/MSYS2).
Führt regelmäßige System-Checks durch und generiert Optimierungsvorschläge.

## Komponenten

```
openamer-laptop/
├── scripts/perf-optimizer.py   # Das Hauptskript
└── skills/perf-optimizer/       # Dieser Skill (Dokumentation)
```

## Funktionen

1. **RAM-Monitoring**
   - Aktuelle RAM-Auslastung (%)
   - Pagefile-Größe und Nutzung
   - Top-10-RAM-Verbraucher (Prozesse)
   - Warmmeldung ab 75%, Kritisch ab 85%

2. **Disk-Monitoring**
   - Speicherplatz pro Laufwerk (GB, %)
   - Temp-Dateien-Größe (User Temp, Windows Temp)
   - OpenAmer Logs-Größe
   - Warmmeldung ab 80%, Kritisch ab 90%

3. **Cron-Timing-Analyse**
   - Cron-Job-Laufzeiten (anhand Datei-Alter)
   - Fehlererkennung in Logs (traceback/exception)
   - Engpass-Erkennung (gleichzeitige Läufe)

4. **Optimierungsvorschläge**
   - Automatisch generierte Handlungsempfehlungen
   - Kategorisiert nach RAM/Disk/Temp/Cron
   - Priorisiert nach severity (high/medium/low)

5. **Auto-Cleanup**
   - Temporäre Dateien löschen (>500 MB)
   - Alte OpenAmer-Logs archivieren (>7 Tage)
   - Im Dry-Run-Modus testbar (`--dry-run`)

## Verwendung

### Einmalig ausführen:

```bash
bash -c 'cd "$(openamer config show home)/scripts" && python3 perf-optimizer.py'
```

### Dry-Run (nur Analyse, keine Löschungen):

```bash
bash -c 'cd "$(openamer config show home)/scripts" && python3 perf-optimizer.py --dry-run'
```

### Ausführliche Ausgabe:

```bash
bash -c 'cd "$(openamer config show home)/scripts" && python3 perf-optimizer.py --verbose'
```

## Exit-Codes

| Code | Bedeutung                              |
|------|----------------------------------------|
| 0    | Alles sauber, keine Optimierung nötig  |
| 1    | Auffälligkeiten erkannt (minor)       |
| 2    | Kritische Probleme (RAM/Disk > Schwelle) |
| 3    | Timeout während der Analyse           |

## Cron-Job (alle 12h)

Der Cron-Job wird via `cronjob`-Tool eingerichtet:

```yaml
schedule: "0 */12 * * *"  # Alle 12 Stunden
command: >
  bash -c 'cd "$(openamer config show home)/scripts" && python3 perf-optimizer.py'
alarm: true  # Alarm bei Exit-Code != 0
```

## JSON-Output-Struktur

Das Skript gibt pro Phase ein JSON-Objekt aus:

- `phase: "ram"` → RAM-Daten
- `phase: "disk"` → Festplatten-Daten
- `phase: "cron_timing"` → Cron-Analyse
- `phase: "suggestions"` → Optimierungsvorschläge
- `phase: "cleanup_executed|cleanup_dry_run"` → Cleanup-Ergebnisse
- `phase: "summary"` → Gesamtbewertung mit Alarm-Status

## Fehlerbehandlung

- Globaler Timeout: 25 Sekunden (verhindert Hänger)
- Encoding-Fallback: utf-8 → cp1252 → cp850 → latin-1
- Powershell-Fallback für WMIC bei fehlenden Berechtigungen
- Alle Exceptions werden abgefangen und als JSON-Fehler gemeldet

## Architektur-Hinweis

Das Skript ist als **externes Python-Skript** in `scripts/` implementiert
(nicht als OpenAmer-Core-Tool), gemäß der OpenAmer-Architektur:
"Capability lives at the edges — baue als Skills + Cron Jobs + Plugins".

Attribution

openameropenamer
View sourceSee grades on GitHubMore from openamer →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →