Claude Skills by fritzprix

Analyze a workspace and generate or maintain a modular project documentation setup with a lean, concise agents.md entrypoint. Governs user directives, precautions, and desired persona, while providing selective on-demand reading of detailed guide files and immediate on-the-fly updates when code or rules change. Triggers: 'agent init', 'agents.md 생성', '워크스페이스 분석', 'agent guideline 생성', 'agents.md 모듈화', 'agent-init'. Not for LibrAgent runtime/harness facts (use libragent-harness-reference).

Critically audit refactorings and design decisions against the real codebase, verify claims vs code, score only relevant quality axes, and write evidence-based tech reports. Use after refactors, when reviewing agent-reported work, or when asking for architecture / ISP / DRY / token-cost / reliability feedback. For builtin MCP tool audits, prefer critique-builtin-tool or lean-builtin-tool-auditor instead.

Comprehensive computer diagnosis and troubleshooting. Use this skill when a user reports issues with their computer (e.g., "my computer is slow", "it's freezing", "loud fan noise", "no disk space") to analyze system metrics (CPU, RAM, Disk, Network) across macOS, Windows, and Linux, and generate a detailed report with actionable recommendations.

Guide for creating builtin MCP tools in LibrAgent. Use when creating a new builtin MCP server, adding tools to existing builtin servers, refactoring tool implementations to follow best practices, or auditing tool compliance with the Tool Design Manifesto v2.1.

Create a GitHub pull request with gh, target the correct base branch, push only committed work, and bind related issues via Fixes/Closes keywords. Use when asked to create a PR, open a pull request, push and open PR, link/bind/associate an issue to a PR, add Fixes #N, or close issues on merge.

Audit and critique builtin MCP tool implementations in LibrAgent. Use when auditing existing builtin MCP server implementations for compliance, reviewing pull requests that add or modify builtin tools, validating tool implementations against the Tool Design Manifesto v2.1, or identifying potential issues before they reach production.

Analyze a codebase to discover documentation gaps in README.md and docs/ directories, then generate or update missing documentation. Use when the user asks to (1) audit README/docs for missing coverage, (2) find undocumented features or modules, (3) fill documentation gaps, (4) update docs to match current code, (5) generate a doc-gap report, (6) "문서 누락 분석", "README/_docs_ 감사", "문서 보완", "docs gap audit", "undocumented features". Triggers on any request to compare codebase structure against ex...

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

Extract and analyze LibrAgent debug logs with pattern matching and context. Use when debugging LibrAgent issues, analyzing agent workflows, investigating tool execution problems, or extracting specific log patterns like errors, warnings, planning operations, MCP tool calls, or browser automation traces. Supports extracting last N lines or searching for patterns with surrounding context.

Analyze codebase against new feature requirements, map affected modules and dependencies, identify architectural risks, and propose a structured refactoring and implementation plan before writing code. Use when starting a new feature, planning refactoring, analyzing codebase impact, or reviewing feature feasibility.

Analyze Harbor benchmark jobs and ATIF trajectories, identify evidence-backed weaknesses across LibrAgent builtin tools, prompts, agent guidance, execution policy, and benchmark instrumentation, then design controlled improvements and rerun comparisons. Use when analyzing Harbor or Terminal-Bench results, optimizing the harness, investigating tool-call failures or retries, auditing prompt/context efficiency, or running repeated BM → analysis → improvement cycles.

Analyze benchmark jobs (Terminal-Bench, Harbor) in jobs/, inspect ATIF trajectory logs, tool call errors, prompt issues, timeout/circuit-breaker failures, and verifier results to identify harness bottlenecks in LibrAgent and generate evidence-based improvement plans. Trigger phrases: 'jobs 트레이스 분석', 'benchmark trace analysis', 'jobs 디렉토리 분석', '하네스 분석', '성적 감점 요인 분석', 'jobs-trace-analyzer'.

Audit builtin MCP tool implementations in LibrAgent for schema accuracy, minimal complexity, and non-bloated hints. Use when reviewing builtin tools for compliance, validating tool schemas, checking for over-engineering, or ensuring next-action hints are concise and relevant.

Code quality validation for LibrAgent project. Use when performing code quality checks, refactoring validation, or ensuring code meets project standards for TypeScript/React frontend and Rust backend. Runs comprehensive validation including linting, formatting, type checking, build verification, and dead code detection.

Refactor oversized source files into smaller, coherent modules while reducing complexity and preserving behavior. Use when Claude needs to split a large component, hook, service, command handler, or Rust module; untangle mixed responsibilities; extract helpers or submodules; or reorganize code into a clearer modular design without changing the public contract.

Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions v...

