「reports」の検索結果

Track and analyze US government shutdown liquidity impacts by monitoring TGA (Treasury General Account), bank reserves, EFFR, and SOFR data from FRED API. Use when user wants to (1) analyze current or past government shutdown effects on financial markets, (2) track liquidity conditions during fiscal policy disruptions, (3) assess "stealth tightening" effects, (4) compare shutdown episodes across different monetary policy regimes (QE vs QT), or (5) generate liquidity stress reports with historical context. Recommended usage frequency is weekly on Wednesdays after TGA/reserve data releases.

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

Start-of-session situational report for a research or code repository. Reads the handoff, log, or status files the project actually keeps, checks live git state, and reports the objective, verified baseline, open tasks, blockers, and next actions, flagging where the documents and the repository disagree. Use when resuming work after time away or before changing anything. Its end-of-session twin is finished.

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

End-of-session closure for a research or code repository. Records what changed into the project's own handoff and log files, separating verified work from work merely attempted, and reports what is left uncommitted. Use when wrapping up a session so the next one can resume without re-deriving state. Its start-of-session twin is sitrep.

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

Launches and configures the standalone presubmit CLI, an API-driven adversarial peer-review pipeline with 30-plus stages, including Red Team finders, Blue Team defence, verification cascade, legal pass, and copyedit, producing one consolidated report on disk. Verifies installation and API key, chooses the output location and smoke, standard, or custom mode, launches the run, and reports the result path. Use when the user asks to run presubmit, wants a deep unattended pre-submission audit, or needs a math or replication-code audit. Everyday self-audits go to paper-review-lite, and external refereeing to journal-review.

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

Audits a methods section against a 45-item reporting checklist synthesized from the APSA Experimental Section rubric, JARS-Quant, CONSORT, and DA-RT, covering pre-registration, recruitment, randomization and treatments, sample flow and attrition, sample-size justification, three-tier results labeling, conjoint reporting, validity, and open-science infrastructure. Use when checking whether a methods section reports enough, preparing a submission or replication archive, asking what CONSORT, JARS, or DA-RT require, or documenting a deviation from a pre-analysis plan. Writing that plan before data collection goes to pre-registration-writing.

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

Writes or reviews a pre-analysis plan before data collection — registry choice (OSF, AEA RCT Registry, AsPredicted, registered reports), PAP structure, models and decision rules locked in advance, analysis code run on simulated data, contingencies for attrition, failed manipulations, and exclusions, deviation records, and timeline. Operationalizes the pre-data-collection side of DA-RT. Use when the user asks to draft or audit a pre-registration or PAP, choose a registry, decide what to lock versus leave exploratory, or handle a later deviation. Hypotheses and estimands come from hypothesis-building, post-hoc reporting from methods-reporting.

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

Organizes an author’s response to peer review. Extracts every referee and editor point, tags severity and type, orders the revision by dependency, flags defensible pushbacks as questions, and builds a numbered comment → response → location letter whose substantive answers the author writes. Use when the user has referee reports, a revise-and-resubmit decision, or an editor’s letter and wants to plan the revision, draft the response letter, or check that every point was addressed. The reviewer-side twin is journal-review.

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

End-of-session closure. Records what changed into the project's own handoff and log files, separating verified from attempted work, and reports what is uncommitted. Use when wrapping up a session. Twin of sitrep.

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

Start-of-session report on where a repository stands. Reads the project's own handoff and log files, checks live git state, and reports objective, verified baseline, open tasks, blockers, and next actions. Use when resuming work. Twin of finished.

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

Writes or reviews a pre-analysis plan before data collection: registry choice (OSF, AEA, AsPredicted, registered reports), locked models and decision rules, code run on simulated data, contingencies, and deviation records. Use when drafting or auditing a pre-registration or PAP, choosing a registry, or handling a deviation.

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

Performance measurement, attribution modeling, and marketing ROI analysis. Use when setting up tracking, analyzing campaign performance, building attribution models, or creating marketing reports.

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

Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines

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

Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.

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

Crawl GitHub trending repositories, analyze with LLM for Chinese insights, categorize by themes, compute diffs against history, and generate Markdown reports. Default brief mode stops at trend analysis; optional detailed mode appends per-project analysis. Supports incremental gap-filling and selective re-analysis with caching.

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

Разбор extraction-reports со status pending-review — решение R15 (accept/reject/defer) ЖИВЫМ ПИЛОТОМ, запись в Pack, обновление статуса, коммит. Вызывать при Close при наличии N>0 pending-review отчётов.

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

Use when verifying information (fact, number, quote, event, statement) against authoritative primary sources, or cross-checking a number via one-level metric decomposition (Z = P × Q). Triggers: "verify X", "is this true", "find the original source", "where is this number from", "two sources disagree", "is it true X never did Y". Covers five scenarios: (1) basic truthfulness check, (2) completeness / out-of-context quoting, (3) one-level reasoning verification, (4) negative-statement handling, (5) multi-source conflict side-by-side output. Dig into whitelisted primary sources only (user-supplied files, official websites & databases, authoritative industry sources); cited reports / charts / datasets must be downloaded and read locally to count as verified — if download is blocked, hand the link to the user. If nothing can be found, plainly state "cannot verify" rather than guessing, patching, or citing secondary paraphrases. Always reply in the user's question language.

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

Measure whether a change made the tree simpler, on numbers rather than impressions — line counts, branching, coupling, interface width, rule count, standing exemptions and model-visible prose — across one diff or a whole stack of pull requests. Use before claiming a pass reduced complexity, when deciding which pull request in the stack added the machinery, and to read a function's branch count, which no v2 gate reports.

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

Launch and collect independent Codex sessions (gpt-6-luna at high, xhigh or max; gpt-6.1-sol at low to xhigh) for bounded parallel work, from Claude Code or from Codex: one manifest, one detached launcher, one report a session, a drain while it runs, and a retry of the sessions that ended without a report. Owns the Codex transport when another skill sets the questions, as whole-run-investigation does for its lanes. Use when the operator asks for Luna or Sol sessions, a swarm, many sessions, a reasoning effort, a Codex subagent from Claude Code, or a later collection of reports. Tell a request to launch from one to wait and collect.

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

Transition from static LLM chats to autonomous agents that execute multi-step tasks. Use this when you need to automate cross-platform reports (e.g., Snowflake to Google Docs), build self-service tools for non-technical teams, or create "anticipatory" engineering workflows that draft PRs based on Slack discussions.

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

Generate markdown reports from issues. Filter by type, priority, epic, date range. Supports summary, detailed, progress, completion, velocity, and backlog analysis views.

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

Orchestrates multi-agent workflows by delegating ALL tasks to spawned subagents via /spawn command. Parallelizes independent work, supervises execution, tracks progress in UUID-based output directories, and generates summary reports. Never executes tasks directly. Triggers on keywords: orchestrate, manage agents, spawn agents, parallel tasks, coordinate agents, multi-agent, orc, delegate tasks

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

Orchestrate a broad Incan review using specialized reviewer roles, parallel slice reports, and a canonical merged review report. Use when the user asks for delegated review, multi-agent review, or when a broad dirty worktree should be reviewed by specialized passes rather than one generic reviewer.

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

Detect, triage, de-duplicate, and raise compiler bug reports when an agent encounters a likely compiler defect during implementation, review, testing, or issue work. Use when a task surfaces an ICE, panic, wrong accept/reject behavior, miscompile, lowering/emission bug, diagnostic bug, formatter/LSP/frontend drift, or other likely compiler/tooling defect; pause current work, minimize the repro, decide whether the bug blocks the task or has a valid workaround, check whether it is already reported, and then use create-github-issue to raise the bug.

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

Investigate an alert, page, or production symptom in an incident channel or a team's oncall / monitoring channel, and report findings a human can verify. Ordinary conversation and chatter are not alerts; leave those alone. Use when an alert or page lands, when error rate, latency or saturation is up, when someone asks "why is X broken", "investigate", "what changed", "root cause this", pastes a monitor, dashboard, trace or error-tracker link, or reports production trouble; also by default when an alert lands in a covered channel unasked. Feed-level asks land here too ("which alerts matter", "triage today's alerts"), plus the scheduled alert-review routine and the ticket path ("customer X can't check out"). Runs a fast first pass posted as a short interim update with a TL;DR, every finding carrying the query or link to verify it, then proposes the fix and — with connector access and confirmation — carries it out, never unattended. Afterwards `incident-postmortem` writes it up.

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