1,990 件 ・ 関連度順
概要と使いどころ
Router for the frontend design stack. Use at the start of any frontend UI task (build a page or component, redesign, pick a style or palette, polish, audit, animate, review UI) to decide which installed skill leads, which ones support, and which rule wins when the packs disagree. Also use when two design skills give contradicting advice.
日本語の概要は準備中です。原文の説明を表示しています。
MUST USE when user wants to research/search/look up/find anything on the internet — e.g. "research this topic", "do a deep dive on X", "search the web for X", "see what people say about X", "look this up". Also MUST USE when user mentions any platform or shares any URL/link: Twitter/X, Reddit, Facebook, Instagram, YouTube, GitHub, Bilibili, XiaoHongShu, Xiaoyuzhou Podcast, LinkedIn/jobs/recruiting, V2EX, Xueqiu (stocks), RSS. 15 platforms, multi-backend routing (OpenCLI / per-platform CLIs / APIs). Zero config for 6 channels. Run `agent-reach doctor --json` to see which backend serves each platform right now. NOT for: writing reports/analysis/translation (this skill only FETCHES internet content); posting/commenting/liking (write operations); platforms that already have a dedicated skill installed (prefer that skill).
日本語の概要は準備中です。原文の説明を表示しています。
Production-ready CSS transition snippets for web apps. Use when adding or reviewing UI motion for badges, dropdowns, modals, panel/page reveals, card resizes, number pop-ins, text/icon swaps, success checks, avatar-group hovers, and validation shakes. Supports namespaced commands: transitions reveal (list catalog), transitions review (audit project fit), and transitions apply (install the best-fit snippet with hooks and reduced-motion handling).
日本語の概要は準備中です。原文の説明を表示しています。
Record a narrated video of a feature running in the local dev app, for a PR or a stakeholder. Drives a headless Chrome over the DevTools Protocol so clicks and keystrokes are real, captures frames, and encodes an mp4 with no extra tooling installed. Use when the user asks to "record a video", "make a demo", "show this working", or wants a screen recording of a change.
日本語の概要は準備中です。原文の説明を表示しています。
Scan and redact PII and sensitive data (emails, phone numbers, SSNs, API keys, IP addresses, credentials, amounts, company/person names) from repository files. Includes a pre-commit hook to block commits containing PII. Use when asked to audit code for sensitive data, sanitize files before publishing, or install PII detection hooks. For application security hardening see security-engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Deep behavioral security audit for AI agent skills and MCP tools. Performs deterministic static analysis (AST + Semgrep + 15 specialized scanners), cryptographic lockfile generation, and optional LLM-powered intent analysis. Use when installing, reviewing, or approving any skill, tool, plugin, or MCP server — especially before first use. Replaces basic safety summaries with full CWE-mapped, OWASP-tagged, line-referenced security reports.
日本語の概要は準備中です。原文の説明を表示しています。
Sync OpenRouter models used by OpenClaw into this installation's config. Fetches the OpenClaw app leaderboard from OpenRouter, verifies model IDs against the API catalog, and adds missing models with correct specs and aliases. Use when asked to "sync openrouter models", "add missing models", "update openrouter config", or "check openrouter models".
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when users need to search academic papers, download research documents, extract citations, or gather scholarly information. Triggers include: requests to "find papers on", "search research about", "download academic articles", "get citations for", or any request involving academic databases like arXiv, PubMed, Semantic Scholar, or Google Scholar. Also use for literature reviews, bibliography generation, and research discovery. Requires OpenClawCLI installation from clawhub.ai.
日本語の概要は準備中です。原文の説明を表示しています。
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
日本語の概要は準備中です。原文の説明を表示しています。
Prepare, validate, package, or review a dygo framework release and its upgrade path. Use for versioning, tags, binaries, Studio and Core bundling, installers, archives, checksums, and release smoke checks.
日本語の概要は準備中です。原文の説明を表示しています。
Get started with Xpoz — set up authentication, verify your account, configure tracking, and discover available skills. Use when asked to "set up Xpoz", "connect to Xpoz", "get started with Xpoz", "what can Xpoz do", "new to Xpoz", "install Xpoz", or "my Xpoz account".
日本語の概要は準備中です。原文の説明を表示しています。
Evaluate an incoming workflow upgrade — a skill, MCP server, subagent, library, external service, prompt, or pattern — through one disciplined pipeline before adopting it. Security is a blocking gate. Records every verdict so the same thing is never evaluated twice. Use when considering a new tool from a post, repo, or recommendation. Triggers — "vet this", "should we adopt", "is this safe to install", "evaluate this skill/MCP", "what do you think of this tool".
日本語の概要は準備中です。原文の説明を表示しています。
Safe deployment workflow for Drupal 10/11 sites: pre-flight checks, backup, the correct update sequence (composer install, database updates, config import, cache rebuild), verification, and rollback plan. Use when deploying to any environment, releasing to production, or when the user asks to "push changes live", "update the server", or run a release. Also use for multisite releases where each site needs its own database update pass.
日本語の概要は準備中です。原文の説明を表示しています。
Delegate implementation to Codex, grok, or cursor-agent, then review the diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex, the grok 后端, or cursor-agent to write code, mentions handing off / delegating implementation to one of those backends, asks to work through a plan or spec unit-by-unit with an implementation backend doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer runs in the real environment behind backend-specific git and publication boundaries, must not be pointed at a full test suite by default, and its self-report is a claim rather than evidence. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the engineering-mode skill when it is installed.
日本語の概要は準備中です。原文の説明を表示しています。
Publish and verify a released GEODE version across GitHub Release and PyPI/uv. Use for uv/uvx distribution, stable promotions, release repair runs, and public installation-channel audits.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite CLI skill. Use when managing Appwrite projects from the command line. Covers installation, login, project initialization, multi-file project configuration, deploying functions/sites/tables/buckets/teams/webhooks/topics, flag-based list queries, non-interactive CI/CD mode, and generating type-safe SDKs.
日本語の概要は準備中です。原文の説明を表示しています。
Gives a repository one idempotent, repo-local worktree setup script (local env files, dependency install, build steps) that worktrunk's `.config/wt.toml` pre-start hook and Orca's `orca.yaml` scripts.setup both call, so every new git worktree is usable at once. Use when adding or fixing worktree setup hooks, writing `wt.toml` or `orca.yaml` setup, when new worktrees lack dependencies or `.env` files, or when asked to make worktrees "just work" in a repo. For creating a worktree in a repo that already has setup, use `git-branch-management` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Deterministic AI development workflow orchestrator. Manages task boards (.jonggrang/jonggrang-tasks.json), runs 16-phase pipelines (BUGFIX/SMALL/MEDIUM/LARGE), installs lifecycle hooks for Claude Code and OpenCode, and coordinates five specialist roles (Lead/Developer/Reviewer/TestLead/Tester). Use when planning features, executing multi-step development workflows, or orchestrating AI coding agents. Run via npx jonggrang.
日本語の概要は準備中です。原文の説明を表示しています。
三方框架特性落地（原 framework-feature-enablement ＋ framework-extension-dev 合并）： 一个入口信号「框架侧特性没落地」，内部分两分支——**分支 A 框架已有 → 使能与验证** （计数契约 + 三层证据 + 使能异常回修）；**分支 B 框架缺失 → 补齐开发** （注入点 + 代码组织/注册机制 + 合入姿势：平台注册优先 / 上游 PR / fork 钉版 / monkey 备选）。 分支 A 触发词：量化/稀疏/缓存开关没生效、融合算子没命中、使能异常或精度不符、 "起 vllm 服务""模型在框架里跑不通""把 mindiesd 接到其他框架"。 分支 B 触发词：框架没 comm-stream 掩盖、框架没缓存消费者、框架不支持某 collective/mask、 feature_* NotImplemented、要给框架补一条结构性能力。 near-miss：纯安装/权重 → env-install；纯采集/分析 → profiling-collect / profiling-analyze； 纯选档（该不该开量化、开哪一档）→ dit-perf-opt； mindiesd 仓内 pattern / 算子 / 图下发开发 → dev-workflow + pattern-dev / operator-dev / aclgraph-dev。 由 model-auto-optimization 的 S1（融合接入）/S4（有损使能）/S5（训练感知）与 §0 缺口补齐策略路由， 亦由 dev-workflow 的框架接入/验证场景指引加载。
日本語の概要は準備中です。原文の説明を表示しています。
host / 辅助段优化模块（L3）：把**非 DiT、非解码段**的固定开销落成可复验的优化—— ① 交付与搬运（mp4/图片编码、worker→API 通路、落盘、异步化）； ② 装载与预热（权重加载、编译与图下发预热、镜像/容器预热）。 当用户说“mp4 编码/传输/落盘慢”“交付这段占了不少时间”“模型加载慢”“首启编译太久” “固定开销占比高”“每个请求都要重新编码/重新写盘”时使用。 **入口条件**：占比已达门限（瓶颈标签 `非DiT-host段`；标签枚举、门限与测点口径的单一真源在 model-auto-optimization/references/bottleneck-labels.md，本技能只消费不定义）。 near-miss（看似相关但不属本技能）： - **并发 / 吞吐 / 批处理调度 / 队列深度与限流** → **不属本技能**（会改变所有性能口径与 SLO 语义， 未来独立立项；本技能只在**不改变请求并发模型**的前提下压固定开销）； - VAE/TAE 解码段（计算或通信）→ `vae-opt`；DiT 计算 → `dit-perf-opt`； 多卡并行 / 通信掩盖 → `dit-parallel-opt`； - **装库 / 下载权重 / 构建镜像 / 创建容器** → `env-install`（本技能只优化装载与预热**过程本身**）； - 编译与图下发的**机制本体**（pattern / Inductor / NPUGraph / 图 pool / 缓存条目）→ `pattern-dev` / `aclgraph-dev`（本技能不另做一套缓存）； - 产物一致性与精度判据 → `accuracy-gate`；收益口径 → `perf-gate`； - 瓶颈未定位 / 没有占比锚点 → `model-auto-optimization`。
日本語の概要は準備中です。原文の説明を表示しています。
简化模型代码的快速验证载体：用随机权重/精简代码在 NPU 上快速验证模型架构 兼容性、算子先接入与融合可行性（产物：架构兼容性 + 基线/快验输出），无需真实权重。 已部署模型的框架侧验证见 framework-integration，环境安装见 env-install。 当用户需要确认模型能否跑通、评估参数量与显存占用、或在算子接入/融合优化前 做快速验证时使用此 skill；即使用户只提到"帮我试试这个模型能不能跑"而未说 dummy run，也应触发。由 model-auto-optimization 的 S0/S1（融合/编译快验）阶段调用， 亦由 dev-workflow 的模型验证阶段指引加载。
日本語の概要は準備中です。原文の説明を表示しています。
环境安装与准备：把部署环境从零安装就绪——mindiesd 编译安装（本地昇腾直装 / SSH 推远端容器 / Docker 镜像直装）与三方推理框架全栈安装（vLLM-Omni 源码构建、DiffSynth-Engine 部署、 LightX2V editable 部署），并负责模型权重确认与下载（下载前先确认远端是否已存在）。不含特性使能与验证 （framework-integration）与 profiling（profiling-collect）；SSH 工具由 remote-access 提供。 当用户需要安装 MindIE-SD、源码构建/直装 vLLM-Omni 或 LightX2V（editable + PLATFORM=ascend_npu）、 或确认/下载模型权重时使用此技能； 即使用户只提到"把代码推到服务器""在容器里装 vllm 全栈""准备 lightx2v 调优环境"而未说昇腾， 只要上下文涉及环境安装与准备都应触发。由 model-auto-optimization S0 与 dev-workflow 部署阶段指引加载。
日本語の概要は準備中です。原文の説明を表示しています。
多模态模型自动优化流程总入口（编排层）：把一个三方框架托管的扩散模型从环境准备到无损/有损 优化自动跑完。任务判定后按 S0 环境准备、S1 kernel 融合优化（原 S1/S2 合并）、S3 并行通信、 S4 有损优化、S5 训练感知（预留，少步蒸馏 + SLA/QAT）、闭环复验路由到能力技能（env-install / framework-integration / profiling-collect / profiling-analyze / performance-optimization / dit-parallel-opt / dummy-run 等），检查各阶段产物与验收并回填经验槽位。 当用户需要对具体模型做框架接入、无损/有损加速、并行调优或确认收益时使用本入口；即使用户只提 模型名加"优化/加速/跑通/采profile"而未说框架或阶段，也应由本入口判定路由。仓库代码开发类任务 请走 dev-workflow。流程执行/验收按 workflows/optimization-flow.md，run-state + stage_gate 门禁。
日本語の概要は準備中です。原文の説明を表示しています。
Coordinates staged or parallel jobs across live-verified coding-agent runtimes (Claude Code, Codex, Cursor, and other installed CLIs) and in-session toolkit subagents. Routes each job by capability and risk tier, isolates parallel writers in git worktrees, captures redacted output, resumes interrupted runs, and blocks completion until an independent arbiter verifies the results. Use when work should be split across multiple runtimes or subagents, run as staged or parallel jobs, and reviewed before handoff. NOT for a single-agent task or the in-session 7-phase flow (use mk:cook / mk:workflow-orchestrator).
日本語の概要は準備中です。原文の説明を表示しています。