Genviral
by @ugenesys
Complete genviral Partner API automation. Create and schedule posts (video + slideshow) across TikTok, Instagram, and any supported platform. Includes slides...
clawhub install genviralπ About This Skill
name: genviral description: Complete genviral Partner API automation. Create and schedule posts (video + slideshow) across TikTok, Instagram, and any supported platform. Includes slideshow generation, file uploads, template/pack management, analytics, and full content pipeline automation. homepage: https://github.com/fdarkaou/genviral-skill metadata: openclaw: emoji: "π¬" requires: bins: ["curl", "jq", "bash"]
genviral Partner API Skill
> TL;DR: Wraps genviral's Partner API into 50+ bash commands. Core flow: get-pack β analyze images (metadata + vision) β generate with pinned_images β render β visual review (hard gate) β create-post β log to workspace/performance/log.json. Studio AI: studio-models β studio-generate-image (sync) or studio-generate-video β studio-video-status --poll (async). Auth via GENVIRAL_API_KEY. Config in defaults.yaml. Instance data in workspace/.
What This Skill Does
trend-brief) for hashtags, sounds, creators, posting windows, and hook anglesHow It Works
1. Generate or upload media 2. Create a post targeting one or more accounts 3. Schedule or publish (for TikTok slideshows, optionally save as drafts so you can add trending audio before publishing β music selection requires human judgment for best results) 4. Track performance via analytics 5. Learn and optimize
All configuration in defaults.yaml. Secrets via environment variables. Everything posted shows up in the Genviral dashboard.
First-Time Setup
If fresh install, read docs/setup.md and walk the user through onboarding conversationally:
1. Set API key and verify it works
2. List accounts and pick which to post to
3. Discuss image strategy (existing packs, create new, generate per post, or mix)
4. Optionally set up product context and brand voice together
No hardcoded defaults. Ask the user what they prefer and adapt. Everything done through this skill shows up in the Genviral dashboard, so the user always has full visibility and control.
File Structure
genviral/
SKILL.md # This file (kernel + routing)
README.md # Human-facing overview
defaults.yaml # API config and defaults docs/
setup.md # Onboarding guide (conversational, 5 phases)
api/
accounts-files.md # accounts, upload, list-files
posts.md # create-post, update-post, retry, list, get, delete
slideshows.md # generate, render, review, update, regenerate, duplicate, list + text styles
packs.md # pack CRUD + smart image selection (MANDATORY reading for any pack workflow)
templates.md # template CRUD + create-from-slideshow
analytics.md # all analytics commands
studio.md # Studio AI: generate images/videos, list models, poll status
subscription.md # subscription status, credits, tier
pipeline.md # content pipeline, performance loop, CTA testing, platform tips
errors.md # error codes and troubleshooting
references/
analytics-loop.md # Full analytics feedback loop and weekly review process
competitor-research.md # How to research competitors
prompts/
slideshow.md # Prompt templates for slideshow generation
hooks.md # Prompt templates for hook brainstorming
workspace/ # All instance/customer data (override with GENVIRAL_WORKSPACE_DIR)
content/
scratchpad.md # Working content plan and drafts
calendar.json # Upcoming planned posts
context/
product.md # Product description, value props, target audience
brand-voice.md # Tone, style, do's and don'ts
niche-research.md # Platform research for the niche
hooks/
library.json # Hook instances (grows over time, tracks performance)
formulas.md # Hook formula patterns and psychology
performance/
log.json # CANONICAL post record (single source of truth)
hook-tracker.json # Hook and CTA tracking with metrics (the feedback loop)
insights.md # Agent learnings from performance data
weekly-review.md # Weekly review notes
competitor-insights.md # Competitor research findings
scripts/
genviral.sh # Main API wrapper (all commands)
update-skill.sh # Self-updater
Command Routing
Load only what you need for the current task:
| Task | Read |
|------|------|
| Account discovery, file upload | docs/api/accounts-files.md |
| Create, update, list, delete posts | docs/api/posts.md |
| Slideshow generation, rendering, editing, text styles | docs/api/slideshows.md |
| Pack management, image selection (ANY pack workflow) | docs/api/packs.md |
| Template creation and management | docs/api/templates.md |
| Analytics queries and target management | docs/api/analytics.md |
| Studio AI: generate images, videos, list models | docs/api/studio.md |
| Subscription: check credits, tier, renewal dates | docs/api/subscription.md |
| Research a specific niche quickly (trend + competitors + hooks) | docs/api/analytics.md, docs/references/competitor-research.md, docs/prompts/hooks.md |
| Full content pipeline, performance loop, CTA testing | docs/api/pipeline.md |
| Error codes, troubleshooting | docs/api/errors.md |
Niche Research Mode (When user asks to research a niche)
When asked things like "research this niche", "find what works in this niche", or "give me niche intelligence":
1. Run trend-brief first for the niche keyword (7d baseline, then 24h for freshness if needed).
2. Extract and report: top hashtags, top sounds, top creators, posting windows (UTC), recommended hook angles.
3. Run competitor deep-dive using docs/references/competitor-research.md (3-5 accounts minimum).
4. Produce a short actionable output with:
- 3 hook angles to test
- 2 CTA suggestions
- 2 best posting windows
- 5 hashtags to start with
- 1 "gap to exploit" insight
5. Save findings to workspace/performance/competitor-insights.md and use them in subsequent content prompts.
Non-Negotiable Rules
These apply regardless of what docs you've loaded:
1. ALWAYS use pinned_images when generating a slideshow with a pack. Never call generate with just --pack-id β the server will pick random images. Read docs/api/packs.md before any pack workflow.
2. ALWAYS visually review every rendered slide before posting. If any slide fails readability, fix it. This is a hard gate β not a suggestion.
3. ALWAYS log to workspace/performance/log.json immediately after posting. This is the canonical record.
4. ALWAYS add a hook-tracker entry after posting. No tracking = no learning.
5. Never use em-dashes in any generated content.
6. Respect workspace/ β all instance data lives here. Do not write state files to the skill root.
Script Usage
/path/to/genviral/scripts/genviral.sh [options]
Requires GENVIRAL_API_KEY as an environment variable (format: public_id.secret). Loads defaults from defaults.yaml. Set GENVIRAL_WORKSPACE_DIR to override the workspace path (defaults to workspace/ relative to the skill dir).
Auto-Updates
This skill includes a self-updater that keeps skill-owned files in sync with the latest version from fdarkaou/genviral-skill.
bash scripts/update-skill.sh # check + apply if updates available
bash scripts/update-skill.sh --dry-run # preview only, no changes
bash scripts/update-skill.sh --force # force re-apply even if already current
What gets updated (skill-owned): SKILL.md, scripts/, docs/ (all subdirs)
What never gets touched (user-owned): workspace/ β your data, context, hooks, and performance logs are always preserved.
Notes
post_mode: MEDIA_UPLOAD to save to drafts inbox for audio additionπ Tips & Best Practices
post_mode: MEDIA_UPLOAD to save to drafts inbox for audio addition