「lab」の検索結果

Give your OpenClaw agent a homelab. Use when managing Docker containers, installing marketplace apps, or any Docker-related tasks on behalf of the user. Scope-based API key permissions — agent can only do what the key allows. On Linux, Docker requires sudo — without root access, WAGMIOS is the only safe interface for agent homelab control. Supports multi-machine management — one agent can manage multiple WAGMIOS instances across different hosts, each with its own scoped key. Requires X-API-Key header on every request (user provides at runtime). Includes Docker installation check and startup validation.

日本語の概要は準備中です。原文の説明を表示しています。

Build a white-labeled, client-facing intelligence dashboard — a live, branded reporting surface an agency stands up per client instead of sending static reports. Covers brand auto-extraction from the client's URL, a three-tier build (Basic/Standard/Advanced), an onboarding feature wizard, a 10-page inventory, public-access tradeoffs, and the retention plays that make the dashboard sticky. Use when "client dashboard", "client intelligence dashboard", "white label dashboard", "client portal", "branded dashboard for my client", "agency dashboard", "build my client a dashboard", "give the client a live view instead of a report", or any request to stand up a durable, client-facing reporting surface.

日本語の概要は準備中です。原文の説明を表示しています。

AppFlowy brings documents, projects, wikis, and AI-assisted collaboration into a self-hosted or desktop-friendly workspace. This skill helps agents work from the real AppFlowy project, docs, and deployment methods when users need an open source Notion-style environment with local control.

日本語の概要は準備中です。原文の説明を表示しています。

