ecom-social
Skill73 starsChanged 3 months agoCC0-1.0View on GitHub
Create and optimize e-commerce social media content, ads, and community management across platforms (Instagram, YouTube, TikTok, Pinterest, Reddit, WhatsApp, 小红书). Use for content creation, posting strategy, hashtags, captions, influencer collaboration, or cross-channel campaigns.
In this repository9 other files it gives its agents.
- opc-ecommerce-infrastructureSkill
- ecom-advertisingSkill
- ecom-applicabilitySkill
- ecom-complianceSkill
- ecom-customer-serviceSkill
- ecom-inventorySkill
- ecom-listingSkill
- ecom-pricingSkill
- ecom-researchSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Create and optimize e-commerce social media content and advertising across platforms.
- Very specific: line 16
Read references/constraints.md for platform-level rules.
- Very specific: line 20
Read references/boundaries.md to know when this skill should NOT be used (e.g.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Social Media Skill
When to Use
Create and optimize e-commerce social media content and advertising across platforms. Use for content creation (Reels, Shorts, Stories, Carousel, Pin, 种草笔记), posting strategy, hashtag research, ad copy, influencer collaboration, community management, or cross-channel repurposing.
Method
Step 1: Read Platform Constraints
Read references/constraints.md for platform-level rules. Social media has no numeric constraints in the ontology yet — platform-specific best practices live in each chapter's prompt templates in the playbook.
Step 2: Review Boundaries
Read references/boundaries.md to know when this skill should NOT be used (e.g. no visual story, no local-language capacity, chasing this-month conversion, mechanical reposting).
Step 3: Pick the Prompt
Pick the appropriate prompt from references/playbook.md for your platform and scenario:
- e1 — Instagram/Facebook: Reels, Stories, Carousel, Shopping, Meta Ads, hashtags, influencer collaboration
- e2 — YouTube: SEO keywords, titles, scripts, Shorts, thumbnails, affiliate descriptions
- e3 — 小红书: 种草笔记, SEO, 达人合作, 算法优化, 数据分析
- e4 — Pinterest: SEO, Pins, Idea Pins, Shopping, seasonal calendar, Shopping Ads
- e5 — WhatsApp: 客服 AI, chatbot flows, 复购营销, sales assistant
- e6 — Reddit: community participation, Ads, reputation monitoring, GEO
- e7 — Cross-channel: content adaptation, weekly repurposing, cross-platform analytics, attribution
Step 4: Execute and Verify
Execute the prompt with your data. Use the <自检>/<self_check>/<セルフチェック> self-check block in each prompt to verify output quality before delivering results.
References
- Constraints — Platform rules and limits
- Playbook — Prompt collection (54 prompts, e1–e7)
- Boundaries — When not to use
Templates
Copy-ready prompt templates (in assets/templates/):
- Instagram Reels Scripts
- YouTube Video Description
- 小红书种草笔记
- Cross-Channel Content Adaptation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

