content publish

Other Community

Skill notes

Voice (MANDATORY — NON-NEGOTIABLE)

EVERY piece of content MUST go through the voice-master skill before publishing. This is a hard requirement, not a suggestion. The voice-master skill is TWO parts — both must be applied: Exemplar matching (tone, vocabulary, rhythm from real user writing) Anti-AI-slop pass (em dashes, hedge words, uniform structure, banned phrases)

Overview

Single skill that covers the full publish pipeline: topic → research → draft → approval → publish. Uses voice-master for drafting, browser MCP tools for publishing, and Telegram for approval. Medium is the only platform currently wired. The pattern extends to other platforms by swapping the publish step.

Prerequisites

Medium login active in Camoufox profile (~/.genesis/camoufox-profile/) Medium username configured in ~/.genesis/config/distribution.yaml Voice-master skill available (exemplars at ~/.claude/skills/voice-master/) Narrative reference card at ~/.genesis/config/genesis-narrative.md Stealth-browser skill (src/genesis/skills/stealth-browser/SKILL.md) —

Browser Rules

Always use Camoufox (default). Never pass stealth=False to browser_navigate. Chromium has SSL cert issues and no anti-detection. Never give up at Turnstile. The browser tool handles it automatically (3-phase: auto-resolve → VNC click → human alert). If you see Turnstile in the response, the tool is ALREADY handling it. Wait and retry.

Step 1 — Determine topic and platform

If the caller provides a topic, use it. If not, check these sources: Ego proposal (if dispatched via publish_content action) Recent recon findings (recon_findings MCP) Knowledge base for trending topics in the user's domain Platform is Medium unless specified otherwise.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@WingedGuardian · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview content-publish.preview
# Step 8 — Report result

- `memory_store` with tags: `["content", "published", "medium"]`
- Content: topic, URL, date, any engagement data later

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.