Menu

Individual skill

marketing-guide

0upvotes

How every GooseWorks marketing playbook runs: connecting, picking the brand, where files go, the shared claims, money, research and schedule rules, and the index of what each playbook saves and who reads it. Load at the start of any playbook run. Not a marketer ask: for "what should I do first?" use where-to-start.

skills/marketing/marketing-guide/SKILL.md

Read pinned source

Source commit df8298140d434a6363de0c265eb6af2e571d97a5

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,315
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# marketing-guide

Every playbook does the same setup and follows the same rules. They live here once.

**Other skills.** A playbook, its steps and these shared rules are separate skills that sit side by side. "The `<slug>` skill (`../<slug>/SKILL.md`)" names one: with files, read that path; in a chat app without files, fetch it from the GooseWorks catalog by its slug (`gooseworks:catalog_fetch`, type `skill`, slug `<slug>`; add `path` for a file inside it, such as `references/<file>.md`). The skills a playbook needs are listed as its dependencies and come with it.

## 1. Connect and pick the brand

1. **Connected?** If no `gooseworks:` tools are listed, call `gooseworks:tools_load` once for the group you need. Still none → a playbook with **local mode** says once "GooseWorks isn't connected, so I'll keep this brand's notes in this folder and you'll approve each change here." (no last clause if it changes nothing) and follows §5; any other says only "Connect GooseWorks first — I <do this job> through it." and stops. Never half-run.
2. **First GooseWorks call of the conversation:** `gooseworks:get_started` with the marketer's own words. Its answer settles setup, and the brand only when the marketer named it; the playbook's gates decide the rest.
3. **Which brand?** `gooseworks:brand_read` lists the brands. One brand → use it. Several and none named → ask which, by name, before any research; never default to one. Keep the brand's `coworker_agent_id`.
4. **Read the brain before asking anything.** Ask only what the brain and the public site cannot answer.
   - **Brain tools.** The Brand Brain tools are `brand_knowledge_browse`, `brand_knowledge_search`, `brand_knowledge_read` and `brand_knowledge_save`. Their presence means the brain path (claims excepted: the `claims-gate` skill decides). Never request `brand_read`'s `sources` section in a routine read: it can pass 100K characters.
   - **When `brand_knowledge_*` tools are listed** (the Brand Brain), start with `gooseworks:brand_knowledge_browse`: the rules, the never-list, the items **waiting for the marketer's yes**, and the chapters' "read when" hints. Open the chapters the task needs and its `required_reads` (`brand_knowledge_browse` `kind` or `gooseworks:brand_knowledge_read`); `gooseworks:brand_knowledge_search` for gaps.
Back to top