Loading...
Loading...
Found 4,147 Skills
Managing dependencies, CI/CD optimization, Docker configuration, and operational observability (logging/alerting/health checks). Use for build errors or dev environment issues.
Use when the user asks to monitor, watch, shepherd, or babysit a PR until it is green and approved.
Use when the user asks to upload a file, or a local screenshot, recording, log, document, or build artifact is needed for a PR or preview.
Workload-aware architecture design for VeloDB/Apache Doris. MUST USE when designing data architectures, choosing between data models, planning ingestion strategies, sizing clusters, or translating business requirements into VeloDB/Doris system designs. Complements velodb-best-practices with decision frameworks and sizing-first workflow. Use when user describes a workload involving: IoT, sensor data, telemetry, real-time analytics, dashboard, log analysis, log search, CDC sync, time-series, device monitoring, point query service, ad-hoc analytics, lakehouse federation, ETL/ELT pipeline, report analytics, clickstream, user behavior, observability, metrics, fleet tracking, or any OLAP workload requiring table design from scratch. Also triggers on prompts like: "design a table for...", "how should I store...", "build an architecture for...", "we have X devices sending data every Y seconds", "recommend a cluster size for...", "what data model should I use for...", "we need to ingest X GB/day", "migrate from MySQL/PostgreSQL to VeloDB". Also use for legacy analytics/search/serving stack consolidation prompts even when VeloDB is not named explicitly, including replacing or migrating from Impala, Kudu, Elasticsearch/ES, Greenplum, Presto, HBase, Hive, Hadoop, Redis, or Lambda-style multi-engine data platforms.
VeloDB/Apache Doris table design and cluster sizing best practices. MUST USE when writing, reviewing, or optimizing Doris CREATE TABLE statements, partition/bucket strategies, data models, or cluster configurations. ALSO MUST USE whenever the velodb-architecture-advisor skill produces DDL — apply the Pre-Flight Checklist to every CREATE TABLE before output. Also triggers on any workload design involving: IoT, analytics, dashboard, CDC, time-series, log analysis, real-time warehouse, point query, data platform, or any scenario where table design decisions are being made. Also triggers on replacing or migrating from legacy analytics/search/serving stacks such as Impala, Kudu, Elasticsearch/ES, Greenplum, Presto, HBase, Hive, Hadoop, Redis, or Lambda-style multi-engine data platforms, even when VeloDB/Doris is not named explicitly. Also use when user provides a VeloDB connection string or asks to get started. Also triggers on slow query investigation, query profiling, runtime performance diagnosis, tablet skew analysis, and table health checks — any scenario where runtime evidence (profile output, tablet distribution) informs optimization. For Cloud operations (auth, cluster lifecycle, billing, networking), defer to the velocli-cloud skill.
Use this skill when committing code, writing commit messages, or reviewing git history in this Next.js project. Triggers on: "commit this", "write a commit message", "what should my commit say", "git commit", or any request to stage and commit changes. Provides project-specific conventional commit format, Thai-language comment conventions, and scope rules matched to this codebase's structure.
Measures one or more FHIR Implementation Guides read-only and reports the numbers as JSON and Markdown — scope, complexity, content hygiene, duplication, linguistics, maturity and risk — and compares several IGs side by side using normalised metrics. It builds, changes and publishes nothing. Use this skill when reviewing or QA-ing an MII KDS module IG before a release, when comparing a module against kerndatensatz-basis or another Implementierungsleitfaden, when tracking how a module grows between releases, or when someone asks how large, how clean or how mature a guide actually is. Do not use for migrating a guide onto the module template or for translating one; see mii-ig-migration and fhir-ig-translation.
Build and run a local production Docker image for a Next.js app safely. Use this skill when the user wants to build a Docker image, run a container with an env file, check whether an image version already exists locally, or deploy a Next.js app locally with Docker without hard-coding the project name.
Use when the user is leaving and wants work carried to completion without them — "I'm going to sleep", "work overnight", "keep working while I'm away", "I'll be offline", "don't wait for me", "don't ask, just do it", "merge it yourself", "full autonomy". Also use when a long task must survive context compaction or session death with an audit trail.
Use when maintaining the English ↔ Simplified Chinese bilingual documentation pairs in a repository — writing a new counterpart, applying a minimal update to keep an existing pair in sync, or verifying pair consistency after an edit.
Review a pull request or a branch against the repository's standards — skill frontmatter and body, docs and bilingual pairs, Agent Notes, and scripts — and report blockers separately from suggestions, prioritizing correctness and required behavior over style.
Configure Azure VNets, NSGs, and Azure Firewall. Implement hub-spoke topology and private endpoints. Use when designing Azure network infrastructure.