Token导航 LogoToken导航

Agent Skill · 待分类

budget-tracker(预算跟踪器)

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

budget-tracker 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描已通过,按安装量在待分类类的 11,208 个 Skill 里排第 4,610。

总安装 710周安装 29GitHub Stars 66下载 227核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

budget-tracker 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合整理仓库状态与协作事项。适用于围绕代码变更、项目进度或团队协作进行信息归纳的场景。通过 npx skills add 命令从指定 GitHub 仓库安装并使用该技能。

安装前需确认权限范围、维护状态及是否涉及联网、命令执行或文件读写操作。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/budget-tracker

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

budget-tracker 怎么安装?

在终端执行 npx skills add https://github.com/indranilbanerjee/digital-marketing-pro --skill budget-tr…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

budget-tracker 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

budget-tracker 需要什么权限?

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

budget-tracker 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

budget-tracker 用的人多吗?

公开数据是累计安装 710 次,近一周安装 29 次,下载 227 次,GitHub 66 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

budget-tracker 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
budget-tracker

预算跟踪器 · 本页

71066调用外部服务未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

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

平台分布

Codex

37.7%
按下载量换算86

Claude

28.12%
按下载量换算64

Cursor

19.19%
按下载量换算44

Gemini CLI

10.11%
按下载量换算23

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

调用外部服务

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

安装前确认

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

继续浏览同类 Skills