420 件 ・ 関連度順
概要と使いどころ
Design, prioritize and run measurable growth experiments across acquisition, activation, retention, referral and revenue. Use when a startup needs an experiment backlog, ICE/RICE prioritization, referral or UGC loops, rapid weekly testing, causal measurement, or stop conditions without spam, fake accounts or dark patterns.
日本語の概要は準備中です。原文の説明を表示しています。
华安保险车险周报自动生成器（麦肯锡风格）。将周度车险数据（支持Excel/CSV/JSON/DuckDB）转化为12-13页董事会级经营分析报告。采用问题导向标题、16:9宽屏、四象限/气泡图可视化、深红#a02724配色。报告结构：经营概览、保费进度、变动成本、损失暴露、费用支出，每个章节分机构和分客户类别双维度分析。支持自定义阈值配置和保费计划。触发场景：用户上传车险周报数据文件（.xlsx/.csv/.json/.db），要求生成董事会汇报PPT。
日本語の概要は準備中です。原文の説明を表示しています。
Design and spec an analytical dashboard — define the question each chart answers, write the SQL queries, spec the layout and refresh cadence. Produces a complete dashboard spec ready to implement. Use when asked to "build a dashboard", "analytics dashboard", "BI dashboard", "weekly product health", or "visualize this data".
日本語の概要は準備中です。原文の説明を表示しています。
直近 1 週間の売上・廃棄・欠品・施策（Cowork から登録した発注を含む）を Dataverse から集計し、SV（スーパーバイザー）向けの週次店舗レポートを、チャットのグラフ（Render UI）と表、HTML レポート（頼まれたら Excel も）で作るスキル。 Use when ユーザーが「週次レポートを作って」「SV に今週の報告をまとめて」「今週の振り返りを Excel にして」と依頼したとき。 Dataverse MCP コネクタ（describe / read_query）を読み取りで使う。
Build a weekly TikTok posting plan from a niche, audience, and content pillars. Produces per-day picks (hook formula, angle, sound, video length, goal, posting time), a hook-batching schedule so you film several openers in one session, a sound shortlist with the trend window, and a completion-rate goal check. Use for a repeatable posting rhythm instead of ad-hoc videos. Not for scripting one hook (use tt-hook-scripter) or one caption (use tt-caption-writer).
日本語の概要は準備中です。原文の説明を表示しています。
Applying motion study and time analysis to household work. Based directly on Lillian Gilbreth's *The Home-Maker and Her Job* and *Cheaper by the Dozen*, this skill covers the therblig-motion catalog, task decomposition, batch processing, parallelism, routine chart design, and the ergonomics of work surfaces. Use when diagnosing why a household is running out of time, designing a weekly routine, teaching task sharing to children, or reducing the friction of any repeated household task.
日本語の概要は準備中です。原文の説明を表示しています。
OpenStack backup operations skill for protecting cloud infrastructure through systematic backup strategies and disaster recovery procedures. Covers database backups (MariaDB full and incremental with mariabackup), configuration backups (globals.yml, inventory, Fernet keys), volume snapshots (Cinder LVM snapshots), image exports (Glance), instance snapshots (Nova), backup encryption (GPG/OpenSSL), retention policies (daily/weekly/monthly rotation), restore procedures (database point-in-time recovery, service rebuild), RPO/RTO planning, and disaster recovery drills. Use when planning backup strategy, scheduling automated backups, testing restore procedures, or executing disaster recovery.
日本語の概要は準備中です。原文の説明を表示しています。
用户在周期性复盘 X 内容数据、分析哪些内容类型表现好、决定下步内容策略调整时使用。四步闭环:数据收集(拉曝光/互动/收藏)→原因分析(按内容类型对比,查Hook/Body/CTA)→优化迭代("如果重来怎么做更好")→记录追踪(Notion模板闭环)。找20%贡献80%价值的内容加倍投入。周复盘聚焦数据(互动率),月复盘审视战略(变现路径)。Trigger signals:"这周发了15条怎么复盘""哪些类型互动高""下周内容策略怎么调""帮我分析数据"/"weekly content review""which content type performs better""optimize next week's content"。不适用于:单条内容生产(用x-short-content-craft)、帖子没爆焦虑心态(用x-longtail-strategy)、理解推荐算法机制(用x-foryou-algorithm)。
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly review of IWE work culture (element 14 — System Evolution). Runs during Week Close.
日本語の概要は準備中です。原文の説明を表示しています。
Стратегическая сессия — диспетчер. День-0 (маркер IWE-INITIAL-NEEDED или нет Strategy.md/WeekPlan) → initial flow (цели, неудовлетворённости, первый WeekPlan). Первая сессия календарного месяца → полный monthly flow (стратегическая сверка + линза калибра). Остальные дни → короткий weekly flow (требует черновик от session-prep). Триггеры — «проведём стратегическую сессию», «первая стратегическая сессия», «strategy session», «давай стратегировать».
日本語の概要は準備中です。原文の説明を表示しています。
Summarise the job search from the markdown tracker - funnel, response rate, what's working, where applications come from, what's pending on the user. Use when the user runs /seekter-report or asks how the search is going, for weekly numbers, or what to change.
日本語の概要は準備中です。原文の説明を表示しています。
Run the oncall handoff for a rotation window — the whole handoff, not just a document: build the summary (what the incoming oncall needs first, what's still open, incidents with impact numbers, alert and page counts, hygiene suggestions, every number traceable to a source), post it for the outgoing oncall to correct, walk the incoming oncall through the open items in the thread, update the list as they respond, and note when they acknowledge. Runs mainly in the team's standing oncall / monitoring channel, normally as a scheduled routine firing at rotation change so the report is waiting when the shift turns over; can also be run by hand and works from an incident channel. Use when a handoff routine fires, or on "handoff", "hand over", "oncall summary", "weekly oncall report", "what happened this shift / this week". Re-running for the same window updates the report rather than duplicating it. Unattended runs carry a run-summary block and at least one chart.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you want a weekly feature announcement package from recent merge requests, including Slack, blog, LinkedIn, and carousel outputs.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a weekly Facebook Page content plan from a theme, audience, and content pillars. Produces per-day picks (short post vs story post, hook formula, angle, posting time, primary goal), a short-to-story post mix, a daily comment-reply target, and a share-optimized goal-mix balance check across shares, comments, and reactions. Use when the user wants to plan a week of Page content. Not for drafting one post (use fb-post-writer) or replying to comments (use fb-engagement-drafter).
日本語の概要は準備中です。原文の説明を表示しています。
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.
日本語の概要は準備中です。原文の説明を表示しています。
Build a weekly YouTube upload plan: long-form vs YouTube Shorts mix, posting cadence, per-slot title and thumbnail pairing, hook angle, community-tab posts between uploads, and a goal balance across CTR, retention, and subscribes. Maps Shorts as top-of-funnel that points at long-form, and long-form as the loyalty and watch-time engine. Use to plan a week or a content calendar instead of shipping ad hoc. Not for writing a single title, description, or hook (use the dedicated yt skills).
日本語の概要は準備中です。原文の説明を表示しています。
Plan, write, and publish for YouTube and YouTube Shorts. Use when the user wants high-CTR video titles, an SEO description with chapters and links, a first-30-seconds retention script (or a 3-second Shorts hook), a designer-ready thumbnail brief, a community-tab post or poll, or a weekly upload plan. The user supplies the video; the skills produce the title, description, hook, and thumbnail brief, then on approval upload and schedule via the Publora API.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and produce newsletter editions — content selection, subject lines, scheduling, and production with quality gates. Use when "newsletter", "plan newsletter", "newsletter content", "email newsletter", "weekly digest", or any request to create or manage a newsletter.
日本語の概要は準備中です。原文の説明を表示しています。
Build and operate a complete, brand-neutral Reddit intelligence system with approved read-only monitoring, grouped keyword rules, evidence-backed AI scoring, a persistent opportunity bank, dashboard review, urgent-alert and weekly-digest previews, content briefs, and human-only response drafts. Use for "reddit intelligence", "reddit monitor", "reddit listener", "watch subreddits", "find reddit opportunities", "content ideas from reddit", "community listening", or setting up this workflow for a client or brand.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-platform brand intelligence pulse - collect cited public reputation evidence across web, news, YouTube, X, LinkedIn, Reddit, and review sites, then turn it into objection mining, content angles, competitor positioning, and surround-sound actions. Use when "brand monitor", "brand pulse", "what are people saying about us", "multi-platform reputation", "brand intelligence", "weekly brand monitoring", "objection mining", or "public reputation scan".
日本語の概要は準備中です。原文の説明を表示しています。
Aider is an open-source AI pair programming tool that runs in your terminal, letting you collaborate with LLMs to edit code across your entire codebase. With 42k+ GitHub stars and 15 billion tokens processed weekly, it features deep git integration, repo-wide code mapping, and support for 100+ programming languages.
日本語の概要は準備中です。原文の説明を表示しています。
Use weekly to find and ship one new automation. Walks the 3Ms interview — Mindset (find the candidate) → Method (scope one) → Machine (build it). Trigger on "let's level up", "what should I automate next", "find me leverage this week", or as a Friday ritual. One run = one shipped artifact.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a weekly Threads (Meta) content plan from a theme, audience, and content pillars. Produces per-day recommendations (single post vs thread, Threads hook formula, angle, posting time, primary goal), a single-to-thread mix, daily reply and quote-post targets, and a goal-mix balance check across replies, reposts, likes, and quotes. Use when the user wants to plan a week of Threads content instead of ad-hoc posting. Not for drafting one post or thread (use threads-post-writer).
日本語の概要は準備中です。原文の説明を表示しています。