pro-skills-repo-administraktor

Use when a task risks running out of context window, when a long-running agent session or multi-step workflow must stay coherent across many turns, when token cost or latency climbs with conversation length, or when the user asks about compaction, summarizing conversation history, truncating tool output, KV-cache or prefix caching, cache-friendly prompt ordering, context budgets, or splitting work across sub-agents. Covers compaction, observation masking, cache-aware layout, and context partitioning, both for an agent managing its own session and for code that builds agent systems. Do not use for RAG retrieval design or vector database selection.

Use when the user asks to optimize, speed up, tune, or make a Linux system faster — laptops, desktops, or servers. Analyzes hardware, kernel and boot parameters, memory/swap/zram, storage, services, GPU, desktop environment, and network; proposes a prioritized, risk-labeled optimization plan; applies ONLY user-approved changes; verifies every change and documents rollback. Idempotent: re-running on the same system converges, never duplicates config, never re-installs. Analyze-only mode is available. Do NOT use for application code, containers, or website performance.

Autonomous, safety-first pull request review-and-merge pass over a repository with many open PRs, on any tech stack (Node, PHP, Go, Python, Rust, Ruby, Java/Kotlin, Android, monorepos). Reviews each PR's full diff, classifies it CLEAN / FIXABLE / BLOCKED, fixes small issues, merges safe PRs one at a time, verifies the default branch still builds and passes tests, and produces a final report. Use this skill whenever the user mentions a backlog of pull requests, asks to review and merge PRs, clear the PR queue, "merge what's safe", check that nothing breaks after merging, or hands PR handling to an agent while they are away, even if they don't say "skill" or name a specific stack. Supports "review only" / "dry run" mode.

Use whenever the user wants to create, rewrite, or improve a README.md for a GitHub/GitLab repo, project, library, CLI tool, app, or package. Trigger on "write me a README", "make a README for this repo", "improve my project's README", "make my repo/GitHub page look professional", or requests for repo docs, project landing content, or quickstart docs. Also trigger when the user pastes project details, a package.json/pyproject.toml, or a repo link and asks for docs. Interviews the user with targeted questions, offers 4 distinct visual/structural README designs to pick from, researches any related or inspirational projects named, and produces a polished, SEO-optimized, beginner-friendly README.md with a full table of contents, working anchor links, badges, and a real quickstart. Not for generic blog posts or non-repo documentation.

Use when the user asks to install, initialize, integrate, upgrade, or document GitHub Spec Kit. Creates a repository-specific constitution and SPECKITINIT.md with complete copy-paste workflows using the public workflow catalog. Do NOT use to implement application features; use the installed Spec Kit implementation command.

Use this skill when designing terminal user interfaces, creating TUI layouts, choosing TUI color schemes, implementing keyboard AND mouse navigation, building terminal dashboards, or working with any TUI framework. Activates on mentions of TUI design, terminal UI, Ratatui layout, Ink components, Textual widgets, Bubbletea views, terminal color palette, keybinding design, panel layout, split panes, terminal dashboard, box-drawing characters, sparklines, progress bars, modal dialogs, focus management, mouse support, clickable terminal UI, or terminal accessibility. Always consult this skill when a TUI is being built or restyled, even if the user only asks for it to "look modern" or "feel clickable" — mouse interaction and visual polish are core to this skill, not an afterthought.

Use when creating WordPress plugins: hooks, admin interfaces, custom tables, REST endpoints, Abilities API, AI Client integration, PHP-only blocks, security hardening, or plugin test setup. Do not use for theme templates or storefront setup; use wordpress-theme-development or wordpress-woocommerce-development.

Use when creating or converting WordPress themes: theme.json v3, template hierarchy, block patterns, template parts, navigation overlays, breadcrumbs, block styles, child themes, or WordPress 7.0 theme features. Do not use for plugin back-end logic or store setup; use wordpress-plugin-development or wordpress-woocommerce-development.

Use when building or customizing WooCommerce stores: product configuration, payment gateways, shipping, checkout flow, custom product types, order automation via the Abilities API, or store performance. Do not use for general theme or plugin work; use wordpress-theme-development or wordpress-plugin-development.