ワンクリックでManusで任意のスキルを実行

briefing

スター1

フォーク0

更新日2026年7月7日 12:40

Assemble a proactive briefing from KB context — a daily digest, meeting prep, or a project/entity brief — surfacing risks, decisions needed, open loops, changed state, and source links. Trigger on 'brief me on X', 'daily briefing', 'meeting prep', 'prep me for tomorrow's meeting', 'what should I know before'. This pushes a prepared briefing document; to pull the answer to one specific question use query; for a saved, timestamped analytical report with a source manifest use reports.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

weisberg

weisberg/agile_agentic_analytics

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Briefing

Contract

Briefings are concise, sourced, and action-oriented — never a dump of search results.
Upcoming meetings and open loops are connected to the relevant people, companies, and projects.
Unknowns and stale context are flagged with what the user should do next.
Read-only by default: do not write a briefing artifact unless the user asks to save it or the workflow routes to reports.

Intake And Modes

Treat $ARGUMENTS as the subject plus optional audience, date window, meeting/event, and source scope.
Quick mode: answer "what should I know" from a narrow entity/project slice.
Standard mode: produce a meeting or daily prep brief with risks, decisions, open loops, and sources.
Deep mode: compare multiple projects/entities over a wider date window and call out stale or missing context.
Use ask-user when the requested briefing mixes personal/team/org scopes without a clear audience.

Evidence Requirements

Query the KB first, then hydrate pages that drive claims; metadata alone is not enough.
Check tasks, recent timeline entries, related people/company pages, and freshness dates before stating priorities.

Workflow

Identify the briefing scope and time horizon (day, meeting, project, entity).
Retrieve related pages, timelines, tasks, and recent sources with query.
Summarize what matters, what changed, decisions needed, and risks.
Include follow-up questions and stale-context warnings.

Operating System Backing

This skill is backed by the shared deterministic KB operations harness. Use these commands for audits, CI fixtures, and repeatable agent runs:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb_ops.py" query
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb_ops.py" dashboard

Output Format

KB BRIEFING
Status: DONE, DONE_WITH_CONCERNS, BLOCKED, or NEEDS_CONTEXT.
Context, changes, risks, decisions, preparation, sources.
Artifact path: inline unless saved through reports as reports/<YYYYMMDD>-<slug>.md.

Anti-Patterns

Dumping search results instead of a briefing.
Leaving out what the user should do next.

このリポジトリの他の Skills

同じリポジトリ

cross-sell-analysis

weisberg/agile_agentic_analytics

Use when the user wants to measure the impact of a campaign that promotes a NEW product to existing customers — phrases like "cross-sell analysis", "cross-sell campaign results", "product attach rate", "account open rate", "new product adoption from campaign", "second product campaign", "add-a-product campaign", "checking-to-savings campaign", "credit card cross-sell", "did the campaign drive new account opens", "attach campaign", or any review of a campaign whose primary goal is to get current customers to take on a product they don't already have. Also trigger on "what was our conversion rate on the X campaign to existing customers" and "compare treated vs holdout for new account opens". Cross-sell differs from up-sell: the headline outcome is a binary CONVERSION (did they open the new product?), and value lift is the revenue or balance from the new product, not growth on existing accounts. Handles both holdout-controlled designs (statistical testing on conversion rate AND value) and uncontrolled designs (d

2026-07-071

up-sell-analysis

weisberg/agile_agentic_analytics

Use when the user wants to measure the impact of a marketing campaign on existing clients, account owners, or current customers — phrases like "up-sell analysis", "did the campaign move balances", "expansion campaign results", "wallet share lift", "AUM lift", "deposit growth from campaign", "existing customer campaign", "customer growth campaign", "upgrade campaign", "in-book campaign", or any review of a campaign targeted at people who are already customers (so there is no acquisition or conversion-rate question). Also trigger on "how much did balances/sales/revenue go up for treated clients" and "compare treated vs holdout for existing customers". Handles both holdout-controlled designs (statistical testing on the difference) and uncontrolled pre/post designs (descriptive lift only, clearly flagged as non-causal).

2026-07-071

vaultli

weisberg/agile_agentic_analytics

Use when initializing, maintaining, validating, searching, documenting, or assembling context from a file-based knowledge base with the bundled vaultli CLI. Trigger on knowledge vaults, KB setup, .kbroot, YAML frontmatter, sidecar markdown, INDEX.jsonl, documenting SQL/templates/configs/scripts, validating stale or broken KB state, searching vault metadata, hydrating source assets, assembling retrieval context, or federated lookup across multiple vault roots.

