🤖 AI Tools
LangSmith Trace Checklist from Run Inventory (No Invented Latencies)
Turn a LangSmith run inventory into a trace checklist only. No invented latencies, token totals, or error rates beyond the inventory.
0Reviews
Prompt
Act as a LangSmith observability engineer who only uses a pasted run inventory. You write a trace checklist the inventory already supports. You do not invent latencies, token totals, error rates, or run IDs. This is not a live LangSmith dashboard and not a cost report. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Run inventory I lock (trace stubs, chain cues, status notes): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required trace or chain names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (latencies, token totals, error rates, run IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented latencies, token totals, error rates, run IDs. Banner: not a live LangSmith dashboard; not a cost report. 2. Trace checklist table: one row per Inventory trace stub or chain cue. Missing status notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed traces stay NOT IN INPUTS. Never print latency or token VALUES not in Inventory. 4. Version lock: print Version. Refuse LangSmith APIs newer than Version if Version is named. 5. Refuse list: inventing latencies, inventing token totals, inventing error rates, inventing run IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented latency VALUES. - Honor Version. No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Inventory: trace Harbor Quay RAG Answer as pasted chain cue retrieval as pasted status note triage open as pasted; trace River Ops Tool Router as pasted chain cue tools as pasted. Latency NOT IN INPUTS. Token total NONE. Version: LangSmith Python SDK 0.1.x as pasted (do not invent unreleased annotation APIs) Workspace: Harbor Quay Observability Project as pasted SpecNames: RAG Answer as pasted; Tool Router as pasted. Eval Suite UNKNOWN. Banned: guaranteed latency, token invent, error invent, runid invent Never: invent latencies, invent token totals, invent error rates, invent run IDs Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: trace Harbor Quay RAG Answer chain cue retrieval status note triage open; trace River Ops Tool Router chain cue tools. Latency NOT IN INPUTS. Token total NONE. Version LangSmith Python SDK 0.1.x. Workspace Harbor Quay Observability Project. SpecNames RAG Answer; Tool Router; Eval Suite UNKNOWN. Lang English. Banner: not a live LangSmith dashboard; not a cost report. Forbidden: invented latencies, token totals, error rates, run IDs, guaranteed latency, token invent, error invent, runid invent. 2. Trace checklist. 1. Harbor Quay RAG Answer | chain retrieval as pasted | status triage open as pasted | latency NOT IN INPUTS | token total NONE. 2. River Ops Tool Router | chain tools as pasted | status NOT IN INPUTS | latency NOT IN INPUTS | token total NONE. Error rates not printed. Run IDs not invented. 3. Spec name set. RAG Answer; Tool Router as SpecNames. Eval Suite UNKNOWN so write Eval Suite NOT IN INPUTS. No latency VALUES printed. No third trace invented. 4. Version lock. LangSmith Python SDK 0.1.x as pasted. Unreleased annotation APIs not used. Dataset schema NOT IN INPUTS. 5. Refuse. Latency invent: refused. Token invent: refused. Error invent: refused. Run-ID invent: refused. Guaranteed latency: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: status for River Ops Tool Router, Eval Suite decision, feedback keys, sampling rules, cost fields if any. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.