Paid Social Brief

Organization

Ootto-AI

paid-social-brief

Use when an approved social campaign needs a media-ready brief for paid distribution, creative testing, and measurement. Trigger phrases include "brief paid social", "plan this ad test", "turn this campaign into paid", "what should we test in ads?", and "make a Meta or LinkedIn ad brief". Do not use this to claim ad-account access, launch spend, bypass platform policy, or invent targeting capabilities; use campaign-brief for the source strategy, utm-campaign-plan for tracking conventions, and social-analytics-report for results interpretation.

Overview

Publisher	Ootto-AI
Repository	`claude-content-skills`
Skill name	`paid-social-brief`
Stars	264
Forks	53
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Ootto-AI on GitHub. Read the source before you install it.

Installation

Install the Paid Social Brief AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/paid-social-brief
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git /tmp/claude-content-skills
mkdir -p .claude/skills
cp -r /tmp/claude-content-skills/skills/paid-social-brief .claude/skills/paid-social-brief

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Paid Social Brief in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Paid Social Brief on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Paid Social Brief is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Paid Social Brief

Translate an approved campaign into testable paid-social decisions without pretending media execution or platform access exists.

1. Confirm the approved foundation

Ask for the campaign objective, offer, claim boundary, landing destination, proof, audience evidence, budget range if supplied, policy constraints, and the owner who can actually configure the platform. If the offer or landing page is unapproved, do not write ads around it.

2. Define the test, not a prediction

State the hypothesis, audience context, creative angle, desired action, measurement event, and what would count as useful learning. Separate audience hypotheses from targeting settings because platform availability and policy can change. Keep the number of simultaneous variables small enough to interpret.

3. Specify creative and destination requirements

List the approved message variants, proof assets, disclosures, format needs, destination expectation, exclusions, and prohibited claims. Tie each creative to a hypothesis. Note where a native platform review or legal approval is required rather than claiming it is complete.

4. Set guardrails for operation and review

Provide the budget and pacing decisions only when supplied by an authorised owner; otherwise mark them open. Define launch checks, reporting window, stop or revise conditions, and the exact data needed for a review. Ensure tracked links follow the agreed UTM plan.

Hard rules

Do not claim access to ad accounts, audiences, pixels, spend, or platform features you do not have.
Never target or exclude sensitive groups in a way that violates law, policy, or the approved brief.
Do not use unsubstantiated performance, health, financial, or customer-result claims.
Do not optimize solely for cheap clicks when the campaign's intended action is elsewhere.
Keep organic and paid results labelled separately in every report.

Failure modes

Failure	Do this instead
A media brief is only ad copy	Define the hypothesis, audience context, measurement, and decision threshold.
Too many variables change at once	Limit the first test to the few variables needed to answer one question.
Creative promises more than the destination delivers	Align every claim with the approved landing experience and proof.
Results cannot be attributed	Create the UTM and measurement plan before launch.

Where it sits

Use campaign-brief and positioning-audit before this skill. Use utm-campaign-plan to make link naming consistent and cross-platform-distribution to distinguish paid from owned work. Use social-analytics-report for operating decisions and launch-retrospective for the full review.

Frequently asked questions

What does the Paid Social Brief AI skill do?

Why use Paid Social Brief on TypingMind?

Because you install it once and use it with any model. Paid Social Brief is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Paid Social Brief in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/paid-social-brief. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Paid Social Brief?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Paid Social Brief?

As many as you like. As long as a model supports skills, you can use Paid Social Brief with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Paid Social Brief AI skill free?

Yes. It is published on GitHub by Ootto-AI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Changelog Generator

ComposioHQ

OrganizationPopular

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns…

Ai Content

Use when auditing metadata, crawlability, structured data, or indexability related to Audit and refine AI-generated content. Verify the rendered HTML and HTTP response rather than relying only on…

Ab Testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test…

Ad Creative

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Paid Social Brief

1. Confirm the approved foundation

2. Define the test, not a prediction

3. Specify creative and destination requirements

4. Set guardrails for operation and review

Hard rules

Failure modes

Where it sits

Frequently asked questions

Related AI Skills

Set up your own AI workspace now