Loading...
Loading...
Found 76 Skills
App stack advisor — essential apps by business stage, cost optimization, performance impact analysis
When the user wants to analyze Google Ads performance by device, geography, day of week, hour of day, or any combination of these dimensions. Also triggers on 'device performance', 'mobile vs desktop', 'bid adjustments', 'geo performance', 'location targeting', 'dayparting', 'ad schedule', 'hourly performance', 'device modifiers', 'geo bid adjustments', 'best time to run ads', 'location exclusions', or 'campaign splits by device or geo'. For full campaign structure see google-ads-search. For Smart Bidding see google-ads-bidding.
Use when profiling CPU/memory hot paths, generating flame graphs, or capturing JFR/perf evidence.
HOWL v2 — Hunt, Optimize, Win, Learn. Nightly self-improvement loop for the WOLF autonomous trading strategy. Runs once per day (via cron) to review all trades from the last 24 hours, compute win rates, analyze signal quality correlation, evaluate DSL tier performance, identify missed opportunities, and produce concrete improvement suggestions for the wolf-strategy skill. v2 adds fee drag ratio (FDR) analysis, holding period bucketing, LONG vs SHORT regime detection, rotation cost tracking, cumulative drift detection, and gross vs net profit factor separation. Use when setting up daily trade review automation, analyzing trading performance, or improving an autonomous trading strategy through data-driven feedback loops. Requires Senpi MCP connection, mcporter CLI, and OpenClaw cron system.
Use when you need to analyze Java profiling data collected during the detection phase — including interpreting flamegraphs, memory allocation patterns, CPU hotspots, threading issues, systematic problem categorization, evidence documentation with profiling-problem-analysis and profiling-solutions markdown files, or prioritizing fixes using Impact/Effort scoring. Part of the skills-for-java project
System Audit - Proactively identify bug risks, security vulnerabilities, performance issues, maintainability debt, and architecture drift from code, and generate a batch list of findings. Triggers: Users say "review the system", "audit code", "scan for issues", "find bugs", "what can be optimized".
Skill Evolver (Taotie) — Strengthen the target skill by "devouring" and analyzing the advantages of other skills. This skill must be triggered when users intend to: integrate two skills, optimize one skill with another, compare and analyze the pros and cons of two skills, extract the strengths of one skill into another, or express intentions like "feed X to Y", "use X to optimize Y", "integrate these two skills", "devour this skill", "skill evolution", "skill upgrade", "merge skills", etc. Even if users don't explicitly mention "Taotie", this skill should be used as long as it involves capability transfer, comparative analysis, or advantage extraction between two skills.
Google API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".
Capture Unreal Engine traces, inspect Trace Store files, keep Unreal Insights GUI open, and export/summarize timing/counter data.
Performance analysis coordination workflow. Guides profiling delegation, bottleneck classification (compute/memory/launch/communication/sync), and structured report generation. Use when the user asks to analyze performance, profile a workload, check MFU/SOL, or diagnose bottlenecks.
Intelligent Code Debugging Assistant that helps you visualize how your code runs. When you say things like "I want to see why this function is so slow", "The code throws an error halfway through execution and I don't know where the problem is", or "This business logic is too complex and I can't figure out the execution order", I will help you trace the code execution path, identify slow-performing sections, and locate the root cause of errors. When skill optimization points are identified, I will ask if you want to call the skill-evolution-driver for optimization
Analyze code for performance issues and suggest optimizations. Use when users ask to "optimize this code", "find performance issues", "improve performance", "check for memory leaks", "review code efficiency", or want to identify bottlenecks, algorithmic improvements, caching opportunities, or concurrency problems.