Audit and update Main README (README.md, README.ko.md) and User Project Website (docs/user/index.md, website/) to ensure newly added features, bundled skills, and tools are properly showcased. Use when the user requests to update the main README, sync landing pages, showcase new features on the project page, or "메인 README 누락 업데이트", "프로젝트 페이지 랜딩 업데이트", "쇼케이스 동기화", "신규 기능 README 반영".

Guide and principles for refactoring built-in MCP tools in LibrAgent. Use this skill when reviewing, refactoring, or optimizing existing built-in tools to reduce AI cognitive load, eliminate internal callback tool exposure, consolidate redundant tools, and ensure strict state synchronization across the system.

Manage the release process for LibrAgent. Use this skill to analyze changes, update the changelog intelligently, synchronize user documentation (docs/ & website/), and publish new versions.

Comprehensive review and audit of uncommitted local code changes in git working copy (staged, unstaged, untracked). Use when asked to review local changes, audit git diff, check uncommitted work before commit/PR/push, or inspect working copy edits for potential bugs, security issues, formatting, or regression risks.

Review and triage PR review comments (from Copilot, bots, or human reviewers) against the actual codebase. Use when a user wants to evaluate the validity, priority, or accuracy of PR review comments before deciding which ones to act on. Also handles applying approved fixes. Triggers on requests like "review all comments in this PR", "evaluate PR feedback", "which PR comments are valid", "apply the PR suggestions".

Use when the user needs to diagnose and install runtime environment dependencies (Python, Node.js, uv) for running LibrAgent or MCP servers. Use on new machines, MCP "command not found" errors, or missing Python/Node runtime failures. LibrAgent 실행에 필요한 Python, Node.js 등의 환경을 자동으로 진단하고 설치하도록 안내하는 마법사입니다.

Re-anchor an AI agent to its SOUL.md persona by re-internalizing tone, rules, and identity. Use when the agent drifts into generic/corporate responses, is explicitly asked to reconnect with its soul, or needs to bootstrap a missing SOUL.md. SOUL content is already injected into the system prompt as ## Persona Template — do not re-read existing soul files.

Analyzes SQLite databases to identify schema issues, data inconsistencies, and relationship problems. Use when investigating database bugs, validating data integrity, debugging ORM mapping issues, or understanding database structure. Particularly useful for diagnosing ID mismatches, foreign key violations, and entity relationship errors.

Code recipes and explanation for synchronizing Rust backend pending tool approvals (YOLO mode/manual approval) to the frontend React UI when a user resumes or opens an existing agent session. Use this skill when modifying the AgentSession state to maintain approval channels or when fixing UI bugs related to missing pending tool executions upon page reload/session switch.

Guide for creating high-quality tool servers (MCP servers) that enable LLMs to interact with external services through well-designed tools. Use when building tool servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Analyzes LibrAgent agent session trace files (.trace.json) to understand what an AI agent actually did during a session. Use when a user shares a .trace.json file, asks "what did the agent do?", wants to debug agent behavior, investigate tool call patterns, validate concurrency limits, or review session results. The trace file is the raw conversation record between the agent and its tools.

Analyze recent git commits and codebase changes to update, synchronize, and align VitePress documentation (docs/user/ and website/). Use when the user requests to update documentation from git diffs, sync VitePress docs, audit doc gaps, or update user guides after code changes. Triggers on "vitepress 문서 현행화", "git 변경사항으로 문서 업데이트", "최신 git commit 반영하여 docs 업데이트", "vitepress-doc-sync", "sync docs with git", "update vitepress docs", "doc sync".

Python CLI wrapper for X (Twitter) interaction using Twikit. Use when the user wants to: (1) post tweets (with text or media, including thread replies), (2) view home timeline, (3) view a user's tweets, (4) search tweets, (5) like/favorite a tweet, (6) retweet a tweet, or (7) delete a tweet. On first use, guide the user through credential setup (username, email, password, optional TOTP) or browser cookie setup. Store config in ~/.libragent/x_config.json and session cookies in ~/.libragent/x_c...

Critically audit refactorings and design decisions against the real codebase, verify claims vs code, score only relevant quality axes, and write evidence-based tech reports. Use after refactors, when reviewing agent-reported work, or when asking for architecture / ISP / DRY / token-cost / reliability feedback. For builtin MCP tool audits, prefer critique-builtin-tool or lean-builtin-tool-auditor instead.

