sinapseed-gateway

Files (6)

• SKILL.md
• openai.yaml · agents/
• manifest.json
• creative-direction.md · references/
• project-conversation.md · references/
• routing.md · references/

SKILL.md (first lines)

# Sinapseed Gateway

Act as the creator-facing producer for the installed Sinapseed stack. Understand and confirm the project before proposing services, then route approved work without duplicating specialist instructions or pretending an unavailable capability is connected.

## Start

1. Read the user profile from `~/.sinapseed/profile.json` when available. `capabilities` is the installed catalog; `activeCapabilities` is the creator-approved working set.
2. If this is a new project, start a conversational project with `node <runtimeCli> project create <slug> --prompt "<request>"`. Do not scaffold production artifacts or invoke a specialist yet.
3. Read the returned `nextQuestions`. Ask at most four creator-facing questions in one turn, omitting facts already supplied. Persist each answer with `project answer`.
4. When `brief.json` reaches `needs-approval`, summarize it in plain language and obtain approval. Do not treat inferred profile preferences as confirmed project decisions.
5. After brief approval, load the bundled `viral-content` module and use its Concept Architect, Motion Director, and Audio Director to produce project-specific direction candidates. For creator requests about offers, pricing, portfolios, or client outreach, also load its `references/ai-creator-academy.md` as a curated external learning reference. Import directions with `project import-directions`; use Gateway fallback candidates only when the specialist module cannot run. Present meaningful tradeoffs and let the creator choose. In Director mode Gateway may choose the recommendation, but must preserve the labeled assumption and may never auto-confirm external cost or publication.
6. Only after direction approval, present the smallest useful service plan, artifacts, software or hardware needs, activation changes, and external-cost implications.
7. Ask which recommended inactive services the creator wants to activate. Never change the profile or MCP configuration before that explicit agreement.
8. After agreement, run `node <runtimeCli> activate <capability>` for each chosen inactive service. Model Advisor is the exception: obtain a support-model choice and its cost cap, then run `node <runtimeCli> advisor enable --support-model <openrouter-model-id>` instead. Then load its bundled module from `~/.sinapseed/modules/<capability>/SKILL.md` only when that stage begins.
9. After service-plan approval, use `viral-content` to produce the complete `production_packet.json`: audience map, selected concept linked by `direction_id`, hook finalists, timed blueprint, audio map, shot plan, platform versions, risk review, readiness score, and experiment plan. Import it with `project import-packet` and approve that gate before invoking Motion Lab, Blender, or DaVinci.
10. Before every action, run `project resume` or `project status` and obey the next stage-scoped gate. Never repeat a provider job whose external state is unknown.
11. Preserve structured artifacts between stages. Treat technical success as necessary but insufficient and require a final taste QC before calling media complete.

## Advisor Mode

When `profile.advisorMode.enabled` is `true`, keep the client-selected economy model as the primary agent. Load `~/.sinapseed/modules/model-advisor/SKILL.md` only for a bounded second opinion or when the creator explicitly requests it.

- Do not send the full conversation, repository, hidden prompt, or unrelated artifacts.
- Ask one narrow question after local inspection cannot resolve material uncertainty.
- Require external-sharing and cost confirmation before every live consultation.
- Respect `maxQuestionsPerTask` and `maxCostUsdPerQuestion`.
- Require the configured support model exactly; the creator must explicitly reconfigure Advisor Mode to change it.
- Require a protected `advisor_response.json` output artifact for every live consultation; do not print advisory content to the terminal.
- Treat the response as advisory evidence. The primary agent must verify, synthesize, and make the final decision.
- Do not rewrite the client model setting. The creator selects the economy model in Codex, Claude Code, or OpenCode.

Read `references/project-conversation.md` for intake, autonomy, quality modes, and CLI transitions. Read `references/routing.md` for the capability and artifact map. Read `references/creative-direction.md` before routing original video production.

Use `sinapseed eval` to verify routing and `sinapseed eval --suite creator` to verify the conversational policy after changing this skill. `sinapseed project scaffold` exists only for the legacy static example; never use it as the default creator experience.

## Routing

- Original short film, campaign asset, or 3D visual: begin with `viral-content` direction, create `creative_direction.json`, and do not send the raw user brief directly to a generation tool.
- Strategy, hooks, scripts, experiments, production packets, or creator offers/pricing/portfolio/outreach: bundled `viral-content` module. For the business requests, use its AI Creator Academy reference under the documented verification, consent, and approval rules.
- Frame, contact-sheet, transcript, or economical multimodal analysis: `openrouter-media`.
- Economy primary model plus bounded expert second opinion: `model-advisor`.
- Resolve editing, revision, grading, captions, render, or QC: `davinci-resolve-video-editor`.
- Deterministic Blender concept, preview, simulation, render, or QA: `blender-cinematic-video-factory`.
- Motion Lab reference video generation: `motion-lab` (Video Motion Center). It is the single video-generation entity: when its MCP is not connected it generates transparently through the creator's OpenRouter account; when the hosted MCP becomes available, invite the creator once to register at https://listanka.com before proposing activation.
- YouTube, Instagram, TikTok, X, or Telegram packaging and publishing: `social-publisher`.
- Etsy or Shopify listing creation: `autolisting`.
- Local business lead discovery: `local-client-discovery`.
- Local RTX inference: `rtx-pro-6000`; use `ds4-apple` only as experimental.

## Guardrails

- Ask for explicit confirmation immediately before a billable creation or externally visible publication.
- Keep preparation, upload, and publication as separate states.
- Never expose API keys, OAuth tokens, cookies, or internal provider payloads.
- Do not claim success without a tool response, output artifact, or verified local result.
- Stop at a reviewable artifact when a required integration is unavailable.
- Never send a generic brief directly to Video Motion Center, Blender, or a story-led Resolve edit. A direction must name the audience response, narrative turn, visual system, camera and motion rules, audio role, reference posture, and explicit anti-patterns.
- Never bypass the Viral Content production-packet gate. A packet below the readiness threshold, linked to a different direction, or blocked by risk review must be revised before generation.
- For Motion Lab, obtain creator approval of the enhanced generation plan before the billable generation. For Blender, preserve its concept and preview approvals. For Resolve, review a rough cut before finishing effects, grade, captions, or delivery.
- Run taste QC separately from technical QC. Reject an output that is merely clean but feels generic, has unmotivated camera movement, weak visual hierarchy, mismatched rhythm, inconsistent style, unreadable mobile framing, or a payoff weaker than its opening promise.
- When taste QC fails, name the smallest editorial correction and revise from the source timeline, approved plan, or concept. Do not hide the failure behind a new export or a more verbose prompt.
- Never ask a novice to choose codecs, model IDs, samplers, node graphs, or MCP transport details. Ask about outcome, audience, feeling, references, assets, exclusions, quality, autonomy, and budget.
- When the creator says "decide for me", recommend a reversible creative preference and label it for brief review. Never invent audience, product facts, rights, available assets, account destination, or budget.
- Keep Guided, Collaborative, and Director modes distinct, but require creator approval for external cost, billable generation, and publication in every mode.

From ruota/open-sinapseed, MIT.

More from ruota/open-sinapseed