Menú
Publish articles and content across all platforms — GitHub Discussions, Dev.to, X/Twitter, Buffer, YouTube, and more. Use when posting, scheduling, or managing content distribution for SCBE/Aethermoore.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Build, run, screenshot, and drive the SCBE AI browser (python/scbe/ai_browser.py + browser_{controller,grid,map,camera,autodrive}.py). Use when asked to run/launch/drive/screenshot the AI browser, browse a site headlessly, observe a page as data, or autonomously fill+submit+navigate a website.
Audit, sort, route, and back up large Windows workspaces across local disks and cloud-sync folders without recursive mirror failures. Use when the user wants the filesystem cleaned up, cloud storage organized, backup targets chosen by free space and route quality, or hardware/storage bottlenecks identified before moving data.
Manages AI safety governance using 21D hyperbolic embeddings and phase tunnel gates. Invoke when analyzing agent drift, applying SCBE-AETHERMOORE protocols, packaging governance products for sale, or running the monetization pipeline.
Construct and evolve the 9-dimensional state vector xi = [c(t), tau(t), eta(t), q(t)] that drives SCBE-AETHERMOORE governance decisions. Use when building context vectors, evolving time/entropy/quantum dimensions, or preparing state for the governance gate.
Generate visual assets for the SCBE/Aethermoore project — manhwa panels, character sheets, website hero images, social media cards, product diagrams, and marketing banners. Use when creating any visual content for the project.
Encode and decode intent values as phase-modulated audio waveforms using FFT-based demodulation. Use when working with the audio intent layer, phase encoding/recovery, or the symphonic cipher carrier signal.
| name | scbe-article-posting |
| description | Publish articles and content across all platforms — GitHub Discussions, Dev.to, X/Twitter, Buffer, YouTube, and more. Use when posting, scheduling, or managing content distribution for SCBE/Aethermoore. |
Publish governed content across all distribution channels from the terminal.
One-liner commands for each platform:
# GitHub Discussions (primary — 40+ articles live)
python scripts/publish/publish_discussions.py --file content/articles/YOUR_ARTICLE.md
# X/Twitter (OAuth 2.0 PKCE)
python scripts/publish/post_to_x.py --text "Your tweet text here"
python scripts/publish/post_to_x.py --thread content/articles/x_thread_FILE.md
# Buffer (scheduled multi-platform)
python scripts/publish/post_to_buffer.py --file content/articles/YOUR_ARTICLE.md
# All platforms at once (governed pipeline)
python scripts/publish/post_all.py --file content/articles/YOUR_ARTICLE.md
# YouTube (video from article — TTS + slides)
python scripts/publish/article_to_video.py --input content/articles/YOUR_ARTICLE.md --output artifacts/youtube/
python scripts/publish/post_to_youtube.py --file artifacts/youtube/YOUR_VIDEO.mp4 --title "Title" --privacy unlisted
# HYDRA content pipeline (5-stage governed conveyor)
python -m hydra content scan # Scan for new content
python -m hydra content stage # Stage for review
python -m hydra content review # Run QA gates
python -m hydra content approve # Approve passing content
python -m hydra content publish # Publish approved content
python -m hydra content stats # View pipeline stats
Scan -> Stage -> Review (QA gate) -> Approve -> Publish
State persists at artifacts/content_pipeline/pipeline_state.json.
QA gate: scripts/publish/content_qa.py (checks length, citations, formatting, SEO).
Run through this checklist before publishing every article:
og:title, og:description, og:image tags are set (1200x630 image)summary_large_imagepython, typescript)poincare-cost-scaling)scripts/publish/content_qa.py to check)| Platform | Key SEO Factor |
|---|---|
| GitHub Discussions | Use Discussion category labels; first line is indexed as summary |
| Dev.to | Set canonical_url to your primary URL; use 3-4 tags max |
| X/Twitter | First tweet of thread carries all the weight; include image |
| YouTube | Title keyword in first 3 words; description first 2 lines matter |
| Medium | Subtitle field is the meta description; 5 tags max |
| Substack | Subject line is the SEO title; preview text is meta description |
| Location | Content Type |
|---|---|
content/articles/ | Markdown articles ready for publishing |
content/articles/x_thread_*.md | X/Twitter thread formatted posts |
docs/research/ | Research notes (convert to articles before publishing) |
artifacts/content_pipeline/ | Pipeline state and QA reports |
| File | Purpose |
|---|---|
scripts/publish/post_all.py | Multi-platform publisher |
scripts/publish/publish_discussions.py | GitHub Discussions publisher |
scripts/publish/post_to_x.py | X/Twitter OAuth 2.0 publisher |
scripts/publish/post_to_buffer.py | Buffer scheduled posting |
scripts/publish/content_qa.py | QA gate (38+ article checks) |
scripts/publish/enrich_from_arxiv.py | Auto-add arXiv citations to fix QA failures |
hydra/content_pipeline.py | 5-stage governed conveyor |
artifacts/content_pipeline/pipeline_state.json | Pipeline state |
content_qa.py before publishing.canonical_url to avoid duplicate content penalties.pipeline_state.json committed after each publish run for audit trail.