Comprehensive computer diagnosis and troubleshooting. Use this skill when a user reports issues with their computer (e.g., "my computer is slow", "it's freezing", "loud fan noise", "no disk space") to analyze system metrics (CPU, RAM, Disk, Network) across macOS, Windows, and Linux, and generate a detailed report with actionable recommendations.

Guide for creating builtin MCP tools in LibrAgent. Use when creating a new builtin MCP server, adding tools to existing builtin servers, refactoring tool implementations to follow best practices, or auditing tool compliance with the Tool Design Manifesto v2.1.

Audit and critique builtin MCP tool implementations in LibrAgent. Use when auditing existing builtin MCP server implementations for compliance, reviewing pull requests that add or modify builtin tools, validating tool implementations against the Tool Design Manifesto v2.1, or identifying potential issues before they reach production.

Extract and analyze LibrAgent debug logs with pattern matching and context. Use when debugging LibrAgent issues, analyzing agent workflows, investigating tool execution problems, or extracting specific log patterns like errors, warnings, planning operations, MCP tool calls, or browser automation traces. Supports extracting last N lines or searching for patterns with surrounding context.

Code quality validation for LibrAgent project. Use when performing code quality checks, refactoring validation, or ensuring code meets project standards for TypeScript/React frontend and Rust backend. Runs comprehensive validation including linting, formatting, type checking, build verification, and dead code detection.

Refactor oversized source files into smaller, coherent modules while reducing complexity and preserving behavior. Use when Claude needs to split a large component, hook, service, command handler, or Rust module; untangle mixed responsibilities; extract helpers or submodules; or reorganize code into a clearer modular design without changing the public contract.

Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions v...

Guide and principles for refactoring built-in MCP tools in LibrAgent. Use this skill when reviewing, refactoring, or optimizing existing built-in tools to reduce AI cognitive load, eliminate internal callback tool exposure, consolidate redundant tools, and ensure strict state synchronization across the system.

Manage the release process for LibrAgent. Use this skill to analyze changes, update the changelog intelligently, synchronize user documentation (docs/ & website/), and publish new versions.

Review and triage PR review comments (from Copilot, bots, or human reviewers) against the actual codebase. Use when a user wants to evaluate the validity, priority, or accuracy of PR review comments before deciding which ones to act on. Also handles applying approved fixes. Triggers on requests like "review all comments in this PR", "evaluate PR feedback", "which PR comments are valid", "apply the PR suggestions".

Re-anchor an AI agent to its `SOUL.md` persona by locating the active soul file, reading it, and re-internalizing its tone, rules, and identity. Use when the agent is starting fresh, drifting into generic/corporate responses, explicitly asked to read its soul, or needs to resync with the dedicated persona layer loaded from `.github/SOUL.md`, `SOUL.md`, or lowercase variants.

Guide for creating high-quality tool servers (MCP servers) that enable LLMs to interact with external services through well-designed tools. Use when building tool servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Guide for creating builtin MCP tools in LibrAgent. Use when creating a new builtin MCP server, adding tools to existing builtin servers, refactoring tool implementations to follow best practices, or auditing tool compliance with the Tool Design Manifesto v2.1.

Audit and critique builtin MCP tool implementations in LibrAgent. Use when auditing existing builtin MCP server implementations for compliance, reviewing pull requests that add or modify builtin tools, validating tool implementations against the Tool Design Manifesto v2.1, or identifying potential issues before they reach production.

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

Integrates with any IMAP/SMTP mail server (Gmail, Outlook, Naver, Kakao, custom servers, etc.). Use when the user wants to read, send, search, reply to, or manage emails. On first use, runs interactive account setup in the terminal to store credentials in a local config file with restricted permissions. Subsequent requests use the stored config without re-asking for credentials. Triggers on requests like: "메일 보여줘", "이메일 확인", "send email", "받은 편지함", "메일 보내줘", "메일 검색".

Extract and analyze LibrAgent debug logs with pattern matching and context. Use when debugging LibrAgent issues, analyzing agent workflows, investigating tool execution problems, or extracting specific log patterns like errors, warnings, planning operations, MCP tool calls, or browser automation traces. Supports extracting last N lines or searching for patterns with surrounding context.

Code quality validation for LibrAgent project. Use when performing code quality checks, refactoring validation, or ensuring code meets project standards for TypeScript/React frontend and Rust backend. Runs comprehensive validation including linting, formatting, type checking, build verification, and dead code detection.

Refactor oversized source files into smaller, coherent modules while reducing complexity and preserving behavior. Use when Claude needs to split a large component, hook, service, command handler, or Rust module; untangle mixed responsibilities; extract helpers or submodules; or reorganize code into a clearer modular design without changing the public contract.