7,723 件 ・ 関連度順
概要と使いどころ
Turn a request for a report or a dashboard widget into something buildable: the question it answers, the metric and its definition, where the data comes from, the query shape, and what it will not answer. Use when a new report or dashboard is requested, when an existing one needs a metric added or changed, when a widget is asked for in a sentence and needs pinning down, or when two reports disagree about the same number.
日本語の概要は準備中です。原文の説明を表示しています。
Check that the scheduled data work behind the reports actually ran and produced something sensible: the daily reshaping scripts, the API pulls, the tables the reports read from. Use each morning before anyone opens a report, when a report looks wrong and nobody knows whether it is the data or the query, after a schema or API change, when a new audience or source is added to the pipeline, or when a scheduled job failed or finished suspiciously fast.
日本語の概要は準備中です。原文の説明を表示しています。
Stand up reporting for a new audience — an external client, a business unit, a region, an executive team — end to end: what they need to see, whether the data exists, access and scoping, their place in the pipeline, the standard report set, and validation against numbers they can check themselves. Use when a new audience is onboarded, when an existing one adds a site, a region or a business unit, when their reporting is rebuilt after a change on their side, or when they say the numbers do not match their own records.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the git commits for a Jira ticket into a short, business-friendly implementation report and save it as local markdown. Use when the user wants to report finished work on a Jira ticket: a Jira report, update, or comment, a summary of their commits or changes for the ticket, or a note telling PM/QA what shipped.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Drafts filing-ready Annual Reports for State Charity Bureaus with certified financials, governance disclosures, and required attachments. Extracts organizational, financial, and programmatic data from uploaded documents, researches state-specific filing requirements, and produces a penalty-of-perjury-certified report. Use when drafting charity bureau annual reports, nonprofit compliance filings, charitable solicitation renewals, or state charity registration renewals.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
日本語の概要は準備中です。原文の説明を表示しています。
Fri→Fri community signals routine across CopilotKit + AG-UI. Orchestrator that supervises subagents — Discord pull, GitHub pull, deep-read, reporter enrichment, Reddit Pulse — and synthesizes a Notion report under the Community Signals parent page. Triggers on "go", "weekly report", "community signals", "run routine".
日本語の概要は準備中です。原文の説明を表示しています。
Enterprise-specific view across CopilotKit + AG-UI. "Enterprise" here = CopilotKit's COMMERCIAL surfaces (Premium / CopilotKit Enterprise / Intelligence Platform / paid tiers), NOT CopilotKit running inside a big company. Tracks the commercial product surfaces (from product-surface-scan — Enterprise Intelligence, Cloud, self-host license, threads/persistence tier, Inspector, premium UI/Angular SDK, analytics, security bundle, Slack/Teams), applies the free-vs-paid classifier to decide if an issue belongs here, surfaces cross-page product contradictions, and tracks enterprise questions/complaints, community-sourced prospects (with a sales owner), and enterprise reporters with prior-week trend. Elevated to the top of the weekly report. Runs standalone ("who's at enterprise this week") or invoked by weekly-report. Triggers on "enterprise report", "enterprise signals", "enterprise status", "who at enterprise this week".
日本語の概要は準備中です。原文の説明を表示しています。
Epic/report dashboard for Codex. Equivalent to the repository's Claude skill: render the orchestration state from bash scripts and summarize it cleanly. Usage: /report [<epic_N> ...]
日本語の概要は準備中です。原文の説明を表示しています。
Creates marketing analytics reports, KPI dashboards, ROI calculations, and performance summaries for SME marketing teams. Handles weekly/monthly reporting, campaign analysis, content performance reviews, and data-driven recommendations. Use when user asks about marketing metrics, reporting, KPIs, dashboards, ROI analysis, performance review, or data-driven marketing decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Turn content into a responsive, presenter-friendly slide deck published at a live URL via ReportRoom. Use when the user says "make this a deck", "turn this into slides", "presentation for", or wants something to present rather than read. Not for long-form documents (use report-publisher) or polishing an existing deck (use report-designer).
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing a .NET pull request for breaking changes that may affect other microservice repositories. Detects cross-repo API, DTO, endpoint, EF entity, and NuGet-package breaks, and checks whether a compatible downstream PR already exists. Keywords: cross-repo impact, breaking change, microservice compatibility, downstream break, compatible PR, blast radius review, api compatibility, contract break, dto shape change, endpoint break.
日本語の概要は準備中です。原文の説明を表示しています。
Maintains repo-local action contracts and harness repositories where product CLI and MCP adapters stay thin over core libraries. Use when adopting or improving steward.yaml actions, capability-level adoption evidence, cold-start proof loops, probes, benchmarks, CLI/MCP/core parity, adapter refactors, packages/core boundaries, or sibling harness layout; use repo-quality-system-lifecycle first for general app/library/tool stewardship baselines.
日本語の概要は準備中です。原文の説明を表示しています。
Master orchestration for repository governance, North Star impact, sub-Star boundaries, and repair-first or evidence-first drift checks. Guides an agent through the complete lifecycle of making architectural decisions, documenting them, writing FAQs, and cleaning up stale plans while adhering strictly to repo ethics and brand tone. Use whenever you need to make a structural change, write an ADR, update the doc lattice, or govern repository architecture.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and safely clean local project repositories or workspaces with excessive generated files, old project residue, dirty Git status, stale worktrees, build caches, duplicate nested projects, confusing roots, or agent context/token waste. Use when the user asks to organize a repo, remove useless files, classify valid project files, clean untracked/deleted files, reduce disk usage, migrate from an old repo layout to a canonical project, or prepare a repository for future Codex/agent work.
日本語の概要は準備中です。原文の説明を表示しています。
Monthly delta tracking and progress reporting for GEO clients. Compares two GEO audits (baseline vs. current), calculates score improvements across all categories, tracks action item completion, and generates a "here's your progress" client report. Use when user says "compare", "delta", "monthly report", "progress", "confronta", "progressi", "report mensile", or when running a monthly client check-in.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update project test-case assets and test reports. Use when Codex is asked to generate test cases in Excel, produce a Word/DOCX test report, summarize automated test execution, turn repository tests into a formal testing artifact, or沉淀/复用 a project testing documentation workflow.
日本語の概要は準備中です。原文の説明を表示しています。
dev-graph を呼出し元 repository/worktree 内へ冪等初期化したいとき、6 content root と repo-local config/state/templates/hook fallback を安全に用意したいときに使う。
Discover, compare, and compose existing open-source GitHub repositories for a user's goal, using GitHub MCP for live discovery and verification plus Context7 semantic retrieval over repository code and official documentation. Use when a user asks for GitHub repo recommendations, open-source alternatives, a multi-repository solution stack, project comparison, or help choosing an implementation to adopt.
日本語の概要は準備中です。原文の説明を表示しています。
設計文書、分析レポート、報告書などを批判的な視点で徹底レビューするスキル。 6つの異なる立場（開発者、PM、顧客、QA、セキュリティ、運用）のペルソナを持つサブエージェントが並列でレビューを実行し、 「本当にそうか？」「根拠は何か？」「テストできるか？」「運用できるか？」という視点で 曖昧さ、根拠不足、論理飛躍、テスト不能、セキュリティリスク、運用懸念を検出する。 Use when reviewing design documents, analysis reports, incident reports, or any document requiring rigorous validation of claims and evidence.
ISTQB/JSTQB のテストプロセス各工程の出口ゲートとして、工程成果物（test-plan.md / test-analysis.md / test-design.md / test-case.md / テスト実装 / test-execution-log.md / test-monitoring.md / test-summary-report.md）をレビューするスキル。決定論スクリプトの機械検査（トレーサビリティ ID 突合・テンプレ準拠）と test-reviewer サブエージェントの定性レビューを行い、利用者が通過/条件付き通過/差し戻しを判定して軽量記録 test-review-<工程>.md を残す。上流の仕様・基本設計（spec / design-doc 工程。docs/dev/<対象>/spec.md・basic-design.md）は機械検査と利用者判定のみの軽量ゲートとして扱う。各工程スキル（test-plan〜test-report / feature-spec / basic-design）が完了宣言の前に本スキルの実行を促す。ソースコード diff のレビュー（diff-review）とは別物で、対象はテストプロセスの成果物のみ。成果物の修正・代作はしない。/test-review <テスト対象名> [工程] で明示的に呼び出されたときのみ使用する。
Produces marketing performance reports and data-driven recommendations from WooCommerce sales data, social media metrics, and campaign analytics. Use when the task asks for "campaign performance", "ROI analysis", "monthly report", "sales trends", "product velocity", "audience insights", or "KPI tracking". Covers metric definition, reporting templates, slow-mover detection, and insight-to-action frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Please browse the current repository under /workspace/{{ REPO_FOLDER_NAME }}, look at the documentation and relevant code, and understand the purpose of this repository.
日本語の概要は準備中です。原文の説明を表示しています。