「daily」の検索結果

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.

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

Compile a month-over-month retrospective from Agent Monitor data — sessions, cost, token volumes, completion rate, top projects by working directory, and notable shifts versus the prior month. Uses daily_sessions/daily_events (365d) from analytics, the session list, and the pricing cost breakdown. Use when doing a monthly retrospective or planning the month ahead.

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

Analyze Claude Code usage trends over time using the Agent Monitor's analytics API — daily session counts, daily event counts, token volumes by type, model distribution, tool usage rankings, and agent/event type distributions across 365-day retention windows.

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

Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turn_count, total_turn_duration_ms).

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

When you want to monitor known sources on a schedule and feed the good stuff into your second brain. Configure sources once (YouTube, RSS/newsletters, subreddits, Hacker News, Bluesky, Mastodon, X, LinkedIn, keyword searches); each run fetches only what's new, scores it against your stated focus, writes one digest to the vault, and auto-captures high-signal items into raw/. Everything else waits in the digest until you promote it. Modes — run, digest, promote, add / sources / pause, doctor, schedule (daily launchd or systemd job). Triggers on "/radar," "run my radar," "check my sources," "what's new from my sources," "add a source," "monitor this channel," "watch this subreddit," "track this account," "daily digest," "promote item 4," "radar doctor." Complements second-brain (radar fills raw/, second-brain compiles it) and deep-research (standing surveillance vs a one-off dive).

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

When you want to set up an agent loop, cron-scheduled task, or recurring workflow that runs autonomously. Judgment layer on top of Claude Code's ScheduleWakeup, CronCreate, and /loop — or, on other hosts, cron/GitHub Actions plus a headless agent CLI. Picks dynamic pacing, fixed cron, or a one-shot loop; designs idempotent loop bodies; sets bail-out conditions so loops don't run forever. Examples — weekly review pulse, daily brief, hourly metric monitor, periodic vault compile, upstream-check for an adapted skill. Triggers on "/loopify," "set up a loop," "schedule this task," "run this daily," "run this weekly," "cron this," "make this recurring," "automate this on a schedule," "keep this running until X." Part of the -ify trifecta (skillify / toolify / loopify). NOT for authoring a new skill — that's skillify. NOT for adding a tool/integration — that's toolify.

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

Daily morning research note for A-share markets. Summarizes overnight developments, pre-market sentiment, trade ideas, and key events for the trading day. Adapted from the original morning-note skill for Chinese market conventions. Triggers on "早报", "晨会纪要", "今日策略", "morning note", "morning meeting", or "daily A-share preview".

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

Generates a variable reward system with randomized rewards, daily bonuses, mystery box mechanics, and ethical engagement caps. Use when user wants daily spins, mystery boxes, random rewards, or gamification reward systems.

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

Autonomous cold email campaign launcher. Takes one target company domain, scrapes their website, generates an ICP with Claude, pulls matching leads via Prospeo, enriches emails + company descriptions, personalizes each lead with parallel Claude Code Task sub-agents (A/B/C variants), and uploads as a live Smartlead campaign. Uses local JSON files for state (no database required). Use for automated daily campaign launches after you have an initial `client-profile.yaml` from /icp-onboarding. Triggers on "auto-research", "launch an automated campaign", "daily campaign", "run the research loop".

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

AI公众号信息源 — Daily scan of AI WeChat public accounts, finding the hottest articles by read count, auto-clustering into topics, and generating a styled HTML report with cover images, metrics, search, and subscription support. Use when the user wants AI daily reports, 公众号爆款, AI content curation, 每日AI热点, or 公众号日报.

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

Query FDA drug labels (DailyMed) via REST API. Search structured product labels (SPLs) by name, NDC, set ID, or RxCUI; get indications, dosage, warnings, adverse reactions, packaging. No auth. For adverse events use fda-database; for DDIs use ddinter-database.

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

Automate daily construction report generation using n8n workflow automation.

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

Automatically generate daily construction reports from field data, worker inputs, weather, and progress photos. Creates professional PDF reports.

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

Generate automated daily progress reports from site data. Track work completed, labor hours, equipment usage, and weather conditions.

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

Reverse weekly review for turning inbox noise, daily plans, diaries, calendars, annual plans, and long-range life plans into one happiness-and-peace-centered weekly plan. Use when the user asks for 週檢視, 反向週計劃, 8 Big Rocks, Inbox Zero weekly review, 幸福寧靜週, or wants to synthesize Todoist/inbox notes, daily diaries, calendars, yearly plans, and life plans into iMandalArt/FIRE/JSON outputs.

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

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

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

Дневной фокус штаба. Собирает открытые задачи всех отделов и пишет файл дня tasks/<ГГГГ-ММ-ДД>.md в штабе со ссылками на задачи. Применять по «что сегодня», «план на день», «задачи на сегодня», «daily».

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

