「report」の検索結果

Use the Crabbox wrapper for OpenClaw remote validation across Linux, macOS, Windows, and WSL2, including delegated Blacksmith Testbox proof. Report the actual provider and id.

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

Review existing analytics — find all dashboards and reports, check who uses them, whether metrics are defined, and whether they drive decisions. Recommend what to keep, kill, or add. Use when asked "are our dashboards useful", "analytics review", or "metrics audit".

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

Design or review org structure - spans of control, reporting lines, role clarity, headcount plan, and team topology. Use when asked to "design our org", "should we restructure", "what is the right team structure", or "plan headcount for next year".

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

Feedback synthesis — cluster support tickets, NPS verbatims, app store reviews, and churn surveys by theme, separate signal from noise, and produce an actionable insight report. Use when asked to "synthesize this feedback", "analyze support tickets", "what are users complaining about", "NPS analysis", "churn feedback synthesis", or "what's the feedback telling us".

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

Run a user interview — produce an interview guide and synthesize the output into an actionable insight report. Use when asked to "run a user interview", "synthesize these interview notes", "what do users actually want", "build a persona from this feedback", "find the JTBD in these transcripts", or "analyze this interview data".

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

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed".

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

Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.

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

Run grok test for Datagrok packages and report results

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

工程の進捗を報告し、3D モデルのどこまで出来ているかを確認する。CAD モデルの施工単位（階・区画）で「3 階の床まで完了」のように報告でき、進捗率に換算して監督確認へ提出する。Use when: 進捗報告, 出来高, 出来形, どこまでできた, 何階まで, 3D, 工程, 施工状況, 進捗を登録

直近 1 週間の売上・廃棄・欠品・施策（Cowork から登録した発注を含む）を Dataverse から集計し、SV（スーパーバイザー）向けの週次店舗レポートを、チャットのグラフ（Render UI）と表、HTML レポート（頼まれたら Excel も）で作るスキル。 Use when ユーザーが「週次レポートを作って」「SV に今週の報告をまとめて」「今週の振り返りを Excel にして」と依頼したとき。 Dataverse MCP コネクタ（describe / read_query）を読み取りで使う。

Teams 会議の録画・文字起こし・会議チャットと予定表から現場日報の下書きを作り、確認後に登録する。 Use when ユーザーが「会議から日報を作って」「今日の現場会議を日報にして」と依頼したとき。

Teams の会話で日報を作る。作業内容・天候・人員を聞き取り、添付された現場写真を確認して登録し、作業ごとの進捗（施工単位でも可）を下書きとして提出する。監督が現場コックピットの「承認待ち」で承認すると工程の進捗と 3D に反映される。Use when: 日報, 日報を報告, 今日の報告, 作業報告, 現場写真, 写真を登録, 出来高

Creates HTML decks, webpages, and social cards with pakco.html templates. Use for slides, PPT-style reports, visual web pages, or the style picker.

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

Count lines, words and characters in files, and report the totals.

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

Generate AI-friendly repository documentation with the SourceSage CLI. Use when Codex needs to run `sage` or `sourcesage` to create `.SourceSageAssets/Repository_summary.md`, analyze the current repository or another local repository, switch the output language between English and Japanese, use `--lite` to keep the summary small, change the output directory, or optionally create a deprecated tag-diff release report with `--diff`.

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

Audit and safely clean Xcode-related developer storage on macOS. Use whenever a developer mentions low disk space, Xcode storage, DerivedData, simulator devices or runtimes, stale beta platforms in Xcode Settings, DeviceSupport, archives, dSYMs, CocoaPods caches, simulator dyld caches, project .build folders, downloaded Xcode DMGs/XIPs, duplicate Xcode installers, or old Xcode applications. Also use this skill proactively when you hit low storage during other work, such as a build, download, or install failing with an out-of-disk-space error. Always measure first, report recoverable GiB with evidence, and obtain explicit itemized approval before any mutation.

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

A survey of the best-known active scientific controversies in nutrition — saturated fat and cardiovascular disease, dietary cholesterol, low-carb vs low-fat, ultra-processed foods, red meat and cancer, salt and blood pressure, and the replication status of popular single-nutrient claims. Use when a question asks whether a widely reported nutritional claim is settled, or when the department needs to distinguish "contested but plausible" from "settled" from "disproven."

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

Identifying species in the field using dichotomous keys, gestalt recognition, diagnostic features, and habitat context. Covers the working identification protocol from first encounter through confidence-rated record, the vocabulary of field marks, the discipline of negative evidence, and the honest reporting of uncertain IDs. Use when the task is to name a living organism encountered in the field.

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

Use when the user reports a bug they can't reproduce, asks where to start debugging, or mentions a Heisenbug / production-only failure. Drives the observe→hypothesize→predict→test→iterate scientific method.

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

Use when reviewing, shipping, or regression-testing a SKILL.md and you hold one or more captured trajectories where that skill was actually loaded. Translates the skill's instructions into behavior constraints, then reports which were EXERCISED (coverage) versus untested, and flags any that were in-scope but VIOLATED (compliance) — a cheap single-trajectory test-adequacy gate. It surfaces untested instructions rather than auto-blocking, and escalates fail-closed only when a violation touches shared repo state, never-surface memory, or self-modification. Complements skill-counterfactual-audit (which measures EFFECT) and skill-causal-curation (which measures contribution); this one asks ADEQUACY. Backed by the agent-skill-coverage metric (arxiv 2606.20659v2). Triggers on skill review, ship gating, and regression-testing a skill against its trajectories.

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

Audit a skill by running a paired probe — the same task once with the skill loaded and once without — segment both traces into goal-directed phases, align phases, and emit a SIP report (surface anchoring, template copy, excess planning, task recovery, off-task artifact). Use whenever a skill is created, modified, or proposed for retirement. Pass-rate is BLIND to most skill effects: CTA (arxiv 2605.11946v1) shows a single skill can produce 522 measurable behavioural changes across 49 tasks while pass-rate moves only +0.3%. Triggers: "audit this skill", "is this skill helping", "retire skill", "before shipping skill", "behavioural impact of skill X", or any skill review event.

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

Audit code changes against Karpathy's 4 principles (Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution). Auto-called after Phase 5 IMPLEMENT; can also be invoked manually. Produces scored compliance report and blocks advancement if threshold not met.

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

Run ship-safe security and quality audit on the current project. Executes npx ship-safe audit . and reports findings by severity. Use before shipping any feature or PR.

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

Audit a MaaFramework/Maa-series project's Git history to learn how Pipeline JSON, interface options, Python AgentServer CustomAction code, and related data tables evolved. Use when asked to review a Maa project from initial commit through a target commit, map `action: Custom` pipeline nodes to `@AgentServer.custom_action(...)` implementations, find pipeline/custom/option patterns or breakages, and produce a report plus skill-improvement recommendations.

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