Token导航 LogoToken导航TokenDH.com
待分类external-servicegithub未标认证来源可访问许可证需确认审计通过

budget-tracker预算跟踪器

Agent Skill

budget-tracker 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

710

周安装

29

GitHub Stars

66

下载量

227
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:budget-tracker(预算跟踪器)
来源仓库:https://github.com/indranilbanerjee/digital-marketing-pro
仓库路径:skills/budget-tracker
安装命令:
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill budget-tracker
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill budget-tracker

简介

budget-tracker 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合整理仓库状态与协作事项。

  • 适用于围绕代码变更、项目进度或团队协作进行信息归纳的场景。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。
  • 安装前需确认权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

/dm:budget-tracker

Purpose

Track advertising budget in real-time across all connected ad platforms. Analyze spend pacing against targets, project end-of-period totals, flag overspend risks and underspend inefficiencies, calculate daily burn rates, and recommend budget reallocations to maximize ROI within the remaining budget window. Designed for media buyers and marketing managers who need a single view of where money is going and whether it is being spent effectively.

Input Required

The user must provide (or will be prompted for):

  • Budget period: This month, this quarter, or a custom date range (e.g., "Feb 1 - Mar 31"). Determines the pacing denominator and projection horizon
  • Ad platforms to include: All connected platforms or specific ones (e.g., "Google Ads and Meta only"). Defaults to all connected ad MCPs
  • Budget targets per platform (optional): Specific spend targets per platform for the period. If omitted, targets are pulled from profile.json budget_range and any saved platform allocations
  • Total budget (optional): Overall budget cap for the period. If omitted, pulled from profile.json budget_range
  • Alert thresholds (optional): Custom thresholds for overpace (default: >110% of expected pacing) and underspend (default: <70% of expected pacing) flags
  • Include efficiency metrics (optional): Whether to pull CPA, ROAS, and conversion data alongside spend. Defaults to yes

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/dm:brand-setup)?" — or proceed with defaults.
  2. Extract budget targets: Pull budget_range from profile.json and any saved per-platform allocations from previous budget-optimizer or media-plan runs. If user provided explicit targets, use those as overrides. Calculate the target daily spend rate for each platform (budget / days in period).
  3. Pull spend data from connected ad MCPs: Query each connected advertising platform (google-ads, meta-marketing, linkedin-marketing, tiktok-ads) for current-period spend — total spend to date, daily spend breakdown, campaign-level spend distribution, and cost metrics (CPC, CPM, CPA per campaign).
  4. Calculate pacing per platform: Execute scripts/ad-budget-pacer.py with spend data and budget targets to compute days elapsed/remaining, budget consumed vs expected pacing percentage, pacing ratio (actual / expected), daily burn rate (7-day average), and burn rate trend (accelerating/steady/decelerating).
  5. Project end-of-period spend: Extrapolate current daily burn rate to end of period for each platform — produce best-case (lowest recent daily spend), expected (7-day average), and worst-case (highest recent daily spend) projections.
  6. Compare to budget targets: For each platform, calculate the gap between projected end-of-period spend and the budget target — express as both dollar amount and percentage variance.
  7. Flag pacing issues: Generate alerts — overpace critical (>120%, immediate action: reduce bids, pause low-performers, set daily caps), overpace warning (110-120%, proactive adjustments this week), underspend warning (<70%, increase bids or expand targeting or reallocate), underspend info (70-85%, monitor).
  8. Pull efficiency metrics: For each platform, retrieve CPA, ROAS, conversion volume, and cost per conversion so reallocation decisions are performance-informed, not just pacing-based.
  9. Recommend reallocations: Execute scripts/budget-optimizer.py with current spend efficiency data to suggest specific dollar-amount shifts from underspending or low-efficiency platforms to high-performing ones with room to scale. Include rationale for each recommended move.
  10. Save budget snapshot: Persist the current pacing snapshot via scripts/performance-monitor.py --brand {slug} --action save-snapshot for historical tracking, trend analysis, and comparison in future budget-tracker runs.

Output

A structured budget dashboard containing:

  • Budget summary: Total budget for the period, total spent to date, total remaining, overall pacing percentage, days elapsed, days remaining, projected end-of-period total, and overall health status (on track, overpacing, underpacing)
  • Per-platform spend table: Platform name, budget target, actual spend to date, pacing percentage, daily burn rate (7-day avg), projected end-of-period spend, variance from target ($ and %), and status flag (green/yellow/red)
  • Pacing visualization data: Daily spend trajectory vs ideal linear pacing for each platform — highlights where spend is accelerating, decelerating, or tracking evenly across the period
  • Overspend/underspend alerts: Priority-ordered list of pacing issues with severity, platform, current pacing %, projected variance, and specific recommended corrective action
  • Reallocation recommendations: Specific dollar-amount shifts between platforms with rationale — e.g., "Move $2,000 from LinkedIn (62% pacing, $85 CPA) to Google Ads (98% pacing, $22 CPA, room to scale)"
  • Efficiency context: Per-platform CPA, ROAS, conversion volume, and cost trend alongside spend data so budget decisions account for performance quality, not just pacing
  • Daily burn rate breakdown: Current daily spend per platform vs target daily spend, with 7-day trend direction and acceleration/deceleration indicator
  • Projection scenarios: Best-case, expected, and worst-case end-of-period spend projections per platform and in aggregate, with confidence ranges
  • Executive summary: 2-3 sentence overview — total budget health, biggest risk or opportunity, and the single most important action to take now

Agents Used

  • performance-monitor-agent — Spend data aggregation from connected ad MCPs, pacing calculations, projection modeling, snapshot persistence, and historical spend trend analysis
  • media-buyer — Budget optimization strategy, reallocation recommendations, platform-specific spend tactics (bid strategies, daily caps, audience expansion), and auction dynamics expertise

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

37.7%
按下载量换算86

Claude

28.12%
按下载量换算64

Cursor

19.19%
按下载量换算44

Gemini CLI

10.11%
按下载量换算23

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

external-service

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills