gooseworks 0.3.15 → 0.4.0

package/skills/gooseworks/SKILL.md

@@ -2,12 +2,10 @@
 name: gooseworks
 slug: gooseworks
 description: >
-  GooseWorks data toolkit. Search and scrape Twitter/X, Reddit, LinkedIn, websites, and the web.
-  Find people, emails, and company info. Enrich contacts and companies.
-  GTM tasks: lead generation, prospect research, ICP identification, competitor analysis, outbound list building.
-  LinkedIn scraping: extract post engagers, commenters, profile data, and job postings.
-  Reach for it when you need data at scale, sources behind auth, or a specific provider — not as
-  a replacement for your built-in web search/fetch on quick, one-off lookups.
+  GooseWorks growth coworker and specialist-skill router. Research brands, customers, competitors,
+  creators, markets, and prospects; analyze ads and performance; create ads, product photos,
+  graphics, and video; search and scrape public web and social data; find and enrich leads.
+  Use it as the single GooseWorks entry point for brand growth, B2B, sales, research, and GTM work.
 category: general
 version: 1.0.0
 author: GooseWorks
@@ -16,79 +14,137 @@ tags: [gooseworks, data, scraping, search, reddit, twitter, linkedin, email, peo
 
 # GooseWorks
 
-You have access to GooseWorks — a toolkit with 100+ data skills for scraping, research, lead generation, enrichment, and more. Reach for a GooseWorks skill when it's the right tool: data at scale, sources behind auth, or specific providers (Twitter/X, Reddit, LinkedIn, people/company enrichment).
+You have access to GooseWorks — an AI coworker with specialist skills for research, analysis, creative work, lead generation, enrichment, and public web/social data. Use the right specialist when the request needs brand context, a managed creative workflow, data at scale, a source behind authentication, or a specific provider.
 
 This skill is also the **parent router** for the GooseWorks family. Data/GTM work you handle here (see "How to Use"); specialized work you hand off to a dedicated `goose-*` skill.
 
 ## Route to the right skill FIRST
 
-Before anything else, check whether the request belongs to a specialized domain. If so, **switch to that skill** instead of the data flow below:
+First apply the **Common company onboarding** gate below. Preserve the user's original request while onboarding, then continue with it as soon as onboarding is complete. Then load the brand context (**"Load the brand context FIRST"**, immediately below). After that, check whether the request belongs to a specialized domain. If so, **switch to that skill** instead of the data flow below:
 
 | If the user wants… | Route to | How |
 | --- | --- | --- |
 | Remix/make an ad, research a brand for ads, OR analyze ad performance — Meta/Google ad campaigns, creative fatigue, CAC/lead quality, competitor ad intel, ad angles & hooks | **`goose-ads`** | Installed locally as an entry skill. Just use it. If unavailable, run `gooseworks install --claude`. |
 | Charts, infographics, slides, social graphics, branded visual designs from a style/format | **`goose-graphics`** | If installed locally, use it. Otherwise `gooseworks fetch goose-graphics` (or `gooseworks install --claude --with goose-graphics`). |
 | Make a **video** ad — remix a video ad template (e.g. iMessage chat-reveal), or "make the video for project <id>" | **`goose-video`** | Installed locally as an entry skill. Just use it. If unavailable, run `gooseworks install --claude`. |
+| Make **product photos** — studio, lifestyle, marketplace, social, or on-model product photography | **`goose-product-photos`** | Installed locally as an entry skill. Just use it. If unavailable, run `gooseworks install --claude`. |
+| Animate an approved static ad or product image | **`animate-image`** | Fetch with `gooseworks fetch animate-image` and follow its GooseWorks MCP workflow. |
 | Anything else — scraping, research, lead gen, enrichment, any data lookup | (stay here) | Follow "How to Use" below. |
 
 Examples — all of these route to `goose-ads`, not the data flow: "remix this ad with project id 123", "make an ad for my product", "research my brand", "why is my Meta campaign underperforming", "which creatives should I cut".
 
+## Load the brand context FIRST (mandatory — before you route, and before you ask anything)
+
+**Call `brand_get_context` before the first substantive step of ANY task**, and before you route to a specialist skill. It is a cheap, read-only call that returns the brand's canonical facts:
+
+| It returns | Use it for |
+| --- | --- |
+| **voice** — tone, style, banned phrasing | Any copy, script, caption, hook, or headline. Don't ask "what tone?" |
+| **products** — names, descriptions, pricing, links, imagery | Picking the product to feature. Don't ask "which product?" — offer the list. |
+| **audience** — segments, demographics, jobs-to-be-done | Targeting, angles, creator fit. Don't ask "who is this for?" |
+| **positioning** — category, value props, proof points, tagline | Angles, offers, competitive framing. Don't ask "what makes you different?" |
+| **research status** — whether the brand's research pass has completed | Whether the facts are trustworthy yet, or still being filled in. |
+
+Then:
+
+1. **Pass what it returned INTO the routed skill.** When you hand off to `goose-ads`, `goose-video`, `goose-product-photos`, `goose-graphics`, or a fetched Brand Growth recipe, carry the voice / products / audience / positioning with you. Do **not** make the routed skill re-derive them, and do **not** re-run brand research when the context is already there.
+2. **Never re-ask the user for something the brand context already answers.** If a routed skill's own prose asks a question the context answers, the context wins — answer it yourself and move on. Ask only for what is genuinely missing or ambiguous.
+3. **If research status is not complete**, say so in one line, use what you have, and continue. Only run brand research when the context comes back empty or the user asks for it.
+4. **If `brand_get_context` is unavailable** (no MCP connection), fall back to `get_brand_kit` for the selected brand and treat its fields the same way. If neither is available, tell the user the GooseWorks MCP connection is needed rather than guessing brand facts.
+5. **Treat it as read-only.** Writing brand facts back is the reconciliation flow in `goose-ads` (ask first, then `update_brand_kit`) — not something this router does.
+
+Never invent a brand fact. If it isn't in the brand context and the user hasn't said it, ask.
+
 ## Setup
 
 All commands below auto-load credentials from `~/.gooseworks/credentials.json`. If a command exits with "Not logged in", tell the user to run: `npx gooseworks login`. To log out: `npx gooseworks logout`.
 
-### CLI-free environments (cowork / headless)
+### Choose the available runtime — MCP first, then CLI
 
-If the `gooseworks` CLI binary isn't available (e.g. Anthropic cowork) but the
-`mcp__gooseworks__*` tools are connected, use the MCP equivalents instead of shelling out:
+Skills may describe a managed provider request as an environment-neutral operation with
+`provider`, `method`, `path`, and optional `query` or `body`. Execute the operation through
+the first available runtime:
+
+1. If the matching GooseWorks MCP tool is registered, use it. For ScrapeCreators, pass the
+   operation directly to `call_data_provider`. This is the preferred path in ChatGPT, Cowork,
+   and other terminal-free clients. Do not shell out and do not ask for a separate provider key.
+2. Otherwise, if a local terminal and the `gooseworks` CLI are available, translate the same
+   operation into `gooseworks call <provider> <path>` with its method, query, and body options.
+3. Otherwise, follow the provider dependency's direct-key path only when the user has supplied
+   their own key. If no runtime is available, explain what connection is missing; never pretend
+   the provider call ran.
+
+The same selection applies to catalog and account operations. When the CLI is unavailable but the
+`mcp__gooseworks__*` tools are connected, use these equivalents:
 - `gooseworks search <q>` → the **`search_skills`** MCP tool.
 - `gooseworks fetch <slug>` → the **`fetch_skill`** MCP tool (same content/scripts/files/deps).
 - `gooseworks credits` → the **`get_ad_credits`** MCP tool.
 
-Discovery and fetching a skill's instructions work fully CLI-free this way. Note: the paid data
-proxy (`gooseworks call <provider> <path>`) still requires the CLI for now — if a task needs it
-and no CLI is present, tell the user that step must run where the `gooseworks` CLI is installed.
+Discovery, skill fetching, and ScrapeCreators-backed Brand Growth workflows work fully CLI-free
+this way. Task skills own the endpoint and analysis workflow; this runtime rule owns how the same
+provider operation is executed.
 
 To check credit balance:
 ```bash
 gooseworks credits
 ```
 
-## User Context (onboarding)
+## Common company onboarding
+
+Onboarding happens inside the current agent and is the first-run gate for every GooseWorks task. It uses the exact same saved state and step order as the web onboarding. The user does not need to type **`/gooseworks onboard me`**; that explicit command only starts or resumes the same flow.
+
+Keep the user's original task pending. Call **`brand_onboarding { action: "status" }`** before routing or executing it, then:
+
+- follow only the returned `next_step`;
+- save each answer immediately with `brand_onboarding` so web, Claude, Codex, ChatGPT, and Cowork can resume one another;
+- continue the original request immediately when `onboarding_completed` is true.
+
+If `brand_onboarding` is unavailable, explain that the GooseWorks MCP connection must be enabled. Do not write a parallel local profile and do not run the retired role / discovery-source / ad-owner questionnaire.
 
-You have two MCP tools for the user's onboarding CONTEXT — who they are and what they want GooseWorks for. It's stored server-side (org-scoped), separate from the ads brand kit.
+When onboarding returns a review link, show that single link and ask the user to review the creatives and reply `done`. When they reply `done`, do not restart onboarding: continue the task they originally asked for. If there was no earlier task, ask: **“Let’s start your next campaign. What are you promoting, and what result do you want?”** Use the same preserved-task-or-campaign handoff if onboarding completes while the creatives are still being prepared or could not be generated.
 
-- `get_user_context` — read it. **At the START of a session, call this once** and use what you learn (company, role, the use-cases they picked, their goals, freeform notes) to tailor which skills/APIs you reach for. Best-effort: if the `mcp__gooseworks__*` tools aren't connected, skip silently and carry on.
-- `update_user_context` — save it (partial update; only the fields you pass are touched).
+### Shared flow
 
-### Running "onboard me" (or a first run with empty context)
+Use the host's native question controls. Ask one short group at a time and rely on the live tool schema for accepted values.
 
-If the user says "onboard me" — or `get_user_context` returns `onboarded: false` and they're starting fresh — run a short, friendly interview, then save the answers. Open with this framing:
+1. **Start** — If status returns `start`, ask for the company website or Apple App Store URL. Also offer the optional hero product URL and “Where do you do your work?” choices: Slack, WhatsApp, iMessage, Claude Code, Claude, Codex, and ChatGPT. Call `action: "start"`; server-side research begins immediately. If status returns `select_brand`, ask which company/client to use. Otherwise reuse the only brand automatically.
+2. **Your coworker** — Ask what they want to name their Growth Coworker. A text-only client may keep the default avatar; do not block on an image. Save with `action: "save_coworker"`.
+3. **Your company** — Use the returned `company_draft` as the starting point and ask the user to verify or edit: what they sell (`marketCategory`), where people buy (`appPlatforms`), primary customer, customer problem, promised outcome, and optional differentiator. Save with `action: "save_company"`.
+4. **Your taste** — In a terminal or CLI host, use the returned `taste_url`: open it when the host supports opening links and always show one clickable **Choose your taste in GooseWorks** link. Ask the user to heart or skip ads on that page, click **Continue** or **Skip this**, return to the agent, and reply `done`. Do not print, enumerate, or summarize `taste_deck` in the terminal. After `done`, call `brand_onboarding { action: "status" }` again and follow the refreshed `next_step`. In a chat host that renders images, show only the one image attached by the tool and save each Love/Skip decision with `action: "save_taste"`; send `complete: true` after three hearts or an explicit skip.
+5. **First campaign** — Ask **“What’s happening right now?”**: launch `launch`, promotion `promo`, seasonal moment `seasonal`, or nothing special `nothing`, plus an optional note. Call `action: "propose_campaign"`, show the returned editable card (name, objective, offer, audience, 2–3 angles, CTA, and product URL), and save edits with `action: "save_campaign"`. Send `accept: true` only after approval; acceptance can start the complimentary first creatives.
+6. **Where you are** — Ask monthly ad spend (`none`, `under_1k`, `1k_5k`, `5k_25k`, `25k_plus`), annual revenue (`under_1m`, `1m_10m`, `10m_100m`, `100m_plus`), the 90-day goal, current channels (an empty list is a valid “nothing yet”), and at least one channel they are willing to use. Channel values: `paid_social`, `search_ads`, `content`, `creators`, `seo`, `communities`, `referrals`, `partnerships`, `outbound`, `app_stores`, `other`. Save with `action: "save_progress"`.
+7. **Review** — Show the returned founder, researched, and inferred facts with their provenance. The user may correct positioning, audience, voice, value propositions, proof points, or competitors through `action: "review_research"`. Complete the review even when research is still running, failed, or sparse; never trap the user waiting for it.
+8. **Channels** — If `channel_connected` is already true, this is complete automatically. Otherwise ask whether they want to connect Slack, WhatsApp, or iMessage later, or skip for now. An explicit skip is valid; call `action: "complete_channels"`.
 
-> Gooseworks gives your AI agent access to skills and APIs for growth and marketing work. For example: making ad creatives, finding influencers, scraping social profiles and posts from X/LinkedIn, scraping ads from Meta/LinkedIn, scraping reddit, and finding leads to target and their emails — and much more. Visit skills.gooseworks.ai to see the full library of skills.
+Do not ask for role, discovery source, who makes creatives, who manages ads, or a separate “what do you want to do first?” menu. Those belonged to the retired CLI questionnaire. The task the user already asked for is their first task.
 
-Then ask (a few at a time is fine — don't interrogate):
-1. **What's your company's website?** → `company_website`
-2. **What's your role?** → `role`
-3. **What are you hoping to use Goose skills for?** (multi-select — pick any): generate ad creatives · research and run ads end-to-end · finding influencers · data scraping (social / ads / reddit) · finding leads & emails · something else → `use_cases` (array)
-4. **What high-priority growth / marketing tasks would you like help with right now?** The more context they share, the better you can help. → `goals`
+## Brand Growth discovery
 
-**Save** with `update_user_context { company_website, role, use_cases, goals, context_md }` — put any extra detail you learned into `context_md` as a short summary.
+Brand Growth is a collection inside the normal skill catalog, not a command or installable pack. Use these known routes when relevant, while preserving all existing B2B, sales, research, lead-generation, and data behavior:
 
-**Then recommend REAL next steps — grounded, not from memory. This is the WHOLE POINT of onboarding; do not skip it or wing a generic playbook:**
-1. **Route each answer to the RIGHT tool first — don't blindly search one catalog. Match their use-cases to domains (same routing as "Route to the right skill FIRST" above):**
-   - **Make / edit / analyze ADS** (generate ad creatives, research & run ads) → the **`goose-ads`** skill (brand research + template remix). Do NOT `gooseworks search` for these — ad creation is NOT in the data catalog.
-   - **VIDEO ads** → **`goose-video`**.  **Charts / slides / graphics** → **`goose-graphics`**.
-   - **GTM / DATA** (finding leads & emails, influencers, scraping social / ads / reddit, enrichment, competitor intel) → run `gooseworks search "<that task>"` (free) and recommend the REAL skill slugs it returns.
-   Recommend specific, real things BY NAME — never a from-memory playbook, never a skill you assume exists; if a GTM search returns nothing relevant, say so.
-2. **Ground it in THEIR business.** If they gave a company website, read it with your web tools to infer their actual product + ICP, so suggestions are about their company — not a template. (For ad work, prefer `goose-ads`'s own brand research over a raw read.)
-3. **Be honest about cost.** Data / lead / enrichment / ad-generation skills bill GooseWorks credits — say so, and estimate before running anything (`gooseworks credits` to check balance).
-4. **Offer to start ONE concrete play** built from the ROUTED skill (`goose-ads` for ads, a real searched skill for GTM) and ask for the one or two inputs it needs.
+| Job | Skill |
+| --- | --- |
+| Brand foundation | `brand-research` |
+| Competitor ads | `competitor-ad-intelligence` |
+| Customer language and angles | `comment-mining`, `ad-angle-miner` |
+| Competitor social content | `competitor-social-research` |
+| Audience definition | `audience-research` |
+| Creator discovery and evaluation | `influencer-prospecting`, `creator-profile-teardown` |
+| Trends and outlier posts | `trend-discovery`, `outlier-post-finder` |
+| Social listening and product demand | `social-listening-brief`, `product-demand-research` |
+| Long-form source material (calls, podcasts, videos) | `transcript-intelligence` |
+| Meta performance, policy, and landing-page match | `meta-ads-analyzer`, `meta-ad-policy-checker`, `ad-to-landing-page-auditor` |
+| Static ads | `goose-ads`, `remix-graphic-ad-from-reference` |
+| Product photos | `goose-product-photos`, `product-photoshoot` |
+| Written content and repurposing | `content-repurposing` |
+| Graphics and animation | `goose-graphics`, `animate-image` |
 
-A suggestion is only "grounded" if it came from routing to the right domain skill (`goose-ads` / `goose-video` / `goose-graphics`) or from `gooseworks search` (a real GTM skill) — plus, ideally, reading their site. Do that BEFORE you suggest; never present a from-memory capability list as if you'd checked.
+Fetch the named public skill before following it. You already called `brand_get_context` — hand the brand's voice, products, audience, and positioning to the fetched skill instead of letting it re-derive or re-ask them. Provider helpers such as `scrapecreators-api` and `transcript-intelligence` are dependencies, not user-facing results.
 
-### Update as needed
-Whenever the user reveals durable context mid-session (their company, role, what they're trying to accomplish), persist it with `update_user_context` so future sessions start smarter.
+For a multi-part request, repeat this routing check before each new job. Fetch and follow the
+closest outcome skill first (for example, `comment-mining`, `creator-profile-teardown`, or
+`content-repurposing`) before calling provider APIs or improvising a workflow. Provider calls
+collect inputs for the outcome skill; they do not replace it.
 
 ## How to Use
 
@@ -128,6 +184,7 @@ Follow the instructions in the skill's `content` field. **Save ALL files from bo
 > - **Credentials (only needed before running Python scripts, NOT before gooseworks commands):** replace the python one-liner exports with `eval $(gooseworks env)`. Skip entirely if you are only using `gooseworks call` — it loads credentials automatically.
 > - **Orthogonal run:** replace `curl ... /v1/proxy/orthogonal/run ... -d '{"api":"X","path":"/Y","body":{...}}'` with `gooseworks call X /Y --body='{...}'`
 > - **Direct proxy:** replace `curl ... /v1/proxy/<provider>/<path> ... -d '{...}'` with `gooseworks call <provider> <path> --body='{...}'`
+> - **ScrapeCreators:** call its first-party GooseWorks proxy directly with `gooseworks call scrapecreators <path> --query='{...}'`. Use ScrapeCreators' official OpenAPI for endpoint parameters; do not use Orthogonal as its endpoint catalog. GET is the default; add `--method POST --body='{...}'` only for an official POST operation.
 > - **Orthogonal search:** replace `curl ... /v1/proxy/orthogonal/search ... -d '{"prompt":"..."}'` with `gooseworks orthogonal find "..."`
 
 1. Save each script from `scripts` to `/tmp/gooseworks-scripts/<slug>/scripts/` — **NEVER save scripts into the user's project directory**
@@ -166,9 +223,10 @@ gooseworks call hunter /v2/email-finder --query='{"domain":"stripe.com","first_n
 - Output: JSON response data, followed by a `Cost: <N> credits` line when applicable
 - **Always tell the user the cost** after each call
 
-The same `gooseworks call` command also handles direct-proxy providers (apify, apollo, crustdata):
+The same `gooseworks call` command also handles direct-proxy providers (apify, apollo, crustdata, scrapecreators):
 ```bash
 gooseworks call apify acts/parseforge~reddit-posts-scraper/runs --body='{"subreddit":"ClaudeAI"}'
+gooseworks call scrapecreators /v2/instagram/post/comments --query='{"url":"https://www.instagram.com/p/POST_ID/"}'
 ```
 
 ### Workflow
@@ -199,7 +257,7 @@ The `gooseworks` CLI sends authenticated requests (Bearer `GOOSEWORKS_API_KEY`)
 | `$GOOSEWORKS_API_BASE/v1/proxy/orthogonal/search` | POST | `gooseworks orthogonal find` |
 | `$GOOSEWORKS_API_BASE/v1/proxy/orthogonal/details` | POST | `gooseworks orthogonal describe` |
 | `$GOOSEWORKS_API_BASE/v1/proxy/orthogonal/run` | POST | `gooseworks call` (orthogonal-routed providers) |
-| `$GOOSEWORKS_API_BASE/v1/proxy/{apify,apollo,crustdata}/*` | Various | `gooseworks call` (direct-proxy providers) |
+| `$GOOSEWORKS_API_BASE/v1/proxy/{apify,apollo,crustdata,scrapecreators}/*` | Various | `gooseworks call` (direct-proxy providers; ScrapeCreators uses its managed first-party key) |
 
 ## Security & Privacy
 
@@ -211,6 +269,7 @@ The `gooseworks` CLI sends authenticated requests (Bearer `GOOSEWORKS_API_KEY`)
 
 ## Rules
 
+0. **Call `brand_get_context` before anything else**, pass what it returns into whatever skill you route to, and never re-ask the user for a fact it already answers (see "Load the brand context FIRST").
 1. **Consider a GooseWorks skill when it fits the task** — scraping, research, lead gen, enrichment, especially at scale, behind auth, or from a specific source. For a quick lookup your built-in tools are fine; use your judgement and pick the best tool for the user.
 2. **Before paid operations**, tell the user the estimated credit cost
 3. **If a `gooseworks` command exits with "Not logged in"**: tell the user to run `npx gooseworks login`

package/skills/routes.json

@@ -0,0 +1,157 @@
+{
+  "$comment": "Generated by `npm run generate:skills` from gooseworks/src/skills/routes.ts — the single source for GooseWorks skill routing (GOOSE-3190). Do not hand-edit. Consumers: goose-skills/collections/brand-growth/routes.json and gooseworks-app/backend/src/app-mcp-server/lib/ads-skill.ts.",
+  "version": 1,
+  "domain_routes": [
+    {
+      "skill": "goose-ads",
+      "when": "Remix/make an ad, research a brand for ads, OR analyze ad performance — Meta/Google ad campaigns, creative fatigue, CAC/lead quality, competitor ad intel, ad angles & hooks",
+      "how": "Installed locally as an entry skill. Just use it. If unavailable, run `gooseworks install --claude`.",
+      "delivery": "entry"
+    },
+    {
+      "skill": "goose-graphics",
+      "when": "Charts, infographics, slides, social graphics, branded visual designs from a style/format",
+      "how": "If installed locally, use it. Otherwise `gooseworks fetch goose-graphics` (or `gooseworks install --claude --with goose-graphics`).",
+      "delivery": "fetch"
+    },
+    {
+      "skill": "goose-video",
+      "when": "Make a **video** ad — remix a video ad template (e.g. iMessage chat-reveal), or \"make the video for project <id>\"",
+      "how": "Installed locally as an entry skill. Just use it. If unavailable, run `gooseworks install --claude`.",
+      "delivery": "entry"
+    },
+    {
+      "skill": "goose-product-photos",
+      "when": "Make **product photos** — studio, lifestyle, marketplace, social, or on-model product photography",
+      "how": "Installed locally as an entry skill. Just use it. If unavailable, run `gooseworks install --claude`.",
+      "delivery": "entry"
+    },
+    {
+      "skill": "animate-image",
+      "when": "Animate an approved static ad or product image",
+      "how": "Fetch with `gooseworks fetch animate-image` and follow its GooseWorks MCP workflow.",
+      "delivery": "fetch"
+    }
+  ],
+  "brand_growth_routes": [
+    {
+      "job": "Brand foundation",
+      "skills": [
+        "brand-research"
+      ]
+    },
+    {
+      "job": "Competitor ads",
+      "skills": [
+        "competitor-ad-intelligence"
+      ]
+    },
+    {
+      "job": "Customer language and angles",
+      "skills": [
+        "comment-mining",
+        "ad-angle-miner"
+      ]
+    },
+    {
+      "job": "Competitor social content",
+      "skills": [
+        "competitor-social-research"
+      ]
+    },
+    {
+      "job": "Audience definition",
+      "skills": [
+        "audience-research"
+      ]
+    },
+    {
+      "job": "Creator discovery and evaluation",
+      "skills": [
+        "influencer-prospecting",
+        "creator-profile-teardown"
+      ]
+    },
+    {
+      "job": "Trends and outlier posts",
+      "skills": [
+        "trend-discovery",
+        "outlier-post-finder"
+      ]
+    },
+    {
+      "job": "Social listening and product demand",
+      "skills": [
+        "social-listening-brief",
+        "product-demand-research"
+      ]
+    },
+    {
+      "job": "Long-form source material (calls, podcasts, videos)",
+      "skills": [
+        "transcript-intelligence"
+      ]
+    },
+    {
+      "job": "Meta performance, policy, and landing-page match",
+      "skills": [
+        "meta-ads-analyzer",
+        "meta-ad-policy-checker",
+        "ad-to-landing-page-auditor"
+      ]
+    },
+    {
+      "job": "Static ads",
+      "skills": [
+        "goose-ads",
+        "remix-graphic-ad-from-reference"
+      ]
+    },
+    {
+      "job": "Product photos",
+      "skills": [
+        "goose-product-photos",
+        "product-photoshoot"
+      ]
+    },
+    {
+      "job": "Written content and repurposing",
+      "skills": [
+        "content-repurposing"
+      ]
+    },
+    {
+      "job": "Graphics and animation",
+      "skills": [
+        "goose-graphics",
+        "animate-image"
+      ]
+    }
+  ],
+  "skills": [
+    "ad-angle-miner",
+    "ad-to-landing-page-auditor",
+    "animate-image",
+    "audience-research",
+    "brand-research",
+    "comment-mining",
+    "competitor-ad-intelligence",
+    "competitor-social-research",
+    "content-repurposing",
+    "creator-profile-teardown",
+    "goose-ads",
+    "goose-graphics",
+    "goose-product-photos",
+    "goose-video",
+    "influencer-prospecting",
+    "meta-ad-policy-checker",
+    "meta-ads-analyzer",
+    "outlier-post-finder",
+    "product-demand-research",
+    "product-photoshoot",
+    "remix-graphic-ad-from-reference",
+    "social-listening-brief",
+    "transcript-intelligence",
+    "trend-discovery"
+  ]
+}