Babel internal issue protocol — list open handoffs by label. Scans designs/*/.handoff/*.md (filtered by label) and best-effort merge with gh issue list. Used by all guru/architect agents at startup to pick up work.

日本語の概要は準備中です。原文の説明を表示しています。

Nature-style materials science manuscript reviewer skill for testing materials design, synthesis, processing, structure-property, mechanism, stability, scalability, computational prediction and application claims against materials evidence chains.

日本語の概要は準備中です。原文の説明を表示しています。

Assesses leadership team capacity to scale with organizational design review, key person risk, and executive bench analysis. Use when evaluating management scalability, identifying talent gaps, or assessing organizational readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates social infrastructure including healthcare, education, and government facilities with availability-based revenue structures. Use when analyzing social infrastructure, evaluating availability payments, or assessing government-backed projects.

日本語の概要は準備中です。原文の説明を表示しています。

Improve UX writing, marketing copy, labels, microcopy, instructions, and error messages so interfaces and product messaging are easier to understand and act on. Use when the user mentions confusing copy, unclear labels, bad error text, weak CTAs, hard-to-follow instructions, or wanting better UX writing.

日本語の概要は準備中です。原文の説明を表示しています。

Restore legibility to an auto-generated graph diagram that has outgrown its canvas - rendering at single-digit percent scale with sub-pixel labels. Covers the levers that measurably reduce layout units (source-level label wrapping, invisible chain links so unconnected nodes stop spreading into one row, per-cluster splitting, layout direction picked by rendering both and measuring) and the rejected ones (raising the render font is a no-op because layout engines measure in text units; a topology heuristic for direction regressed 13 of 38 diagrams). Use when a generated Mermaid/Graphviz/DOT diagram is too small to read; not for hand-authoring a small diagram.

日本語の概要は準備中です。原文の説明を表示しています。

Set up centralized log aggregation with Loki and Promtail (or ELK stack), including log parsing, label extraction, retention policies, and integration with metrics for correlation. Use when consolidating logs from multiple services into a searchable system, replacing local log files with centralized queryable storage, correlating logs with metrics and traces, implementing structured logging with label extraction, or troubleshooting production incidents requiring cross-service log analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Configure reverse proxy patterns across multiple tools including Nginx, Traefik, and ShinyProxy. Covers WebSocket proxying, path-based and host-based routing, SSL termination, and Docker label auto-discovery. Use when routing multiple services behind a single entry point, proxying WebSocket connections (Shiny, Socket.IO), auto-discovering Docker services with Traefik labels, or adding SSL termination to services that don't handle TLS natively.

日本語の概要は準備中です。原文の説明を表示しています。

Collect and preserve insect specimens following museum-grade standards including legal compliance, collection methods, humane dispatch, dry pinning, wet preservation, labeling, storage, and curation. Covers permit requirements, protected species regulations, sweep nets, beating trays, pitfall traps, light traps, Malaise traps, aspirators, ethyl acetate killing jars, freezing, pin placement by order, wing spreading, ethanol preservation for soft-bodied specimens, specimen labeling with locality and date, storage with pest management, and database entry. Use when building a reference collection for taxonomic study, preserving voucher specimens for ecological research, preparing specimens for identification by specialists, or curating an existing collection.

日本語の概要は準備中です。原文の説明を表示しています。

Create and manage pull requests using GitHub CLI. Covers branch preparation, writing PR titles and descriptions, creating PRs, handling review feedback, and merge/cleanup workflows. Use when proposing changes from a feature or fix branch for review, merging completed work into the main branch, requesting code review from collaborators, or documenting the purpose and scope of a set of changes.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate multi-LLM parallel debate and synthesis. Dispatches prompts to available omega CLI wrappers in parallel, collects independent responses, runs anonymized peer review ranking, and synthesizes via a chairman model. Supports collaboration templates, idle watchdog, inter-agent messaging, worktree isolation, and multi-turn sessions. No server required.

日本語の概要は準備中です。原文の説明を表示しています。

Collaborative document creation via a structured three-stage workflow. Use for writing specs, PRDs, design docs, proposals, RFCs, and any long-form document where quality and clarity matter. Brainstorms 5-20 options per section, builds iteratively, and tests with reader sub-agents.

日本語の概要は準備中です。原文の説明を表示しています。

Check voice message pipeline config — verify Whisper, ElevenLabs/OpenAI TTS keys and dependencies.

日本語の概要は準備中です。原文の説明を表示しています。

Specialized business strategy prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output formats) for consulting, M&A, corporate strategy, and strategic planning tasks. Use when building prompts for deal evaluation, due diligence, portfolio strategy, business model analysis, board narratives, investment cases, market entry plans, or strategic options assessments. Trigger on: "build a prompt for M&A analysis," "due diligence prompt," "board narrative," "investment case," "market entry strategy," "strategic options," "portfolio strategy prompt," "business model analysis prompt," "consulting-style analysis." Do NOT use for evaluating or scoring existing prompts (use rootnode-prompt-validation if available) or for auditing Claude Projects (use rootnode-project-audit if available).

日本語の概要は準備中です。原文の説明を表示しています。

Specialized prompt-building methodology for content and communications tasks. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for writing, editing, content strategy, copywriting, audience analysis, editorial evaluation, cross-channel adaptation, and persuasion design. Use when building a Claude prompt or system prompt for content creation, editorial workflows, or communications tasks. Trigger on: "build a prompt for writing," "prompt for content strategy," "prompt for copywriting," "prompt for blog posts," "prompt for email sequences," "system prompt for editorial," "prompt for messaging framework," "content brief prompt," "prompt for audience analysis," "prompt that produces better content." Do NOT use for writing content directly — this Skill builds prompts that produce better content. Do NOT use for evaluating or scoring existing prompts — use rootnode-prompt-validation if available. Do NOT use for general prompt compilation — use rootnode-prompt-compilation if available.

日本語の概要は準備中です。原文の説明を表示しています。

Specialized research and analysis prompt methodology for Claude. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for data analysis, policy research, systematic evidence review, investigative research, and research-specific deliverables. Use when building prompts for quantitative data interpretation, evidence-based policy recommendations, literature reviews, causal analysis, hypothesis-driven investigation, or briefing documents. Trigger on: "prompt for data analysis," "research prompt," "policy brief prompt," "literature review prompt," "prompt for investigating," "systematic review prompt," "build a prompt for evidence synthesis," "causal analysis prompt," "briefing document prompt." Also use when user describes a research or analytical task and needs a structured Claude prompt for it. Do NOT use for evaluating existing prompts (use rootnode-prompt-validation if available) or auditing Claude Projects (use rootnode-project-audit if available).

日本語の概要は準備中です。原文の説明を表示しています。

Builds complete, optimized Claude prompts and Project scaffolds from task descriptions. Use when building, designing, creating, or structuring a Claude prompt or system prompt. Trigger on: "build me a prompt," "compile a prompt for," "create a system prompt," "write a Claude prompt," "design a prompt for," "help me write a prompt," "scaffold a Claude Project," "design a Project for." Uses a four-stage methodology (Parse, Select, Construct, Validate) and a tested 5-layer architecture (Identity, Objective, Context, Reasoning, Output + Quality Control). In Project Mode, the Compiler is global-layer-aware — checks User Preferences, installed Skills, and MCP Connectors to avoid redundancy and flag gaps. Do NOT use for auditing existing prompts (use rootnode-prompt-validation if available) or diagnosing existing Projects (use rootnode-project-audit if available). Run on Opus 5 or Sonnet 5 at `high` effort (both defaults); depth reduces on legacy models.

日本語の概要は準備中です。原文の説明を表示しています。

Modern PHP idioms for any PHP project (PHP 8.1+): readonly properties, enums, match expressions, constructor property promotion, typed properties, named arguments, nullsafe operator, first-class callable syntax, strict_types, PSR-12 style, and null discipline. Apply when the project is a PHP 8.1+ project. Stack-agnostic — referenced by every PHP plugin in the marketplace. Use this skill to: - Write strongly-typed, immutable-by-default value objects with readonly properties and enums. - Replace switch ladders and magic constants with match expressions and backed enums. - Cut constructor boilerplate with property promotion and express optionality with typed nullable returns. - Keep code PSR-12 compliant with declare(strict_types=1) in every file. Do NOT use this skill for: - Framework-specific idioms (Eloquent, Doctrine, Symfony services, Laravel facades — those live in framework plugin skills). - Composer / autoloading / dependency management — see php-foundation:composer-tooling. - Testing patterns — see php-foundation:php-testing.

日本語の概要は準備中です。原文の説明を表示しています。

Entity Framework Core patterns for ASP.NET Core projects: DbContext design, code-first entity configuration (Fluent API via IEntityTypeConfiguration<T>), relations (HasOne/HasMany, cascade/restrict/set-null), indexes and unique constraints, projection to DTOs (Select + AsNoTracking), avoiding N+1 (Include, AsSplitQuery), transactions, parameterized raw SQL (FromSql with FormattableString), and connection string from IConfiguration. Works alongside aspnet-core-plugin:aspnet-conventions. Use this skill to: - Design a clean DbContext with ApplyConfigurationsFromAssembly for scalable entity registration. - Configure entity properties (column types, max length, precision, nullability) via Fluent API. - Avoid N+1 query problems with explicit Include / projection to DTOs. - Use transactions correctly for multi-entity operations. - Write parameterized raw SQL safely when LINQ is not expressive enough. Do NOT use this skill for: - Migration generation commands (that is efcore-specialist's job in the database extra phase). - ASP.NET Core middleware, DI, or validation — see aspnet-core-plugin:aspnet-conventions. - C# language idioms — see csharp-foundation:csharp-conventions.

日本語の概要は準備中です。原文の説明を表示しています。

Modern C# idioms for any .NET project (C# 10+, .NET 6+): nullable reference types, records, readonly structs, primary constructors, pattern matching, async/await with CancellationToken, IDisposable/IAsyncDisposable, file-scoped namespaces, var usage, naming conventions (PascalCase members, _camelCase fields, I-prefixed interfaces), and class design rules. Apply whenever the project is a .NET 6+ project. Stack-agnostic — referenced by every .NET plugin in the marketplace. Use this skill to: - Write self-documenting immutable value types with records and readonly structs. - Handle nullable reference types explicitly to eliminate NullReferenceException at compile time. - Implement async/await correctly with CancellationToken propagation and ConfigureAwait(false) in libraries. - Dispose unmanaged resources correctly via IDisposable / IAsyncDisposable and using statements. - Apply C# pattern matching (switch expressions, property patterns, list patterns) for cleaner branching logic. Do NOT use this skill for: - Framework-specific idioms (ASP.NET Core controllers, minimal APIs, EF Core — those live in aspnet-core-plugin skills). - Build tooling (dotnet CLI, NuGet, csproj) — see csharp-foundation:dotnet-tooling. - Testing patterns — see csharp-foundation:dotnet-testing.

日本語の概要は準備中です。原文の説明を表示しています。

Apply one exact-target Proto UI collaboration update through the ordinary governed primitive or an explicitly current-user connected-operation path for archive/ref recovery, Issue reopening/linking, additive carrier publication and service control. Do not manufacture review dispositions, merge, close, release or change privileged settings.

日本語の概要は準備中です。原文の説明を表示しています。