「weekly-report」の検索結果

OpenDesign's weekly growth review: stars, installs, activation — the number, the driver, and the recommended move. Built as a decision-grade data & finance deck for growth & product team.

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

Subagent that scans CopilotKit + AG-UI releases shipped in (and just after) the report window, diffs the git tags to extract what each release actually fixed, and returns a fix-map the weekly-report writer cross-checks against open issues. Catches issues that are quietly already-fixed in a shipped release, and is the authoritative source for the "current release vX.Y.Z" version claims. Invoked by weekly-report (spawned in parallel with the Discord/GitHub pulls); runs as a general-purpose subagent so the orchestrator's context stays small.

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

Structure and data sources for the weekly inventory report. Load this when the task is "weekly report", "Monday report", or "summarize inventory status".

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

Write a Chinese workplace weekly or monthly report (周报 / 月报) for a manager: results with numbers, progress against goals, risks raised early, next week's plan and the support needed, in the structure Chinese managers expect. Use when asked 帮我写周报, 写月报, 整理本周工作, weekly report in Chinese, or turn my notes into a 周报. Produces the report in Chinese with 本周完成, 关键数据, 问题与风险, 下周计划 and 需要的支持, plus a one-line summary for chat apps.

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

Compile a weekly productivity report using Agent Monitor data — daily_sessions and daily_events trends, per-session costs from pricing engine, token volumes (input/output/cache_read/cache_write + baselines), tool usage top 20, session completion rates by status, and workflow intelligence metrics.

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

Weekly. Scores the week from the ledgers with a source path beside every number and never writes a number it did not count in a file this run. It names exactly two things and files both as cards, the one fix worth doing next week and the one thing to stop, and it replays every learned browser flow once, read only, so a drifted selector is found on a Friday rather than on a Tuesday morning a routine needed it.

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

Twitter/X Agent Operations SOP v2 — Rebuilt from real dual-account operations. Real data: • CN account: grew from 1,150 → 3,679 followers (~14 months), 1 tweet/day, OAuth1 direct post • EN account: Buffer API • Real incidents: cron silent-failed for 2 weeks unnoticed, analytics data off by 17×, thread performance worse than single posts What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily log after every tweet + weekly report every Monday • Pre-publish safety checklist (agent must pass before posting) • Content pool tracker (used/unused) + alert when ≤3 items remain • Dual-account credential separation (CN: OAuth1 / EN: Buffer API) • MASTER-STATUS.md as the single source of truth — read + write every session 🇨🇳 Twitter/X Agent 运营 SOP v2 — 基于真实双账号运营经验重写。 开局对话式收集 context、强制日报+周报、发推前红线自检、素材库追踪、双账号凭证分离、MASTER-STATUS.md 单一真相来源。 真实数据：中文账号从 1,150 粉增长至 3,679 粉（约14个月），1条/天。 Triggers: "twitter运营" | "推特agent" | "发推SOP" | "AI代运营" | "推文日报" | "素材库" | "Buffer API" | "OAuth1发推" | "twitter automation" | "tweet sop" | "推特涨粉"

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

华安保险车险周报自动生成器（麦肯锡风格）。将周度车险数据（支持Excel/CSV/JSON/DuckDB）转化为12-13页董事会级经营分析报告。采用问题导向标题、16:9宽屏、四象限/气泡图可视化、深红#a02724配色。报告结构：经营概览、保费进度、变动成本、损失暴露、费用支出，每个章节分机构和分客户类别双维度分析。支持自定义阈值配置和保费计划。触发场景：用户上传车险周报数据文件（.xlsx/.csv/.json/.db），要求生成董事会汇报PPT。

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

Subagent flow for deep-reading GitHub issues + their linked/closing PRs to the bottom. Captures CURRENT state, maintainer status updates, reporter repro, blocking reviewer concerns, hidden second bugs, cross-repo duplicates. Invoked by weekly-report orchestrator; runs as a general-purpose subagent so the orchestrator's context stays small.

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

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".

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

After a weekly report is built, diff it against the PRIOR report to find items that appear in BOTH weeks, then print the Owner (and prospect "Passed to") value recorded last week so it can be carried forward. Print-only — never edits the owner fields; Nathan verifies and re-tags in Notion. Invoked by weekly-report near the end, and standalone on "carry forward owners", "who owned this last week", "owner continuity".

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

