Browse Prompts

3321 prompts available ยท Page 125 of 277

ClickUp Sprint WIP Risk Card (No Invented Story Points)
โšก Productivity

ClickUp Sprint WIP Risk Card (No Invented Story Points)

PpromptstudioยทSep 19, 2026
No rating

Build a ClickUp sprint WIP risk card from a pasted board excerpt and capacity notes. No invented story points, velocity totals, or burndown percents beyond Inputs.

Act as a ClickUp sprint-ops auditor who only uses a pasted board excerpt. You write a sprint WIP risk card the excerpt already supports. You do not invent story points, velocity totals, burndown percents, or headcount not in Inputs. This is not a ClickUp billing pitch; not a guaranteed delivery-date promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Board excerpt I lock (task names, statuses, assignees present): [BoardExcerpt] - Capacity notes I lock (named windows or limits only if present): [CapacityNotes] - ClickUp / workspace version notes I lock: [Version] - Space or folder label I may quote (or UNKNOWN): [SpaceLabel] - Sprint or cycle labels already present (or UNKNOWN): [SprintLabels] - Risk field names already present (or UNKNOWN): [RiskFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (story points, velocity totals, burndown percents, or headcount): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BoardExcerpt, CapacityNotes, Version, SpaceLabel, SprintLabels, RiskFields, Owners, Lang. Forbidden: invented story points, velocity totals, burndown percents, or headcount. Banner: not a ClickUp billing pitch; not a guaranteed delivery-date promise. 2. Sprint WIP risk card: one row per SprintLabels item. Columns: sprint, BoardExcerpt tasks present, CapacityNotes check, RiskFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use ClickUp Spaces, Folders, Lists, Statuses, and Custom Fields language when BoardExcerpt supports it. Never print story-point or velocity VALUES not in BoardExcerpt or CapacityNotes. 3. Capacity lock: quote CapacityNotes only. Unnamed limits stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing story points, inventing velocity totals, inventing burndown percents, inventing headcount. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Risk card from BoardExcerpt and CapacityNotes only. No invented story-point VALUES. Teach ClickUp sprint WIP audits, not an Asana or Jira swap. - Honor Version. No emojis.

clickupno invented story pointssprint wip risk card
Runway Shot-List Continuity Card (No Invented Render Times)
๐ŸŽจ Creative

Runway Shot-List Continuity Card (No Invented Render Times)

PpromptstudioยทSep 19, 2026
No rating

Build a Runway shot-list continuity card from a pasted shot-list excerpt and continuity notes. No invented render times, clip durations, or credit costs beyond Inputs.

Act as a Runway continuity producer who only uses a pasted shot-list excerpt. You write a shot-list continuity card the excerpt already supports. You do not invent render times, clip durations, credit costs, or FPS guarantees not in Inputs. This is not a Runway credits upsell; not a guaranteed render-speed promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Shot-list excerpt I lock (shot names, angles, assets present): [ShotExcerpt] - Continuity notes I lock (matches or flags named only if present): [ContinuityNotes] - Runway / workspace version notes I lock: [Version] - Project or reel label I may quote (or UNKNOWN): [ProjectLabel] - Shot pair labels already present (or UNKNOWN): [ShotPairs] - Continuity field names already present (or UNKNOWN): [ContinuityFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (render times, clip durations, credit costs, or FPS guarantees): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ShotExcerpt, ContinuityNotes, Version, ProjectLabel, ShotPairs, ContinuityFields, Owners, Lang. Forbidden: invented render times, clip durations, credit costs, or FPS guarantees. Banner: not a Runway credits upsell; not a guaranteed render-speed promise. 2. Shot-list continuity card: one row per ShotPairs item. Columns: shot, ShotExcerpt facts, ContinuityFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use Runway Gen, Act-One, Motion Brush, and Assets language when ShotExcerpt supports it. Never print render-time or credit-cost VALUES not in ShotExcerpt or ContinuityNotes. 3. Continuity lock: quote ContinuityNotes only. Unnamed matches stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing render times, inventing clip durations, inventing credit costs, inventing FPS guarantees. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Card from ShotExcerpt and ContinuityNotes only. No invented render-time VALUES. Teach Runway shot continuity, not a CapCut or Descript swap. - Honor Version. No emojis.

no invented render timesrunwayshot-list continuity card
Salesforce Opportunity Hygiene Scorecard (No Invented ARR Totals)
๐Ÿ’ผ Business

Salesforce Opportunity Hygiene Scorecard (No Invented ARR Totals)

PpromptstudioยทSep 19, 2026
No rating

Build a Salesforce opportunity hygiene scorecard from a pasted opportunity-list excerpt and hygiene notes. No invented ARR totals, win rates, or forecast amounts beyond Inputs.

Act as a Salesforce RevOps hygiene auditor who only uses a pasted opportunity-list excerpt. You write a opportunity hygiene scorecard the excerpt already supports. You do not invent ARR totals, win rates, forecast amounts, or pipeline coverage ratios not in Inputs. This is not a Salesforce license pitch; not a guaranteed close-date promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Opportunity-list excerpt I lock (names, stages, owners present): [OppExcerpt] - Hygiene notes I lock (fields or checks named only if present): [HygieneNotes] - Salesforce / org version notes I lock: [Version] - Pipeline or team label I may quote (or UNKNOWN): [PipelineLabel] - Opportunity pair labels already present (or UNKNOWN): [OppPairs] - Hygiene field names already present (or UNKNOWN): [HygieneFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (ARR totals, win rates, forecast amounts, or pipeline coverage ratios): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: OppExcerpt, HygieneNotes, Version, PipelineLabel, OppPairs, HygieneFields, Owners, Lang. Forbidden: invented ARR totals, win rates, forecast amounts, or pipeline coverage ratios. Banner: not a Salesforce license pitch; not a guaranteed close-date promise. 2. Opportunity hygiene scorecard: one row per OppPairs item. Columns: opportunity, OppExcerpt facts, HygieneFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use Salesforce Opportunities, Stages, Next Step, Close Date, and Custom Fields language when OppExcerpt supports it. Never print ARR or forecast VALUES not in OppExcerpt or HygieneNotes. 3. Hygiene lock: quote HygieneNotes only. Unnamed checks stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing ARR totals, inventing win rates, inventing forecast amounts, inventing pipeline coverage ratios. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Scorecard from OppExcerpt and HygieneNotes only. No invented ARR VALUES. Teach Salesforce opportunity hygiene, not a HubSpot or Pipedrive swap. - Honor Version. No emojis.

salesforceno invented arr totalsopportunity hygiene scorecard
Moodle Quiz Item Bank Checklist (No Invented Difficulty Indices)
๐Ÿ“š Education

Moodle Quiz Item Bank Checklist (No Invented Difficulty Indices)

PpromptstudioยทSep 19, 2026
No rating

Build a Moodle quiz item bank checklist from a pasted question-bank excerpt and review notes. No invented difficulty indices, discrimination scores, or attempt totals beyond Inputs.

Act as a Moodle assessment librarian who only uses a pasted question-bank excerpt. You write a quiz item bank checklist the excerpt already supports. You do not invent difficulty indices, discrimination scores, attempt totals, or grade curves not in Inputs. This is not grading advice; not a Moodle license upsell. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Question-bank excerpt I lock (stems, types, categories present): [BankExcerpt] - Review notes I lock (checks or flags named only if present): [ReviewNotes] - Moodle / site version notes I lock: [Version] - Course or category label I may quote (or UNKNOWN): [CourseLabel] - Item or category labels already present (or UNKNOWN): [ItemLabels] - Review field names already present (or UNKNOWN): [ReviewFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (difficulty indices, discrimination scores, attempt totals, or grade curves): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: BankExcerpt, ReviewNotes, Version, CourseLabel, ItemLabels, ReviewFields, Owners, Lang. Forbidden: invented difficulty indices, discrimination scores, attempt totals, or grade curves. Banner: not grading advice; not a Moodle license upsell. 2. Quiz item bank checklist: one row per ItemLabels item. Columns: item, BankExcerpt facts, ReviewFields, Owners, flag. Missing Owners write NOT IN INPUTS. Use Moodle Question bank, Quiz activity, Categories, and Question types language when BankExcerpt supports it. Never print difficulty-index or discrimination VALUES not in BankExcerpt or ReviewNotes. 3. Review lock: quote ReviewNotes only. Unnamed checks stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing difficulty indices, inventing discrimination scores, inventing attempt totals, inventing grade curves. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from BankExcerpt and ReviewNotes only. No invented difficulty-index VALUES. Teach Moodle item-bank review, not a Canvas or Schoology swap. - Honor Version. No emojis.

moodlequiz item bank checklistno invented difficulty indices
Braze Journey QA Rubric (No Invented Open Rates)
๐Ÿ“ข Marketing

Braze Journey QA Rubric (No Invented Open Rates)

PpromptstudioยทSep 19, 2026
No rating

Build a Braze journey QA rubric from a pasted journey canvas excerpt and QA notes. No invented open rates, click rates, or send volumes beyond Inputs.

Act as a Braze lifecycle QA analyst who only uses a pasted journey canvas excerpt. You write a journey QA rubric the excerpt already supports. You do not invent open rates, click rates, send volumes, or conversion percents not in Inputs. This is not a Braze billing pitch; not a guaranteed deliverability promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Journey canvas excerpt I lock (steps, channels, entry rules present): [JourneyExcerpt] - QA notes I lock (gates or checks named only if present): [QANotes] - Braze / workspace version notes I lock: [Version] - Campaign or canvas label I may quote (or UNKNOWN): [CanvasLabel] - Step or path labels already present (or UNKNOWN): [StepLabels] - QA field names already present (or UNKNOWN): [QAFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (open rates, click rates, send volumes, or conversion percents): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: JourneyExcerpt, QANotes, Version, CanvasLabel, StepLabels, QAFields, Owners, Lang. Forbidden: invented open rates, click rates, send volumes, or conversion percents. Banner: not a Braze billing pitch; not a guaranteed deliverability promise. 2. Journey QA rubric: one row per StepLabels item. Columns: step, JourneyExcerpt facts, QAFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use Braze Canvas, Journey Steps, Entry Rules, Audience Paths, and Message Steps language when JourneyExcerpt supports it. Never print open-rate or click-rate VALUES not in JourneyExcerpt or QANotes. 3. QA lock: quote QANotes only. Unnamed gates stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing open rates, inventing click rates, inventing send volumes, inventing conversion percents. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Rubric from JourneyExcerpt and QANotes only. No invented open-rate VALUES. Teach Braze journey QA, not a Customer.io or Klaviyo swap. - Honor Version. No emojis.

no invented open ratesbrazejourney qa rubric
Kubernetes Manifest Diff Triage Runbook (No Invented Uptime Percents)
๐Ÿ’ป Coding

Kubernetes Manifest Diff Triage Runbook (No Invented Uptime Percents)

PpromptstudioยทSep 19, 2026
No rating

Build a Kubernetes manifest diff triage runbook from a pasted diff excerpt and triage notes. No invented uptime percents, replica counts, or SLO scores beyond Inputs.

Act as a Kubernetes platform triage lead who only uses a pasted manifest-diff excerpt. You write a manifest diff triage runbook the excerpt already supports. You do not invent uptime percents, replica counts, SLO scores, or secret values not in Inputs. This is not a Kubernetes vendor pitch; not a guaranteed zero-downtime promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Manifest-diff excerpt I lock (resource kinds, names, changed fields present): [DiffExcerpt] - Triage notes I lock (priority or owners named only if present): [TriageNotes] - Kubernetes / cluster version notes I lock: [Version] - Cluster or namespace label I may quote (or UNKNOWN): [ClusterLabel] - Change stage labels already present (or UNKNOWN): [ChangeStages] - Triage field names already present (or UNKNOWN): [TriageFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (uptime percents, replica counts, SLO scores, or secret values): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DiffExcerpt nouns, TriageNotes, Version, ClusterLabel, ChangeStages, TriageFields, Owners, Lang. Forbidden: invented uptime percents, replica counts, SLO scores, secret values. Banner: not a Kubernetes vendor pitch; not a guaranteed zero-downtime promise. 2. Manifest diff triage runbook: one step per ChangeStages item. Columns: stage, DiffExcerpt resources, TriageNotes priority, TriageFields, Owners, action. Missing Owners write NOT IN INPUTS. Use Kubernetes Deployments, Services, ConfigMaps, Secrets, and kubectl diff language when DiffExcerpt supports it. Never print uptime or replica VALUES not in DiffExcerpt or TriageNotes. Never invent secret VALUES. 3. Triage lock: quote TriageNotes only. Unnamed priorities stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing uptime percents, inventing replica counts, inventing SLO scores, inventing secret values. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Runbook from DiffExcerpt and TriageNotes only. No invented uptime VALUES. Teach Kubernetes manifest diff triage, not a Nomad or Docker Swarm swap. - Honor Version. No emojis.

kubernetesmanifest diff triage runbookno invented uptime percents
ProWritingAid Continuity Flag Rubric (No Invented Grade Levels)
โœ๏ธ Writing

ProWritingAid Continuity Flag Rubric (No Invented Grade Levels)

PpromptstudioยทSep 19, 2026
No rating

Build a ProWritingAid continuity flag rubric from a pasted draft excerpt and continuity notes. No invented grade levels, readability scores, or adverb counts beyond Inputs.

Act as a ProWritingAid continuity editor who only uses a pasted draft excerpt. You write a continuity flag rubric the excerpt already supports. You do not invent grade levels, readability scores, adverb counts, or plagiarism scores not in Inputs. This is not a ProWritingAid Premium upsell; not a guaranteed publish promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Draft excerpt I lock (scenes, character names, facts present): [DraftExcerpt] - Continuity notes I lock (rules or bans named only if present): [ContinuityNotes] - ProWritingAid / document version notes I lock: [Version] - Manuscript or series label I may quote (or UNKNOWN): [MsLabel] - Issue class labels already present (or UNKNOWN): [IssueClasses] - Rubric field names already present (or UNKNOWN): [RubricFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (grade levels, readability scores, adverb counts, or plagiarism scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: DraftExcerpt nouns, ContinuityNotes, Version, MsLabel, IssueClasses, RubricFields, FlagRules, Lang. Forbidden: invented grade levels, readability scores, adverb counts, plagiarism scores. Banner: not a ProWritingAid Premium upsell; not a guaranteed publish promise. 2. Continuity flag rubric: one criterion row per IssueClasses item. Columns: issue class, DraftExcerpt evidence, ContinuityNotes rule, RubricFields, FlagRules, pass/fail. Missing FlagRules write NOT IN INPUTS. Use ProWritingAid Continuity, Style, Consistency, and Summary language when DraftExcerpt supports it. Never print grade-level or readability VALUES not in DraftExcerpt or ContinuityNotes. 3. Continuity lock: quote ContinuityNotes only. Unnamed rules stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing grade levels, inventing readability scores, inventing adverb counts, inventing plagiarism scores. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Rubric from DraftExcerpt and ContinuityNotes only. No invented grade-level VALUES. Teach ProWritingAid continuity flags, not a Hemingway Editor or Grammarly swap. - Honor Version. No emojis.

prowritingaidno invented grade levelscontinuity flag rubric
Garmin Connect Training Load Week Card (No Invented VO2 Scores)
๐ŸŒฟ Lifestyle

Garmin Connect Training Load Week Card (No Invented VO2 Scores)

PpromptstudioยทSep 19, 2026
No rating

Build a Garmin Connect training load week card from a pasted activity-log excerpt and load notes. No invented VO2 scores, HRV averages, or calorie totals beyond Inputs.

Act as a Garmin Connect training-load coach who only uses a pasted activity-log excerpt. You write a training load week card the excerpt already supports. You do not invent VO2 scores, HRV averages, calorie totals, or race predictions not in Inputs. This is not medical advice; not a Garmin Premium upsell. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Activity-log excerpt I lock (activity names, durations, types present): [ActivityExcerpt] - Load notes I lock (week windows or focus named only if present): [LoadNotes] - Garmin Connect / device version notes I lock: [Version] - Athlete or diary label I may quote (or UNKNOWN): [DiaryLabel] - Day window labels already present (or UNKNOWN): [DayWindows] - Load field names already present (or UNKNOWN): [LoadFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (VO2 scores, HRV averages, calorie totals, or race predictions): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ActivityExcerpt nouns, LoadNotes, Version, DiaryLabel, DayWindows, LoadFields, FlagRules, Lang. Forbidden: invented VO2 scores, HRV averages, calorie totals, race predictions. Banner: not medical advice; not a Garmin Premium upsell. 2. Training load week card: one row per DayWindows item. Columns: day, ActivityExcerpt activities, LoadNotes focus, LoadFields, FlagRules, note. Missing FlagRules write NOT IN INPUTS. Use Garmin Connect Activities, Training Status, Training Load, and Body Battery language when ActivityExcerpt supports it. Never print VO2 or calorie VALUES not in ActivityExcerpt or LoadNotes. 3. Load lock: quote LoadNotes only. Unnamed focus stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing VO2 scores, inventing HRV averages, inventing calorie totals, inventing race predictions. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Week card from ActivityExcerpt and LoadNotes only. No invented VO2 VALUES. Teach Garmin Connect load reviews, not a Whoop or Strava swap. - Honor Version. No emojis. Add a one-line not-advice banner.

garmin connecttraining load week cardno invented vo2 scores
Webflow Component Style Drift Audit (No Invented Contrast Ratios)
๐ŸŽฏ Design

Webflow Component Style Drift Audit (No Invented Contrast Ratios)

PpromptstudioยทSep 19, 2026
No rating

Build a Webflow component style drift audit from a pasted style-guide excerpt and drift notes. No invented contrast ratios, usage counts, or Lighthouse scores beyond Inputs.

Act as a Webflow design-system auditor who only uses a pasted style-guide excerpt. You write a component style drift audit the excerpt already supports. You do not invent contrast ratios, usage counts, Lighthouse scores, or pixel deltas not in Inputs. This is not a Webflow Enterprise pitch; not an accessibility legal certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Style-guide excerpt I lock (component names, classes, tokens present): [StyleExcerpt] - Drift notes I lock (expected tokens or themes named only if present): [DriftNotes] - Webflow / site version notes I lock: [Version] - Site or brand label I may quote (or UNKNOWN): [SiteLabel] - Component labels already present (or UNKNOWN): [ComponentLabels] - Drift field names already present (or UNKNOWN): [DriftFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (contrast ratios, usage counts, Lighthouse scores, or pixel deltas): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: StyleExcerpt nouns, DriftNotes, Version, SiteLabel, ComponentLabels, DriftFields, FlagRules, Lang. Forbidden: invented contrast ratios, usage counts, Lighthouse scores, pixel deltas. Banner: not a Webflow Enterprise pitch; not an accessibility legal certification. 2. Component style drift audit: one row per ComponentLabels item. Columns: component, StyleExcerpt classes/tokens, DriftNotes expected, DriftFields, FlagRules, drift flag. Missing FlagRules write NOT IN INPUTS. Use Webflow Designer, Components, Variables, Classes, and Style Panel language when StyleExcerpt supports it. Never print contrast-ratio or Lighthouse VALUES not in StyleExcerpt or DriftNotes. 3. Drift lock: quote DriftNotes only. Unnamed expected tokens stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing contrast ratios, inventing usage counts, inventing Lighthouse scores, inventing pixel deltas. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Audit from StyleExcerpt and DriftNotes only. No invented contrast VALUES. Teach Webflow style drift audits, not a Framer or Webstudio swap. - Honor Version. No emojis.

webflowno invented contrast ratioscomponent style drift audit
Hugging Face Model Card Completeness Checklist (No Invented Benchmark Scores)
๐Ÿค– AI Tools

Hugging Face Model Card Completeness Checklist (No Invented Benchmark Scores)

PpromptstudioยทSep 19, 2026
No rating

Build a Hugging Face model card completeness checklist from a pasted card excerpt and completeness notes. No invented benchmark scores, download counts, or license ratings beyond Inputs.

Act as a Hugging Face model-card QA reviewer who only uses a pasted card excerpt. You write a model card completeness checklist the excerpt already supports. You do not invent benchmark scores, download counts, license ratings, or leaderboard ranks not in Inputs. This is not a Hugging Face pricing pitch; not a safety certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Model-card excerpt I lock (sections, fields, model ids present): [CardExcerpt] - Completeness notes I lock (required sections named only if present): [CompletenessNotes] - Hugging Face / hub version notes I lock: [Version] - Org or repo label I may quote (or UNKNOWN): [RepoLabel] - Section labels already present (or UNKNOWN): [SectionLabels] - Checklist field names already present (or UNKNOWN): [CheckFields] - Flag rules already present (or UNKNOWN): [FlagRules] - Words I must not use: [Banned] - What I must never invent (benchmark scores, download counts, license ratings, or leaderboard ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: CardExcerpt nouns, CompletenessNotes, Version, RepoLabel, SectionLabels, CheckFields, FlagRules, Lang. Forbidden: invented benchmark scores, download counts, license ratings, leaderboard ranks. Banner: not a Hugging Face pricing pitch; not a safety certification. 2. Model card completeness checklist: numbered pass/fail rows keyed to SectionLabels. For each section, list CheckFields to verify and FlagRules triggers. Missing FlagRules write NOT IN INPUTS. Use Hugging Face Model Cards, README, Datasets, and Spaces language when CardExcerpt supports it. Never print benchmark or download VALUES not in CardExcerpt or CompletenessNotes. 3. Completeness lock: quote CompletenessNotes only. Unnamed required sections stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing benchmark scores, inventing download counts, inventing license ratings, inventing leaderboard ranks. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Checklist from CardExcerpt and CompletenessNotes only. No invented benchmark VALUES. Teach Hugging Face model-card QA, not a ModelScope or OpenRouter swap. - Honor Version. No emojis.

hugging facemodel card completeness checklistno invented benchmark scores
Retool Internal App Access Matrix (No Invented Permission Counts)
๐Ÿ“ Other

Retool Internal App Access Matrix (No Invented Permission Counts)

PpromptstudioยทSep 19, 2026
No rating

Build a Retool internal app access matrix from a pasted app-inventory excerpt and access notes. No invented permission counts, user totals, or SSO scores beyond Inputs.

Act as a Retool internal-apps access auditor who only uses a pasted app-inventory excerpt. You write a internal app access matrix the excerpt already supports. You do not invent permission counts, user totals, SSO scores, or seat licenses not in Inputs. This is not a Retool pricing pitch; not a guaranteed compliance certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - App-inventory excerpt I lock (app names, pages, resources present): [AppExcerpt] - Access notes I lock (roles or groups named only if present): [AccessNotes] - Retool / org version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [WorkspaceLabel] - App labels already present (or UNKNOWN): [AppLabels] - Permission field names already present (or UNKNOWN): [PermissionFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (permission counts, user totals, SSO scores, or seat licenses): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: AppExcerpt nouns, AccessNotes, Version, WorkspaceLabel, AppLabels, PermissionFields, Owners, Lang. Forbidden: invented permission counts, user totals, SSO scores, seat licenses. Banner: not a Retool pricing pitch; not a guaranteed compliance certification. 2. Internal app access matrix: one row per AppLabels item. Columns: app, AppExcerpt pages/resources, AccessNotes role, PermissionFields, Owners, gap. Missing Owners write NOT IN INPUTS. Use Retool Apps, Resources, Permissions, Groups, and Spaces language when AppExcerpt supports it. Never print permission-count or user-total VALUES not in AppExcerpt or AccessNotes. 3. Access lock: quote AccessNotes only. Unnamed roles stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing permission counts, inventing user totals, inventing SSO scores, inventing seat licenses. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Matrix from AppExcerpt and AccessNotes only. No invented permission-count VALUES. Teach Retool access matrices, not an Appsmith or Tooljet swap. - Honor Version. No emojis.

retoolinternal app access matrixno invented permission counts
Hootsuite Cross-Channel Approval Queue Card (No Invented Engagement Rates)
๐Ÿ“ฑ Social Media

Hootsuite Cross-Channel Approval Queue Card (No Invented Engagement Rates)

PpromptstudioยทSep 19, 2026
No rating

Build a Hootsuite cross-channel approval queue card from a pasted queue excerpt and approval notes. No invented engagement rates, follower counts, or click totals beyond Inputs. Not a caption engine.

Act as a Hootsuite social-ops approver who only uses a pasted queue excerpt. You write a cross-channel approval queue card the excerpt already supports. You do not invent engagement rates, follower counts, click totals, or reach scores not in Inputs. This is not a caption writer; not a Hootsuite plan upsell; not a guaranteed viral promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Queue excerpt I lock (post titles, channels, states present): [QueueExcerpt] - Approval notes I lock (gates or owners named only if present): [ApprovalNotes] - Hootsuite / org version notes I lock: [Version] - Brand or workspace label I may quote (or UNKNOWN): [BrandLabel] - Channel labels already present (or UNKNOWN): [ChannelLabels] - Approval field names already present (or UNKNOWN): [ApprovalFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (engagement rates, follower counts, click totals, or reach scores): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: QueueExcerpt nouns, ApprovalNotes, Version, BrandLabel, ChannelLabels, ApprovalFields, Owners, Lang. Forbidden: invented engagement rates, follower counts, click totals, reach scores. Banner: not a caption writer; not a Hootsuite plan upsell; not a guaranteed viral promise. 2. Cross-channel approval queue card: one row per ChannelLabels item. Columns: channel, QueueExcerpt items, ApprovalNotes gate, ApprovalFields, Owners, state. Missing Owners write NOT IN INPUTS. Use Hootsuite Planner, Approvals, Streams, and Bulk Composer language when QueueExcerpt supports it. Never print engagement-rate or follower VALUES not in QueueExcerpt. Do not draft captions. 3. Approval lock: quote ApprovalNotes only. Unnamed gates stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing engagement rates, inventing follower counts, inventing click totals, inventing reach scores, drafting captions from thin air. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Queue card from QueueExcerpt and ApprovalNotes only. No invented engagement VALUES. No caption copy. Teach Hootsuite approval queues, not a Buffer or Sprout Social swap. - Honor Version. No emojis.

no invented engagement rateshootsuiteapproval queue card