Instagram Marketing
sergebulaev/instagram-skills
Plan, draft, audit, and publish content for Instagram. An agent skill from sergebulaev/instagram-skills.
A skill your agent uses when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic.
Install Community Engagement Plan
$ npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ootto-AI/claude-content-skills community-engagement-plan --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/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/community-engagement-plan .claude/skills/community-engagement-plan && 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 "community-engagement-plan" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/community-engagement-plan into .claude/skills/community-engagement-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-engagement-plan", 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/Ootto-AI/claude-content-skills/tree/main/skills/community-engagement-planType 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 Ootto-AI/claude-content-skills --skill community-engagement-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ootto-AI/claude-content-skills community-engagement-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/community-engagement-plan .agents/skills/community-engagement-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "community-engagement-plan" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/community-engagement-plan into .agents/skills/community-engagement-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-engagement-plan", 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 Ootto-AI/claude-content-skills --skill community-engagement-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ootto-AI/claude-content-skills community-engagement-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/community-engagement-plan .cursor/skills/community-engagement-plan && 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 "community-engagement-plan" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/community-engagement-plan into .cursor/skills/community-engagement-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-engagement-plan", 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/Ootto-AI/claude-content-skills.git --path skills/community-engagement-plan--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 Ootto-AI/claude-content-skills --skill community-engagement-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ootto-AI/claude-content-skills community-engagement-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/community-engagement-plan .gemini/skills/community-engagement-plan && 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 "community-engagement-plan" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/community-engagement-plan into .gemini/skills/community-engagement-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-engagement-plan", 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 Ootto-AI/claude-content-skills community-engagement-planInstalls 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 Ootto-AI/claude-content-skills --skill community-engagement-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/community-engagement-plan .github/skills/community-engagement-plan && 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 "community-engagement-plan" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/community-engagement-plan into .github/skills/community-engagement-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-engagement-plan", 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 Ootto-AI/claude-content-skills --skill community-engagement-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ootto-AI/claude-content-skills community-engagement-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ootto-AI/claude-content-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/community-engagement-plan .opencode/skills/community-engagement-plan && 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 "community-engagement-plan" agent skill from https://github.com/Ootto-AI/claude-content-skills/tree/main/skills/community-engagement-plan into .opencode/skills/community-engagement-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-engagement-plan", 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
community-engagement-plan- GitHub stars
- 130
- Token cost
- ~855 tokens
- SKILL.md length
- 374 words
- Files
- 1
- Skills in repo
- 52
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic.
- Works in 4 steps: Define the community and permission… → Identify contribution opportunities → Establish response boundaries and routing → …
- A team needs a deliberate
- SKILL.md covers 1. Define the community and…, 2. Identify contribution…, 3. Establish response… and 4. Run a light learning loop, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Community Engagement Plan is an agent skill from Ootto-AI/claude-content-skills. Use when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic. Trigger phrases include "plan community engagement", "how should we join this conversation?", "what should we reply to?", "make an engagement playbook", and "how do we support this community?". Do not use this to automate unsolicited replies, manipulate conversations, impersonate people, or create comment copy at scale; use comment-responder for a specific approved…
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO, covering Social media marketing. The repository describes itself as: Free, copy-paste Claude skills that run your content growth factory — turn ideas + your NotebookLM memory into scroll-stopping Instagram reels. By Ootto. The licence is MIT.
When your agent uses it
- A team needs a deliberate
- Human-led plan for participating in comments
- Audience conversations around an approved topic
- Phrases include plan community engagement
Example prompts
- “plan community engagement”
- “how should we join this conversation?”
- “what should we reply to?”
- “/community-engagement-plan”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5263be7. 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.
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
Community Engagement Plan loads about 855 tokens when it runs. Until then it costs about 149 tokens; SKILL.md has 374 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 Ootto-AI/claude-content-skills at commit 5263be7, republished under its MIT licence (© Ootto-AI). 374 words, ~855 tokens.
Download SKILL.mdSave it as
.claude/skills/community-engagement-plan/SKILL.md (or your agent's skills folder).- name
- community-engagement-plan
- description
- Use when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic. Trigger phrases include "plan community engagement", "how should we join this conversation?", "what should we reply to?", "make an engagement playbook", and "how do we support this community?". Do not use this to automate unsolicited replies, manipulate conversations, impersonate people, or create comment copy at scale; use comment-responder for a specific approved reply and social-listening to analyse recurring themes.
Community Engagement Plan
Set a useful participation standard: where the team can add value, what it can truthfully say, and when it should not speak.
1. Define the community and permission boundary
Ask which owned or external community is in scope, its rules, the team's legitimate role, the topic, and any moderator or brand constraints. Read supplied rules before proposing interaction. If the community does not welcome promotion or brand participation, do not design a workaround.
2. Identify contribution opportunities
Use real questions, recurring friction, useful resources, corrections, and support needs as evidence. Classify participation as answer, clarification, acknowledgement, escalation, or observation. Give priority to helping people complete a task, not inserting the brand into every thread.
3. Establish response boundaries and routing
Define approved facts, prohibited claims, tone, disclosure, escalation owners, response windows, and cases that require silence or human review. Route product bugs, safety concerns, account-specific issues, legal questions, and hostile interactions to the appropriate owner rather than improvising publicly.
4. Run a light learning loop
Set a small cadence to review unanswered questions, recurring themes, and useful contributions. Capture aggregate learning for social-listening. Measure quality through resolved questions, informed feedback, and community trust signals where available, not reply volume alone.
Show full SKILL.md (171 more words)Show less
Hard rules
- Never automate unsolicited replies, direct messages, follows, or engagement.
- Do not misrepresent an employee, customer, or independent community member.
- Follow each community's rules and moderator direction; leave when asked.
- Do not reveal private account, customer, or support information in public conversation.
- Avoid argumentative pile-ons, engagement bait, and opportunistic promotion during sensitive events.
Failure modes
| Failure | Do this instead |
|---|---|
| The plan is "reply to everything" | Define situations where the team can add real value and where it should observe. |
| A public reply attempts to solve a private account issue | Acknowledge the issue and route through the approved support path. |
| Replies become repetitive promotion | Lead with the user's question, resource, or correction rather than the product. |
| Community rules are discovered after posting | Review rules and obtain required permission before engaging. |
Where it sits
Use social-listening to identify recurring questions and comment-responder for a particular reply. Use campaign-brief only when a campaign has a legitimate community role. Feed patterns into audience-personas and positioning-audit; never treat a community plan as a mass-outreach mechanism.
© Ootto-AI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/community-engagement-plan of Ootto-AI/claude-content-skills.
Open the folder on GitHubat commit 5263be7
Compare with similar skills
Community Engagement Plan 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 |
|---|---|---|---|---|---|---|
| Community Engagement Plan this skillOotto-AI/claude-content-skills | 130 | — | ~855 | Automated safety check: Pass | MIT | |
| Instagram Marketingsergebulaev/instagram-skills | 347 | — | ~1.9k | Automated safety check: Notes | MIT | |
| Getxapi ConnectLeoYeAI/openclaw-marketing-skills | 1k | 1 repos | ~715 | Automated safety check: Pass | Custom licence | |
| Competitor Social ResearchScrapeCreators/social-media-research-skills | 3.4k | — | ~1.1k | Automated safety check: Notes | MIT | |
| Business Contact and Social Links Finderbrowser-act/skills | 6.1k | 1 repos | ~1.6k | Automated safety check: Pass | MIT | |
| LinkedIn Ads Managementivangfalco/ads-skills | 279 | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
Getxapi Connect
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
Competitor Social Research
ScrapeCreators/social-media-research-skills
A skill your agent uses when the user wants to research competitors' social media strategy, compare brands or creators, find what content is working in a niche, identify content gaps, or produce a…
Business Contact and Social Links Finder
browser-act/skills
Finds a company's official website and social profiles from its name, or collects social links from a website URL, using BrowserAct templates run by a Python script.
LinkedIn Ads Management
ivangfalco/ads-skills
Routes LinkedIn Ads work for B2B SaaS to the right playbook: campaign planning, performance analysis, account audits, creative, scaling and account-based campaigns.
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…
More from Ootto-AI/claude-content-skills
All 52 skills in this repoAgent Reach
Ootto-AI/claude-content-skills
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g.
Ab Hook Tester
Ootto-AI/claude-content-skills
Generates two genuinely distinct hook variants for the same reel so you can post-test which opening actually wins.
AI Brain
Ootto-AI/claude-content-skills
Give Claude a permanent, searchable long-term memory using an Obsidian vault as the store.
Caption And Hashtags
Ootto-AI/claude-content-skills
Write the caption, hashtag set, and first comment for a reel or post.
Collab Outreach
Ootto-AI/claude-content-skills
Drafts personalized pitches to creators and brands for collab reels, shoutouts and partnerships.
Comment Responder
Ootto-AI/claude-content-skills
Turn every comment into a lead on autopilot. An agent skill from Ootto-AI/claude-content-skills.
Related
Categories
Questions about Community Engagement Plan
What does Community Engagement Plan do?
A skill your agent uses when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic. Community Engagement Plan is an agent skill from Ootto-AI/claude-content-skills. Use when a team needs a deliberate, human-led plan for participating in comments, communities, or audience conversations around an approved topic.
When should I use Community Engagement Plan?
Community Engagement Plan fits situations like: A team needs a deliberate; human-led plan for participating in comments; audience conversations around an approved topic; phrases include plan community engagement.
How do I install Community Engagement Plan in Claude Code?
Run `npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a claude-code`. Or copy the skill folder (skills/community-engagement-plan in Ootto-AI/claude-content-skills) into .claude/skills/community-engagement-plan in your project. Claude Code loads it when a task matches its description.
How do I install Community Engagement Plan in Codex?
Run `npx skills add Ootto-AI/claude-content-skills --skill community-engagement-plan -a codex`. Or copy the skill folder (skills/community-engagement-plan in Ootto-AI/claude-content-skills) into .agents/skills/community-engagement-plan in your project. Codex loads it when a task matches its description.
Can I use Community Engagement Plan 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 Ootto-AI/claude-content-skills --skill community-engagement-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/community-engagement-plan, .gemini/skills/community-engagement-plan, .github/skills/community-engagement-plan and .opencode/skills/community-engagement-plan in your project.
What does Community Engagement Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Community Engagement Plan is instructions for the agent only.
Does Community Engagement Plan 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 Community Engagement Plan 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 Community Engagement Plan use?
Community Engagement Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Community Engagement Plan use?
About 855 tokens (SKILL.md is roughly 3.4k 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 Community Engagement Plan?
Skills that share tags, products or a category with Community Engagement Plan: Instagram Marketing (sergebulaev/instagram-skills, 347 stars), Getxapi Connect (LeoYeAI/openclaw-marketing-skills, 1k stars), Competitor Social Research (ScrapeCreators/social-media-research-skills, 3.4k stars) and Business Contact and Social Links Finder (browser-act/skills, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Community Engagement Plan?
Ootto-AI (a GitHub organization) maintains it in Ootto-AI/claude-content-skills, which has 130 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 8, 2026.
Source: Ootto-AI/claude-content-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.