Auto-activates when user mentions load test, performance test, stress test, k6, Artillery, benchmark, or scalability testing. Expert in designing and executing performance tests.

Delegate complex, multi-step codebase exploration to local Ollama models. Best for analysis, review, and understanding tasks that require reasoning across multiple files.

This skill should be used for configuring devloop project settings via .devloop/local.md, git workflow preferences, commit settings, review options

PM2-based local development server management for Empathy Ledger. Handles port conflicts and auto-restart.

Local Kubernetes development with EKS parity using Kind, LocalStack for AWS services, and local Keycloak for authentication testing

Local Frappe development environment for testing APIs before production deployment. Use when developing or testing Python/API changes locally.

Review current changes against project guidelines before PR

Use when code changes touch database, cache, queue, or other service-dependent components - enforces testing against real local services instead of mocks

Test local Jekyll build and visualize pages using Playwright MCP. Starts the development server, navigates through key pages, captures screenshots, and validates rendering. Use when testing local changes before deployment.

Audit a skill against Anthropic skill-creator standards

Run local AI models with LocalAI. Deploy OpenAI-compatible API for LLMs, embeddings, audio, and images. Use for self-hosted AI, offline inference, and privacy-focused AI deployments.

Specialized in multi-language support (i18n) for Gravito. Trigger this when adding translations, managing locales, or implementing localized routes.

Use when creating llmring.lock file for new project (REQUIRED for all applications), configuring model aliases with semantic task-based names, managing environment-specific profiles (dev/staging/prod), or setting up fallback models - lockfile creation is mandatory first step, bundled lockfile is only for llmring tools

Fast log file analysis with lnav, multi-framework support (Laravel, CodeIgniter, React, Next.js), automatic log pruning, and 70-80% token savings vs reading entire logs

Parse and analyze logs to identify errors, patterns, and issues.

解析和分析日志文件，支持模式匹配、过滤、统计和错误检测。

log-auditor

Captures Claude Code conversation sessions in structured markdown format tied to work items with redaction

Classifies logs by type (session, test, build) using path patterns and frontmatter analysis

Orchestrates multi-log workflows with parallel execution for batch operations across many logs

Parses log files to identify errors and self-correction attempts.

Read MetaTrader 5 log files. TRIGGERS - MT5 logs, Experts pane, indicator errors, compilation errors.

Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.

Validates logs against type-specific schemas checking frontmatter, structure, and required fields

Creates or updates logs using type-specific templates with automatic validation and formatting

>

Writes user-friendly logger messages in active voice for Simple History event logs. Fixes passive voice issues. Use when creating or modifying logger classes in loggers/ directory, writing getInfo() messages, fixing passive voice, reviewing log message clarity, or adding new events to the activity log.

Configures logging systems, log aggregation, and log analysis pipelines

Structured JSON logging with correlation IDs, request context propagation across async boundaries, performance timing decorators, and worker metrics collection.

Comprehensive guide to preventing PII and secrets from appearing in logs through redaction strategies, safe logging practices, and automated filtering.

Guide logging practices based on Dave Cheney's minimalist philosophy. Use when adding log.Info/Debug/Error/Warn/Fatal calls, reviewing logging code, handling errors with log+return pattern, discussing log levels, or designing error handling strategies.

UTF-8 file logging with automatic date-based filenames and thread-safe operations for RocsMiddleware services

Pure logic and math testing with Vitest. Use for single-point assertions on functions, state transitions, and physics calculations. Auto-apply when editing *.test.ts files (except *Progressions.test.ts).

File descriptor abuse, race conditions, and TOCTOU vulnerabilities

Decode intermediate layer predictions using the Logit Lens technique. Use when analyzing what a model predicts at each layer, understanding information flow, or visualizing layer-wise processing.

logos-reader-architect

Migrate Logseq graphs to Obsidian vaults. Use when the user wants to convert their Logseq notes to Obsidian format, migrate from Logseq, or mentions both Logseq and Obsidian in a migration context. Handles property conversion, admonition blocks, block references, journal renaming, collapsed states, numbered lists, and image syntax. Designed for Claude Code usage from within the user's Logseq graph folder.

Query and analyze logs using Loki and LogQL. Provides patterns for correlation ID tracing, error investigation, and service debugging using HuleEdu's structured logging. Integrates with Context7 for latest Loki documentation.

Help craft efficient Grafana Loki / LogQL queries for debugging logs — with label‑based filtering, narrow time windows, and best‑practice guidance to avoid expensive or overly broad scans.

Framework for building AI agents that work effectively across multiple context windows on complex, long-running tasks. Use when building agents for multi-hour/multi-day projects, implementing persistent coding workflows, creating systems that need state management across sessions, or when an agent needs to make incremental progress on large codebases. Provides initializer and coding agent patterns, progress tracking, feature management, and session handoff strategies.

Autonomous multi-step work with dual-reviewer supervision (1A2A workflow) and compound engineering principles

Library documentation via Context7. Use for API references, code examples, framework docs.

REQUIRED skill for creating Loom execution plans. Designs DAG-based plans with mandatory knowledge-bootstrap and integration-verify bookends, parallel subagent execution within stages, and concurrent worktree stages for maximum throughput. Trigger keywords: loom, plan, stage, worktree, orchestration, parallel execution, parallel stages, concurrent execution, knowledge-bootstrap, integration-verify, acceptance criteria, signal, handoff, execution graph, dag, dependencies, loom plan, create plan, write plan, execution plan, orchestration plan, stage dependencies, parallel subagents, functional verification, wiring verification, smoke test.

Browse, inspect, compare, and clean up past pipeline runs. Each run is a

Audit all outdated dependencies with detailed research on changelogs, breaking changes, bug fixes, and deprecations. Creates a temporary plan without updating anything. Use when you want to review what changed in your dependencies before upgrading.

OpenSpec workflow management system for creating, planning, implementing, and archiving specification-driven development changes with comprehensive lifecycle management

This skill should be used when users need to write, review, or debug Stata code for data cleaning and analysis. Use this skill for tasks involving data import, variable management, data documentation, merging/appending datasets, creating analysis variables, and following IPA/DIME Analytics coding standards. This skill should be invoked when working with .do files, .dta files, or any Stata-related data processing tasks.

E2E development: investigate → dig → decompose → implement → test → review → PR

Create a GitHub pull request using gh CLI with proper formatting