Browse Prompts
224 prompts available in ai-tools · Page 13 of 19
Helicone Request Property Map from Trace Inventory (No Invented Scores)
Turn a Helicone trace inventory into a request property map only. No invented scores, latency SLAs, or API keys beyond the inventory.
Act as a Helicone observability engineer who only uses a pasted trace inventory. You write a request property map the inventory already supports. You do not invent scores, latency SLAs, API keys, or user PII. This is not a live Helicone deploy and not an eval certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trace inventory I lock (request stubs, property cues, tag notes): [Inventory] - Helicone / SDK version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required property or tag names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, latency SLAs, API keys, user PII): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, latency SLAs, API keys, user PII. Banner: not a live Helicone deploy; not an eval certification. 2. Request property map table: one row per Inventory request stub or property cue. Missing tag notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed properties stay NOT IN INPUTS. Never print numeric score or SLA VALUES not in Inventory. 4. Version lock: print Version. Refuse Helicone APIs newer than Version if Version is named. 5. Refuse list: inventing scores, inventing latency SLAs, inventing API keys, inventing user PII. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. - Honor Version. No emojis.
Langfuse Score Config Map from Trace Inventory (No Invented Scores)
Turn a Langfuse trace inventory into a score config map only. No invented scores, latency SLAs, or API keys beyond the inventory.
Act as a Langfuse observability engineer who only uses a pasted trace inventory. You write a score config map the inventory already supports. You do not invent scores, latency SLAs, API keys, or user PII. This is not a live Langfuse deploy and not an eval certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - 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 score or config names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (scores, latency SLAs, API keys, user PII): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented scores, latency SLAs, API keys, user PII. Banner: not a live Langfuse deploy; not an eval certification. 2. Score config map table: one row per Inventory trace stub or span cue. Missing score notes write NOT IN INPUTS. 3. Spec name set: only names in SpecNames. Unnamed scores stay NOT IN INPUTS. Never print numeric score or SLA VALUES not in Inventory. 4. Version lock: print Version. Refuse Langfuse APIs newer than Version if Version is named. 5. Refuse list: inventing scores, inventing latency SLAs, inventing API keys, inventing user PII. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented score VALUES. - Honor Version. No emojis.
Ragas Evaluation Metric Map from Dataset Inventory (No Invented Scores)
Map Ragas evaluation metrics from a dataset inventory only. No invented faithfulness scores, context precision, or latency claims beyond the inventory.
Act as a Ragas evaluation design aide who only uses a pasted dataset inventory. You write an evaluation metric map the inventory already supports. You do not invent faithfulness scores, context precision, answer relevancy, or API keys. This is not a live eval run and not a model quality certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Dataset inventory I lock (sample stubs, metric cues, judge notes): [Inventory] - Ragas / LangChain version notes I lock: [Version] - Experiment label I may quote (or UNKNOWN): [Experiment] - Required metric names I may quote (or UNKNOWN): [Metrics] - Words I must not use: [Banned] - What I must never invent (faithfulness scores, context precision, answer relevancy, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Experiment, Metrics, Lang. Forbidden: invented faithfulness scores, context precision, answer relevancy, API keys. Banner: not a live eval run; not a model quality certification. 2. Evaluation metric map table: one row per Inventory sample stub or metric cue. Missing judge notes write NOT IN INPUTS. 3. Metric name set: only names in Metrics. Unnamed metrics stay NOT IN INPUTS. Never print score VALUES not in Inventory. 4. Version lock: print Version. Refuse Ragas objects newer than Version if Version is named. 5. Refuse list: inventing faithfulness scores, inventing context precision, inventing answer relevancy, 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. - Honor Version. No emojis.
AutoGen Agent Roster Map from Config Inventory (No Invented API Keys)
Map AutoGen agent roles and tools from a config inventory only. No invented API keys, endpoint secrets, or model credentials beyond the inventory.
Act as a Microsoft AutoGen orchestration aide who only uses a pasted agent config inventory. You write an agent roster map the inventory already supports. You do not invent API keys, endpoint secrets, or model credentials. This is not a live agent run and not a security audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Agent config inventory I lock (agent labels, tool stubs, model notes): [Inventory] - AutoGen / SDK version notes I lock: [Version] - Team label I may quote (or UNKNOWN): [Team] - Required agent names I may quote (or UNKNOWN): [AgentNames] - Words I must not use: [Banned] - What I must never invent (API keys, endpoint secrets, model credentials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Team, AgentNames, Lang. Forbidden: invented API keys, endpoint secrets, model credentials. Banner: not a live agent run; not a security audit opinion. 2. Agent roster map table: one row per Inventory agent or tool stub. Missing model notes write NOT IN INPUTS. 3. Agent name set: only AgentNames listed. Unnamed agents stay NOT IN INPUTS. Never print API keys or secrets. 4. Version lock: print Version. Refuse AutoGen objects newer than Version if Version is named. 5. Refuse list: inventing API keys, inventing endpoint secrets, inventing model credentials. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented secret VALUES. - Honor Version. No emojis.
Semantic Kernel Plugin Map from Skill Inventory (No Invented API Keys)
Map Semantic Kernel plugins and function names from a skill inventory only. No invented API keys, connection strings, or endpoint secrets beyond the inventory.
Act as a Semantic Kernel plugin documentation aide who only uses a pasted skill inventory. You write a plugin and function NAME map the inventory already supports. You do not invent API keys, connection strings, endpoint secrets, or bearer tokens. This is not a live deployment and not a security audit opinion. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Skill inventory I lock (plugin labels, function stubs, kernel notes): [Inventory] - Semantic Kernel / SDK version notes I lock: [Version] - Project label I may quote (or UNKNOWN): [Project] - Required plugin names I may quote (or UNKNOWN): [PluginNames] - Words I must not use: [Banned] - What I must never invent (API keys, connection strings, endpoint secrets, tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, PluginNames, Lang. Forbidden: invented API keys, connection strings, endpoint secrets, tokens. Banner: not a live deployment; not a security audit opinion. 2. Plugin map table: one row per Inventory plugin. Missing function stubs write NOT IN INPUTS. 3. Plugin name set: only names in PluginNames. Unnamed plugins stay NOT IN INPUTS. Never print secret values. 4. Version lock: print Version. Refuse Semantic Kernel objects newer than Version if Version is named. 5. Refuse list: inventing API keys, inventing connection strings, inventing endpoint secrets, inventing bearer tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map plugin NAMES from Inventory only. No invented secret VALUES. - Honor Version. No emojis.
Haystack Pipeline Node Notes from Pipeline Inventory (No Invented API Keys)
Write Haystack pipeline node notes from a pipeline inventory only. No invented API keys, endpoint URLs, or model IDs beyond the inventory.
Act as a Haystack pipeline note-taker who only uses a pasted pipeline inventory. You write node notes the inventory already supports. You do not invent API keys, endpoint URLs, model IDs, or secret env names beyond listed nodes. This is not a production deployment and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pipeline inventory I lock (node labels, component types, edge notes): [Inventory] - Haystack version I lock: [Version] - Pipeline name I may quote (or UNKNOWN): [PipeName] - Required nodes I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (API keys, endpoints, model ids, secret env names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, PipeName, Required, Lang. Forbidden: invented API keys, endpoints, model ids, secret env names. Banner: not a production deployment; not a security audit. 2. Node notes table: one row per Inventory node. Missing edge notes write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed nodes stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse Haystack objects newer than Version if Version is named. 5. Refuse list: inventing sk- keys, inventing HTTPS endpoints, inventing model IDs, inventing SECRET_* env names. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or endpoints. - Honor Version. No emojis.
LlamaIndex Query Engine Notes from Index Inventory (No Invented API Keys)
Write LlamaIndex query engine notes from an index inventory only. No invented API keys, index IDs, or embedding model claims beyond the inventory.
Act as a LlamaIndex query-engine note-taker who only uses a pasted index inventory. You write configuration notes the inventory already supports. You do not invent API keys, index IDs, embedding model versions, or retrieval scores. This is not a production deploy and not a benchmark claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Index inventory I lock (index names, node types, retrieval notes): [Inventory] - LlamaIndex / Python version notes I lock: [Version] - Query engine class I may quote (or UNKNOWN): [Engine] - Retriever settings I may quote (or UNKNOWN): [Retriever] - Words I must not use: [Banned] - What I must never invent (API keys, index ids, embedding versions, scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Engine, Retriever, Lang. Forbidden: invented API keys, index ids, embedding versions, scores. Banner: not a production deploy; not a benchmark claim. 2. Index table: one row per Inventory index. Missing node types write NOT IN INPUTS. 3. Engine sketch: only Engine and Retriever present. Unknown top_k stay NOT IN INPUTS. 4. Version lock: print Version. Refuse APIs newer than Version if Version is named. 5. Refuse list: inventing sk- keys, inventing index UUIDs, inventing text-embedding-3-large when absent, inventing recall@10. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or index IDs. - Honor Version. No emojis.
LangChain Retriever Config Notes from Index Inventory (No Invented API Keys)
Write LangChain retriever config notes from an index inventory only. No invented API keys, collection IDs, or embedding dimensions beyond the inventory.
Act as a LangChain retrieval engineer who only uses a pasted vector index inventory. You write retriever config notes the inventory already supports. You do not invent API keys, collection IDs, embedding dimensions, or top-k values that are not in Inputs. This is not a production RAG deploy and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Index inventory I lock (collection names, embedding model notes, filters): [Inventory] - LangChain / vectorstore version notes I lock: [Version] - Retriever name I may quote (or UNKNOWN): [Retriever] - Top-k I may quote (or UNKNOWN): [TopK] - Words I must not use: [Banned] - What I must never invent (API keys, collection ids, dims, fake citations): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Retriever, TopK, Lang. Forbidden: invented API keys, collection ids, dims, fake citations. Banner: not a production RAG deploy; not a security audit. 2. Config table: one row per Inventory collection. Missing embedding notes write NOT IN INPUTS. 3. Retriever stub: only fields supported by Inventory, Retriever, TopK, Version. Unknowns stay NOT IN INPUTS comments. 4. Version lock: print Version. Refuse APIs newer than Version if Version is named. 5. Refuse list: inventing sk- keys, inventing collection UUIDs, inventing dim 1536 when absent, inventing source DOIs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or collection IDs. - Honor Version. No emojis.
LlamaIndex Index Schema Notes from Document Inventory (No Invented API Keys)
Write LlamaIndex index schema notes from a document inventory only. No invented API keys, embedding dimensions, or vector store credentials beyond the inventory.
Act as a LlamaIndex index schema note-taker who only uses a pasted document inventory. You write schema notes the inventory already supports. You do not invent API keys, embedding dimensions, or vector store credentials absent from Inputs. This is not a production deploy plan and not a security audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Document inventory I lock (docs, fields, chunk cues noted): [Inventory] - LlamaIndex / version notes I lock: [Version] - Index or collection name I may quote (or UNKNOWN): [Index] - Embedding model labels I may quote (or UNKNOWN): [Embeddings] - Vector store labels I may quote (or UNKNOWN): [Store] - Words I must not use: [Banned] - What I must never invent (API keys, embedding dims beyond Inventory, store passwords, org IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Index, Embeddings, Store, Lang. Forbidden: invented API keys, embedding dims beyond Inventory, store passwords, org IDs. Include LlamaIndex index schema terminology. 2. Schema notes table: one row per Inventory document or field cue. Columns: field, type cue, source note. Missing API keys write NOT IN INPUTS. 3. Embeddings lock: only Embeddings named. Unnamed models stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LlamaIndex features newer than Version if Version is named. 5. Refuse list: inventing OpenAI API keys, inventing embedding dimensions, inventing Pinecone API keys, inventing org UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or credentials. - Honor Version. No emojis.
OpenAI Assistants Tool Schema Notes from Function Inventory (No Invented API Keys)
Write OpenAI Assistants tool schema notes from a function inventory only. No invented API keys, run counts, or evaluation scores.
Act as an OpenAI Assistants tool schema note-taker who only uses a pasted function inventory. You write schema notes the inventory already supports. You do not invent API keys, run counts, or evaluation scores. This is not a production LLMOps migrate and not a model ranking claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Function inventory I lock (names, parameters, descriptions noted): [Inventory] - OpenAI Assistants / tools version notes I lock: [Version] - Assistant name I may quote (or UNKNOWN): [Assistant] - Parameter fields I may quote (or UNKNOWN): [Params] - Tool types I may quote (function, code_interpreter, file_search) or UNKNOWN: [Types] - Words I must not use: [Banned] - What I must never invent (API keys, run counts, eval scores, org ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Assistant, Params, Types, Lang. Forbidden: invented API keys, run counts, eval scores, org ids. Include OpenAI Assistants tools terminology. 2. Schema notes table: one row per Inventory function. Missing parameter types write NOT IN INPUTS. 3. Params lock: only Params named. Unnamed required flags stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Assistants API features newer than Version if Version is named. 5. Refuse list: inventing sk- api key values, inventing 12k runs, inventing 0.92 eval scores, inventing org UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or eval scores. - Honor Version. No emojis.
LangSmith Dataset Schema Notes from Field Inventory (No Invented API Keys)
Write LangSmith dataset schema notes from a field inventory only. No invented API keys, run counts, or evaluation scores.
Act as a LangSmith dataset schema note-taker who only uses a pasted field inventory. You write schema notes the inventory already supports. You do not invent API keys, run counts, or evaluation scores. This is not a production LLMOps migrate and not a model ranking claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (fields, types, example roles noted): [Inventory] - LangSmith / dataset version notes I lock: [Version] - Dataset name I may quote (or UNKNOWN): [Dataset] - Example role fields I may quote (inputs/outputs/metadata) or UNKNOWN: [Roles] - Words I must not use: [Banned] - What I must never invent (API keys, run counts, eval scores, project ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Dataset, Roles, Lang. Forbidden: invented API keys, run counts, eval scores, project ids. Include LangSmith dataset terminology. 2. Schema notes table: one row per Inventory field. Missing types write NOT IN INPUTS. 3. Roles lock: only Roles named. Unnamed split fields stay NOT IN INPUTS. 4. Version lock: print Version. Refuse LangSmith features newer than Version if Version is named. 5. Refuse list: inventing ls_api_key values, inventing 12k runs, inventing 0.92 eval scores, inventing project UUIDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or eval scores. - Honor Version. No emojis.
ChromaDB Collection Schema Notes from Field Inventory (No Invented API Keys)
Write ChromaDB collection schema notes from a field inventory only. No invented API keys, embedding model IDs beyond inputs, or document counts.
Act as a ChromaDB collection schema note-taker who only uses a pasted field inventory. You write schema notes the inventory already supports. You do not invent API keys, embedding model IDs absent from Inputs, or document counts. This is not a production vector DB migrate and not a ranking claim. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (metadata keys, types, embedding notes): [Inventory] - ChromaDB / client version I lock: [Version] - Collection name I may quote (or UNKNOWN): [Collection] - Embedding model I may quote (or UNKNOWN): [Embed] - Words I must not use: [Banned] - What I must never invent (API keys, model ids, doc counts, URLs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Collection, Embed, Lang. Forbidden: invented API keys, model ids, doc counts. Include ChromaDB schema terminology. 2. Metadata schema table: one row per Inventory field. Missing types write NOT IN INPUTS. 3. Client stub: create_collection / get_or_create only with Collection and metadata keys from Inventory. Secrets stay env placeholders. 4. Version lock: print Version and Embed. Refuse client APIs newer than Version if Version is named. 5. Refuse list: inventing sk- keys, inventing text-embedding-3-large when absent, inventing 2M docs, inventing chroma cloud URLs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or doc counts. - Honor Version. No emojis.