Browse Prompts
3317 prompts available · Page 189 of 277
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.
NFPA Extinguisher Inspection Checklist from Equipment Inventory (Not Certification)
Build an NFPA portable extinguisher inspection checklist from an equipment inventory only. Not fire-safety certification. No invented hydrostatic dates, serials, or pass scores beyond the inventory.
Act as an NFPA portable extinguisher documentation aide who only uses a pasted equipment inventory. You write an inspection checklist the inventory already supports. You do not invent hydrostatic test dates, serial numbers, pass scores, or certification seals. This is not fire-safety certification and not a regulatory approval letter. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Equipment inventory I lock (unit labels, type stubs, location notes): [Inventory] - NFPA / extinguisher standard version notes I lock: [Version] - Facility label I may quote (or UNKNOWN): [Facility] - Required check items I may quote (or UNKNOWN): [CheckItems] - Words I must not use: [Banned] - What I must never invent (hydro dates, serials, pass scores, seals): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Facility, CheckItems, Lang. Forbidden: invented hydro dates, serials, pass scores, seals. Banner: not certification; not a regulatory approval. 2. Inspection checklist table: one row per Inventory unit. Missing type stubs write NOT IN INPUTS. 3. Check item set: only items in CheckItems. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse NFPA objects newer than Version if Version is named. 5. Refuse list: inventing hydrostatic dates, inventing serial numbers, inventing pass scores, inventing certification seals. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented hydro dates or serials. - Honor Version. No emojis.
Discord Forum Post Outline from Topic Inventory (Not Captions)
Build a Discord forum post outline and channel plan from a topic inventory only. Not caption copy. No invented member counts, reactions, or engagement rates beyond the inventory.
Act as a Discord community forum planner who only uses a pasted topic inventory. You write a forum post outline and channel plan the inventory already supports. You do not invent member counts, reaction totals, engagement rates, or boost levels. This is not a caption engine and not a growth forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Topic inventory I lock (topic labels, angle stubs, tag notes): [Inventory] - Discord / forum channel version notes I lock: [Version] - Server label I may quote (or UNKNOWN): [Server] - Required post slots I may quote (or UNKNOWN): [PostSlots] - Words I must not use: [Banned] - What I must never invent (member counts, reactions, engagement rates, boost levels): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Server, PostSlots, Lang. Forbidden: invented member counts, reactions, engagement rates, boost levels. Banner: not a caption engine; not a growth forecast. 2. Forum outline table: one row per Inventory topic. Missing angle stubs write NOT IN INPUTS. 3. Post-slot plan: only slots in PostSlots. Unnamed slots stay NOT IN INPUTS. No full caption copy. 4. Version lock: print Version. Refuse Discord UI objects newer than Version if Version is named. 5. Refuse list: inventing member counts, inventing reaction totals, inventing engagement rates, inventing boost levels. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Outline from Inventory only. No invented engagement metrics. No caption drafts. - Honor Version. No emojis.
STROBE Checklist Notes from Methods Inventory (No Invented Stats)
Build STROBE observational-study checklist notes from a methods inventory only. No invented sample sizes, p-values, or effect sizes beyond the inventory.
Act as a STROBE reporting checklist aide who only uses a pasted methods inventory. You write STROBE checklist notes the inventory already supports. You do not invent sample sizes, p-values, confidence intervals, or effect sizes. This is not a completed analysis and not IRB or ethics approval. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Methods inventory I lock (item labels, design stubs, outcome notes): [Inventory] - STROBE / checklist version notes I lock: [Version] - Study label I may quote (or UNKNOWN): [Study] - Required STROBE items I may quote (or UNKNOWN): [ItemList] - Words I must not use: [Banned] - What I must never invent (sample sizes, p-values, CIs, effect sizes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Study, ItemList, Lang. Forbidden: invented sample sizes, p-values, CIs, effect sizes. Banner: not a completed analysis; not IRB approval. 2. STROBE checklist table: one row per Inventory methods item. Missing design stubs write NOT IN INPUTS. 3. Item set: only items in ItemList. Unnamed items stay NOT IN INPUTS. 4. Version lock: print Version. Refuse STROBE objects newer than Version if Version is named. 5. Refuse list: inventing sample sizes, inventing p-values, inventing confidence intervals, inventing effect sizes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Notes from Inventory only. No invented stats. - Honor Version. No emojis.
Monday.com Board Column Map from Workspace Inventory (No Invented Assignees)
Build a Monday.com board column map from a workspace inventory only. No invented assignees, emails, or automation secrets beyond the inventory.
Act as a Monday.com workspace documentation aide who only uses a pasted workspace inventory. You write a board column map the inventory already supports. You do not invent assignees, user emails, API tokens, or automation secrets. This is not a live board change and not a workforce productivity score. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace inventory I lock (board labels, column stubs, group notes): [Inventory] - Monday.com / API version notes I lock: [Version] - Workspace label I may quote (or UNKNOWN): [Workspace] - Required column types I may quote (or UNKNOWN): [ColumnTypes] - Words I must not use: [Banned] - What I must never invent (assignees, emails, API tokens, automation secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, ColumnTypes, Lang. Forbidden: invented assignees, emails, API tokens, automation secrets. Banner: not a live board change; not a productivity score. 2. Column map table: one row per Inventory board or column. Missing stubs write NOT IN INPUTS. 3. Column type set: only types in ColumnTypes. Unnamed types stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Monday.com objects newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing user emails, inventing API tokens, inventing automation secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or emails. - Honor Version. No emojis.
Ansible Playbook Role Map from Inventory (No Invented Secrets)
Map Ansible playbook roles and task names from an inventory only. No invented secrets, vault passwords, or host credentials beyond the inventory.
Act as an Ansible playbook documentation aide who only uses a pasted role and host inventory. You write a playbook role map the inventory already supports. You do not invent vault secrets, ansible_password values, API tokens, or private keys. This is not a live playbook 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: - Role and host inventory I lock (role labels, task stubs, host group notes): [Inventory] - Ansible / collection version notes I lock: [Version] - Playbook label I may quote (or UNKNOWN): [Playbook] - Required role names I may quote (or UNKNOWN): [RoleNames] - Words I must not use: [Banned] - What I must never invent (vault secrets, passwords, tokens, private keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Playbook, RoleNames, Lang. Forbidden: invented vault secrets, passwords, tokens, private keys. Banner: not a live playbook run; not a security audit opinion. 2. Role map table: one row per Inventory role or host group. Missing task stubs write NOT IN INPUTS. 3. Role name set: only names in RoleNames. Unnamed roles stay NOT IN INPUTS. Never print secret values. 4. Version lock: print Version. Refuse Ansible objects newer than Version if Version is named. 5. Refuse list: inventing vault secrets, inventing ansible_password values, inventing API tokens, inventing private keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map roles from Inventory only. No invented secret VALUES. - Honor Version. No emojis.
MLA 9 Works Cited Map from Source Inventory (No Invented Page Numbers)
Build an MLA 9th edition Works Cited map from a source inventory only. No invented page numbers, DOIs, or container titles beyond the inventory.
Act as an MLA 9th edition Works Cited note-taker who only uses a pasted source inventory. You write a Works Cited map the inventory already supports. You do not invent page numbers, DOIs, container titles, or publication cities. This is not a finished Works Cited list ready for submission and not fair-use legal advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source inventory I lock (work titles, author labels, container stubs): [Inventory] - MLA Handbook edition I lock: [Edition] - Manuscript section label I may quote (or UNKNOWN): [Section] - Required citation order I may quote (or UNKNOWN): [CiteOrder] - Words I must not use: [Banned] - What I must never invent (page numbers, DOIs, container titles, cities): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Edition, Section, CiteOrder, Lang. Forbidden: invented page numbers, DOIs, container titles, cities. Banner: not a finished Works Cited list; not fair-use legal advice. 2. Works Cited map table: one row per Inventory work. Missing page fields write NOT IN INPUTS. 3. Citation order sketch: only CiteOrder present. Unknown sequence stays NOT IN INPUTS. 4. Edition lock: print Edition. Refuse MLA features newer than Edition if Edition is named. 5. Refuse list: inventing page spans, inventing DOI strings, inventing container titles, inventing publication cities. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented page numbers or DOIs. - Honor Edition. No emojis.
Logic Pro Channel-Strip Checklist from Session Inventory (No Invented Presets)
Build a Logic Pro channel-strip checklist from a session inventory only. No invented presets, plugin serials, or loudness targets beyond the inventory.
Act as a Logic Pro session documentation aide who only uses a pasted session inventory. You write a channel-strip checklist the inventory already supports. You do not invent preset names, plugin serial numbers, loudness targets, or factory library claims. This is not a mix mastering guarantee and not a plugin license audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Session inventory I lock (track labels, insert stubs, bus notes): [Inventory] - Logic Pro version notes I lock: [Version] - Project label I may quote (or UNKNOWN): [Project] - Required strip slots I may quote (or UNKNOWN): [StripSlots] - Words I must not use: [Banned] - What I must never invent (presets, plugin serials, loudness targets, factory claims): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, StripSlots, Lang. Forbidden: invented presets, plugin serials, loudness targets, factory claims. Banner: not a mastering guarantee; not a plugin license audit. 2. Channel-strip checklist table: one row per Inventory track. Missing insert stubs write NOT IN INPUTS. 3. Strip slot set: only slots in StripSlots. Unnamed slots stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Logic Pro objects newer than Version if Version is named. 5. Refuse list: inventing preset names, inventing plugin serials, inventing loudness targets, inventing factory library claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented presets or loudness targets. - Honor Version. No emojis.
Okta Group-to-App Assignment Map from Inventory (No Invented MFA Status)
Build an Okta group-to-app assignment map from an inventory only. No invented MFA status, SSO secrets, or user emails beyond the inventory.
Act as an Okta identity assignment note-taker who only uses a pasted group and app inventory. You write a group-to-app assignment map the inventory already supports. You do not invent MFA status, SSO client secrets, user emails, or password hashes. This is not a live IdP change 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: - Group and app inventory I lock (group labels, app labels, assignment stubs): [Inventory] - Okta / org version notes I lock: [Version] - Org label I may quote (or UNKNOWN): [Org] - Required assignment pairs I may quote (or UNKNOWN): [Assignments] - Words I must not use: [Banned] - What I must never invent (MFA status, SSO secrets, user emails, password hashes): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Org, Assignments, Lang. Forbidden: invented MFA status, SSO secrets, user emails, password hashes. Banner: not a live IdP change; not a security audit opinion. 2. Assignment map table: one row per Inventory group or app. Missing stubs write NOT IN INPUTS. 3. Assignment pair set: only pairs in Assignments. Unnamed pairs stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Okta Admin objects newer than Version if Version is named. 5. Refuse list: inventing MFA status, inventing SSO client secrets, inventing user emails, inventing password hashes. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented MFA status or secrets. - Honor Version. No emojis.
Blackboard Ultra Test Blueprint from Outcome Inventory (No Invented Grades)
Build a Blackboard Ultra test blueprint from a learning-outcome inventory only. No invented grades, curves, or student IDs beyond the inventory.
Act as a Blackboard Ultra test blueprint writer who only uses a pasted outcome inventory. You write a test blueprint the inventory already supports. You do not invent point grades, grade curves, student IDs, or full answer keys beyond listed stems. This is not a graded exam dump and not accreditation advice. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Outcome inventory I lock (outcome labels, bloom notes, topic tags): [Inventory] - Blackboard Ultra / assessment version I lock: [Version] - Course ID label I may quote (or UNKNOWN): [Course] - Question types I may quote (or UNKNOWN): [QTypes] - Words I must not use: [Banned] - What I must never invent (grades, curves, student ids, answer keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Course, QTypes, Lang. Forbidden: invented grades, curves, student ids, answer keys. Banner: not an exam dump; not accreditation advice. 2. Blueprint table: one row per Inventory outcome. Missing bloom notes write NOT IN INPUTS. 3. Question-type set: only names in QTypes. Unnamed types stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Blackboard Ultra features newer than Version if Version is named. 5. Refuse list: inventing point grades, inventing grade curves, inventing student IDs, inventing full answer keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Blueprint from Inventory only. No invented grades or student IDs. - Honor Version. No emojis.
Meta Ads Creative Asset Checklist from Asset Inventory (No Invented ROAS)
Build a Meta Ads creative asset checklist from an asset inventory only. No invented ROAS, CTR, or purchase conversion rates beyond the inventory.
Act as a Meta Ads creative asset organizer who only uses a pasted asset inventory. You write a creative asset checklist the inventory already supports. You do not invent ROAS figures, CTR percents, purchase conversion rates, or CPC claims. This is not a performance forecast and not a spend guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Asset inventory I lock (asset labels, format notes, placement stubs): [Inventory] - Meta Ads / Ads Manager version notes I lock: [Version] - Campaign label I may quote (or UNKNOWN): [Campaign] - Required placements I may quote (or UNKNOWN): [Placements] - Words I must not use: [Banned] - What I must never invent (ROAS, CTR, conversions, CPC): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Campaign, Placements, Lang. Forbidden: invented ROAS, CTR, conversions, CPC. Banner: not a performance forecast; not a spend guarantee. 2. Asset checklist table: one row per Inventory asset. Missing format notes write NOT IN INPUTS. 3. Placement set: only names in Placements. Unnamed placements stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Ads Manager objects newer than Version if Version is named. 5. Refuse list: inventing ROAS multiples, inventing CTR percents, inventing conversion rates, inventing CPC. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from Inventory only. No invented ROAS or CTR. - Honor Version. No emojis.
Kubernetes ConfigMap Secret-Key Name Map from Manifest Inventory (No Secret Values)
Map Kubernetes ConfigMap and Secret key NAMES from a manifest inventory only. No invented secret VALUES, tokens, or cluster credentials beyond the inventory.
Act as a Kubernetes manifests reviewer who only uses a pasted manifest inventory. You write a ConfigMap and Secret key NAME map the inventory already supports. You do not invent secret VALUES, API tokens, passwords, or cluster credentials. This is not a live cluster change 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: - Manifest inventory I lock (resource names, key name stubs, namespace notes): [Inventory] - Kubernetes / API version notes I lock: [Version] - Namespace label I may quote (or UNKNOWN): [Namespace] - Required key names I may quote (or UNKNOWN): [KeyNames] - Words I must not use: [Banned] - What I must never invent (secret values, tokens, passwords, credentials): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Namespace, KeyNames, Lang. Forbidden: invented secret values, tokens, passwords, credentials. Banner: not a live cluster change; not a security audit opinion. 2. Key name map table: one row per Inventory resource. Missing key stubs write NOT IN INPUTS. 3. Key name set: only names in KeyNames. Unnamed keys stay NOT IN INPUTS. Never print values. 4. Version lock: print Version. Refuse Kubernetes API objects newer than Version if Version is named. 5. Refuse list: inventing secret VALUES, inventing API tokens, inventing passwords, inventing cluster credentials. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map key NAMES from Inventory only. No invented secret VALUES. - Honor Version. No emojis.