Installable skills for Claude and other agents, published by Scout7.
Download a .skill file and open it in Claude (Save skill), or copy the
unzipped folder into ~/.claude/skills/. Agents can discover these skills
automatically via index.json
(Agent Skills Discovery RFC).
scout7-run-organic-loop
Runs a brand's organic growth loop on Scout7 — plans, produces, and publishes image posts, videos, blogs, and LinkedIn carousels, then reports the impact. One approval up front; the rest runs unattended — or in manual mode, each piece pauses for your OK before it is made.
What it can do
Audit the connected Scout7 workspace — topic coverage, calendar, growth state — and top up topics when coverage is thin.
Interrogate you — researching the brand and market on the web — to pin the loop's focus, your philosophy, and your target, then record it in the brand's canonical facts so the topics chosen and every angle drafted all come from it.
Draft a 1-day or 1-week content plan (topics, angles, platforms and timing) and refine it with you until you approve.
Lock every decision into a plan file on disk, so the plan — not a human — answers every question the run hits later.
End planning with your choice of run mode: fully autonomous, or manual — where each blog outline, post concept, and video script comes back to you for approval before anything is generated, and the finished pieces return for a final OK before they're scheduled.
Generate each piece with Scout7, wait out the async renders, and end every run by showing you the finished content itself — copy, images, blog, video — then schedule or publish to your connected accounts exactly as approved; anything you mark draft-only stays a draft.
Register its own daily Executor and Reporter jobs with a durable scheduler, so creation and reporting fire without anyone watching.
Answer blog author-interview questions from the brand's recorded facts/ and stance/ files — it never invents the founder's voice.
Write an end-of-day impact-and-learnings report from live Scout7 metrics, closing the loop that feeds the next day's plan.
What it needs
A connected Scout7 workspace (MCP).
A brand knowledge folder with facts/canonical.md + stance/*.md — bootstrapped automatically from Scout7 brand context on first run.
A durable scheduler for the unattended stages (e.g. scheduled tasks in Claude/Cowork).
Onboards a new person and brand onto the engagement-engine: verified social logins, an interviewed config, a learned brand voice, and a standalone engine folder that starts paused — ready for any scheduled agent to run.
What it can do
Preflight the agent's built-in browser and every social login before anything else: you sign in yourself (it never touches credentials), and it verifies the on-screen handle matches the brand account — the check that prevents posting as the wrong person.
Interview you for brand, account, and platform config across 11 platforms, with sensible defaults for daily targets, ramp-up, quiet hours, and hard-stops.
Learn the voice from reality: reads your real posts and product site, drafts the persona/stance and canonical brand facts, and shows you both for correction before anything is generated.
Generate a fresh, brand-agnostic engine folder — config, stance, facts, controls, empty state — with every trace of the previous operator substituted out.
Verify the scaffold with a dry-run cycle plan and ledger check, then hand over a human go-live checklist.
Produce an engine any runner can drive — Cowork, cron + a browser agent, or a plain loop — via the generated docs/RUNNER.md contract.
What it needs
An agent runtime with a built-in, drivable browser (hard requirement for the engine it produces).
You at the keyboard during setup, to sign in to the social accounts it verifies.
The engine stays paused until you flip it on after a supervised first run.