solar-delegation

v1.0.0

Delegate longer user-facing text generation to Upstage Solar Pro3 while keeping the primary model for planning and tool calls. Use when drafting explanations...

1· 266·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for upstage-deployment/solar-delegation.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "solar-delegation" (upstage-deployment/solar-delegation) from ClawHub.
Skill page: https://clawhub.ai/upstage-deployment/solar-delegation
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install solar-delegation

ClawHub CLI

Package manager switcher

npx clawhub@latest install solar-delegation
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's stated purpose (route long user-facing text to Upstage Solar Pro3 while keeping the primary model for planning/tool calls) matches the runtime instructions: estimating token length, checking session enablement, and spawning a Solar Pro3 session via sessions_spawn. Requesting an OpenRouter provider and configuring Solar in the gateway is consistent with that purpose.
Instruction Scope
SKILL.md stays on task: estimate output tokens, check session enablement, spawn Solar, and forward results. It also instructs keeping orchestration minimal and to include a 'no tool call' instruction in spawn requests. However, the instructions explicitly require modifying persistent memory/config (storing thresholds and per-session enablement) and gateway provider config (adding OpenRouter + API key). Those are broader actions than simple runtime behavior and should be surfaced in metadata/permissions.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so it does not write or execute new artifacts on disk by itself. That lowers installation risk; however, it directs manual edits to the gateway config and restarting the gateway, which are outside the skill bundle and require administrator action.
!
Credentials
The SKILL.md and setup guide require an OpenRouter API key (sk-or-...) and reference a primary model API key, but the registry metadata lists no required environment variables or primary credential. This mismatch is significant: the skill will not function without adding provider credentials to the gateway, and those credentials are not declared in the skill metadata for user review.
Persistence & Privilege
The skill does not request always:true or autonomous-only elevation, but its setup instructions call for persistent changes: adding a provider to gateway config, storing API keys in that config, and writing delegation policy to persistent memory. Those changes are legitimate for this feature but are system-wide and should be made knowingly and securely by an admin.
What to consider before installing
This skill appears to do what it says (delegate long-form generation to Upstage Solar via OpenRouter) but the package metadata fails to declare the API keys and config changes it needs. Before installing: (1) confirm you or an admin are willing to add an OpenRouter provider and store its API key in your gateway config (and understand where/how keys are stored), (2) verify the OpenRouter domain (https://openrouter.ai) is the intended endpoint, (3) ensure the skill will not be given broader credentials than needed (don’t reuse admin secrets unnecessarily), (4) ask the skill author/registry maintainer to update metadata to declare required env vars/credentials and document exactly what gateway config changes are required, and (5) consider limiting delegation to specific sessions or setting a conservative default threshold until you’ve tested behavior. If you cannot verify those points, treat the metadata omission as a red flag and do not enable this skill in production systems.

Like a lobster shell, security has layers — review code before you run it.

latestvk973bx35rg6ddjxy8rejr44rth828939
266downloads
1stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Solar Delegation

Route long user-facing text generation to Upstage Solar Pro3 (via OpenRouter), while the primary model handles planning/reasoning/tool use.

Model reference: https://openrouter.ai/upstage/solar-pro-3

Enabled Sessions

Check runtime/session settings to see where delegation is enabled.

Typical values:

  • main: direct/main session
  • slack: Slack messages
  • telegram: Telegram messages

If the current session is not enabled, skip delegation and respond directly.

Delegation Threshold

Use a minimum output-token threshold:

  • estimated output tokens >= threshold → delegate to Solar
  • estimated output tokens < threshold → respond directly

Common examples:

  • 0: delegate all responses
  • 200: delegate medium/long responses only

If no threshold is configured, use 200 as default.

How to Delegate

  1. Estimate output token length.
  2. Check whether current session is enabled.
  3. If enabled and estimate >= threshold, run sessions_spawn with Solar Pro3.

Example spawn task pattern:

<context + writing instruction>

중요: 도구(tool)를 사용하지 말고 텍스트만 바로 출력해줘. 파일 읽기/쓰기 등 도구 호출 금지.

Set model to:

  • openrouter/upstage/solar-pro-3

Main Session

Use sessions_spawn and wait for auto-announced result.

Messenger Sessions (Slack/Telegram/etc.)

Use sessions_spawn, then fetch the final assistant text and forward it through the appropriate message channel/thread.

If no final text arrives within a reasonable timeout, fall back to direct response.

Rules

  • Pass through Solar output as-is (no extra summary/footer/metadata).
  • Keep non-user-facing orchestration text minimal.
  • Do not output intermediate narration between tool calls.
  • Always include the “no tool call” instruction in spawn tasks.

Decision Guide

Delegate when above threshold and user expects substantial writing:

  • explanations
  • summaries
  • reports
  • long-form answers

Keep direct response for:

  • short operational confirmations
  • urgent low-latency replies
  • responses that must include immediate tool-call outputs

Configuration Changes

Users may request:

  • threshold changes (e.g., “set threshold to 300”)
  • session enable/disable (e.g., enable delegation in Slack)

Apply updates to persistent memory/config used by your environment.

First-Time Setup

If Solar Pro3 is not configured:

  1. Confirm user wants setup.
  2. Confirm OpenRouter API key is available.
  3. Add OpenRouter provider + Solar model via gateway config update.
  4. Restart/reload gateway as required.
  5. Confirm delegation is active and report current threshold.

For manual setup details, see references/setup-guide.md.

Comments

Loading comments...