Loading...
Loading...
Found 112 Skills
Diagnose risks and inefficiencies in an existing investment portfolio. Use when the user asks to review, audit, or stress-test their current holdings, evaluate portfolio concentration, check factor exposures, assess correlation risks, identify hidden tilts, or get actionable improvement suggestions for a portfolio they already own.
Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki quality.
When the user says phrases like "update the index", "add this to the index", "added a new file", "added a new book/note/document", "need to update the material library index", the **Incremental Maintenance Mode** of this skill should be used. When the user says phrases like "index health check", "index体检", "check the index", "sync the index", "fill in missing index entries", the **Health Check Mode** of this skill should be used to scan all libraries ↔ INDEX to find missing/invalid entries and batch fill them in. Applicable to all libraries with INDEX.md: Reading Notes Library, Core Concepts Library, Viral Script Library, 04-Methodology Precipitation, and any newly created libraries in the future. The value of an index depends on content accuracy—you must fully read the original text before writing; inferring based on file names or impressions will render the index useless for reference. Even if the user only says "I added a file" or "put this in", as long as it involves the index, this skill should be triggered. Do NOT trigger for: Only viewing the index (directly Read), deepening topics (use li-topic), generating scripts (use li-writer). Use when the user adds new content to any indexed library, OR runs a global index health-check to find missing/stale entries.
Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki, second brain, or knowledge base quality.
Replay-first debug flow for SGLang serving problems. Use when a live or recent server shows health-check failures, latency or throughput regressions, queue growth, timeouts, distributed stalls, crash dumps, wrong outputs after deploys, or PD/EP/HiCache issues, and the job is to turn the problem into a replay plus the right next debug tool.
Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.
Run a health check on existing memory (the wiki substrate) and goal artifacts. Use this when the user wants to lint the wiki, health-check the knowledge base, find orphan pages, spot broken or missing cross-links, clean up stale claims and unresolved wikilinks with safe local fixes, consolidate a legacy root `overview.md` into `index.md`, or health-check goal artifacts. Not for adding new material; use /loam::adding-to-memory or /loam::learning-from-session for that.
Debug and troubleshoot production issues on Azure. Covers Container Apps diagnostics, log analysis with KQL, health checks, and common issue resolution for image pulls, cold starts, and health probes. USE FOR: debug production issues, troubleshoot container apps, analyze logs with KQL, fix image pull failures, resolve cold start issues, investigate health probe failures, check resource health, view application logs, find root cause of errors DO NOT USE FOR: deploying applications (use azure-deploy), creating new resources (use azure-prepare), setting up monitoring (use azure-observability), cost optimization (use azure-cost-optimization)
Set up monitoring, logging, and observability for applications and infrastructure. Use when implementing health checks, metrics collection, log aggregation, or alerting systems. Handles Prometheus, Grafana, ELK Stack, Datadog, and monitoring best practices.
Performs a comprehensive health check of a CockroachDB cluster. Gathers deployment context first, then provides tier-appropriate diagnostics. Self-Hosted uses SQL against node-level system tables and CLI. Advanced/BYOC use Cloud Console and SQL with node visibility. Standard monitors provisioned compute and workload via Cloud Console. Basic monitors Request Unit consumption and connectivity. Use for daily checks, pre-maintenance validation, post-incident verification, or production readiness assessment.
Create and manage Oodle synthetic monitors — HTTP and TCP health checks with assertions and configurable intervals.
Use when service fails with Connection refused to database or redis. Use when API crashes because DB not ready.