social-media-automation-orchestrator
Skill0 starsChanged 47 days agoMITView on GitHub
Operational guidelines and orchestration patterns for high-concurrency social media automation across Bun API Gateway, Go Task Scheduler, Python Growth Analytics, and Redis.
In this repository22 other files it gives its agents.
- async-python-patternsSkill
- bun-runtimeSkill
- contract-firstSkill
- distributed-tracingSkill
- docker-patternsSkill
- fastapi-patternsSkill
- golang-concurrencySkill
- golang-error-handlingSkill
- golang-grpcSkill
- golang-patternsSkill
- golang-performanceSkill
- golang-testingSkill
- grpc-microservices-guardSkill
- microservices-patternsSkill
- openapi-spec-generationSkill
- redis-patternsSkill
- tdd-workflowSkill
- verification-loopSkill
- x-apiSkill
- grpc-microservices-guardSkill
- tiktok-growth-automation-meshSkill
- social-media-automation-orchestratorSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Run AI trend analysis and sentiment scoring asynchronously using FastAPI + gRPC server.
- Distinctive: line 41
Use Bun's native HTTP server and Elysia schema validation.
- Very specific: line 49
Verify container mesh via docker compose up --build.
≈ “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 Automation Orchestrator
Overview
This skill guides development, operational workflows, and integration patterns for the social media automation platform. The platform coordinates high-throughput content scheduling, automated campaign optimization, AI analytics inference, and rate-limited social network interactions.
Architecture Alignment
In accordance with microservices_manifest.toon:
- North-South Boundary (Client -> API Gateway):
- Framework: Bun + Elysia (Port 8080)
- Protocol: REST HTTP/JSON (OpenAPI 3.1)
- Validates incoming campaign requests, authenticates callers, and handles rate limiting.
- East-West Boundary (Service -> Service Mesh):
- Protocol: Pure gRPC over HTTP/2 + Protobuf (HTTP/JSON strictly prohibited)
- Gateway -> Task Scheduler (
task-scheduler-service:50051) - Gateway -> Analytics Engine (
growth-analytics-engine:50052)
- Distributed Coordination & Locking:
- Engine: Redis 7 (
redis:6379) - Manages distributed locks (preventing duplicate post execution), priority queues, and token bucket counters.
- Engine: Redis 7 (
Key Operating Workflows
1. High-Concurrency Task Scheduling (Go)
- Worker pools in Go should maintain bounded concurrency (
WORKER_CONCURRENCY, default 50). - Leverage Redis distributed locks (
SET key val NX PX ttl) when dequeueing scheduled social media actions. - Implement exponential backoff with jitter on transient network/API rate-limit errors (HTTP 429).
- Gracefully drain worker routines on
SIGTERM.
2. Predictive Growth & Content Analytics (Python)
- Run AI trend analysis and sentiment scoring asynchronously using FastAPI + gRPC server.
- Cache computed embeddings and score vectors in Redis to avoid recomputation under high ingress.
- Support fallback heuristic inference if ML inference latency exceeds SLO (p99 < 150ms).
3. API Gateway Ingress (Bun / Elysia)
- Use Bun's native HTTP server and Elysia schema validation.
- Translate external REST requests into typed gRPC calls via protobuf stubs.
- Return structured problem-details errors (RFC 7807) to API clients.
4. Verification & Testing
- Unit test Go routines with table-driven tests (
go test -race ./...). - Validate Bun endpoints using
bun test. - Validate Python gRPC handlers using
pytestandpytest-asyncio. - Verify container mesh via
docker compose up --build.
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.

