source-command-system-efficiency-benchmark

Run system-efficiency-benchmark to measure Antigravity routing latency, route quality, performance, context footprint, command bloat, overengineering risk, command-surface size, feedback coverage, plugin readiness, hot/cold workflow tiers, and whether plugin packaging beats simpler router or metadata cleanup.

الانتقال إلى التثبيت

المستودع: Farrice/mes-knowledge-base
آخر نشاط في المصدر: ١١ يونيو ٢٠٢٦ في ٢٣:٢٨
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٠
التفرعات: ١

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/Farrice/mes-knowledge-base --skill source-command-system-efficiency-benchmark

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

generate

The /generate front door — in-house, pay-as-you-go creative generation (Higgsfield replacement). One command for image, video, and audio: routes each request to the right model recipe (skills/generate/models/*.json), defers to binding creative_router lanes (people → fal-people, style-family → fantastic-posters; Higgsfield fully retired 2026-08-06), quotes paid video before running, honors prompt-level budgets ("total budget $3"), runs comparison batches across models, logs every prompt beside its asset, and auto-refreshes the Asset Command Center (/assets-board). Use when the user says "generate", "make an image/video/voiceover", "create ads/assets/creative", names a model (recraft, kling, seedance, nano banana, gpt image), or asks for a multi-model comparison. Source: RoboNuggets 9C4TRbucmhQ, rebuilt on our fal-first stack.

2026-08-06

video-studio

The Edit Bay — in-house conversational video studio (VOX-style explainers, documentaries, shorts, LinkedIn video). Transcript-driven cutting, B-roll ladder, motion graphics as code, captions, music, publish-ready packages — all agent-operated, free-first. Use when Farrice says "edit this video/footage", "make an explainer/documentary/short", "cut this recording", "add B-roll/captions/music", "turn this essay/post into a video", or any video production ask. Front door for three modes: talking-head, VO-only, zero-camera (his recorded VO + assembled visuals — NO voice clone, NO TTS narration, his ruling 2026-08-06). Source: Brad Bonanno agentic edit pipeline (extractions/brad-bonanno-edit-bay/), rebuilt on the house stack: WhisperX local + edit_bay.py ffmpeg assembly + HyperFrames/Remotion graphics + /generate (fal) — NO Higgsfield (retired 2026-08-06).

2026-08-06

brad-bonanno-explainer-video-architecture

Architects technical explainer videos using Brad Bonanno's structural patterns — survives short attention spans, communicates complete systems (not just teasers), and functions as a channel-building artifact (one video pulls subscribers, not just views). Use when planning a long-form technical explainer (5-20 min) for YouTube, structuring an explanation of a complex system the user knows but can't teach yet, balancing depth vs accessibility for a technical audience, or building an evergreen video meant to compound subscriber growth over years rather than spike then die. Trigger proactively whenever the user says "explainer video", "technical explainer", "how do I explain X", "long-form YouTube", "evergreen video", or has a complex system that needs to land with a non-expert. For Instagram-format shareworthy content use brock-johnson-shareworthy-content; for short-form video patterns use a TikTok/Reels-specific skill.

2026-08-06

عرض الكل من هذا المستودع

name	source-command-system-efficiency-benchmark
description	Run system-efficiency-benchmark to measure Antigravity routing latency, route quality, performance, context footprint, command bloat, overengineering risk, command-surface size, feedback coverage, plugin readiness, hot/cold workflow tiers, and whether plugin packaging beats simpler router or metadata cleanup.