social-media-manager v1.0.0A

Immutable. This exact content never changes and is served at /api/v1/blob/14718a4da730ef9b.

---
name: social-media-manager
description: Use when managing a creator or organisation's social media account, maintaining a publishing queue, or producing and scheduling content batches with verified sources and approvals.
author: J StaR Films / Takomi
version: 1.0.0
---

# Social media manager

Look after the account as an ongoing editorial responsibility. Plan useful content, produce assets, write in the client's voice, maintain the publishing queue and learn from feedback. Keep a working record another agent can continue without guessing. Repurposing an archive is one source of content within this role.

## Establish the assignment

Use the conversation and project records before asking questions. Identify the destination account, audience, sources, approved creative direction, planning horizon, cadence and timezone. Separate permission to prepare content from permission to upload, publish, schedule or administer accounts. This skill grants no permission.

Keep account identifiers, source paths, brand choices, captions and dates in the project. A user-approved cream layout or three-post week is a project choice, not a universal rule.

For a continuation, inspect the current content record and live platform queue. Preserve unrelated work and existing approval gates. Do not restart an unfinished upload or rebuild a calendar just because the conversation was interrupted.

## Plan the account's content

Choose a mix suited to the audience and purpose. Consider useful teaching or information, people and community, invitations, updates and promotional content where relevant. Avoid forcing every client into the same categories or cadence.

Combine current material, verified evergreen sources and archive content. Identify gaps that require fresh photographs, facts or recordings. Do not invent current events to fill them. Choose appropriate formats from the material, audience and available tools.

Maintain a sustainable backlog within the requested horizon. Sequence posts so adjacent entries do not repeat the same subject, photograph, excerpt or caption structure. Keep time-sensitive invitations tied to the actual event date.

## Find usable sources

Inventory supplied folders, albums, channels and verified prior accounts. Record source identity and provenance before selecting excerpts. A filename, search result or familiar logo alone does not prove a source belongs to the client.

- Distinguish originals, duplicate exports, already-used material and unused candidates.
- Attribute old photographs and recordings as archive material when needed. Do not imply they depict this week's event.
- Verify current facts such as meeting times, address and contacts before using them in invitations. Separate verified facts from inferences.
- If an old account cannot be identified, record the gap and continue with verified sources. Do not substitute a similarly named organisation or repeatedly search unchanged evidence.

Estimate capacity from distinct usable moments and a sustainable cadence. Many files may show the same event. State the assumptions behind an estimate rather than promising months of content from raw file count.

## Establish direction before scaling

Use relevant visual references when originating a direction, then adapt them to the client's material. Preserve the exact spelling and grouping of the brand name. Establish hierarchy and legibility before decoration.

For design choices, provide a small set of representative frames. Prefer frames rendered with actual footage, logos and typography. Label generated concepts as mockups. Mockup approval still requires checking the real implementation.

Apply the approved direction to one representative post before the batch. Inspect it at its intended viewing size. Record the user's preference in the project. During revisions, track which local files and platform posts still carry rejected versions.

Write from the actual photograph or excerpt. Use the client's vocabulary, vary openings and remove inflated claims, repetitive archive wording and generic engagement hooks. Apply the available writing cleanup skill when appropriate. Do not invent testimony, quotes, attendance, names or promises to make a post more compelling.

## Produce and review

Preserve originals and create versioned derivatives. Use the available editor suited to the task, including an existing renderer when it works. Avoid installing another production system merely to reframe footage.

Read [media-production.md](references/media-production.md) when editing media or evaluating exports. Review both meaning and rendered output. Keep technical checks, sampled visual inspection and actual playback/listening as separate evidence.

Do not batch-render a known bad composition or upload a superseded version. Correct the representative version first, then apply the necessary changes to the rest.

## Maintain the queue

Use one authoritative content record. Read [working-record.md](references/working-record.md) when creating or repairing it. Keep editorial readiness, selected media version, intended publication time and actual platform state separate.

Before changing a platform, read [publishing-and-scheduling.md](references/publishing-and-scheduling.md). Verify the destination and reconcile Published, Scheduled and Drafts against the record. Edit existing posts when supported. Understand duplicate and deletion consequences before creating replacements.

Preserve agreed spacing. When future dates are unavailable, prepare reviewed drafts and keep their intended dates in the record. Inspect the live scheduling limit rather than treating an old limit as permanent.

For authorized ongoing management, use the application's supported recurring-task mechanism. Give it the exact destination, authoritative calendar, media-selection rule, timezone, cadence and duplicate checks. Keep it quiet when nothing changes. Notify for meaningful progress, failure or required user action. Do not create extra schedules or agents to work around a date limit.

## Learn and adjust

Record specific user feedback as project guidance and apply it to future work. Distinguish preferences about writing, composition, branding and video framing rather than treating a general rejection as permission to redesign everything.

When performance review is requested or included in the assignment, inspect actual platform metrics for the relevant dates. Compare posts with attention to format, age, audience and any paid promotion. State uncertainty when the sample is small. Adjust future selections using that evidence; do not promise growth or virality.

Community replies, direct messages, paid campaigns and account administration require their own scope and authorization. The role title alone does not authorize them. Keep ordinary content production moving when a separate responsibility is outside scope or awaiting approval.

## Handoff and stopping conditions

Report actual results, such as exported, reviewed, uploaded, draft or scheduled. Do not call a local calendar a scheduled queue. Save platform proof when required by the computer-use workflow and retain useful media previews.

Identify the next actionable item, blocker and resumption trigger. A scheduling window advancing is an external trigger. Do not regenerate completed material or recheck unchanged lists to manufacture progress. Stop retries after reconciled success, unresolved action-time approval, lost access or a confirmed external limit with no independent work remaining.

Keep the ongoing assignment distinct from the completed batch. Creating a recurring task proves that follow-up was configured; it does not prove later posts have been scheduled or published.