Builds the "Report Sources" child page for a finished Weekly Community Signal report — an evidence-backed defense of WHY every item landed in the column/section/rank it did. The agent argues each placement like a lawyer (claim → evidence → rule → rebuttal) but is under oath: it CANNOT invent, spin, or overstate — every claim ties to a verifiable fact (issue #, label, PR type, quoted comment, npm output, the front-door test). Not CYA — it's so Nathan can defend the report with facts and see the exact reasoning behind each call. Runs after the report (invoked by weekly-report, last steps) and on "report sources", "defend the report", "why is this here".

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

Scans CopilotKit's public product / pricing / Premium pages at the start of every weekly report to produce the authoritative list of COMMERCIAL surfaces (Premium · CopilotKit Enterprise · Intelligence Platform · paid tiers) and detect any newly-added or changed commercial feature since last week. This list defines what the report's 🏢 Enterprise section is about — CopilotKit's commercial/paid product, NOT "CopilotKit running inside an enterprise company." Emits the surface list + a free-vs-paid classifier the report uses to decide "does this issue hit a commercial surface?", plus a diff of what changed. Runs as a subagent (many web fetches) so the orchestrator's context stays small. Invoked by weekly-report (spawned at report start) and the enterprise skill; also triggers on "scan product surfaces", "what's premium", "commercial surfaces", "did we add a premium feature".

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

Generate the ≤10-minute Loom walkthrough script for a completed Weekly Community Signal report — a plain spoken briefing that dives straight into what the team needs to know, walking the report top to bottom (CopilotKit page first, then AG-UI in the same order). Straightforward and factual, NOT a radio show or a performance; no hype opener, no blame framing. Runs after every report (invoked by weekly-report) and on "loom script", "walkthrough script", "record the loom", "narrate the report".

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

P0 classification rules for community reports. Six categories that auto-headline regardless of reporter count. Reference doc — invoked by weekly-report when classifying.

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

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".

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

Subagent for GitHub author enterprise enrichment. Runs gh api users/<login> for each unique handle and classifies enterprise vs indie. Invoked by weekly-report or enterprise skills; runs as Explore subagent so the orchestrator's context stays small.

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

Deep enrichment for community-sourced enterprise PROSPECTS (the 🎯 Prospective enterprise customers subsection). For each prospect, resolve their LinkedIn from their GitHub self-linked accounts FIRST (search only if none is self-linked), verify the employer matches, capture their full name, then list the company website + company size (ARR / latest funding round / employee count). Runs as a general-purpose subagent (many web searches) so the orchestrator's context stays small. Invoked by weekly-report (enterprise section) and the enterprise skill.

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

Writes a DRAFT weekly KPI report from the figures the user pastes or attaches (this week, last week, optionally target and earlier weeks): a metrics table with change versus last week computed only from the stated figures, plain-language notes per metric, and numbered questions on every figure that moved more than the agreed threshold, crossed its target or broke its run. Use when the user asks to "write the weekly KPI report", "turn these numbers into this week's metrics report", "what changed versus last week", "draft the Monday numbers update" or "add commentary to this metrics table". Do not use for a recurring emailed report with a maintained trend sheet, use report-attachment-analyzer instead; for actuals versus budget, use budget-variance-explainer. Drafts for human review; never approves, authorises or signs off.

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

Turns a list of KPIs or metrics into a DRAFT definition sheet: one row per KPI with the name as stated, formula quoted from a source, source system, owner, refresh cadence, unit, filters and known caveats, with UNKNOWN in every cell no source fills and a gap list grouped by data owner. Never composes a formula, sets a target or names an owner the sources do not state. Use when the user asks to "define these KPIs", "build a metrics definition sheet", "document how each KPI is calculated", "which of our KPIs have no owner or formula" or "reconcile the two KPI lists". Do not use for the weekly numbers report, use kpi-weekly-report-writer instead; for field-level definitions of a table, use data-dictionary-builder; for logging a wrong figure as a defect, use data-quality-issue-log. Drafts for human review; never approves, authorises or signs off.

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

Turns an actuals-versus-budget extract (spreadsheet, export or pasted table) into a DRAFT variance table with absolute and percentage variances, favourable or adverse marking and a ranking by size, then drafts plain-language driver hypotheses for each material variance as questions to verify with a named owner, never as asserted causes. Use when the user asks to "explain these variances", "why are we over budget on this line", "write the variance commentary for the management pack", "actuals versus budget analysis" or "which lines drive the variance". Do not use for a dataset with no budget or comparison column, use dataset-insight-pack instead; for weekly operational figures against last week, use kpi-weekly-report-writer. Drafts for human review; never approves, authorises or signs off.

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

Monday morning full pipeline review with metrics, channel performance, and forecast. Reads all CRM tabs, calculates deltas vs previous week, and generates actionable recommendations.

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