「pe」の検索結果

OpenClawのターミナル画面を固定のサンプルデータで試作し、実際の描画部品を使った2〜6案をtmuxで並べて操作・比較するスキル。

• 初期設定画面の案を比較したいとき
• チャットや選択画面の配置検討
• 既存画面と改善案を比べたいとき

OpenClawから指定した電話番号へ音声通話を開始し、通話中のメッセージ送信、状態確認、終了までをCLIやエージェント用ツールで操作するスキル。

• 電話番号へメッセージを伝えたいとき
• 通話中に追加メッセージを送りたいとき
• 通話状態の確認と終了

OpenClawのモデル通信やツール実行の不具合を、ログと再現操作で切り分けるスキル。保存済みの会話や添付資料も調べ、原因の修正と再検証につなげます。

• ローカルと実サービスの動作差を調べたいとき
• モデルに見えるツールの確認
• 応答ストリーミングの遅延・停止調査

Feishuのファイルで共同編集者と共有権限を確認し、依頼に沿って追加・削除するスキル。対象と相手の識別情報を確かめ、必要な範囲の権限を設定します。

• ファイルの共有相手を確認したいとき
• 必要な権限で共同編集者を追加
• 特定の共同編集者のアクセスを削除

OpenClawを動かす端末やサーバーの安全性を点検し、SSH、ファイアウォール、更新、暗号化、バックアップの状態から、段階的な改善策を提案します。

• OpenClaw実行環境の安全性点検
• サーバーの外部公開を確認したいとき
• バックアップと暗号化の状態確認

TypeScriptのパッケージ内部への直接参照や循環依存を検出し、公開ファイルだけを入口にする構成を、設定・検証・文書化まで整えるスキル。

• パッケージ内部への直接参照を防ぎたいとき
• 型チェックと一緒に境界を確認したいとき
• コピー用のパッケージ雛形を作りたいとき

絞り込んだ競合を九つの観点で採点し、根拠付きの比較カードと戦略の二軸図に整理するスキル。各社の強みや、自社が狙う領域の競合を確認します。

• 競合を共通の基準で比較したいとき
• 出典付きの競合紹介カード作成
• 戦略の二軸で競合を配置したいとき

Pythonコードの作成・レビューで、PEP 8や型ヒント、例外処理、パッケージ構成を整え、読みやすさと保守性、メモリ効率を考えた改善を支援するスキル。

• Pythonの可読性と記述規約のレビュー
• 型ヒントと例外処理を整えたいとき
• パッケージやモジュールの構成整理

非公開プロジェクトを公開用に複製し、秘密情報や個人情報の除去・検証から、READMEやセットアップ手順、ライセンスの整備まで進めるスキル。

• 非公開プロジェクトを公開したいとき
• 秘密情報や個人情報の残存確認
• 利用者向けの説明と導入手順の整備

自社の強みや顧客像を基に、比較すべき競合と調査先を選びます。直接競合・周辺競合・目標となる企業に分類し、根拠付きの候補一覧を作って詳しい比較の準備を整えます。

• 競合比較の対象を決めたいとき
• 直接競合・周辺競合・目標企業の分類
• 市場調査レポートの候補を絞りたいとき

Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".

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

Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx explore".

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

Workflow 3: Full paper writing pipeline. Orchestrates paper-plan → paper-figure → paper-write → paper-compile → auto-paper-improvement-loop to go from a narrative report to a polished, submission-ready PDF. Use when user says \"写论文全流程\", \"write paper pipeline\", \"从报告到PDF\", \"paper writing\", or wants the complete paper generation workflow.

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

Use when authoring rig specs, agent specs, workflow specs, startup/context fragments, operating-mode declarations, or designing the user spec library. Covers the 4 failure modes (spec instantiates topology but not workflow/mode; spec depends on local paths and fails on another host; agents modify specs as one-off files instead of preserving reusable intent; validation proves YAML shape but not whether topology can run) and the validation-vs-runtime-realization distinction.

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

Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 9-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow.

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

