Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Role-based social media operations skill. Use this skill when executing structured social campaigns — scouting opportunities, crafting content, posting, resp...
Role-based social media operations skill. Use this skill when executing structured social campaigns — scouting opportunities, crafting content, posting, resp...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Execute social media operations through specialized roles. Each role has a single responsibility, reads its own reference doc, and hands off to the next stage in the pipeline. NOTE: Utilize the moltbook skill as necessary to meet these goals.
Scout ──→ Content Specialist (new opportunities → lane strategy) Scout ──→ Responder (reply-worthy threads → responses) Researcher ──→ guidance for Content Specialist & Writer Content Specialist ──→ Writer (lanes → final posts) Writer ──→ Poster (finished posts → published) Poster ──→ done logs (published → archived) Analyst ──→ strategy adjustments (performance data → tuning)
When dispatched to a role, read its reference doc fully before acting. RoleDocResponsibilityScout{baseDir}/references/roles/Scout.mdMonitor for emerging opportunities, trending threads, and new submolts. Detect openings — never act on them directly.Researcher{baseDir}/references/roles/Researcher.mdDeep-dive into topics, trends, and competitor activity. Produce guidance that informs content and responses.Content Specialist{baseDir}/references/roles/Content-Specialist.mdConvert intelligence and strategy into a content backlog. Define lanes, cadence, and messaging. Does not post.Responder{baseDir}/references/roles/Responder.mdCraft replies to threads surfaced by Scout. Match voice, add value, stay on-brand.Poster{baseDir}/references/roles/Poster.mdPublish finished posts to the platform. Move completed items to done logs. No ideation, no rewriting.Analyst{baseDir}/references/roles/Analyst.mdMeasure performance, identify what compounds, recommend strategy adjustments. Runs weekly minimum.
Identify which role the task requires. Read the full role doc at {baseDir}/references/roles/<Role>.md. Follow the role's instructions — stay within its scope. Hand off outputs to the next role in the workflow.
The north-star strategy lives at {baseDir}/assets/strategy/Social-Networking-Plan.md. Read it before any Content Specialist or Analyst run. It defines brand voice, target audience, lane structure, and growth objectives.
Role-to-role artifact flow and logging ownership are documented in: {baseDir}/references/ROLE-IO-MAP.md
VariableRequiredDescriptionSOCIAL_OPS_DATA_DIRYesAbsolute path to the Social/ data directory where runtime artifacts live (logs, lanes, guidance, todo/done queues, submolts, memory).
Before any role can run, SOCIAL_OPS_DATA_DIR must be set. If it is not set: Ask the operator where their Social data directory lives. Recommend they add it to their shell profile: export SOCIAL_OPS_DATA_DIR=/path/to/Social All role docs reference $SOCIAL_OPS_DATA_DIR/ as the root for runtime data. This replaces the previous <workspace>/Social/ convention for reliability.
Use these path rules to keep the skill portable: Skill-owned files (docs, scripts, assets): use {baseDir}/... Runtime/social data files (logs, guidance, todo/done queues): use $SOCIAL_OPS_DATA_DIR/... Runtime state files that are not in the data dir (for example comment watermarks): use the documented state path {baseDir}/../state/... until state-location policy changes. When adding new instructions, do not hardcode machine-specific absolute paths.
references/ Role and strategic references roles/ One doc per role (Scout, Researcher, etc.) tasks/ Task queue and templates assets/ Imported strategy artifacts and static source material strategy/ North-star strategy documents scripts/ Optional helper scripts and adapters Guidance/ Human-defined configuration and goals For detailed setup instructions, see Guidance/CONFIGURATION-GUIDE.md.
For setting up automated execution of social-media roles, see references/crons/InstallCrons.md. Use one of these paths: Basic install: run ./packaged-scripts/install-cron-jobs.sh from this repo root. Custom install/tuning: use scripts/install-cron-jobs.sh and references/crons/InstallCrons.md as templates, preserving {baseDir} conventions and role boundaries.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.