Instagram Marketing
sergebulaev/instagram-skills
Plan, draft, audit, and publish content for Instagram. An agent skill from sergebulaev/instagram-skills.
Build a community management playbook for a brand's social media channels.
$ npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills community-management-playbook --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/community-management-playbook .claude/skills/community-management-playbook && 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-management-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/community-management-playbook into .claude/skills/community-management-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management-playbook", 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/mohitagw15856/pm-claude-skills/tree/main/skills/community-management-playbookType 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 mohitagw15856/pm-claude-skills --skill community-management-playbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills community-management-playbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/community-management-playbook .agents/skills/community-management-playbook && 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-management-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/community-management-playbook into .agents/skills/community-management-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management-playbook", 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 mohitagw15856/pm-claude-skills --skill community-management-playbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills community-management-playbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/community-management-playbook .cursor/skills/community-management-playbook && 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-management-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/community-management-playbook into .cursor/skills/community-management-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management-playbook", 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/mohitagw15856/pm-claude-skills.git --path skills/community-management-playbook--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 mohitagw15856/pm-claude-skills --skill community-management-playbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills community-management-playbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/community-management-playbook .gemini/skills/community-management-playbook && 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-management-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/community-management-playbook into .gemini/skills/community-management-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management-playbook", 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 mohitagw15856/pm-claude-skills community-management-playbookInstalls 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 mohitagw15856/pm-claude-skills --skill community-management-playbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/community-management-playbook .github/skills/community-management-playbook && 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-management-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/community-management-playbook into .github/skills/community-management-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management-playbook", 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 mohitagw15856/pm-claude-skills --skill community-management-playbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills community-management-playbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/community-management-playbook .opencode/skills/community-management-playbook && 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-management-playbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/community-management-playbook into .opencode/skills/community-management-playbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "community-management-playbook", 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.
community-management-playbookBuild a community management playbook for a brand's social media channels.
Community Management Playbook is an agent skill from mohitagw15856/pm-claude-skills. Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
Its SKILL.md is about 4k 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: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
9 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Community Management Playbook loads about 4k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 1,972 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.
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.
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 1,972 words, ~3,986 tokens.
.claude/skills/community-management-playbook/SKILL.md (or your agent's skills folder).This skill produces a complete community management playbook covering response frameworks, tone guidelines, comment moderation rules, DM handling, crisis and escalation paths, response templates, and community health metrics. Output gives a community manager or social media team everything they need to manage public interactions consistently, professionally, and at speed.
Ask the user for these if not provided:
Version: 1.0 Platforms covered: [List] Team: [Names or roles] Last updated: [Date]
[2–3 sentences on what's at stake: brand reputation, customer loyalty, algorithm signals, trust-building. Frame community management as a business function, not just social admin.]
Our community management goals:
Use this decision tree for every comment or message:
Is it spam, phishing, or dangerous content?
→ YES: Delete immediately. Report if platform requires. Log in moderation tracker.
→ NO: Continue ↓
Is it a hate comment, harassment, or offensive content?
→ YES: Hide or delete. Consider account block. Escalate if ongoing. See Section 6.
→ NO: Continue ↓
Is it a customer complaint or support question?
→ YES: Respond within SLA. Acknowledge, empathise, resolve or redirect. See Section 4.
→ NO: Continue ↓
Is it positive — praise, testimonial, or user win?
→ YES: Like + reply with warm acknowledgement. Flag for social proof content if suitable.
→ NO: Continue ↓
Is it a question about the brand, product, or content?
→ YES: Answer clearly and helpfully. Include a CTA if relevant.
→ NO: Continue ↓
Is it a general conversation starter or neutral engagement?
→ YES: Engage authentically — like, reply briefly, or ask a follow-up question.| Channel | Comment type | Target response time | Owner |
|---|---|---|---|
| [Instagram] | Customer complaint | [2 hours (business hours)] | [CM Lead] |
| [Instagram] | General comment / question | [Same day] | [CM team] |
| [Instagram] | DM | [4 hours (business hours)] | [CM Lead] |
| [LinkedIn] | Professional comment / question | [4 hours (business hours)] | [CM / Marketing] |
| [X / Twitter] | Public reply / mention | [2 hours (business hours)] | [CM Lead] |
| [X / Twitter] | DM | [4 hours (business hours)] | [CM team] |
| [Facebook] | Comment | [4 hours (business hours)] | [CM team] |
| [TikTok] | Comment on promoted post | [8 hours] | [CM team] |
| [YouTube] | Comment | [24 hours] | [CM team] |
Out-of-hours coverage:
These are starting-point templates — always personalise with the person's name and specific context.
Praise / testimonial:
"Thank you so much, [name]! 🙌 This genuinely made our day. So glad [product/service] is working for you. [Add specific personal note if possible]."
User-generated content / sharing their experience:
"Love seeing this, [name]! Thanks for sharing 🙌. [Relevant genuine comment on their specific post or experience]."
Review or recommendation:
"Thank you for taking the time to share this, [name] — really appreciate it. [Add genuine specific reaction]. If you ever want to [next step / share more / join community], we'd love to have you."
Feature question:
"Great question, [name]! [Answer clearly in 1–3 sentences]. If you'd like more detail, [link to docs / help centre / DM us]. Happy to help with anything else!"
Pricing / availability question:
"[Answer] — [link if relevant]. Feel free to DM us if you need anything specific. 😊"
"Is this available in [region/format]?" question:
"[Answer with current availability]. If that's changed, you'll always see it first at [link / newsletter sign-up / our channels]. 🙌"
Product issue — acknowledged, redirecting to support:
"Hi [name], really sorry to hear this — that's definitely not the experience we want for you. 😔 Could you DM us with [order number / account email / details]? We'll get this sorted as quickly as possible."
Shipping / fulfilment complaint:
"Hi [name], thank you for letting us know and I'm so sorry for this. We want to make it right. Please DM us with your order reference and we'll investigate right away."
General dissatisfaction:
"Hi [name], I'm sorry to hear you're not happy — your feedback genuinely matters to us. Could you DM us or email [support email] so we can understand what happened and fix it? We really do want to get this right."
Public complaint that needs urgent attention:
"Hi [name], I can see why that would be frustrating and I want to make sure we sort this out properly. I'm going to DM you now — please look out for a message from us."
Polite but persistent critic:
"Hi [name], thank you for the honest feedback — we do read and take this seriously. We can't always respond to every individual point publicly, but if you'd like to share more detail, [DM us / email us at X]. We're genuinely working on [relevant area] and appreciate you holding us accountable."
Misinformation or incorrect claim about the brand:
"Hi [name], just wanted to gently clarify — [correct the record factually in 1–2 sentences]. Happy to share more if useful! [Link to source / official page if relevant]."
Competitor attack or negative comparison:
[Do NOT engage publicly with competitive comparisons. Respond only if there's factual misinformation. Template: "Hi [name], happy to share what makes [brand] work for our customers — feel free to DM us if you'd like to know more."]
First DM response — complaint:
"Hi [name], thanks for reaching out. I'm [name] from the [brand] team. I've seen your [comment/message] and want to make sure we get this sorted for you properly. Could you share [details needed — order number, email, screenshots]? I'll personally make sure this is resolved."
First DM response — support question:
"Hi [name]! Thanks for getting in touch. Happy to help — [answer or next step]. If you need anything else, just reply here. 😊"
Issue resolved — closing DM:
"Glad we could sort that out, [name]! If you ever need anything else, we're here. Have a great [day/weekend]! 🙌"
Content that must be deleted immediately:
Content that should be hidden (not deleted) — review within 4 hours:
Content that should be left (even if negative) — respond and monitor:
Account-level actions:
| Action | When to use |
|---|---|
| Comment hide | First instance of borderline content |
| Comment delete | Clear rule violation |
| User block | Repeated harassment / spam after warning |
| Report to platform | Content that may breach platform T&Cs or laws |
"Never delete to silence" rule: Never delete a genuine complaint or criticism just because it's uncomfortable. Deleting legitimate negative feedback damages trust more than the original complaint.
Tier 1 — CM handles directly:
Tier 2 — Escalate to [Marketing Lead / Brand Manager] within 2 hours:
Tier 3 — Escalate to [CMO / Founder / CEO] immediately:
Out-of-hours escalation contacts:
| Situation | Tone | Example phrase | Avoid |
|---|---|---|---|
| Complimenting content | Warm, genuine, specific | "This genuinely made our day 🙌" | Generic "Thank you!" |
| Answering a product question | Helpful, clear, not jargony | "Great question — here's exactly how it works…" | "Per our FAQs…" |
| Resolving a complaint | Empathetic, responsible, action-oriented | "Really sorry to hear this — let's sort it out." | "This is not our fault" |
| Engaging with light content | Playful, natural, on-brand | [Match the energy of the post — don't be stiff] | Corporate speak |
| Handling criticism | Measured, honest, not defensive | "We hear you and we're working on it." | "As per our T&Cs…" |
| Addressing a crisis | Calm, clear, factual, empathetic | "We're aware of this and are treating it as an urgent priority." | Defensive or dismissive |
Emoji use: [Define brand's emoji policy — e.g. "Use emojis sparingly — 1 per response max, only on positive interactions. Never on complaints or sensitive topics."]
Track these weekly:
| Metric | What it measures | Target | Current |
|---|---|---|---|
| Average response time | Speed of community management | [≤ X hours] | [X hours] |
| Response rate | % of comments/DMs replied to | [≥ X%] | [X%] |
| Comment sentiment ratio | Positive : Neutral : Negative split | [≥ X% positive] | [X%] |
| Escalation rate | % of interactions escalated | [≤ X%] | [X%] |
| DM resolution time | Time to resolve a DM complaint | [≤ X hours] | [X hours] |
| Content reports / removals | Volume of content moderated | [Track trend] | [X/week] |
Weekly CM review (15 min):
| Platform | Key nuance | Best practice |
|---|---|---|
| Comments move fast on Reels; DMs high volume | Prioritise Reel comments; use saved replies for FAQ DMs | |
| Professional audience; public replies visible to networks | Keep responses professional; avoid humour on complaints | |
| X / Twitter | Real-time; pile-ons escalate fast | Monitor with keyword alerts; act on Tier 2 triggers quickly |
| TikTok | Comment culture is more casual; meme responses ok | Match platform tone but keep brand voice; don't try too hard |
| YouTube | Older comments resurface regularly | Monitor new comments on older videos; set up notifications |
| Groups + page comments; older audience | More formal tone; monitor group dynamics separately | |
| Discord | Real-time community; requires moderators | Designate community moderators; publish community rules prominently |
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/community-management-playbook of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Community Management Playbook 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 Management Playbook this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~4k | 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 |
sergebulaev/instagram-skills
Plan, draft, audit, and publish content for Instagram. An agent skill from sergebulaev/instagram-skills.
LeoYeAI/openclaw-marketing-skills
Connect GetXAPI to pull public X/Twitter marketing signals into OpenClaw workflows.
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…
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.
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.
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…
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Categories
Build a community management playbook for a brand's social media channels. Community Management Playbook is an agent skill from mohitagw15856/pm-claude-skills. Build a community management playbook for a brand's social media channels.
Community Management Playbook fits situations like: asked to create guidelines for managing comments; community interactions; define a moderation policy; build response frameworks for social media community managers.
Run `npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -a claude-code`. Or copy the skill folder (skills/community-management-playbook in mohitagw15856/pm-claude-skills) into .claude/skills/community-management-playbook in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -a codex`. Or copy the skill folder (skills/community-management-playbook in mohitagw15856/pm-claude-skills) into .agents/skills/community-management-playbook in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill community-management-playbook -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-management-playbook, .gemini/skills/community-management-playbook, .github/skills/community-management-playbook and .opencode/skills/community-management-playbook in your project.
SKILL.md names no scripts, command-line tools or credentials: Community Management Playbook is instructions for the agent only.
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.
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.
Community Management Playbook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Community Management Playbook: 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.
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.