Summarize each day's Git activity into a concise daily work log, for a single date or a range. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required.

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

Pieter Levels (@levelsio) 视角. 海外 indie hacker / solo builder 极致代表 — Nomad List + Photo AI + Interior AI + Remote OK 多产品 portfolio, 单人 $250K+/月 MRR, 零员工. 把"用 AI agent 赚钱"从"融资 + 招人 + scale 到 unicorn"的 VC 操作系统, 翻成"audience first + ship daily + stay solo + $10K MRR = 自由"的 indie 操作系统. 用途: 当用户问"我应该融资吗" / "AI 产品怎么 0→$1M ARR" / "1 个人能做多大" / "build in public 还有用吗" / "我应该招人吗" 时, 用 Pieter 视角先反问"你要的到底是 freedom 还是 valuation" — 如果是前者, 那 path 跟 VC 派完全相反. 当用户提到 "Pieter Levels" / "@levelsio" / "indie hacker" / "solo founder" / "Nomad List" / "Photo AI" / "build in public" / "ship daily" / "$10K MRR" 时使用. 即使用户只是说 "我想做个 SaaS 副业" / "怎么 bootstrap" 也应触发.

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

Suede-owned Instagram growth operating system for account-specific audits, Reels, carousels, Stories, conversion mapping, calendars, and daily candidate-production loops. Use when the user names Instagram, IG, Reels, Stories, asks to analyze recent posts, grow a handle, run a daily workflow, create or repurpose Instagram content, or distinguish views from follows, leads, and sales. NOT FOR: multi-platform organic strategy (use suede-social), full video rendering or editing (use suede-video), paid Meta campaigns (use suede-ads or suede-ad-creative), analytics instrumentation (use suede-analytics), or any publish, comment, follow, like, or DM action without exact approval.

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

Nexscope Ozon product detail query: fetches the complete detail of a single Ozon product by SKU, returning title, price (RUB), rating, review count, QA count, total and daily average sales within the stats window, revenue, stock, category ranking, daily sales trend, brand, seller, fulfillment method (FBO/FBS/OZON), weight, and listing time/days/months. Use for single product deep analysis, competitor product teardown, Ozon product selection assessment, listing diagnosis, sales trend and category ranking tracking. Trigger when the user mentions Ozon product detail, Ozon single product analysis, Ozon SKU query, competitor product data, Ozon sales trend, Ozon category ranking, Ozon stock, Ozon listing time, Nexscope Ozon product search, Ozon product detail, Ozon SKU lookup, single product analysis, competitor product teardown, Ozon sales trend, category rank. Also trigger when the intent is to view detailed data of an Ozon product, even without explicitly mentioning Nexscope.

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

It's 11pm before your launch. Your PH page is ready but you have no idea what actually moves the ranking algorithm. Upvotes? Comments? Time-of-day? This is the hour-by-hour operations manual from someone who's coached 30+ #1 finishes. What's inside: • Ranking algorithm deep-dive (it's not just upvotes — weighted factors decoded) • Launch day minute-by-minute checklist (PST timing, first 3 hours are critical) • Voter mobilization strategies (ethical, anti-spam-safe approaches) • Asset preparation templates (gallery, tagline ≤60 chars, maker comments) • Post-launch 72h momentum plan (convert PH traffic → retained users) Built from: 30+ PH #1 daily wins, 10+ weekly top 3, 2 monthly top 5. 3,000-5,000+ upvotes per launch. Triggers: "Product Hunt" | "PH launch" | "Product Hunt #1" | "PH ranking" | "Product Hunt strategy" | "PH upvotes" | "launch day" | "PH打榜" | "Product Hunt攻略" | "PH ranking algorithm"

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

Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 你的团队自由度很高——但 standup 越来越糊，例会变成汇报，1:1 问不出真话。这套三层 Motivation 操作手册解决的正是这件事：standup 是信息层，例会是对齐层，1:1 是个人层。三件事做好了，motivation 不是管出来的，是长出来的。 🇯🇵 チームの自律性は高いのに、スタンドアップは曖昧で、週次ミーティングは進捗報告になり、1on1では「大丈夫です」しか返ってこない——このプレイブックは、その3層すべてを同時に解決します。 🇰🇷 팀의 자율성은 높은데 스탠드업은 두루뭉술하고, 주간 회의는 진척 보고가 되어버리고, 1:1에서는 진심을 들을 수 없다면 — 이 플레이북이 세 레이어 모두를 동시에 해결합니다. Triggers: "团队 motivation" | "standup 没人写" | "例会变成汇报" | "1:1 问不出真话" | "高自由度团队管理" | "COO 如何管人" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "チームモチベーション" | "팀 동기부여" | "AI startup team ops" | "remote team alignment" | "engagement下降"

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

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