Library · Team · LM Studio · support-triage
Support Triage — LM Studio
Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (LM Studio system prompt + local server notes.)
Id: lm-studio/support-triage · Slug: support-triage · Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
What is this
Prompt for LM Studio. Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (LM Studio system prompt + local server notes.)
How this runtime fits
This LM Studio recipe is a local AI agent / local AI workflow for the parent AI Team. It is a single-prompt (or system-prompt) recipe — do not force multi-agent system language here.
Parent AI Team: support-triage · What is an AI Team?
What it does
Classify an inbound message, propose a first reply hold, and flag escalation — human sends. (LM Studio system prompt + local server notes.)
Who for
Builders working on Support jobs who can run LM Studio themselves.
Need to run
- You will run this locally or on infra you control.
- No production credentials in prompts or committed files.
- LM Studio installed
- A GGUF/instruct model loaded
How to use
- Open LM Studio and load a local instruct model.
- Paste system-prompt.txt into the System Prompt field.
- Apply sampler hints (temperature ~0.3).
- Chat with the Example in payload; copy the structured reply.
- If using the local server, keep it bound to localhost.
Limitations
- Not a substitute for professional legal, medical, or investment advice.
- Outputs can be wrong; human review required before publish or spend.
- Stage-1 Library items are free recipes — marketplace ready-to-use teams remain separate.
- Local models may omit sections; re-prompt once if needed.
- No harvesting of personal data beyond what the operator pasted.
Test status
Status: Untested · Untested on this machine — recipe reviewed for safety (no secrets, no destructive commands, no auto-spend). Mark tested after you run it locally.
Files
system-prompt.txt— Paste into LM Studio system promptpreset.hints.json— Suggested sampler settings (manual)
Full prompt / config / code
Free. No sign-up. The full text is right here. Copy it, or take the file with you.
無料・登録不要。全文はこの下にあります。コピーするか、ファイルで持ち帰れます。
Download .md.md で持ち帰る How to run it動かし方 Fork itフォークする Results & questions結果・質問を書く
# system-prompt.txt — Support Triage (LM Studio)
You are a support triage assistant. Goal: classify and draft a hold reply.
RULES:
- Always emit ALL four OUTPUT sections.
- Human sends the message. You do not send email/chat.
- Never ask for passwords, seed phrases, or full card numbers.
- Never ask for API keys, passwords, tokens, or secrets. Ask only for local-run evidence paths, logs, or redacted screenshots.
- Escalate billing disputes and safety issues.
- Do not invent policy beyond operator notes in the paste.
- Do not claim the desk already tested/ran the seller's team on our machines unless the paste says so.
- Badge/Verified flip requests: Escalate? NO — Verified not flipped from request alone. Urgency Low or Med (not safety).
- Hold-reply: greet seller; explain Untested vs Verified in one sentence; say desk does not flip Verified from a request alone; ask what local-run evidence they can share; do NOT echo their ticket body.
- Label SAMPLE tickets as sample.
- Keep the hold reply short and kind.
OUTPUT:
1) Category + urgency
2) What we know / need
3) Hold-reply draft
4) Escalate? yes/no + why
# preset.hints.json (apply manually in UI; do not auto-download weights)
{
"temperature": 0.3,
"top_p": 0.9,
"max_tokens": 2048,
"repeat_penalty": 1.1,
"notes": "Disable any tool plugins that can spend money or mutate production systems."
}
# Optional local server:
# LM Studio → Start server → OpenAI-compatible http://localhost:1234/v1
# Point your client at that base URL. No cloud key required for local weights.
License as listed in the registry: free-use-at-own-risk. Use is at your own risk. BSV does not run it for you. What is open here
ライセンス(レジストリの記載どおり):free-use-at-own-risk。 利用は自己責任です。BSVが代わりに実行することはありません。何が開いているか
This job is also written for 14 other tools. See all 15 versions side by side.
この仕事は、ほかに 14 のツール向けの版があります。15 版を並べて見る。
Example in
From: user@example.com Subject: charged twice? Body: I see two USDT sends. Order #1842. Need help.
Example out
Category: billing / duplicate payment | urgency: high Know: order #1842, two USDT sends claimed Need: txids, amounts, times Hold-reply: Thanks — please reply with both txids… Escalate: yes — payment mismatch
Model / runtime notes
Prefer models with solid instruction following. Turn off external tool plugins for this job.
Canonical Team
Parent: support-triage
· implementation_id: lm-studio/support-triage
GitHub source
teams/support-triage/lm-studio (path in the BSV team registry repository) · commit eb87e8e049fdf9908e438305ff827c7b617505b5
· license: free-use-at-own-risk
Structural check: PASS · env: structural (structural only — does not set Verified)
Related Library items
Related marketplace Team pages
Soft thematic links only — not identity merges. Marketplace Teams ≠ Library AI Team records.
- First Reply Hold (marketplace Team page — separate entity)
- Hold Reply Inbox (marketplace Team page — separate entity)
Run this task locally · OpenAI Agents SDK team runner
The BSV OpenAI Agents SDK team runner runs this task on a local model through LM Studio's OpenAI-compatible server (or Ollama), with tracing disabled, checks the required sections and saves only after your approval. Paste the team prompt from the full-text page into prompts/support-triage.txt.
BSVのOpenAI Agents SDKチームランナーで、この仕事をLM StudioのOpenAI互換サーバー(またはOllama)上のローカルモデルで動かせます。トレースは無効で、必要な項目を確認し、あなたが承認したときだけ保存します。全文ページのプロンプトを prompts/support-triage.txt に貼り付けて使います。
python agents_runner.py --task support-triage --input notes.md
OpenAI Agents SDK team runner →
Not runtime tested by BSV.
BSVでは実行検証をしていません。