「tracking」の検索結果

メールやウェブサイト、ローカルファイルから進捗を集め、定期更新するダッシュボードを作成。要対応事項や変更履歴をまとめ、重要な変化があったときに通知します。

• メールとサイトで申請状況を追いたいとき
• 商談や配送の進捗を一か所で確認
• 重要な状況変化の通知を受けたいとき

大規模言語モデルの知識・推論・コード生成を共通の課題で評価するスキル。複数モデルの比較表や学習途中の成績推移を作り、評価結果と個別の回答を保存します。

• MMLU・GSM8Kでのモデル評価
• 複数モデルの比較表作成
• 学習途中のモデルの成績追跡

文章をAIが扱う小さな単位に分け、大量のテキスト処理や独自の語彙学習を支援するスキル。分割結果と元の文章の位置対応、入力の長さ調整も扱います。

• 大量の文章をモデル入力用に処理したいとき
• 文章ファイルから独自の語彙を学習
• 予測結果を元の文章の位置に対応づける

エミュレーター上のPokemonをAIに操作させ、移動や会話、バトルを進めるスキル。画面とメモリ内の状態を確認しながら遊び、ブラウザーでの観戦や保存・再開も扱います。

• AIのPokemonプレイを観戦したいとき
• 用意したROMでゲームを始めたいとき
• 保存した状態から再開したいとき

システムの構成やデータの流れを、クリックして詳しく読める立体的なHTMLマップに整理します。同じデータから説明文も生成し、設計上の判断や未解決の質問を管理します。

• システム構成とデータの流れの説明
• 新しい設計をチームで検討したいとき
• レビュー中の未解決の質問の管理

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.

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

Audit cloned or reimplemented websites for fidelity gaps, tracking scripts, source-brand and language residue, placeholders, and risky external dependencies. Use before handoff or deployment, or when asked to review a website clone for cleanup and readiness.

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

Implement ReasoningBank adaptive learning with AgentDB's 150x faster vector database. Includes trajectory tracking, verdict judgment, memory distillation, and pattern recognition. Use when building self-learning agents, optimizing decision-making, or implementing experience replay systems.

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

Automate customer engagement workflows including broadcast triggers, message analytics, segment management, and newsletter tracking through Customer.io via Composio

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

Automate time tracking workflows in Clockify -- create and manage time entries, workspaces, and users through natural language commands.

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

Auto-capture per-session token usage from the Claude Code session jsonl and persist to the cost-tracking namespace

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

Read accumulated cost-tracking spend + budget config, compute utilization, emit 50/75/90/100% alert ladder

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

Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost

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

Export cost-tracking telemetry in Prometheus textfile or webhook JSON formats — for external observability (Grafana, Datadog, custom dashboards)

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

Worker-Agent integration for intelligent task dispatch and performance tracking

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

Implement ReasoningBank adaptive learning with AgentDB's 150x faster vector database. Includes trajectory tracking, verdict judgment, memory distillation, and pattern recognition. Use when building self-learning agents, optimizing decision-making, or implementing experience replay systems.

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

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

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

Use when auditing URL structure or configuring search engine handling of filtered, sorted, or tracked URLs. Applies to e-commerce sites, filtered content directories, and any site appending tracking or session parameters.

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

Prepare restaurant food orders for delivery or pickup; use for cart, checkout and tracking. Placing the order requires authorization.

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

Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling. Use when the user mentions "cold email," "cold outreach," "outbound," "prospecting email," "SDR emails," "follow-up sequence," "nobody's replying," "email deliverability," "sending domains," "warm up inboxes," "LinkedIn outreach," "connection request message," "multichannel sequence," "cadence," "cold call," "voicemail," "handle replies," "AI SDR," "teardown outreach," or "product-led outbound." Send from secondary domains, verify lists first, turn off open tracking, and stop every channel when a prospect replies. Copy avoids AI tells like 'it's not X, it's Y' reveals. For building the list and account research, see prospecting. For lifecycle email, see emails. For call scripts and sales collateral, see sales-enablement.

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

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI, see ads. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo.

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

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

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

Writes an architecture decision record (ADR) for a decision the team has already reached: the context, the options weighed, the choice and its consequences. Use when the user says "record this decision", "write an ADR", "we decided X, capture it", or asks to document a technical choice already made. Not for making the decision itself or for tracking the work it leads to.

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

Uses Parallel CLI for web search, URL extraction, deep research, structured data enrichment, entity discovery, and recurring web monitoring. Best for requests that explicitly need current web evidence, academic-source discovery, repeated entity lookups, exhaustive reports, or ongoing change tracking.

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