Use this skill when wiring the DOCA SHA Offload Engine (an OpenSSL ENGINE) into an existing OpenSSL pipeline to offload one-shot SHA-1, SHA-256, or SHA-512 (EVP_Digest) onto DOCA SHA hardware without rewriting against doca-sha. Covers engine load mechanics (`openssl engine dynamic`, `set_pci_addr` ctrl, `-engine_impl`), the SHA-224 negative test that proves offload engaged, the message-size window where offload beats CPU SHA, and engine-vs-library selection. Trigger even when the user does not say "DOCA SHA Offload Engine" or "OpenSSL ENGINE" — typical implicit phrasings: "speed up openssl SHA on BlueField", "offload SHA without code changes", "is openssl using the accelerator or falling back to software", "prove DOCA SHA actually ran", "openssl dgst hashed but I'm not sure it was offloaded". Refuse and route elsewhere for new SHA pipelines (use doca-sha), MD5 / SHA-3 / SHA-224 / HMAC-SHA offload, incremental hashing via chained `EVP_DigestUpdate`, or OpenSSL PROVIDER authoring.

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

Guide for ingesting the latest OpenAI TypeSpec specification into the openai-dotnet SDK. Use this when asked to update or ingest OpenAI API specs, copy base TypeSpec files from upstream, fix client TSP compile errors, or run code generation for new API areas.

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

Systematic strategic planning framework for philosophy and interdisciplinary academic papers targeting preprint platforms (PhilArchive, arXiv, PhilSci-Archive). Use when users want to: (1) plan a paper on a specific topic, (2) identify research gaps and assess originality, (3) develop optimized paper outlines, (4) prepare for preprint submission, or (5) understand platform requirements and writing standards. Triggered by phrases like 'plan a paper on,' 'help me design a paper about,' 'identify research gaps in,' 'is this idea original,' or when users need structured research planning. The skill guides through three phases: Platform Analysis (identifying target venue and studying sample papers), Theoretical Framework (AI-driven literature search and gap identification), and Outline Optimization (structured design with reviewer-perspective self-assessment). Each phase includes quality evaluation standards and validation checkpoints. Output: optimized detailed outline ready for systematic writing (use with academic-paper-composer skill).

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

Create, amend, or backprop bugs into SPEC.md at repo root. Sole mutator of the project spec. Triggers when the user asks to write a spec, start a new spec, distill a spec from existing code, add invariants, amend sections (§G, §C, §I, §V, §T, §B), or record a bug via backprop. Common phrasings: "write the spec for...", "new spec", "bug: ...", "amend §V.3", "distill spec from code", "spec this idea". Reads and follows FORMAT.md for the caveman encoding rules and pipe-table shape of §T and §B.

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

When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.

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

Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host is bound to the source env, provisions a new **Platform Host** (recommended, idempotent) or a **Custom Host** via the BAP env-create API with the `D365_ProjectHost` template, or guides the user through PPAC install / `New custom host` (manual fallbacks). Polls lifecycle operations, verifies the host responds to Pipelines API calls, writes a host-check artifact other ALM skills consume. Use when asked to: "set up pipelines host", "ensure pipelines host", "no pipelines host", "install pipelines", "create pipelines host", "provision platform host", "provision custom host". Also invoked transparently by /power-pages:setup-pipeline when its host discovery step finds nothing.

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

A platform decision framework for experimentation. When to use Statsig vs PostHog vs GrowthBook vs Optimizely vs Amplitude vs Eppo vs Kameleoon. How to migrate between them. How to coordinate when multi-platform is genuinely warranted. The decisions that compound for years and the ones you can defer. Triggers on which experimentation platform, choose Statsig vs PostHog, evaluate experimentation tools, switch experimentation platform, migrate from Optimizely, consolidate experimentation tools, multi-platform experimentation, experimentation platform decision, ab test platform selection, feature flag platform vs experiment platform, warehouse-native experiments, vendor lock-in experimentation. Also triggers when a team is asking about cost, governance, or migration cost across experimentation tools, or when an evaluation is starting.

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

Structured competitive analysis with feature matrices, SWOT, positioning maps, and UX review. Covers research frameworks, pricing comparison, review mining, and visual deliverables. Use for: market research, competitive intelligence, investor decks, product strategy, sales enablement. Triggers: competitor analysis, competitive analysis, competitor teardown, market research, competitive intelligence, swot analysis, competitor comparison, market landscape, competitor review, competitive landscape, feature comparison, market positioning

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

Provides AWS Lambda integration patterns for TypeScript with cold start optimization. Use when creating or deploying TypeScript Lambda functions, choosing between NestJS framework and raw TypeScript approaches, optimizing cold starts, configuring API Gateway or ALB integration, or implementing serverless TypeScript applications. Triggers include "create lambda typescript", "deploy typescript lambda", "nestjs lambda aws", "raw typescript lambda", "aws lambda typescript performance".

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