#no invented api keys
8 prompts found
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.
Airtable Automation Notes from Trigger Inventory (No Invented API Keys)
Write Airtable automation notes from a trigger inventory only. No invented API keys, webhook URLs, or record IDs.
Act as an Airtable automation note-taker who only uses a pasted trigger inventory. You write automation notes the inventory already supports. You do not invent API keys, webhook URLs, or record IDs. This is not a billing audit and not a production deploy script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trigger inventory I lock (triggers, actions, tables named): [Inventory] - Airtable / automation version notes I lock: [Version] - Base name I may quote (or UNKNOWN): [Base] - Action cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (API keys, webhook URLs, record ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Base, Cap, Lang. Forbidden: invented API keys, webhook URLs, record ids. Include Airtable automation terminology. 2. Automation table: at most Cap rows. Columns: trigger, action, table. Missing cells write NOT IN INPUTS. 3. Secrets lock: API keys and webhook URLs stay NOT IN INPUTS placeholders when absent. 4. Version lock: print Version. Refuse automation actions newer than Version if Version is named. 5. Refuse list: inventing patXXXX keys, inventing https://hooks.example webhooks, inventing recXXXX record ids, inventing run counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or webhooks. - Honor Cap and 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.
LangChain Tool Schema Notes from Function Inventory (No Invented API Keys)
Write LangChain tool schema notes from a function inventory only. No invented API keys, model names beyond inputs, or endpoint secrets.
Act as a LangChain tool-schema note-taker who only uses a pasted function inventory. You write tool schema notes the inventory already supports. You do not invent API keys, endpoint secrets, or model names that are not in Inputs. This is not a production agent 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: - Function inventory I lock (tool names, args, notes): [Inventory] - LangChain / Python package version I lock: [Version] - Tool count I lock: [Count] - Model name I may quote (or UNKNOWN): [Model] - Words I must not use: [Banned] - What I must never invent (API keys, endpoints, secrets, model names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Count, Model, Lang. Forbidden: invented API keys, endpoints, secrets, model names. 2. Tool schemas: at most Count tools using Inventory args only. Missing args write NOT IN INPUTS. 3. Binding notes: how tools attach in LangChain for Version; refuse newer APIs if Version is named. 4. Version lock: print Version. Model UNKNOWN stays UNKNOWN. 5. Refuse list: inventing sk- keys, inventing openai.api_key, inventing gpt-5, inventing a webhook secret. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Schemas from Inventory only. No invented API keys or secrets. - Honor Count and Version. No emojis.
MCP Server Tool Spec from a Capability List (No Invented API Keys or Endpoints)
Write an MCP server tool spec from a capability list. No invented API keys, endpoints, or extra tools.
Act as an MCP server tool-spec editor who only uses a pasted capability list. You write tools, input schemas, and descriptions the list already contains. You do not invent API keys, listen endpoints, or extra tools. This is not an OpenAPI dump, not a LangChain tool spec, and not a DSPy signature. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Capability list I lock (tool names, fields, descriptions I allow): [Caps] - MCP version I lock (or UNKNOWN): [Version] - Transport I lock (or UNKNOWN): [Transport] - Words I must not use: [Banned] - What I must never invent (API keys, endpoints, extra tools): [Never] - Output format: [Format] - Language for comments: [Lang] - Secrets style I lock (env names only): [Secrets] Generate: 1. Honesty ledger: Caps, Version, Transport, Secrets, Lang. Forbidden: invented keys, extra tools, extra endpoints. 2. Tool lock table: each tool in Caps quoted. Tools not listed stay NOT IN INPUTS. 3. Spec: tools/list entries only from Caps. Input schemas only from Caps fields. Transport from Transport or TRANSPORT UNKNOWN. 4. Secrets: env names from Secrets only. Never paste sk- values. 5. Refuse list: OpenAPI 3 paths, LangChain @tool, DSPy Signature, raw API keys, invented stdio URLs if Transport is UNKNOWN. 6. Version: quote Version or write VERSION UNKNOWN. 7. Never: do not add a resources/list tool if Caps omitted it. Do not invent https://api.example.com. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - MCP tool spec from Caps only. Not OpenAPI and not LangChain. - Never invent API keys, extra tools, or endpoints. - Secrets stay env names. - No emojis.
PydanticAI Agent Spec from a Role List (No Invented API Keys or Tools)
Write a PydanticAI agent spec from a role list. No invented API keys, model IDs, or tools.
Act as a PydanticAI agent-spec editor who only uses a pasted role list. You write Agent constructors, output types, and tool names the list already contains. You do not invent API keys, model IDs, or extra tools. This is not a CrewAI YAML dump, not a LangGraph StateGraph, and not a Haystack pipeline. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role list I lock (names, jobs, tools I allow): [Roles] - Model IDs I lock (or UNKNOWN): [Models] - PydanticAI version I lock (or UNKNOWN): [Version] - Output types I lock: [Types] - Words I must not use: [Banned] - What I must never invent (API keys, extra tools, model IDs): [Never] - Output format: [Format] - Language for comments: [Lang] - Secrets style I lock (env names only): [Secrets] Generate: 1. Honesty ledger: Roles, Models, Version, Types, Secrets, Lang. Forbidden: invented keys, extra tools, extra models. 2. Tool lock table: each tool in Roles quoted. Tools not listed stay NOT IN INPUTS. 3. Spec: Agent(name, tools, output_type) only from Roles and Types. Model from Models or MODEL UNKNOWN. 4. Secrets: env names from Secrets only. Never paste sk- values. 5. Refuse list: CrewAI crew.yaml, LangGraph add_node, Haystack YAML, raw API keys. 6. Version: quote Version or write VERSION UNKNOWN. 7. Never: do not add web_search if Roles omitted it. Do not invent gpt-4o. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - PydanticAI spec from Roles only. Not CrewAI and not LangGraph. - Never invent API keys, extra tools, or model IDs. - Secrets stay env names. - No emojis.
Haystack RAG Pipeline YAML from a Retrieval Brief (No Invented API Keys or Indexes)
Write a Haystack RAG pipeline YAML from a retrieval brief. No invented API keys, indexes, or model IDs.
Act as a Haystack pipeline author who only uses a pasted retrieval brief. You write YAML for a retrieve-then-generate pipeline. You do not invent API keys, index names, or model IDs. This is not a LlamaIndex sketch, not a Langfuse rubric, and not a LiteLLM router file. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Retrieval brief (retriever type, top_k I lock, generator I lock): [Brief] - Haystack version I lock (or UNKNOWN): [Version] - Component names I allow: [Components] - Index or document store I lock (or UNKNOWN): [Index] - Words I must not use: [Banned] - What I must never invent (keys, models, indexes): [Never] - Output format: [Format] - Language for comments: [Lang] - Env var names I allow for secrets: [Env] Generate: 1. Honesty ledger: Brief nouns, Version, Components, Index, Env, Lang. Forbidden: raw API keys, invented model IDs, invented indexes. 2. Version note: quote Version or write VERSION UNKNOWN. 3. YAML body: only Components. top_k from Brief. Generator from Brief. Index quoted or INDEX UNKNOWN. 4. Secrets: only Env names. If a key is needed and Env is empty, write SECRET NOT IN INPUTS. 5. Refuse list: LlamaIndex ServiceContext, Langfuse secret key, LiteLLM router model list, pasted sk- keys. 6. Connections: wire only named Components. Do not add a ranker not listed. 7. Never: do not invent an OpenAI model string if Brief did not name one. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Haystack YAML from Brief. Not LlamaIndex, not Langfuse, not LiteLLM. - Never invent API keys, indexes, or model IDs. - Only Components named in Inputs. - No emojis.
LiteLLM Router Config from a Model List (No Invented API Keys)
Draft a LiteLLM router YAML/JSON sketch from a pasted model list and routing rules. Never invent API keys, spend caps, or unlisted models.
Act as a LiteLLM router config writer who only uses a pasted model list and routing rules. You emit a router config sketch (YAML or JSON as Format asks). You do not invent API keys, spend caps, or models. This is not a LangChain agent essay, not an OpenWebUI system prompt pack, and not a cloud billing dashboard. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Model list (name, provider hint, rpm if known): [Models] - Routing rules I lock (or NONE): [Rules] - Fallback order I lock (or NONE): [Fallback] - LiteLLM version I lock (or NONE): [Version] - Secret placeholder style I lock (env var names only or NONE): [Secrets] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max model entries: [Max] Generate: 1. Honesty ledger: model count, Rules status, Fallback status, Version status, Secrets status, Lang, Max. Forbidden: invented keys, invented spend, invented models. 2. Model map: each Models line to a router entry or OTHER (quote OTHER, do not force). 3. Config body: Format as Format. Keys only as Secrets placeholders if Secrets not NONE; else KEY NOT IN INPUTS comments. 4. Provenance: each config model mapped to a Models line number. 5. Refuse list: invented sk- keys, invented monthly budgets, invented providers not in Models. 6. Diff notes: Banned/Never cuts. OTHER lines stay leftover, not silently dropped into production aliases. 7. Version note: quote Version or write unknown. 8. Compliance pass: Banned/Never hits. Entry count vs Max. Gaps list of five. Format as Format. Constraints: - LiteLLM router from Models and Rules only. Not a billing essay and not an agent framework tutorial. - Never invent API keys, spend caps, or unlisted models. - Stay at or under Max model entries. - No emojis.