「daily」の検索結果

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" | "推特涨粉"

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

🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" | "engineering operations" | "product development SOP" | "sprint planning" | "iteration management" | "cross-functional alignment" | "product engineering ops" | "dev ops collaboration" | "产研运协同" | "迭代管理" | "产品研发运营" | "プロダクト開発運営" | "제품개발운영"

Use when creating or backfilling AI-categorized daily GitHub releases from branch commits.

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

When the user wants an agent to run SEO for a product end to end on a daily schedule, with state kept in a seo/ folder in the repo. Covers site health checks, fact checks against commits, page 2 to page 1 pushes, AI answer tracking, competitor sitemap diffs, a monthly keyword map, articles, comparison pages, free tools and link drafts. Also use when the user mentions "seo autopilot" or asks for a daily SEO run.

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

Use when a human explicitly requests the daily on-call issue digest from a named issue tracker for a configured Slack channel. Not for posting without explicit human authorization for that run.

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

コンペ戦略の横断synthesis を実行する。competition-strategist agent を起動し、daily_reports/* と全 SESSION_NOTES.md / claudeSummary.md / submit/SUBMISSIONS.md / KAGGLE_DIRECTION.md を一括ロードして「次の一手」を出力する。週1回や局面の変わり目で使う。

Create today's daily_reports/YYYYMMDD.md by carrying over pending TODOs and recent experiment results from yesterday's report. Use at the start of a session.

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

コンペ知識を knowledge/ ストック層（原子ページ + INDEX）に効率よく蓄積・検索する。daily_report のフローから再利用可能な知見を蒸留して昇格させ、重複を排除しながら最新化する。知見が出たとき・週次整理・過去知見を引きたいときに使う。

Start your day with a prioritized sales briefing. Works standalone when you tell me your meetings and priorities, supercharged when you connect your calendar, CRM, and email. Trigger with "morning briefing", "daily brief", "what's on my plate today", "prep my day", or "start my day".

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

Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.

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

职场日报/周报/月报智能生成助手。将零碎的工作记录、会议笔记、聊天记录等碎片化信息， 自动转化为结构清晰、成果导向的专业汇报文档。支持日报、周报、月报三种模式， 内置 OKR 逻辑重组引擎，自动识别核心产出与日常维护，确保汇报内容重点突出。 适用场景：每日工作汇报、周度进度同步、月度/季度复盘总结。 当用户提到"写日报"、"生成周报"、"月报总结"、"工作汇报"、"进度同步"时触发。

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

Time-blind friendly planning, executive function support, and daily structure for ADHD brains. Specializes in realistic time estimation, dopamine-aware task design, and building systems that actually work for neurodivergent minds.

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

Time-blind friendly planning, executive function support, and daily structure for ADHD brains. Specializes in realistic time estimation, dopamine-aware task design, and building systems that actually work for neurodivergent minds.

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

Time-blind friendly planning, executive function support, and daily structure for ADHD brains. Specializes in realistic time estimation, dopamine-aware task design, and building systems that actually work for neurodivergent minds.

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

This skill suggests using real-time continuous glucose monitoring (CGM) and algorithm-driven insulin pumps (ADIPs) rather than multiple daily injections (MDIs) with self-monitoring of blood glucose (SMBG) three or more times daily for adults and children with type 1 diabetes (T1D). Trigger phrases include "Should I use RT-CGM+ADIP or MDI+SMBG for this T1D patient?" or "Is intensive pump therapy indicated for this patient?"

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

Systematically interpret a Medtronic CareLink or MiniMed 780G Daily Review download in a structured 6-step clinical workflow — covering Time in Range, insulin delivery, day/night patterns, hypo and hyperglycemia root causes, and a prioritised action plan. Trigger when a clinician uploads or shares a CareLink report, MiniMed download, 780G Daily Review, pump download, or asks to review a patient's CGM or insulin pump data.

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

The skill suggests using real-time continuous glucose monitoring (CGM) combined with algorithm-driven insulin pumps (ADIPs) rather than multiple daily injections (MDIs) with self-monitoring of blood glucose (SMBG) three or more times daily for adults and children with type 1 diabetes (T1D) to lower hypoglycemia incidence. Clinical triggers include discussions about insulin pump therapy, CGM use, or reducing hypoglycemia in T1D patients on intensive insulin regimens.

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

Suggests using longer-acting glucocorticoids when standard hydrocortisone regimens are impractical due to nonavailability, poor adherence, or need for once-daily dosing. Triggers include glucocorticoid replacement therapy decisions where patients report difficulty with multiple daily doses, lack of access to hydrocortisone, or preference for simplified regimens.

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

Suggests using hydrocortisone 15–25 mg or cortisone acetate 20–35 mg daily in two or three divided oral doses for adult primary adrenal insufficiency (PAI) patients initiating glucocorticoid replacement. The highest dose is given upon awakening, with the second dose either early afternoon (≈2 h after lunch) or split into lunch and afternoon doses; consider total daily dose calculation based on chosen formulation and frequency.

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

Morning startup workflow for daily notes, yesterday summary, agenda, status comments, meeting sections, and daily branch setup. Use when invoked as `$work-start-day` or when the user asks to start the work day.

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

Daily Linear update

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

Generate a daily "where are we?" digest from this repo's GitHub epics — a render-only HTML + plain-text email summarising the last 24h of activity plus a progress snapshot of every open epic. Use when asked for a "daily digest", "epic report", "status rapport", "what moved this week", or "where are we on the epics".

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

日次ジャーナルを作りたいとき、今日やったことを会話で振り返りながら Obsidian の Daily へ構造化したファイルを生成・再生成したいときに使う。

Track and update action item status from natural language updates like 'Seanのメールには返信しておいた' or 'Lu対応予定'. Integrates with daily-comms-ops workflow. Use when managing action items across communication channels.