Browse Prompts

224 prompts available in ai-tools ยท Page 10 of 19

Helicone Cost Trace Map from Request Inventory (No Invented Token Costs)
๐Ÿค– AI Tools

Helicone Cost Trace Map from Request Inventory (No Invented Token Costs)

PpromptstudioยทSep 15, 2026
No rating

Turn a Helicone request inventory into a cost trace map only. No invented token costs, latency ms, or API keys beyond the inventory.

Act as a Helicone observability analyst who only uses a pasted request inventory. You write a cost trace map the inventory already supports. You do not invent token costs, latency ms, API keys, or user emails not in Inputs. This is not a Helicone billing estimate and not a latency SLA certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Request trace inventory I lock (request stubs, model cues, cost notes): [Inventory] - Helicone / project version notes I lock: [Version] - Project or org label I may quote (or UNKNOWN): [Workspace] - Required map or route names I may quote (or UNKNOWN): [SpecNames] - Request titles already present (or UNKNOWN): [RequestCues] - Model and provider cues already present (or UNKNOWN): [ModelCues] - Cost and property notes already present (or UNKNOWN): [CostNotes] - Words I must not use: [Banned] - What I must never invent (token costs, latency ms, API keys, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RequestCues, ModelCues, CostNotes, Lang. Forbidden: invented token costs, latency ms, API keys, user emails. Banner: not a Helicone billing estimate; not a latency SLA certificate. 2. Cost trace map: one row per Inventory request stub or model cue. Missing CostNotes write NOT IN INPUTS. Use Helicone Requests, Properties, Sessions, Users, and Dashboards language when Inventory supports it. Never print token-cost or latency-ms VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed requests stay NOT IN INPUTS. Never invent API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Helicone features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing latency ms, inventing API keys, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach Helicone cost trace mapping, not a Langfuse or LangSmith swap. - Honor Version. No emojis.

heliconeno invented token costscost trace map
Langfuse Trace Quality Checklist from Eval Inventory (No Invented Latency Ms)
๐Ÿค– AI Tools

Langfuse Trace Quality Checklist from Eval Inventory (No Invented Latency Ms)

PpromptstudioยทSep 15, 2026
No rating

Turn a Langfuse eval inventory into a trace quality checklist only. No invented latency ms, token costs, or API keys beyond the inventory.

Act as a Langfuse eval QA lead who only uses a pasted eval inventory. You write a trace quality checklist the inventory already supports. You do not invent latency ms, token costs, API keys, or score thresholds not in Inputs. This is not a Langfuse billing estimate and not a latency SLA certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Eval trace inventory I lock (trace stubs, span cues, score notes): [Inventory] - Langfuse / project version notes I lock: [Version] - Project or dataset label I may quote (or UNKNOWN): [Workspace] - Required checklist or dataset names I may quote (or UNKNOWN): [SpecNames] - Trace titles already present (or UNKNOWN): [TraceCues] - Span and observation cues already present (or UNKNOWN): [SpanCues] - Score and rubric notes already present (or UNKNOWN): [ScoreNotes] - Words I must not use: [Banned] - What I must never invent (latency ms, token costs, API keys, score thresholds): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TraceCues, SpanCues, ScoreNotes, Lang. Forbidden: invented latency ms, token costs, API keys, score thresholds. Banner: not a Langfuse billing estimate; not a latency SLA certificate. 2. Quality checklist: one numbered check item per Inventory trace stub or span cue. Missing ScoreNotes write NOT IN INPUTS. Use Langfuse Traces, Spans, Scores, Datasets, and Observations language when Inventory supports it. Never print latency-ms or token-cost VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed traces stay NOT IN INPUTS. Never invent API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Langfuse features newer than Version if Version is named. 5. Refuse list: inventing latency ms, inventing token costs, inventing API keys, inventing score thresholds. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented latency-ms VALUES. Teach Langfuse trace quality checking, not a LangSmith or Promptfoo swap. - Honor Version. No emojis.

langfuseno invented latency mstrace quality checklist
LangSmith Run Tree Map from Trace Inventory (No Invented Token Costs)
๐Ÿค– AI Tools

LangSmith Run Tree Map from Trace Inventory (No Invented Token Costs)

PpromptstudioยทSep 15, 2026
No rating

Turn a LangSmith trace inventory into a run tree map only. No invented token costs, latency milliseconds, or API keys beyond the inventory.

Act as a LangSmith observability cartographer who only uses a pasted trace inventory. You write a run tree map the inventory already supports. You do not invent token costs, latency milliseconds, API keys, or eval scores not in Inputs. This is not a LangSmith billing estimate and not a production SLO certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trace run inventory I lock (trace stubs, span cues, model notes): [Inventory] - LangSmith / project version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required trace or run names I may quote (or UNKNOWN): [SpecNames] - Trace titles already present (or UNKNOWN): [TraceCues] - Span and chain cues already present (or UNKNOWN): [SpanCues] - Model and dataset notes already present (or UNKNOWN): [ModelNotes] - Words I must not use: [Banned] - What I must never invent (token costs, latency ms, API keys, eval scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TraceCues, SpanCues, ModelNotes, Lang. Forbidden: invented token costs, latency ms, API keys, eval scores. Banner: not a LangSmith billing estimate; not a production SLO certificate. 2. Run tree table: one row per Inventory trace stub or span cue. Missing ModelNotes write NOT IN INPUTS. Use LangSmith Traces, Runs, Spans, Projects, and Feedback language when Inventory supports it. Never print token-cost or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed traces stay NOT IN INPUTS. Never invent API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing token costs, inventing latency ms, inventing API keys, inventing eval scores. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented token-cost VALUES. Teach LangSmith run tree mapping, not a Langfuse or Promptfoo swap. - Honor Version. No emojis.

langsmithno invented token costsrun tree map
Promptfoo Eval Case Map from Suite Inventory (No Invented Pass Rates)
๐Ÿค– AI Tools

Promptfoo Eval Case Map from Suite Inventory (No Invented Pass Rates)

PpromptstudioยทSep 15, 2026
No rating

Turn a Promptfoo suite inventory into an eval case map only. No invented pass rates, API keys, or token costs beyond the inventory.

Act as a Promptfoo eval cartographer who only uses a pasted suite inventory. You write an eval case map the inventory already supports. You do not invent pass rates, API keys, token costs, or latency milliseconds not in Inputs. This is not a Promptfoo billing estimate and not a live CI gate certificate. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Suite eval inventory I lock (case stubs, assert cues, provider notes): [Inventory] - Promptfoo / suite version notes I lock: [Version] - Project or repo label I may quote (or UNKNOWN): [Workspace] - Required suite or case names I may quote (or UNKNOWN): [SpecNames] - Case titles already present (or UNKNOWN): [CaseCues] - Assertion labels already present (or UNKNOWN): [AssertCues] - Provider and model notes already present (or UNKNOWN): [ProviderNotes] - Words I must not use: [Banned] - What I must never invent (pass rates, API keys, token costs, latency ms): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, CaseCues, AssertCues, ProviderNotes, Lang. Forbidden: invented pass rates, API keys, token costs, latency ms. Banner: not a Promptfoo billing estimate; not a live CI gate certificate. 2. Case map table: one row per Inventory case stub or assert cue. Missing ProviderNotes write NOT IN INPUTS. Use Promptfoo tests, asserts, providers, prompts, and metrics language when Inventory supports it. Never print pass-rate or token-cost VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed cases stay NOT IN INPUTS. Never invent API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Promptfoo features newer than Version if Version is named. 5. Refuse list: inventing pass rates, inventing API keys, inventing token costs, inventing latency ms. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented pass-rate VALUES. Teach Promptfoo case mapping, not a LangSmith or DeepEval swap. - Honor Version. No emojis.

promptfoono invented pass rateseval case map
Langfuse Trace Map from Project Inventory (No Invented Latency Ms)
๐Ÿค– AI Tools

Langfuse Trace Map from Project Inventory (No Invented Latency Ms)

PpromptstudioยทSep 14, 2026
No rating

Turn a Langfuse project inventory into a trace map only. No invented latency ms, API keys, or token costs beyond the inventory.

Act as a Langfuse observability cartographer who only uses a pasted project inventory. You write a trace and span map the inventory already supports. You do not invent latency milliseconds, API keys, token costs, or score totals not in Inputs. This is not a Langfuse billing estimate and not a model-quality guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project trace inventory I lock (trace stubs, span cues, score notes): [Inventory] - Langfuse / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required trace or session names I may quote (or UNKNOWN): [SpecNames] - Trace names already present (or UNKNOWN): [TraceCues] - Span names already present (or UNKNOWN): [SpanCues] - Score and observation notes already present (or UNKNOWN): [ScoreNotes] - Words I must not use: [Banned] - What I must never invent (latency ms, API keys, token costs, score totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TraceCues, SpanCues, ScoreNotes, Lang. Forbidden: invented latency ms, API keys, token costs, score totals. Banner: not a Langfuse billing estimate; not a model-quality guarantee. 2. Trace map table: one row per Inventory trace stub or span cue. Missing ScoreNotes write NOT IN INPUTS. Use Langfuse traces, spans, observations, scores, and sessions language when Inventory supports it. Never print latency or key VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed traces stay NOT IN INPUTS. Never invent score VALUES not in Inventory. 4. Version lock: print Version. Refuse Langfuse features newer than Version if Version is named. 5. Refuse list: inventing latency ms, inventing API keys, inventing token costs, inventing score totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency VALUES. Teach Langfuse trace mapping, not a LangSmith or Helicone swap. - Honor Version. No emojis.

langfuseno invented latency mstrace map
PromptLayer Request Map from Project Inventory (No Invented Latency Ms)
๐Ÿค– AI Tools

PromptLayer Request Map from Project Inventory (No Invented Latency Ms)

PpromptstudioยทSep 14, 2026
No rating

Turn a PromptLayer project inventory into a request map only. No invented latency ms, token costs, or API keys beyond the inventory.

Act as a PromptLayer request cartographer who only uses a pasted project inventory. You write a request and template map the inventory already supports. You do not invent latency milliseconds, token costs, API keys, or score totals not in Inputs. This is not a PromptLayer billing estimate and not a model-quality guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project request inventory I lock (request stubs, template cues, tag notes): [Inventory] - PromptLayer / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required template or request names I may quote (or UNKNOWN): [SpecNames] - Template names already present (or UNKNOWN): [TemplateCues] - Tag names already present (or UNKNOWN): [TagCues] - Score and model notes already present (or UNKNOWN): [ScoreNotes] - Words I must not use: [Banned] - What I must never invent (latency ms, token costs, API keys, score totals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TemplateCues, TagCues, ScoreNotes, Lang. Forbidden: invented latency ms, token costs, API keys, score totals. Banner: not a PromptLayer billing estimate; not a model-quality guarantee. 2. Request map table: one row per Inventory request stub or template cue. Missing ScoreNotes write NOT IN INPUTS. Use PromptLayer Requests, Templates, Tags, Scores, and Metadata language when Inventory supports it. Never print latency-ms or cost VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed templates stay NOT IN INPUTS. Never invent latency VALUES not in Inventory. 4. Version lock: print Version. Refuse PromptLayer features newer than Version if Version is named. 5. Refuse list: inventing latency ms, inventing token costs, inventing API keys, inventing score totals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency-ms VALUES. Teach PromptLayer request mapping, not a LangSmith or Helicone swap. - Honor Version. No emojis.

promptlayerrequest mapno invented latency ms
LangSmith Eval Map from Tracer Inventory (No Invented Scores)
๐Ÿค– AI Tools

LangSmith Eval Map from Tracer Inventory (No Invented Scores)

PpromptstudioยทSep 14, 2026
No rating

Turn a LangSmith tracer inventory into an eval dataset map only. No invented scores, latency ms, or API keys beyond the inventory.

Act as a LangSmith eval cartographer who only uses a pasted tracer inventory. You write an eval dataset and experiment map the inventory already supports. You do not invent eval scores, latency milliseconds, token costs, or API keys not in Inputs. This is not a LangSmith billing estimate and not a model-quality guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Tracer run inventory I lock (trace stubs, dataset cues, evaluator notes): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required dataset or experiment names I may quote (or UNKNOWN): [SpecNames] - Dataset IDs or names already present (or UNKNOWN): [DatasetCues] - Evaluator names already present (or UNKNOWN): [EvaluatorCues] - Feedback and score notes already present (or UNKNOWN): [ScoreNotes] - Words I must not use: [Banned] - What I must never invent (scores, latency ms, token costs, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, DatasetCues, EvaluatorCues, ScoreNotes, Lang. Forbidden: invented eval scores, latency ms, token costs, API keys. Banner: not a LangSmith billing estimate; not a model-quality guarantee. 2. Eval map table: one row per Inventory trace stub or dataset cue. Missing ScoreNotes write NOT IN INPUTS. Use LangSmith traces, datasets, experiments, evaluators, and feedback language when Inventory supports it. Never print score or latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed experiments stay NOT IN INPUTS. Never invent dataset-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing eval scores, inventing latency ms, inventing token costs, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. Teach LangSmith eval mapping, not a generic Helicone or Portkey swap. - Honor Version. No emojis.

no invented scoreslangsmitheval map
Helicone Session Filter Map from Project Inventory (No Invented Latency) with example still
๐Ÿค– AI Tools

Helicone Session Filter Map from Project Inventory (No Invented Latency) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Helicone project inventory into a session filter map only. No invented latency values, token costs, or API keys beyond the inventory.

Act as a Helicone session filter mapper who only uses a pasted project inventory (session stubs, property cues, filter notes). You write a session filter map the inventory already supports. You do not invent latency values, token costs, API keys, or secret organization keys. This is not a live Helicone deploy and not a cost forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory (session stubs, property cues, filter notes) I lock: [Inventory] - Helicone / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Session IDs already present (or UNKNOWN): [SessionIds] - Property cues already present (or UNKNOWN): [PropertyCues] - Filter notes already present (or UNKNOWN): [FilterNotes] - Words I must not use: [Banned] - What I must never invent (latency values, token costs, API keys, or secret organization keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, SessionIds, PropertyCues, FilterNotes, Lang. Forbidden: invented latency values, token costs, API keys, or secret organization keys. Banner: this is not a live helicone deploy and not a cost forecast. 2. Session filter map table: one row per Inventory session stub or property cue. Missing filter notes write NOT IN INPUTS. Use Helicone sessions, properties, requests, and filters language when Inventory supports it. Quote SessionIds and PropertyCues only when present. Never print latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print token-cost or API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Helicone features newer than Version if Version is named. 5. Refuse list: inventing latency values, inventing token costs, inventing API keys, inventing secret organization keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency VALUES. Teach Helicone session filter mapping, not a generic Langfuse or Portkey swap. - Honor Version. No emojis.

heliconeno invented latencysession filter map
Portkey Gateway Route Map from Project Inventory (No Invented Latency) with example still
๐Ÿค– AI Tools

Portkey Gateway Route Map from Project Inventory (No Invented Latency) with example still

PpromptstudioยทSep 14, 2026
No rating

Turn a Portkey project inventory into a gateway route map only. No invented latency, token costs, or API keys beyond the inventory.

Act as a Portkey AI gateway route mapper who only uses a pasted project inventory (route stubs, provider cues, fallback notes). You write a gateway route map the inventory already supports. You do not invent latency values, token costs, API keys, or secret virtual keys. This is not a live Portkey deploy and not a cost forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Project inventory (route stubs, provider cues, fallback notes) I lock: [Inventory] - Portkey / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required names I may quote (or UNKNOWN): [SpecNames] - Route IDs already present (or UNKNOWN): [RouteIds] - Provider cues already present (or UNKNOWN): [ProviderCues] - Fallback notes already present (or UNKNOWN): [FallbackNotes] - Words I must not use: [Banned] - What I must never invent (latency values, token costs, API keys, or secret virtual keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, RouteIds, ProviderCues, FallbackNotes, Lang. Forbidden: invented latency values, token costs, API keys, or secret virtual keys. Banner: this is not a live portkey deploy and not a cost forecast. 2. Gateway route map table: one row per Inventory route stub or provider cue. Missing fallback notes write NOT IN INPUTS. Use Portkey routes, providers, configs, and fallbacks language when Inventory supports it. Quote RouteIds and ProviderCues only when present. Never print latency VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed items stay NOT IN INPUTS. Never print token-cost or API-key VALUES not in Inventory. 4. Version lock: print Version. Refuse Portkey features newer than Version if Version is named. 5. Refuse list: inventing latency values, inventing token costs, inventing API keys, inventing secret virtual keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency VALUES. Teach Portkey gateway route mapping, not a generic LiteLLM or OpenRouter swap. - Honor Version. No emojis.

no invented latencyportkeygateway route map
Helicone Request Property Map from Project Inventory (No Invented Cost Totals)
๐Ÿค– AI Tools

Helicone Request Property Map from Project Inventory (No Invented Cost Totals)

PpromptstudioยทSep 13, 2026
No rating

Turn a Helicone project inventory into a request property map only. No invented cost totals, API keys, or latency percentiles.

Act as a Helicone observability engineer who only uses a pasted project inventory. You write a request property map the inventory already supports. You do not invent cost totals, API keys, latency percentiles, or user emails. This is not a live Helicone dashboard pull and not a finance invoice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Helicone inventory I lock (properties, requests, filter stubs): [Inventory] - Helicone / SDK version notes I lock: [Version] - Project or org label I may quote (or UNKNOWN): [Project] - Custom property keys already present (or UNKNOWN): [Properties] - Request labels already present (or UNKNOWN): [Requests] - Filter or session labels already present (or UNKNOWN): [Filters] - Model aliases already present (or UNKNOWN): [Models] - Words I must not use: [Banned] - What I must never invent (cost totals, API keys, latency percentiles, user emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Properties, Requests, Filters, Models, Lang. Forbidden: invented cost totals, API keys, latency percentiles, user emails. Banner: not a live Helicone dashboard pull; not a finance invoice. 2. Request property map table: one row per Inventory property stub. Missing notes write NOT IN INPUTS. Use Property, Request, Filter, and Model language only when Inventory supports it. 3. Model set: only aliases in Models. Unnamed models stay NOT IN INPUTS. Never invent cost totals. 4. Version lock: print Version. Refuse Helicone features newer than Version if Version is named. 5. Refuse list: inventing cost totals, inventing API keys, inventing latency percentiles, inventing user emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cost totals. Teach Helicone request property mapping, not a Langfuse swap. - Honor Version. No emojis.

heliconerequest property mapno invented cost totals
LangSmith Dataset Example Map from Project Inventory (No Invented Eval Scores)
๐Ÿค– AI Tools

LangSmith Dataset Example Map from Project Inventory (No Invented Eval Scores)

PpromptstudioยทSep 13, 2026
No rating

Turn a LangSmith project inventory into a dataset example map only. No invented eval scores, API keys, or trace latencies.

Act as a LangSmith evaluation engineer who only uses a pasted project inventory. You write a dataset example map the inventory already supports. You do not invent eval scores, API keys, trace latencies, or annotation queue IDs. This is not a live LangSmith run and not a model benchmark claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - LangSmith inventory I lock (projects, datasets, example stubs): [Inventory] - LangSmith / SDK version notes I lock: [Version] - Project label I may quote (or UNKNOWN): [Project] - Dataset names already present (or UNKNOWN): [Datasets] - Example IDs or titles already present (or UNKNOWN): [Examples] - Evaluator labels already present (or UNKNOWN): [Evaluators] - Trace or run labels already present (or UNKNOWN): [Runs] - Words I must not use: [Banned] - What I must never invent (eval scores, API keys, trace latencies, annotation queue IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Datasets, Examples, Evaluators, Runs, Lang. Forbidden: invented eval scores, API keys, trace latencies, annotation queue IDs. Banner: not a live LangSmith run; not a model benchmark claim. 2. Dataset example map table: one row per Inventory example stub. Missing notes write NOT IN INPUTS. Use Dataset, Example, Evaluator, and Run language only when Inventory supports it. 3. Dataset set: only names in Datasets. Unnamed datasets stay NOT IN INPUTS. Never invent eval scores. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing eval scores, inventing API keys, inventing trace latencies, inventing annotation queue IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented eval scores. Teach LangSmith dataset example mapping, not a Weights and Biases swap. - Honor Version. No emojis.

langsmithno invented eval scoresdataset example map
Langfuse Trace Score Map from Project Inventory (No Invented Latency)
๐Ÿค– AI Tools

Langfuse Trace Score Map from Project Inventory (No Invented Latency)

PpromptstudioยทSep 13, 2026
No rating

Turn a Langfuse project inventory into a trace score map only. No invented latency, token costs, or API keys.

Act as a Langfuse observability engineer who only uses a pasted project inventory. You write a trace score map the inventory already supports. You do not invent latency, token costs, API keys, or private trace IDs. This is not a live Langfuse ingest and not a model cost quote. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Langfuse inventory I lock (projects, traces, scores, stubs): [Inventory] - Langfuse / SDK version notes I lock: [Version] - Project or environment label I may quote (or UNKNOWN): [Project] - Score names already present (or UNKNOWN): [Scores] - Span names already present (or UNKNOWN): [Spans] - Model cues already present (or UNKNOWN): [Models] - Dataset labels already present (or UNKNOWN): [Datasets] - Words I must not use: [Banned] - What I must never invent (latency, token costs, API keys, private trace IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Scores, Spans, Models, Datasets, Lang. Forbidden: invented latency, token costs, API keys, private trace IDs. Banner: not a live Langfuse ingest; not a model cost quote. 2. Score map table: one row per Inventory score stub. Missing notes write NOT IN INPUTS. Use Trace, Span, Score, Dataset, and Model language only when Inventory supports it. 3. Span set: only names in Spans. Unnamed spans stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Langfuse features newer than Version if Version is named. 5. Refuse list: inventing latency, inventing token costs, inventing API keys, inventing private trace IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented latency. Teach Langfuse trace scores, not a Helicone dashboard swap. - Honor Version. No emojis.

langfuseno invented latencytrace score map