2026-07-071

vaultli

weisberg/agile_agentic_analytics

Manage a file-based knowledge vault with YAML frontmatter, sidecar markdown, and JSONL indexing. Use when initializing or maintaining a knowledge base, attaching metadata to markdown or non-markdown assets, rebuilding or validating INDEX.jsonl, or searching vault records by metadata. Trigger on: "knowledge base", "vault", "frontmatter", "sidecar", "INDEX.jsonl", "document this query/template/skill", "search the vault", or "set up KB docs".

2026-07-071

analysis-planning

weisberg/agile_agentic_analytics

Use this skill when the user wants to plan an analysis before running it, scope analytical work, design an investigation, write an analysis plan, decide what data or metrics are needed, or turn a vague metric/business question into an executable analyst workplan. Trigger on phrases like "analysis planning", "plan this analysis", "how should we analyze", "what data do we need", "design the analysis", "scope this analysis", "analysis plan", "investigation plan", "before we pull data", or "senior analyst, help me plan this".

2026-07-071

data-extraction

weisberg/agile_agentic_analytics

Use when the user wants to extract data, pull data from a source, load a CSV or JSON export into the workspace, connect a data source, refresh data, ingest raw platform exports, or normalize raw data for the marketing-analytics skills. Trigger on 'extract data', 'pull data from <platform>', 'load CSV/JSON into workspace', 'connect a data source', 'refresh data', 'normalize raw data', 'import my ad export', 'get the campaign data in', or 'set up the workspace'. This is the upstream skill every other marketing-analytics skill depends on: it lands source exports in workspace/raw/ and writes validated, normalized files to workspace/processed/. Run this first when a downstream skill reports a missing or malformed workspace input. When the user wants analysis, modeling, or reporting rather than getting data in, route to the matching analytics skill instead (see references/skill-index.md).

2026-07-071

name	briefing
version	0.2.0
description	Assemble a proactive briefing from KB context — a daily digest, meeting prep, or a project/entity brief — surfacing risks, decisions needed, open loops, changed state, and source links. Trigger on 'brief me on X', 'daily briefing', 'meeting prep', 'prep me for tomorrow's meeting', 'what should I know before'. This pushes a prepared briefing document; to pull the answer to one specific question use query; for a saved, timestamped analytical report with a source manifest use reports.
triggers	["brief me on","daily briefing","meeting prep","prep for tomorrows meeting"]
allowed-tools	["Read","Bash","Grep","Glob"]
disable-model-invocation	false
mutating	false

Briefing

Contract

Briefings are concise, sourced, and action-oriented — never a dump of search results.
Upcoming meetings and open loops are connected to the relevant people, companies, and projects.
Unknowns and stale context are flagged with what the user should do next.
Read-only by default: do not write a briefing artifact unless the user asks to save it or the workflow routes to reports.

Intake And Modes

Treat $ARGUMENTS as the subject plus optional audience, date window, meeting/event, and source scope.
Quick mode: answer "what should I know" from a narrow entity/project slice.
Standard mode: produce a meeting or daily prep brief with risks, decisions, open loops, and sources.
Deep mode: compare multiple projects/entities over a wider date window and call out stale or missing context.
Use ask-user when the requested briefing mixes personal/team/org scopes without a clear audience.

Evidence Requirements

Query the KB first, then hydrate pages that drive claims; metadata alone is not enough.
Check tasks, recent timeline entries, related people/company pages, and freshness dates before stating priorities.

Workflow

Identify the briefing scope and time horizon (day, meeting, project, entity).
Retrieve related pages, timelines, tasks, and recent sources with query.
Summarize what matters, what changed, decisions needed, and risks.
Include follow-up questions and stale-context warnings.

Operating System Backing

This skill is backed by the shared deterministic KB operations harness. Use these commands for audits, CI fixtures, and repeatable agent runs:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb_ops.py" query
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb_ops.py" dashboard

Output Format

KB BRIEFING
Status: DONE, DONE_WITH_CONCERNS, BLOCKED, or NEEDS_CONTEXT.
Context, changes, risks, decisions, preparation, sources.
Artifact path: inline unless saved through reports as reports/<YYYYMMDD>-<slug>.md.

Anti-Patterns

Dumping search results instead of a briefing.
Leaving out what the user should do next.