Ecommerce Content Marketing
LeoYeAI/openclaw-master-skills
E-commerce content marketing strategy planner. An agent skill from LeoYeAI/openclaw-master-skills.
When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand.
Install Content Opportunity Brief
$ npx skills add unifapi-agent/agents --skill content-opportunity-brief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install unifapi-agent/agents content-opportunity-brief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/content-strategy-agent/content-opportunity-brief .claude/skills/content-opportunity-brief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "content-opportunity-brief" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/content-strategy-agent/content-opportunity-brief into .claude/skills/content-opportunity-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-opportunity-brief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/unifapi-agent/agents/tree/main/skills/content-strategy-agent/content-opportunity-briefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add unifapi-agent/agents --skill content-opportunity-brief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install unifapi-agent/agents content-opportunity-brief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/content-strategy-agent/content-opportunity-brief .agents/skills/content-opportunity-brief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "content-opportunity-brief" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/content-strategy-agent/content-opportunity-brief into .agents/skills/content-opportunity-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-opportunity-brief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add unifapi-agent/agents --skill content-opportunity-brief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install unifapi-agent/agents content-opportunity-brief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/content-strategy-agent/content-opportunity-brief .cursor/skills/content-opportunity-brief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "content-opportunity-brief" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/content-strategy-agent/content-opportunity-brief into .cursor/skills/content-opportunity-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-opportunity-brief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/unifapi-agent/agents.git --path skills/content-strategy-agent/content-opportunity-brief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add unifapi-agent/agents --skill content-opportunity-brief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install unifapi-agent/agents content-opportunity-brief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/content-strategy-agent/content-opportunity-brief .gemini/skills/content-opportunity-brief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "content-opportunity-brief" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/content-strategy-agent/content-opportunity-brief into .gemini/skills/content-opportunity-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-opportunity-brief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install unifapi-agent/agents content-opportunity-briefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add unifapi-agent/agents --skill content-opportunity-brief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/content-strategy-agent/content-opportunity-brief .github/skills/content-opportunity-brief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "content-opportunity-brief" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/content-strategy-agent/content-opportunity-brief into .github/skills/content-opportunity-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-opportunity-brief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add unifapi-agent/agents --skill content-opportunity-brief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install unifapi-agent/agents content-opportunity-brief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/unifapi-agent/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/content-strategy-agent/content-opportunity-brief .opencode/skills/content-opportunity-brief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "content-opportunity-brief" agent skill from https://github.com/unifapi-agent/agents/tree/main/skills/content-strategy-agent/content-opportunity-brief into .opencode/skills/content-opportunity-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "content-opportunity-brief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
content-opportunity-brief- GitHub stars
- 589
- Token cost
- ~2.3k tokens
- SKILL.md length
- 976 words
- Files
- 2
- Skills in repo
- 47
- Repo updated
- First seen
- Licence
- MIT
At a glance
When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand.
- Works in 6 steps: Frame the scope. Take the topic (or… → Pull demand across all sources for the… → Cluster repeated questions into… → …
- Wants to turn a topic
- SKILL.md covers Use UnifAPI for live evidence, Workflow, Output: ranked topic map and Scoring rubric, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Content Opportunity Brief is an agent skill from unifapi-agent/agents. When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand. Also use on "content opportunity brief," "what should we write about," "content ideas backed by data," "find content gaps," "what questions is my audience asking," "ranked content topics," "where's the demand for content," or "prove this topic is worth writing." Each opportunity is tied to the public source that proves people are asking. For the broader plan (pillars, cadence), see content-strategy…
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).
It sits in Writing & Content, covering Content strategy and Market research. It works with Reddit, TikTok and YouTube. The repository describes itself as: Open-source marketing agents for Claude, ChatGPT, Codex, OpenClaw & Hermes. One plugin: SEO audits, GEO / AI-visibility, local SEO, KOL pricing, social listening & competitive… The licence is MIT.
When your agent uses it
- Wants to turn a topic
- Audience into a ranked list of content opportunities backed by real demand
Example prompts
- “content opportunity brief,”
- “what should we write about,”
- “content ideas backed by data,”
- “/content-opportunity-brief”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Frame the scope. Take the topic (or product) and the audience. If .agents/product-marketing.md (or .claude/product-marketing.md) exists…
- Pull demand across all sources for the topic and its natural variations: seo/keywords/ideas/related/overview, seo/serp (incl…
- Cluster repeated questions into candidate topics. Merge near-duplicate phrasings (e.g. "how much does X cost" and "X pricing") into one…
- Score each candidate with the rubric below and sort the table by total score.
- Write the brief for the top opportunities, each tied to the evidence that proves it, and note what you discarded and why.
- State sources and date range so the brief is reproducible.
What it can do on your machine
Read from SKILL.md and the folder at commit fb53247. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Content Opportunity Brief loads about 2.3k tokens when it runs. Until then it costs about 151 tokens; SKILL.md has 976 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from unifapi-agent/agents at commit fb53247, republished under its MIT licence (© unifapi-agent). 976 words, ~2,303 tokens.
Download SKILL.mdSave it as
.claude/skills/content-opportunity-brief/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- content-opportunity-brief
- description
- When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand. Also use on "content opportunity brief," "what should we write about," "content ideas backed by data," "find content gaps," "what questions is my audience asking," "ranked content topics," "where's the demand for content," or "prove this topic is worth writing." Each opportunity is tied to the public source that proves people are asking. For the broader plan (pillars, cadence), see content-strategy. For the underlying audience language, see customer-research.
- license
- MIT
- metadata.author
- UnifAPI
- metadata.version
- 1.0.0
Content Opportunity Brief
You are a content-opportunity analyst. Turn a topic or audience into a ranked list of content opportunities, each one backed by the public source that proves demand. Instead of brainstorming titles, you mine the questions and language people repeat across search, Reddit, YouTube, TikTok, X, and news — and only recommend topics where the evidence shows real, cross-source pull.
This is an enhanced skill: it reads live public data through UnifAPI.
Use UnifAPI for live evidence
The whole point is to find the same question surfacing across more than one source — that overlap is what separates a real opportunity from a hunch, and no single platform can prove it alone. Use the unifapi skill to connect (OAuth MCP), then call:
- Search demand —
seo/keywords/ideas+seo/keywords/related(the question and "also-ranks-for" variants people actually type for the topic and its modifiers — what/how/best/vs/pricing/alternatives),seo/keywords/overview(volume + CPC + competition to size each variant). - SERP shape (winnability) —
seo/serpto see which result types own the query and how strong/fresh the ranking pages are, so you can tell a beatable SERP from an entrenched one. - Reddit questions (no keyword search) — run
seo/serpforsite:reddit.com <topic>to find threads, thenreddit/posts/{id}/commentsto capture recurring questions and exact phrasing; note thread score + comment count as the demand signal. - Video / short-form demand —
youtube/search(which titles already pull views — use titles, descriptions, view/like counts andyoutube/videos/{id}/related; no comment endpoint, do not promise comment mining),tiktok/search+tiktok/search/hashtags(rising framings and hashtag pull, with view/like counts and recency). - Real-time chatter —
x/tweets/search/recent(live questions and complaints on the topic; note engagement),threads/search/recent+threads/search/top(text-first questions and the highest-engagement takes on the topic), andnews/search(recent coverage and angles, with publish dates) to catch timely hooks before search volume reflects them.
UnifAPI reads public data only — it never publishes or touches any account. Keep any billing metadata so the output can state record cost.
Workflow
- Frame the scope. Take the topic (or product) and the audience. If
.agents/product-marketing.md(or.claude/product-marketing.md) exists, read it first and only ask for what's missing. - Pull demand across all sources for the topic and its natural variations:
seo/keywords/ideas/related/overview,seo/serp(incl.site:reddit.com→reddit/posts/{id}/comments),youtube/search,tiktok/search/search/hashtags,x/tweets/search/recent,news/search. For each captured item, log: source, source URL, the verbatim question or phrasing, a raw demand number (volume / upvotes / views / engagement / recency), and the date. - Cluster repeated questions into candidate topics. Merge near-duplicate phrasings (e.g. "how much does X cost" and "X pricing") into one cluster and keep every source URL attached. A cluster that appears across two or more sources is a stronger candidate than one that appears once with high volume.
- Score each candidate with the rubric below and sort the table by total score.
- Write the brief for the top opportunities, each tied to the evidence that proves it, and note what you discarded and why.
- State sources and date range so the brief is reproducible.
Output: ranked topic map
A ranked table of content opportunities, sorted by score descending:
# Content Opportunity Brief — <topic> — <date>
Sources checked: SEO (keywords/ideas, related, overview, serp), Reddit, YouTube, TikTok, X, News. Date range: <range>.
| # | Topic / working title | Stage | Score (Rep×(Vol+Win)) | Proving source(s) + verbatim question | Why now / winnability | Suggested format & angle |
| --- | ----------------------- | ------------- | --------------------- | ------------------------------------------------------------------------------- | --------------------------------------- | ---------------------------------- |
| 1 | "X vs Y, which to pick" | consideration | 40 (4×(5+5)) | reddit.com/… "is X worth it vs Y?" 310↑; SEO "X vs Y" 2.4k/mo; x.com/… 90 likes | top result is a 2021 listicle, no owner | comparison guide, practitioner POV |Below the table, for each top opportunity, a short paragraph: the demand evidence (sources + verbatim questions with URLs), the gap it fills, and the recommended format and angle. Then a one-line Discarded list so the operator knows what was checked and rejected, and why. Lead with the highest-scoring opportunities.
Show full SKILL.md (431 more words)Show less
Scoring rubric
Score every candidate cluster on three axes, 1–5, then combine. Repetition is the multiplier because cross-source overlap is the strongest signal that demand is real.
| Axis | What it measures | 1 | 3 | 5 |
|---|---|---|---|---|
| Repetition | How many independent sources show the same question | 1 source | 2 sources | 3+ sources |
| Volume / intensity | Size of the demand on its strongest source | low volume / few upvotes | moderate, steady | high volume or a spiking thread/video |
| Winnability | How beatable the current results are | strong incumbents, fresh, comprehensive | mixed; some thin or dated pages | thin, dated, off-topic, or no clear owner |
Score = Repetition × (Volume + Winnability). Range 2–50. This rewards cross-source overlap and penalizes a single loud thread that nobody else echoes. Tie-break toward higher buyer-stage intent (decision > consideration > awareness) and toward fresher evidence (weight the last 6–12 months more).
Drop any candidate that scores Repetition = 1 AND Winnability ≤ 2 (a one-source question in a saturated SERP) — note it as discarded rather than ranking it.
Worked example (abbreviated)
Topic: "API observability" for a developer-tools brand. Cross-source pull found "how do I trace a request across microservices" in r/devops (340 upvotes, via
site:reddit.comSERP →reddit/posts/{id}/comments), as ayoutube/searchtitle with 88k views, and as an SEO query "distributed tracing tutorial" (1.9k/mo viaseo/keywords/overview). Repetition = 5 (3 sources), Volume = 4, Winnability = 4 (top SERP result is a vendor doc, no neutral tutorial). Score = 5 × (4 + 4) = 40 → rank #1. Format: hands-on tutorial with a runnable example. A single-source TikTok trend on "observability memes" scored 1 × (3 + 2) = 5 and was discarded.
Guardrails
- Read-only ("eyes, not hands"); public data only. It briefs from public demand; it does not write or publish — the ranked brief is the deliverable, the operator's own assistant drafts and ships.
- Confirmed vs. inferred: every opportunity must cite the source that proves demand. No source, no recommendation — and no fabricated volumes or quotes; carry the real numbers and URLs through.
- Demand signals (volume, views, upvotes, engagement) are public-data estimates — present ranges and dated snapshots, and treat AI/social signals as directional, not guaranteed traffic.
- Community sources skew toward power users and strong opinions; weight by overlap across sources rather than any single thread, exactly as the scoring rubric enforces.
- UnifAPI reads public data only; it cannot see your analytics, Search Console, or CMS. Combine those privately if you have them.
Related Skills
- content-strategy (Content Strategy Agent): roll a batch of these briefs into pillars, formats, and a cadence.
- customer-research (Content Strategy Agent): synthesize the audience language and pains behind these topics into reusable research.
- unifapi: the shared data skill — connect MCP and discover the SEO/Reddit/YouTube/TikTok/X/News operations this brief reads.
© unifapi-agent, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/content-strategy-agent/content-opportunity-brief of unifapi-agent/agents.
- SKILL.md
- README.md
Open the folder on GitHubat commit fb53247
Compare with similar skills
Content Opportunity Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Content Opportunity Brief this skillunifapi-agent/agents | 589 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Ecommerce Content MarketingLeoYeAI/openclaw-master-skills | 2.2k | 1 repos | ~5.3k | Automated safety check: Pass | MIT | |
| Comment MiningScrapeCreators/social-media-research-skills | 3.4k | — | ~1k | Automated safety check: Notes | MIT | |
| Trend DiscoveryScrapeCreators/social-media-research-skills | 3.4k | — | ~789 | Automated safety check: Notes | MIT | |
| Video Content Strategistalirezarezvani/claude-skills | 28k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Influencer Discoverytigerless-labs/influencer-discovery | 212 | — | ~2.5k | Automated safety check: Notes | None |
Similar skills
Comment Mining
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to mine comments and replies for audience reactions, customer language, questions, objections, complaints, product ideas, buying intent, sentiment, or…
Trend Discovery
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to discover trending social topics, hashtags, sounds, posts, reels, shorts, creators, or formats in a niche.
Video Content Strategist
alirezarezvani/claude-skills
A skill your agent uses when planning video content strategy, writing video scripts, optimizing YouTube channels, building short-form video pipelines (Reels, TikTok, Shorts), or repurposing…
Influencer Discovery
tigerless-labs/influencer-discovery
Find the bloggers/creators who can help promote your work, capture their contact info, and append them to the target sheet in Google Sheets.
Social Media Management
manojbajaj95/claude-gtm-plugin
Comprehensive social media management for all platforms (LinkedIn, Twitter/X, Instagram, TikTok, Facebook, Pinterest, YouTube).
More from unifapi-agent/agents
All 47 skills in this repoLLM Mention Tracking
unifapi-agent/agents
When the user wants to track how often their brand or domain gets mentioned across ChatGPT and AI search engines over a set of prompts, and how that share of voice compares to named competitors over…
Buying Signal Monitor
unifapi-agent/agents
When a seller or SDR wants to catch public buying intent on X/Twitter and LinkedIn — someone asking for a tool they sell, complaining about or switching off a competitor, or hiring for a role that…
Customer Research
unifapi-agent/agents
When the user wants to research customers from public communities, or synthesize customer language, pains, and objections.
Keyword Research
unifapi-agent/agents
When the user wants to research keywords, find keyword opportunities, run a keyword gap analysis, build topic clusters, or compare what competitors rank for.
Schema
unifapi-agent/agents
When the user wants to add, fix, or optimize schema markup and structured data on their site.
SEO Audit
unifapi-agent/agents
When the user wants to audit, review, or diagnose SEO issues on their site.
Related
Categories
Questions about Content Opportunity Brief
What does Content Opportunity Brief do?
When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand. Content Opportunity Brief is an agent skill from unifapi-agent/agents. When the user wants to turn a topic or audience into a ranked list of content opportunities backed by real demand.
When should I use Content Opportunity Brief?
Content Opportunity Brief fits situations like: wants to turn a topic; audience into a ranked list of content opportunities backed by real demand.
How do I install Content Opportunity Brief in Claude Code?
Run `npx skills add unifapi-agent/agents --skill content-opportunity-brief -a claude-code`. Or copy the skill folder (skills/content-strategy-agent/content-opportunity-brief in unifapi-agent/agents) into .claude/skills/content-opportunity-brief in your project. Claude Code loads it when a task matches its description.
How do I install Content Opportunity Brief in Codex?
Run `npx skills add unifapi-agent/agents --skill content-opportunity-brief -a codex`. Or copy the skill folder (skills/content-strategy-agent/content-opportunity-brief in unifapi-agent/agents) into .agents/skills/content-opportunity-brief in your project. Codex loads it when a task matches its description.
Can I use Content Opportunity Brief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add unifapi-agent/agents --skill content-opportunity-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/content-opportunity-brief, .gemini/skills/content-opportunity-brief, .github/skills/content-opportunity-brief and .opencode/skills/content-opportunity-brief in your project.
What does Content Opportunity Brief need to run?
SKILL.md names no scripts, command-line tools or credentials: Content Opportunity Brief is instructions for the agent only.
Does Content Opportunity Brief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Content Opportunity Brief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Content Opportunity Brief use?
Content Opportunity Brief is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Content Opportunity Brief use?
About 2.3k tokens (SKILL.md is roughly 9.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Content Opportunity Brief?
Skills that share tags, products or a category with Content Opportunity Brief: Ecommerce Content Marketing (LeoYeAI/openclaw-master-skills, 2.2k stars), Comment Mining (ScrapeCreators/social-media-research-skills, 3.4k stars), Trend Discovery (ScrapeCreators/social-media-research-skills, 3.4k stars) and Video Content Strategist (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Content Opportunity Brief?
unifapi-agent (a GitHub organization) maintains it in unifapi-agent/agents, which has 589 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on September 5, 2026.
Source: unifapi-agent/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.