「report」の検索結果

Consolidate the five tdmcp surveyor reports into one prioritized FEATURE_BACKLOG.md — dedupe cross-surface overlaps, reconcile every candidate against the roadmap (NEW vs planned vs extension), rank by a selectable impact×effort weighting profile into P0/P1/P2 (high-confidence first), and emit per-surface tables + a recommended-next shortlist that hands straight to the build pipeline. Use when a td-synthesizer agent is consolidating surveys during the feature-discovery harness.

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

Run a security sweep over one repo: secrets, dependencies and the diff, a security review and a silent-failure hunt, one deduped and ranked findings report, issues filed for blocking findings only after GO, each one handed to pb-bug-fix. Use for "security sweep", "audit this repo", "check for leaked secrets and vulnerable deps".

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

Use when the user just says "plan", "planen" or "roadmap": offer a template via aos-plan-canvas templates. Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use for planning, whenever a user says "plan", "roadmap", "visualize the plan", "review the plan" or /plan-canvas, right after a brainstorm or grill interview has produced a plan, and whenever any skill's artifact (plan, design, comparison, report, diagram) can be reviewed visually instead of with typed feedback.

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

Run autonomous research tasks that plan, search, read, and synthesize information into comprehensive reports.

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

Experimental workflow for collecting and triaging product feedback, product telemetry, runtime errors, and issue reports. Use when scanning configured signal sources and applying separate fix, reply, or close rules.

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

テスト実行結果を集計してテスト結果報告書を生成する。 「テスト報告書を作って」「テスト結果をまとめて」「リリース判定用の報告書が必要」などのリクエストで使用する。

Generate Japanese PDFs using reportlab or fpdf2 with CJK font embedding, vertical text, business document templates, and inkan image placement. Triggers on requests to create 日本語PDF, 請求書PDF, 領収書PDF, PDF帳票, 縦書きPDF.

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

A skill for AI agents that want to produce better daily reports and discover more of what their users actually want. Scans source front pages, diffs them against yesterday, prescreens with a weighted profile, reviews with an LLM, deduplicates, publishes, and evolves the profile from user feedback. All decisions go to an append-only tape for audit and replay.

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

When designing how a system recovers from and reports failures.

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

Triage TestFlight crashes, beta feedback, and performance diagnostics using asc. Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.

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

Use when managing Apple Ads with asc, including OAuth profiles, ad-account discovery, Platform API v1 campaigns and targeting, reports, assets, recommendations, guarded mutations, raw requests, and Campaign Management API v5 migration.

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

Diagnose, fix, or validate SwiftUI animation and scroll behavior by temporarily instrumenting views with MotionEyes, capturing console traces over time, and comparing motion data to user intent or test expectations. Use when users report bugs such as wrong direction, premature fade, timing or easing mismatch, unexpected movement, missing movement, incorrect relative movement between views, scroll jumps, scroll restoration drift, content-offset desynchronization, or when they want to turn MotionEyes traces into focused assertions. Prefer XcodeBuildMCP log capture first and fallback to CLI log streaming; remove only agent-added MotionEyes instrumentation after validation.

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

When the user wants to monitor competitor apps on an ongoing basis — tracking metadata changes, keyword shifts, screenshot updates, rating trends, or new features. Use when the user mentions "competitor monitoring", "track competitors", "competitor alert", "competitor changed their title", "watch a competitor app", "competitor weekly report", "competitive intelligence", or "what changed in competitor's listing". For a one-time deep competitive analysis, see competitor-analysis. For market-wide chart movements, see market-movers.

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

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

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

When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.

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

Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.

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

Craft a single, high-quality GitHub issue from a developer's description of a bug, unexpected behavior, or desired enhancement. Walks through reproduction, codebase exploration, and structured drafting so the issue is actionable on arrival. Use when user wants to file an issue, report a bug, request a feature, or document a problem they've encountered.

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

NotebookLM でレポート・ブリーフィングを作成する。「NotebookLM レポート」「NotebookLM ブリーフィング」「NotebookLM 学習ガイド」「NotebookLM ブログポスト」などで起動。notebooklm-mcp を使用。

bengo-toolkit に対する不具合の報告・機能の要望・フィードバックを送りたい場合に使う。GitHub アカウントなしで、ブラウザの専用フォームから送信できる。「バグを報告したい」「不具合を伝えたい」「こんな機能が欲しい」「フィードバックを送りたい」等の発話で起動する。

Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.

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

Use when asked to report the deployment sentinel value. Provides the sentinel string that proves a vendored skill reached the agent's context.

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

Guide for training outputs, metrics logging, logtree reports, tracing/profiling, and debugging training runs. Use when the user asks about training logs, metrics, debugging, tracing, profiling, timing, Gantt charts, or understanding training output files.

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

Use when the team lead points Architect at a prior agistra.dev hub path and asks it to check for or perform additional migration — trigger phrasing such as 'migrate my data from <path>', 'check what didn't get migrated', 'did we miss anything from my old hub', or 'do a completeness pass on <path>'. Walks the prior hub's full directory tree read-only, diffs it against the fixed scripted migration scope plus any existing migration report, and asks the team lead one clear question at a time about anything a scripted migration would never have discovered. Never writes or copies anything itself — every confirmed item is delegated to the existing migration primitives. Do not use for the first-run scripted migration prompt during `npm run setup` — that is unrelated, already-automated flow this skill does not replace.

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

Use when the team lead points Architect at a prior agistra.dev hub path and asks it to check for or perform additional migration — trigger phrasing such as 'migrate my data from <path>', 'check what didn't get migrated', 'did we miss anything from my old hub', or 'do a completeness pass on <path>'. Walks the prior hub's full directory tree read-only, diffs it against the fixed scripted migration scope plus any existing migration report, and asks the team lead one clear question at a time about a

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