SocialSeal Multi-stage Production Agent Skill

Use this skill when the user requests a multi-stage content calendar, content plan or production programme combining research, videos…

Context cost
10.9k tokensestimated from the bundle, loaded when it triggers
Bundle
7 files · 43.8 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Use this skill when the user requests a multi-stage content calendar, content plan or production programme combining research, videos, carousels, and editor handoff. Coordinate only the requested creative deliverables.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

researchsocial media
Filed under

Sales & CRM

The skill itself

A skill is instructions the model reads, and here they are in full: the front matter loads with every session, and the body below it loads when the skill triggers. The other files in the bundle are listed further down.

SKILL.md3.0 kB
--- name: socialseal-orchestrator license: MIT metadata: socialseal: phase: orchestration tags: - socialseal - orchestration - routing - workflow - getting-started ---
18# SocialSeal Multi-stage Production
19
20Use this guidance for an explicitly requested production programme. Routine group reads, named-account metrics, supplied-video analysis, exports, and compound analytical requests work through the host's direct tools without this skill.
21
22Agree the requested delivery state: plan, brief, draft, externally edited rough cut, editor-ready, or post-ready export. Read references/creative-production-gates.md for the stages that apply to those deliverables. Reuse approved inputs and decisions.
23
24- Retrieve available brand facts and evidence. Use strategy-readiness only when missing foundations affect the creative work; missing strategy does not prevent reading existing evidence.
25- For demand research, preserve the requested markets, languages, platforms, and sample. Use opportunity or competitor analysis guidance only when that analysis is requested or needed for the production.
26- For content calendars and posting schedules, use socialseal-social-plan-builder for composition, cadence checks and revision consistency. Calendar-only requests do not require generating every brief.
27- For video/editor/UGC briefs, including Word/PDF delivery, use socialseal-creator-briefing to discover generation/read/update/export actions. Reuse an existing blueprint or supported scope; loading a skill does not execute generation.
28- For creative production, use the relevant concept, reference-video, blueprint, brief, asset, or carousel skill when its guidance improves the deliverable. Load only the current task's instructions.
29- Keep one opportunityKey across blueprint, brief, and handoff. SocialSeal does not assemble generated videos or export FCPXML; deliver source clips and briefs to the user's editor.
30- Apply demand, benchmark, asset, prototype, and final-QA gates only to the creative artifacts they protect. Present material creative choices, not routine execution questions.
31- New collection and external effects retain the operation's quote, approval, budget, and idempotency requirements. Reuse authorization already given for the same scope.
32- Cite source URLs and scoped evidence; distinguish observations, sampled statistics, and creative inference. Do not substitute unverified location imagery without the user's choice and a caveat.
33
34For access, actual schemas, artifact reading, and polling, read references/mcp-and-cli-usage.md. The host discovers and composes tools directly; a semantic resolver or prescribed workflow is never a prerequisite. Keep a compact artifact/decision manifest only for a large production task.
35
This is the whole of SKILL.md. Install the skill to get it and everything beside it.
In the file
SKILL.md388 words
Files7
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈110
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
10,840
on trigger
The instruction body and 6 supporting files, read only when the skill fires.
5.5%
of a 200k window
Ten skills this size would take about 55% of the window before you open a file.
050k100k150k200k context window

10.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md, shown in full above.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

7 files, 43.8 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md3.0 kB
  • references/creative-production-gates.md4.7 kB
  • references/evidence-and-confidence.md6.4 kB
  • references/mcp-and-cli-usage.md10.6 kB
  • references/onboarding-and-auth.md3.8 kB
  • references/production-pipeline.md10.2 kB
  • references/socialseal-data-contract.md5.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 7 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# SocialSeal Multi-stage Production · 10.9k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/socialseal-multi-stage-production/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/socialseal-multi-stage-production" ] && { [ ! -e .claude/skills/socialseal-multi-stage-production ] || { mv .claude/skills/socialseal-multi-stage-production "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/socialseal-multi-stage-production" .claude/skills/ && echo "Installed .claude/skills/socialseal-multi-stage-production"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add opensealai/socialseal-multi-stage-production

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/socialseal-multi-stage-production/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/socialseal-multi-stage-production/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/socialseal-multi-stage-production" ] && { [ ! -e ~/.claude/skills/socialseal-multi-stage-production ] || { mv ~/.claude/skills/socialseal-multi-stage-production "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/socialseal-multi-stage-production" ~/.claude/skills/ && echo "Installed ~/.claude/skills/socialseal-multi-stage-production" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/socialseal-multi-stage-production/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as socialseal-orchestrator in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, socialseal-multi-stage-production.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referenceopensealai/socialseal-multi-stage-production

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill