CtrlK
BlogDocsLog inGet started
Tessl Logo

budget-pacing-monitor

Use when the user asks to "check pacing", "am I over/under-spending", "is this campaign on track to hit budget", or "why did spend spike/stall mid-flight"; returns a spend-vs-target-curve read, learning-phase status, an over/under-delivery call, and a reallocation trigger. Not for initial budget allocation — use budget-optimizer; not for choosing the bid strategy — use bid-strategy-planner; not for the RQS gate — use ad-account-auditor. 付费广告预算节奏监控/跑量过快过慢/在途配速

72

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a clear, validated workflow and concrete commands. Its main weakness is progressive disclosure: the skill advertises a reference/bundle tree that does not exist in its own directory, and its boundary-framing is repeated across several sections.

Suggestions

Either ship the referenced files (skill-contract.md, CONNECTORS.md, SECURITY.md, measurement-protocol.md, roas-benchmark.md, scripts/connectors/README.md) inside the skill's bundle, or drop the links and inline the essential bits so the body matches the actual bundle structure.

De-duplicate the niche-distinction framing: state once which sibling skill owns which lever, and stop re-explaining the same boundaries in the intro, Instructions closing line, Reference Materials, and Next Best Skill.

Tighten the Quick Start and intro paragraphs so the body stays lean; the repeated "this skill does X, not Y" caveats can be folded into a single one-line scope note.

DimensionReasoningScore

Conciseness

The body is dense but mostly every token earns its place; however the niche-distinction framing repeats across the intro, the closing line, and the Reference Materials/Next Best Skill sections, so it could be tightened. It sits between the 'mostly efficient' (2) and 'lean and efficient' (3) anchors.

2.5 / 3

Actionability

Provides copy-paste-ready commands (the ledger.py record/trend invocations), an explicit pace formula, a four-value verdict taxonomy, and labeled-figure rules — fully executable guidance rather than vague direction.

3 / 3

Workflow Clarity

Six numbered, sequenced steps with explicit validation checkpoints — fix the curve before reading spend, confirm learning-phase before acting, fire/hold gating on the band — giving clear feedback/guardrail logic for a risky reallocation operation.

3 / 3

Progressive Disclosure

Sections are well-organized with one-level-deep reference links, but every referenced file points outside the skill bundle (../../../…) and none are present in ./references, ./scripts, or ./assets, so the actual bundle structure is empty while the body implies a rich reference tree.

2 / 3

Total

10.5

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise yet complete: it states concrete outputs, quotes natural trigger phrases, and clearly distinguishes the skill from three adjacent siblings. It is among the strongest examples in the rubric.

DimensionReasoningScore

Specificity

Lists multiple concrete outputs — "a spend-vs-target-curve read, learning-phase status, an over/under-delivery call, and a reallocation trigger" — matching the rubric's top anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what it returns and when to use it via a "Use when…" clause, plus what it is not for — both what and when are clearly stated with explicit triggers.

3 / 3

Trigger Term Quality

Quotes natural phrases users would say ("check pacing", "am I over/under-spending", "is this campaign on track to hit budget", "why did spend spike/stall mid-flight"), giving good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Explicitly carves a clear niche and names three sibling skills it is not (budget-optimizer, bid-strategy-planner, ad-account-auditor), making it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 14 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.