maintenance
OpenClaw 运维与故障修复
firewall
防火墙配置
ansible
Ansible 自动化运维
cloud-backup
云备份方案
proxy
代理服务器配置
compose
Docker Compose 编排
image-management
Docker 镜像管理
tar-compression
归档与压缩
configmap-secret
Kubernetes ConfigMap 与 Secret
load-balancer
负载均衡配置
pod-management
Kubernetes Pod 管理与调试
service-ingress
Kubernetes Service 与 Ingress
monitoring
监控与告警
mongodb
MongoDB 数据库管理
shell-scripting
Bash Shell 脚本编写
deployment
Kubernetes Deployment 管理
ci-cd
CI/CD 流水线配置
disaster-recovery
灾难恢复
elasticsearch
Elasticsearch 集群管理
pulumi-esc
Guidance for working with Pulumi ESC (Environments, Secrets, and Configuration). Use when users ask about managing secrets, configuration, environments, short-term credentials, configuring OIDC for AWS, Azure, GCP, integrating with secret stores (AWS Secrets Manager, Azure Key Vault, HashiCorp Vault, 1Password), or using ESC with Pulumi stacks.
cloudformation-to-pulumi
Convert an AWS CloudFormation stack or template to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of CloudFormation to Pulumi.
pulumi-arm-to-pulumi
Convert or migrate Azure ARM (Azure Resource Manager) templates, Bicep templates, or code to Pulumi, including importing existing Azure resources. This skill MUST be loaded whenever a user requests migration, conversion, or import of ARM templates, Bicep templates, ARM code, Bicep code, or Azure resources to Pulumi.
pulumi-cdk-to-pulumi
Convert an AWS CDK application to Pulumi. This skill MUST be loaded whenever a user requests migration or conversion of a CDK application to Pulumi.
pulumi-terraform-to-pulumi
Migrate Terraform projects to Pulumi. Use when users need to move infrastructure from Terraform to Pulumi, translate HCL configurations, or convert Terraform modules to Pulumi components.
pulumi-automation-api
Best practices for using Pulumi Automation API to programmatically orchestrate infrastructure operations. Covers multi-stack orchestration, embedding Pulumi in applications, architecture choices, and common patterns.
pulumi-component
Guide for authoring Pulumi ComponentResource classes. Use when creating reusable infrastructure components, designing component interfaces, setting up multi-language support, or distributing component packages.
pulumi-best-practices
Best practices for writing reliable Pulumi programs. Covers Output handling, resource dependencies, component structure, secrets management, safe refactoring with aliases, and deployment workflows.
zotero-mcp-code
Search Zotero library using code execution for efficient multi-strategy searches without crash risks. Use this skill when the user needs comprehensive Zotero searches with automatic deduplication and ranking.
pda-reframing
Rephrase tasks and requests by avoiding Demand Avoidance triggers for someone with PDA autism spectrum disorder. It transforms demands into exploration and autonomous actions.
HLS Troubleshooting
This skill should be used when the user mentions "HLS not working", "haskell-language-server issues", "Haskell LSP problems", "no completions in Haskell", "HLS diagnostics not showing", "troubleshoot HLS", "Haskell code analysis not working", or asks why HLS features aren't available in Claude Code.
tmux
This skill should be used when the agent needs to drive, observe, or manage ANOTHER interactive command-line program inside tmux — especially other agent CLIs such as codex, gemini, or aider. Triggers on spawning or reusing a tmux session/window/pane for a long-lived CLI, typing input with send-keys, reading output with capture-pane, detecting when the driven CLI is idle/done, binding one Claude session to its sub-process, serializing concurrent drivers (sync/locking), and lifecycle/cleanup of those windows. Do NOT trigger for plain one-shot shell commands that finish on their own, for tmux questions unrelated to driving an interactive program, or when the user is merely discussing tmux as a topic.
gemini
This skill should be used when the user wants to invoke Google Gemini CLI for complex reasoning tasks, research, and AI assistance. Trigger phrases include "use gemini", "ask gemini", "run gemini", "call gemini", "gemini cli", "Google AI", "Gemini reasoning", or when users request Google's AI models, need advanced reasoning capabilities, research with web search, or want to continue previous Gemini conversations. Automatically triggers on Gemini-related requests and supports session continuation for iterative development.
telegram
This skill should be used when the user asks to send a file, artifact, image, document, PDF, video, audio, or text message to their Telegram chat. Triggers include "use asun:telegram to send …", "send this to telegram", "telegram this file", "post to telegram", "share via telegram", or any phrase that asks Claude to push content through the user's personal Telegram channel. The skill is one-way (Claude → Telegram); it does not read incoming Telegram messages.
nanobanana
This skill should be used when the user wants to generate, create, make, draw, design, edit, or restore any image or visual content. Trigger phrases include "generate an image", "create an illustration", "make an icon", "draw a diagram", "design a pattern", "edit this photo", "restore a photo", "use nanobanana", "nano banana", "make a thumbnail", "featured image", "visual asset", "graphic", "artwork", "background image", "wallpaper", "texture". Standalone image generation using the Nano Banana MCP server with Gemini image models. No Gemini CLI required.
codex
This skill should be used whenever the user names codex as the actor for ANY task, regardless of verb or phrasing — "use codex" / "using codex", "ask codex", "run codex", "call codex", "have/let/tell/get codex do X", "delegate this to codex", "with/via codex", "codex cli", "codex: <task>", or bare imperatives like "codex review/fix/implement …" — or explicitly asks to delegate work to a frontier reasoning model (e.g., "have GPT-5 review this", "get the OpenAI reasoning model to design X", "ask the high-reasoning model"). Also triggers on "continue codex" / "resume the codex session" for iterative development, and on "have codex review this PR / branch / diff / my changes" for delegated code review. Do NOT trigger when codex / GPT-5 is merely a discussion topic rather than the requested actor.
fa-product-discovery
Provides Stage 1 product-discovery guidance for consumer one-off / in-app-purchase products - trend scanning (Sensor Tower, AppMagic, data.ai, store charts, Steam tags/wishlists, TikTok/Reddit/Product Hunt), opportunity sourcing, demand-signal harvesting as the cheapest kill gate, competitor teardowns, persona + JTBD + WTP-by-segment, and bottoms-up TAM/SAM/SOM sized net-of-fee. Use to find one buildable, monetizable bet and exit with an Opportunity Thesis, unit-economics model v0, and a GO/NO-GO/PIVOT call.
fa-product-compliance
Provides the Stage-7 compliance, ratings, legal and certification playbook for consumer one-off / in-app-purchase products - IARC age ratings and content descriptors, store/console submission and resubmission loops, loot-box/gacha/gambling-law handling (odds disclosure, disable-where-banned, minor spend limits), kids/privacy/consent (COPPA, GDPR-K, ATT, GDPR/CCPA), indirect tax, IP/asset licensing carry-through, and the EULA/ToS/Privacy-Policy set. Use to clear certification before soft-launch and to loop rejections back to production hardening. Money-gated and net-of-fee aware (store-remitted vs developer-remitted tax changes net revenue).
fa-create-skill
Provides Gaia skill-definition maintenance guidance with clear naming, descriptions, ownership boundaries, references, and reuse decisions. Use it by following the skills-specification reference (naming, formatter shape, scope sections, references) when adding or revising a SKILL.md, and by mirroring changes across both ".claude/skills/" and ".github/skills/" trees. Use it when adding, revising, auditing, or rationalizing skills, improving invocation quality, or consolidating drifting procedural guidance.
fa-create-plan
Researches and outlines multi-step plans. Use this skill when you want to create a detailed, actionable plan for a complex task or feature. The skill clarifies requirements with the user, fans out 3 identical parallel subagents to produce dispassionate plan proposals, critiques them, and synthesizes the best single plan for others to execute.
fa-create-agent
Provides custom-agent definition guidance with clear role boundaries, strong descriptions, valid tool scopes, delegation rules, and overlap control. Use it by following the agents-specification reference (formatter, role contract, tool allow-list, delegation rules) when adding or revising an agent file, and by mirroring changes across both ".claude/agents/" and ".github/agents/" trees. Use it when adding, revising, auditing, or rationalizing agent files, role ownership, naming, or contract alignment.
fa-ui-engineering
Provides React UI implementation guidance that enforces the design system, shadcn/ui composition, semantic Tailwind tokens, and responsive layout discipline. Use it by composing shadcn/ui primitives with semantic Tailwind tokens (no raw color/spacing literals), respecting the responsive layout rules, and removing dead tokens as you go. Use it when building or refactoring user-facing React components, screens, forms, dialogs, or styling where UI consistency and token cleanup matter.
fa-testing
Provides Gaia's formal validation guidance across unit, integration, manual regression, automated regression, and evidence review. Use it by running the test layers required by each task's gates (unit → integration → e2e → manual regression), recording proof labels (e.g. 'curl', 'playwright-mcp') on tasks_complete, and vetoing completion when evidence is missing. Use it when a branch is stable enough for hardening, when high-risk behavior needs targeted early validation, or when release readiness depends on a clear QA signal.
fa-process
Provides Gaia's end-to-end workflow coordination guidance for intake, routing, QA checkpoints, release gates, and proof expectations. Use it by routing every meaningful request through the intake → architecture → planning → engineering → testing → release sequence and only completing tasks once the corresponding gates and proof are recorded. Use it for meaningful requests, workflow resets after drift or blockers, and maintenance work that changes Gaia's operating model.
fa-planning
Provides execution planning guidance that turns approved architecture into a branch-aware plan with dependencies, QA checkpoints, release gates, and proof expectations. Use it by translating the current architecture into MCP tasks (tasks_create) sequenced by branch, with explicit required_gates and blockers, then keeping the plan current as new work is discovered. Use it after architecture is current, when work needs explicit sequencing instead of informal next steps, or when new branches, blockers, or gate definitions require re-planning.
fa-engineering
Provides planned implementation delivery guidance that keeps a branch coherent, stabilized, and ready for testing without redefining the target solution. Use it by implementing the planned tasks against existing repo conventions, keeping diffs scoped, running lint/build locally, and updating tasks_update as work progresses. Use it when a current plan branch is ready for code or definition-file edits, when implementation-side cleanup is needed, or when targeted early QA support is useful during delivery.
fa-architecture
Provides Gaia architecture documentation guidance that keeps docs, README messaging, and design decisions aligned to the current operating model. Use it by updating the relevant files under /docs/architecture/ (system components, use cases, class diagrams, UI) before any planning or implementation that changes structure, then resolving doc↔code drift before resuming feature work. Use it when system structure, trust boundaries, interfaces, workflows, ownership, or architectural assumptions change, or when architecture drift blocks planning or delivery.
fa-default-tech-stack
Provides Gaia's default full-stack baseline with React, TypeScript, Redux Toolkit, Tailwind CSS, and shadcn/ui on the frontend plus .NET, EF Core, PostgreSQL, and MCP exposure on the backend. Use it by adopting the documented baseline (versions, scaffolds, references) for any new app or unspecified-stack request, and by declaring the stack explicitly before planning when the request leaves it implicit. Use it when the request or repo leaves stack choice open, when bootstrapping a new application, or when standardizing an existing codebase onto Gaia's preferred platform.
fa-unit-economics-model
Provides the single shared, versioned unit-economics model for consumer one-off / in-app-purchase products, created in Discovery and re-run at every gate. Covers inputs (CPI, install->payer conversion, ARPPU, repeat purchase, ad ARPDAU), the gross-to-net stack (store commission, refunds, chargebacks, fraud, tax), LTV by segment, payback window, and a cashflow/working-capital check. Use whenever product economics must be initialized, updated with measured data, or evaluated at a gate.
fa-product-vertical-slice
Provides Stage 5 vertical-slice / MVP guidance for consumer one-off / in-app-purchase products - the spec stack (one-pager -> PRD/GDD -> monetization design doc as a binding instrumentation contract), MLP vs MVG with a designed purchase moment, a prototyping fidelity ladder, tech/billing spikes (StoreKit/Play Billing/Steamworks sandbox), server-authority and anti-cheat decisions, building analytics and IAP/entitlement rails first, and a shippable slice with one of every SKU type. Use to ship a lovable core loop with a live sandbox purchase and a clean reconciled funnel.
fa-product-validation
Provides Stage 4 validation guidance for consumer one-off / in-app-purchase products - framing falsifiable money hypotheses under a cost ceiling, IP/trademark/name/domain clearance, problem and solution interviews that probe real past spend, concept tests with a clickable paywall, deflated willingness-to-pay (Van Westendorp, conjoint/MaxDiff), fake-door and painted-price tests, landing-page commitment ladders, ad-creative CPI testing that replaces the placeholder CAC, and community pre-validation. Use to get a go/no-go with at least one money-on-the-line signal before building.
Page 875 of 1704 · 85159 results
