Skip to content

mbfinotti/advertising-skills / skills/advertising-kickoff

advertising-kickoff

Verified

Before starting any paid advertising work, before each recurring advertising review, and whenever routing is unclear, route the task to the right skill of the advertising-skills collection - or say plainly that none fits - and bootstrap or resume the project's shared context artifact. Use at every advertising project start, on later sessions of the same project to re-route without re-interviewing, and whenever the user mentions a new ad campaign or paid media project, asks which advertising skill they need, or wants a periodic advertising check-in - even if they name no skill at all. Prefer this whenever several skills could apply, since the collection has three colliding clusters - the hirer-vs-candidate pair, the budget cluster, the creative cluster - and it returns a short-list plus an ordered skill chain rather than a single guess. Do NOT use when the task already maps cleanly to one skill, such as a pure account audit - that is mbfinotti/advertising-skills@ad-account-diagnostic.

FileKindSize
SKILL.mdskill md33.0 KB
evals/evals.jsonconfig45.0 KB
references/context-artifact.mdmarkdown5.2 KB
references/routines.mdmarkdown2.9 KB
references/skill-routing.mdmarkdown22.5 KB

references/routines.md

View on GitHub
# Routines - dry-run format, anchoring, cleanup

Applies only where the harness supports scheduled routines. Otherwise: one recurring calendar reminder ("Advertising check-in - re-run the advertising kickoff") is the whole fallback - do not simulate a scheduler.

## Dry-run format

Show every proposed routine in this shape and get explicit approval before creating anything:

```
Routine:    <name>
Runs:       <trigger  -  anchored, see below>
Does:       <one line  -  which skill it invokes, on what input>
Outputs to: <explicit channel  -  team chat, issue tracker, document, email>
First run:  <date> (dry run  -  produces the output, creates nothing recurring yet)
```

Create the recurring version only after the user approves the dry-run output. A routine approved on its description alone still surprises on its first real output.

## Trigger anchoring

Anchor to the media calendar, not arbitrary dates, whenever the routine's value depends on timing. Listed in the rung order of the skill's § 7 so the two never disagree - this section fixes each routine's timing, never its priority:

- Spend health check → monthly or quarterly, before the allocation decision it feeds - never after
- Pacing check → weekly, on the day the team reviews spend; tighten to daily during a flight's final week
- Kickoff re-invocation → monthly or quarterly, whichever matches the project's pace from the git log
- Search term mining → monthly, after the month-end budget reset
- Creative wear-out check → weekly or biweekly, aligned to the creative refresh cadence in `advertising-context.md`
- Seasonal-peak routines → computed from the flight dates in the artifact's constraints (e.g. peak-start minus 14 days), removed after the flight ends

Prefer an event trigger over a schedule when the harness offers one and it fits better. For example, run the pacing check when a fresh ad-account export lands, or the wear-out check when a new creative batch goes live, rather than on a clock that may fire against stale data.

## Output channels

Every routine names exactly one channel its result lands in. "Notify me" is not a channel.

Good channels:

- a named team-chat channel
- an issue in the project tracker
- a section appended to a standing document

If no channel can be named, the routine is not ready to exist.

## Cleanup

Before adding routines, list the existing ones and remove the obsolete:

1. List all scheduled routines the harness reports for this project.
2. Flag any anchored to an ended flight, a past seasonal peak, a paused channel, or a skill/process no longer in use.
3. Show the flagged list; delete only with approval.
4. Record surviving and new routines in `advertising-context.md` under in-flight work, so the next warm start knows what is already running.

Stale routines from a finished flight fire noise; noise trains the user to silence notifications, which buries the one routine that mattered.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall