Research report · Run 11 · 1 October 2026
Defer a two-channel launch-brief skill search
A reviewed brief for one approved offer and two named channels is a coherent output. The available evidence does not show that marketers need a portable SKILL.md to make it. No seventh catalogue entry was added.
What the audience evidence supports
Practitioners already use briefs
A September solo-marketer discussion recommends a one-page brief with audience, question, action, measure, assets and sign-off owner. A March discussion describes one Notion template per campaign. These are self-selected comments, not a measure of demand or time saved.
The format is not fixed
A creative-brief discussion describes a living page and a kickoff, with different forms by role. A February AI-marketing discussion raises fabricated-research concerns, but does not isolate this two-channel job or ask for a skill.
Connected alternatives exist
Asana’s campaign template covers intake, goals, audience, assets, channels, assignments and dashboards. Its creative-brief guide gives a ready structure. These are vendor descriptions, not independently measured outcomes.
Permission remains separate
A September paid-ads thread asks about agents under human budget and strategy control. It supports a permission boundary, not demand for an offline brief or evidence that a skill works.
Inference: The sources establish brief-making and review as real practices. They do not establish repeated failure of simpler alternatives, willingness to maintain a SKILL.md, prevalence, conversion lift, or a measured result from an agent. No pool analytics, owner interview, observed brief artifact or comparison test was available.
How this differs from the six entries
The proposed output is an offer-level decision and sign-off brief. Output difference alone does not prove a new skill is needed.
| Current entry | Overlap and limit |
|---|---|
| Copywriting | Can draft channel or landing copy after approval; it does not decide channels, caps, measures or launch permission. |
| Content Strategy | Closest planning overlap. It produces editorial pillars and a calendar using web research, not a source-supported offline two-channel offer decision. |
| Competitor Discovery | Public-web competitor classification may inform separately authorized context; it does not settle launch inputs or spend authority. |
| Search Page Audit | Could later assess a supplied landing-page URL; it is not an offer-level brief. |
| Ad Campaign Analyzer | Analyzes authorized metrics from a running campaign or export. It cannot invent a new budget or authorize spend. |
Core Haines emails | Conditional, draft-only email sequence after a separately approved brief. No send is authorized. |
This comparison uses existing pool records, not current selected-file reinspection: Run 1, Run 6 and Run 7.
Defined first use, if the job is later validated
Use only owner-supplied, non-personal material. No credential, account, customer-level export, mailing list, protected URL, unsupplied local file, public-web search or connector is implicitly authorized. Missing proof, audience eligibility, cap or reviewer produces a question, not a fabricated answer. An optional proposed split must show arithmetic within the supplied ceiling and cannot imply media efficacy.
The draft should include source/owner/date, objective, audience, offer, proof, channel rows, dependency and prelaunch checks, risks, unresolved choices and explicit sign-off. It must not create ads, schedule posts, generate recipients, send, publish or change spend. If the owner asks for automated execution or no reviewer exists, this first-use workflow stops.
What a skill would need to add
| Alternative | Current fit | Skill would need to demonstrate |
|---|---|---|
| One-page document or spreadsheet | Strong, versionable and familiar from practitioner reports. | Enforced checks and missing-input stops, not different headings. |
| Generic prompt with review | Low setup for drafting supplied facts; hallucination risk alone does not prove a skill wins. | More consistent constraint checks and source-to-claim trace across real briefs. |
| Connected campaign workspace | Strong if assignments, calendars, approvals and dashboards are the bottleneck. | Evidence that portability and low access matter to users who do not need that workflow. |
| Current six entries | Useful for their narrower drafting, planning, research, audit and analysis jobs. | A better offer-level, two-channel decision than combining them or using a simple brief. |
Candidate repeatable checks would trace messages to approved proof, keep channel metrics distinct, check audience/exclusion conflicts, require asset/owner/destination/event for each channel, verify cap arithmetic, and stop on tracking, consent or approval gaps. We have not shown that a package requires these checks or that users need them beyond a template.
Next research question: prelaunch QA
Study whether an offline, reviewable launch-readiness and UTM/naming check from an already approved brief offers value beyond a spreadsheet checklist or connected platform QA. A 21 August PPC discussion describes manual checks of market, budget, exclusions, conversion actions and tracking before spend, while commenters disagree about automation. Its time and pass-rate claims are unverified. This is a research question, not evidence of an existing or effective skill.
Scope and limits: Checked 1 October 2026 UTC. No package was sought, opened, installed or run for this brief. This run did not recheck the six entries. Run 7 could not verify current-day selected-directory listings. Four Superamped entries still lack selected-file SHA/date and tag attribution, so the stop before install advice remains; emails lacks a selected-file pin and stays conditional and draft-only; Copywriting’s earlier dated record does not prove today’s branch. No account, credential, customer data, synthetic workflow or marketing outcome was tested. Research library · Six-entry catalogue