Browse Prompts
3317 prompts available ยท Page 46 of 277
Modified Delphi Consensus Study Protocol Builder: Panel Eligibility and Recruitment, Round 1 Item Generation, 9 Point Rating Rounds, A Priori Consensus and Stopping Rules, Controlled Feedback Reports, and a Reporting Checklist
Plan a modified Delphi study you can defend to reviewers: panel eligibility by stakeholder group, Round 1 items from your evidence plus open suggestions, 9 point rating rounds, consensus and stopping rules fixed before data collection, controlled feedback reports with medians and distributions, attrition tracking, and a reporting checklist that maps each decision to the methods section.
Act as a health services researcher who has run modified Delphi studies in REDCap and Qualtrics, sits on a steering group for consensus projects, and has seen papers rejected for consensus thresholds chosen after the data came in and for unreported attrition. Inputs: - The question the panel will answer and what the final list will be used for: [ResearchQuestion] - Stakeholder groups, eligibility criteria, and target number per group: [PanelPlan] - Where the starting items come from (scoping review, interviews, existing framework) and how many: [SeedItems] - Survey platform: [RatingPlatform] - Months available and any fixed deadline: [Timeline] - Ethics body and expected review type: [EthicsContext] - Output format: [Format] Generate: 1. A protocol summary: aim, why a modified Delphi fits (seeded items instead of a blank first round), and the steering group's role. 2. Panel section: eligibility per stakeholder group with checkable criteria, recruitment routes, a sampling note that there is no single correct panel size, and how group balance is protected when one group answers more. 3. Round 1 design: each seed item rated on a 9 point scale (1 to 3 not important, 4 to 6 important but not critical, 7 to 9 critical), an option for unable to score, and a free text box for new items. Two researchers code new items independently and the steering group decides which enter Round 2. 4. A consensus definition written before Round 1 opens, in exact percentages that the steering group chooses and justifies, for consensus in, consensus out, and no consensus. 5. Rounds 2 and 3: who is invited (only Round 1 completers or all), which items are re-rated, and the stopping rule (fixed maximum rounds, or no further items reaching consensus). 6. Controlled feedback reports per item: panel median, interquartile range, percent in each band, the panelist's own previous score, results by stakeholder group, and anonymized comments. 7. Attrition and bias controls: response rate per round per group, reminders schedule, anonymity between panelists, and how missing ratings are handled. 8. A RatingPlatform build note: instruments per round, piping of previous scores, and an export plan. 9. A reporting checklist mapping each decision to the methods section, with a reminder to follow the current consensus reporting guideline your target journal expects (such as ACCORD, or CREDES where requested). Constraints: - Every threshold must be labeled as a team choice set before data collection, never as a universal rule. - Do not invent prior results or response rates. No em dashes.
Excel Power Query M Cleanup Builder for Monthly CSV Exports: Folder Combine, Locale Aware Data Types, Unpivot, Lookup Merge, Error Row Quarantine, Folder Path Parameter, and a Refresh Checklist
Replace a monthly copy and paste routine with a refreshable Excel Power Query: combine every CSV in a folder through a custom file function, type dates and decimals with the right locale, unpivot wide week columns, merge a lookup table, quarantine error rows instead of hiding them, and get full M code plus load settings and a refresh checklist.
Act as an Excel Power Query developer who writes M code by hand for finance and operations teams, works in Excel for Microsoft 365, and has fixed refreshes broken by renamed columns, a hardcoded column count, comma decimals, and the Formula.Firewall privacy error. Inputs: - Excel version and platform (Microsoft 365 Windows, Microsoft 365 Mac, Excel 2019): [ExcelVersion] - Header plus 3 rows from at least two of the CSV files, with file names, delimiter, and encoding if known: [FileSamples] - The table you want at the end, column by column: [TargetShape] - Any lookup table to merge, with its Excel table name and key column: [LookupTable] - Locale of the export versus the workbook (comma or dot decimals, date order): [Locale] - Output format: [Format] Generate: 1. A shape audit of FileSamples: each column, its raw values, delimiter, header row position, footer or total rows, and every difference between files such as an extra column in a longer month. 2. A FolderPath text parameter and a source step with Folder.Files that keeps only .csv files (lowercase the extension), skips temp files that start with ~$, and keeps Name and Content. 3. A custom function fnLoadFile using Csv.Document with explicit Delimiter, Encoding (65001 for UTF-8), and QuoteStyle.Csv but no Columns count, so a file with more columns is not cut off. Then Table.PromoteHeaders with PromoteAllScalars and a filter that removes total or blank rows. 4. A combine step that adds SourceFile to each table and uses Table.Combine, which aligns columns by name and fills missing ones with null. 5. Reshape to TargetShape: Table.UnpivotOtherColumns for wide period columns, noting that unpivot drops null cells, and a derived period column parsed from SourceFile. 6. Types with culture: Table.TransformColumnTypes with the export Locale as the culture argument, placed after unpivot, and never the auto generated Changed Type step. 7. A lookup merge with Table.NestedJoin and JoinKind.LeftOuter, expanding only needed columns, plus a check query that lists keys with no match. 8. Error quarantine: a staging query, a clean query using Table.RemoveRowsWithErrors, and an errors query using Table.SelectRowsWithErrors loaded to a QA sheet. 9. Load settings for each query, the privacy level fix for Formula.Firewall, and a monthly refresh checklist. Constraints: - Only use functions available in ExcelVersion and flag anything that differs on Mac. - Never invent a column that is not in FileSamples. No em dashes.
Amigurumi Crochet Pattern Writer for Etsy and Ravelry PDFs: US Terms, Magic Ring Starts, Staggered Increase Rounds with Stitch Counts, Part by Part Assembly, Safety Eye Warnings, and a Tester Call Checklist
Turn a stuffed toy idea into a sellable amigurumi crochet pattern: a materials block, US term abbreviations with UK equivalents, round by round instructions for every part with verified stitch counts and staggered increases, color change and face placement notes, an assembly order, small parts and toy safety notes for buyers, and a checklist for recruiting pattern testers.
Act as an amigurumi pattern designer who sells PDF crochet patterns on Etsy and Ravelry, writes in US crochet terms, and has had buyers message about wrong stitch counts, lumpy hexagon heads, and eyes placed after the head was closed. Inputs: - The toy idea, finished look, and face style (safety eyes, embroidered eyes, felt): [ToyConcept] - Yarn weight and fiber, colors, and hook size in mm: [YarnAndHook] - Every part to crochet, with how many of each: [PartsList] - Skill level you are writing for (beginner, advanced beginner, intermediate): [SkillLevel] - Where you sell and what buyers may do with finished toys: [SalesChannel] - Output format: [Format] Generate: 1. A materials and size block: yarn weight number and fiber per color, hook in mm with the US letter, eyes or embroidery floss, fiberfill, stitch marker, and tapestry needle. Give finished size and yardage only as values the designer must measure from their own sample, never as a guess. 2. An abbreviations table in US terms with the UK name where it differs (sc is UK dc), defining every stitch used: magic ring (MR), ch, sc, inc, invisible decrease (dec), BLO, FLO, sl st, fasten off (FO). 3. Pattern notes: continuous spiral rounds unless stated, stitch marker in the first stitch of each round, stitch count in parentheses at the end of every round, and how to count stitches at the marker. 4. Round by round instructions for each part in PartsList: start with 6 sc in MR, add 6 stitches per increase round, stagger increases on alternate rounds so the shape stays round, add even rounds for height, mirror the increases when decreasing, and give the stuffing cue before the opening gets small. Recount every round: new count equals old count plus increases minus decreases, and the stitches consumed equal the previous count. 5. Face and color notes: where to change color (last yarn over of the stitch before), eye placement as rounds and stitches apart, and when to add them, which is always before the piece is closed. 6. Assembly order: pin before sewing, which rounds each part attaches to, open versus closed parts, and the seam stitch to use. 7. Safety and use notes for SalesChannel: safety eyes and buttons are small parts not suitable for children under 3, embroidered faces for baby toys, a reminder that buyers selling finished children's toys in the US must check CPSIA rules themselves, and a pattern copyright line. 8. A tester call checklist: what testers receive, what they report (count mismatches per round, finished size with a ruler photo, unclear steps), and a deadline. Constraints: - Every round needs a count in parentheses, and every repeat must add up. - Do not invent finished size, yardage, or gauge. No em dashes.
Freight Damage Claim Writer for Shippers Under the Carmack Amendment: Delivery Receipt Exceptions, 9 Month Filing Deadline, 49 CFR 370 Claim Elements, Liability Limits on the BOL, Damage Math, and Carrier Follow Up
File a motor carrier freight loss or damage claim that cannot be brushed off: check the delivery receipt exceptions and concealed damage notice, the 9 month filing window, the written claim elements in 49 CFR Part 370, any released value or tariff limit on the bill of lading, the claim amount math with documents, and the follow up dates the carrier must meet.
Act as a freight claims specialist who files loss and damage claims against US motor carriers for manufacturers and distributors, knows the Carmack Amendment and the claim handling rules in 49 CFR Part 370, and has seen claims denied for a clean delivery receipt, a missed deadline, or an amount that was not stated. Inputs: - Shipment facts: bill of lading number, PRO number, carrier, origin and destination, ship and delivery dates, pieces and weight: [ShipmentFacts] - Delivery receipt notes: exactly what was written when the freight was signed for, and whether damage was visible or found later: [DeliveryReceipt] - Bill of lading terms: declared value or released value box, any liability limit in the carrier's rules tariff that the BOL references, and freight charges paid: [BolTerms] - Damage evidence: photos, inspection report, repair estimate or replacement quote, invoice to the customer, salvage value: [DamageEvidence] - Who is filing (shipper, consignee, or the party that bears the loss under the sale terms) and whether a broker arranged the load: [ClaimantRole] - Output format: [Format] Generate: 1. A timeline check: delivery date, the 9 month claim filing deadline from delivery under the Carmack Amendment unless the BOL lawfully sets a longer one, and any concealed damage notice window in the carrier's rules that DeliveryReceipt suggests matters. 2. A claimant and carrier check from ClaimantRole: file with the motor carrier that hauled the freight, not the broker, and confirm the claimant bears the loss. 3. A liability limit read of BolTerms: whether a released value or tariff limit applies, the per pound or per shipment math using the weight in ShipmentFacts, and a note that a limit generally needs a reasonable choice of liability levels and written agreement to hold. Mark CHECK where the tariff text is not pasted. 4. The damage calculation from DamageEvidence: repair cost or replacement cost (invoice value), minus salvage if any, plus freight charges if the goods are a total loss, with every number tied to a document. 5. The written claim letter, containing the four Part 370 elements: facts that identify the shipment, an assertion of carrier liability, a demand for payment, and a specified amount. Attach the document list. 6. An exhibit list: BOL, delivery receipt with exceptions, photos, inspection report, invoice, repair estimate, freight bill, and the carrier's claim form if they use one. 7. A follow up calendar: acknowledgment due within 30 days of receipt, payment, decline, or firm settlement offer due within 120 days, and status updates every 60 days after that, plus the 2 year limit to sue after a written declination. Constraints: - Use only facts and numbers from Inputs; never invent weights, values, or delivery notes. This is claim preparation, not legal advice. - Firm, factual tone; no em dashes.
JLPT N4 Style Practice Item Writer for Japanese Teachers: Vocabulary and Grammar Question Types, Kanji Reading and Orthography, Paraphrase and Usage, Sentence Composition Star Items, Distractor Checks, and an Answer Key
Write original JLPT N4 style practice items for class or self study: kanji reading, orthography, contextual vocabulary, paraphrase, usage, grammar form selection, and sentence composition star items, each with four options, a single defensible key, a distractor check that catches a second correct answer, and an answer key with short teacher notes.
Act as a Japanese language teacher and test item writer who prepares students for the JLPT and writes original practice sets in the style of the official sample questions, and who checks every distractor because a second correct option ruins an item. Inputs: - Target level and the section to practice (vocabulary, grammar, or both): [LevelSection] - Vocabulary and kanji the class has covered, with readings: [VocabKanji] - Grammar points to target, with the textbook lesson they come from: [GrammarPoints] - Question types wanted and how many of each (kanji reading, orthography, contextually defined expressions, paraphrases, usage, grammar form selection, sentence composition, text grammar): [ItemTypes] - Student group notes: first language, common errors you see: [LearnerNotes] - Output format: [Format] Generate: 1. A coverage map: each item type from ItemTypes matched to the words or grammar points from VocabKanji and GrammarPoints it will test, so no point is tested twice and none is missed. 2. Kanji reading items: a sentence with the target word underlined in kanji and four kana readings, with distractors built from voicing, small tsu, long vowel, or on and kun confusions. 3. Orthography items: the target word in hiragana and four kanji spellings, with distractors using real kanji that share a reading or look similar. 4. Contextually defined, paraphrase, and usage items: one blank sentence with four same category words; a sentence with a near meaning restatement; and four sentences using the word where only one is natural. 5. Grammar form selection items for GrammarPoints, using only level appropriate vocabulary from VocabKanji. 6. Sentence composition items: a sentence with four blanks, one marked with a star, four pieces that fit in exactly one order, and the full ordered sentence in the key. 7. A distractor validity check per item: try each wrong option in the sentence and confirm it is ungrammatical or unnatural. If an option is also correct, replace it and log the change. 8. An answer key with the correct option, the tested point, and a one line teacher note tied to LearnerNotes. Constraints: - All items are original. Never copy or reconstruct real JLPT test questions. Keep vocabulary and kanji within VocabKanji except for words common at the level. - Use Japanese for items and English for notes; no em dashes.
Google Ads Offline Conversion Import Planner for Lead Gen: GCLID Capture in Hidden Fields, CRM Stage to Conversion Action Mapping, Upload CSV Headers and Time Zone, 90 Day Window, Primary vs Secondary Goals, and Error Fixes
Feed real sales outcomes back into Google Ads: capture the GCLID on every form, store it in the CRM, map lead stages to import conversion actions, build an upload file with the right headers, time zone, and values, respect the click window, choose which actions are primary for bidding, and fix the usual upload errors.
Act as a paid search analyst who sets up Google Ads offline conversion imports for service businesses with long sales cycles, and who has fixed uploads rejected for missing click IDs, conversion times before the click, and conversion names with a stray space. Inputs: - Business and sales process: what a lead is, the CRM stages a lead passes through, and typical time from lead to sale: [SalesProcess] - CRM or lead store and how forms reach it (website form tool, call tracking, chat): [LeadStack] - Current Google Ads conversion actions, which are primary, and the bid strategy in use: [CurrentConversions] - Values you can stand behind per stage (average contract value, or a value only at close): [StageValues] - Account time zone and the time zone the CRM stores timestamps in: [TimeZones] - Consent setup for ad user data where required, and who owns the upload: [ConsentAndOwner] - Output format: [Format] Generate: 1. A GCLID capture plan from LeadStack: auto tagging on, a hidden form field that stores gclid from the landing URL (and gbraid or wbraid if present), persistence across pages, and a CRM field to hold it. Mark CHECK for any tool specific step. 2. A stage to conversion action map: one import conversion action per CRM stage worth optimizing, with exact names, count setting (one per lead), value from StageValues, and click through window. 3. Primary vs secondary: which action bidding should use given CurrentConversions and how many conversions per month each stage produces, and which stay secondary for reporting so nothing is double counted. 4. The upload file: a Parameters:TimeZone line from TimeZones, then the headers Google Click ID, Conversion Name, Conversion Time, Conversion Value, Conversion Currency, with three sample rows and the time format. 5. Timing rules: conversion time must be after the click, clicks older than the action's window will be rejected, and how often to upload (scheduled file, Sheets, or API). 6. A fallback for leads with no click ID: enhanced conversions for leads with hashed email, and where consent from ConsentAndOwner limits it. 7. An upload error table: common errors, what causes each, and the fix. 8. A first month QA plan: compare CRM counts to imported counts by week and flag gaps over a set threshold. Constraints: - Use only facts from Inputs. Never promise lower cost per lead or quote typical lift. Mark UI paths that may have moved as CHECK. - Plain language for the business owner; no em dashes.
Pydantic v1 to v2 Migration Planner for FastAPI and Python Services: bump-pydantic First Pass, validator to field_validator, root_validator to model_validator, Config to ConfigDict, BaseSettings Move, and Behavior Changes
Migrate a codebase from Pydantic v1 to v2 without silent behavior changes: run bump-pydantic first, convert validators and root validators, move Config to model_config with renamed keys, replace dict, json, parse_obj, and from_orm calls, move BaseSettings to pydantic-settings, and catch Optional default and strict coercion changes with targeted tests.
Act as a Python backend engineer who has migrated several FastAPI and worker services from Pydantic v1 to v2, uses bump-pydantic for the mechanical pass, and knows which changes it cannot make for you: validator signatures, Optional defaults, and coercion that v1 did quietly. Inputs: - Current versions: Python, pydantic, FastAPI or other frameworks that depend on pydantic, and the target versions: [Versions] - Pasted model code: the models, validators, Config classes, and settings classes to migrate: [ModelCode] - Call sites: where the code uses .dict(), .json(), parse_obj, parse_raw, from_orm, schema(), copy(), or __fields__: [CallSites] - Test coverage and CI notes: what tests exist around these models and which payloads are known in production: [TestNotes] - Rollout constraints: big bang or gradual, other services that import these models, a deadline: [Rollout] - Output format: [Format] Generate: 1. A plan header: dependency changes from Versions (pydantic 2, pydantic-settings if BaseSettings is used, a FastAPI release that supports v2), and whether to use the pydantic.v1 namespace for a gradual path given Rollout. 2. bump-pydantic first pass: the command to run on the package and a list of what it will and will not rewrite in ModelCode. 3. Validator conversions: each @validator to @field_validator with @classmethod, each pre=True to mode='before', each always=True to validate_default, each values argument to info.data via ValidationInfo, and each @root_validator to @model_validator with the right mode. 4. Config conversions: class Config to model_config = ConfigDict(...) with renamed keys (orm_mode to from_attributes, allow_population_by_field_name to populate_by_name, anystr_strip_whitespace to str_strip_whitespace, schema_extra to json_schema_extra), and json_encoders replaced by field_serializer where needed. 5. Field changes: regex to pattern, const removed, __root__ models to RootModel, and Optional fields with no default that become required. 6. Call site replacements from CallSites: dict to model_dump, json to model_dump_json, parse_obj to model_validate, parse_raw to model_validate_json, from_orm to model_validate with from_attributes, schema to model_json_schema, copy to model_copy, __fields__ to model_fields. 7. Behavior change tests from TestNotes: payloads that v1 coerced (an int into a str field), Optional without default, validator order, and serialized output shape, each as a pytest case. 8. A rollout checklist: order of services, the diff to review, and what to watch in logs after deploy. Constraints: - Show before and after code for every model in ModelCode. Do not invent fields or call sites; mark anything unclear as CHECK. - Mark API names that changed between minor v2 releases as CHECK against the installed version. No em dashes.
Character Reference Letter Writer for a Criminal Sentencing Hearing: Addressed to the Judge, Who You Are and How Long You Have Known Them, Acknowledging the Offense, Specific Character Evidence, Support Plan, and Attorney Review
Help a friend, employer, or family member write a character letter a judge will read at sentencing: proper address to the court, who the writer is and how long they have known the defendant, an honest acknowledgment of the offense, specific examples of character and change, the concrete support the writer will give, and a check list for the defense attorney before submission.
Act as a criminal defense paralegal who collects and edits character letters for sentencing memoranda, and who has watched judges discount letters that deny the crime, attack the victim, or say only that the defendant is a good person. Inputs: - Writer: name, job, where they live, relationship to the defendant, and how many years they have known them: [WriterProfile] - Case basics the attorney approved sharing: court, judge's name and title, case number if given, the offense of conviction or plea, and sentencing date: [CaseBasics] - Specific memories of the defendant's character: things you saw them do, with rough dates: [CharacterEvidence] - What you have seen since the offense: remorse, treatment, restitution, sobriety, work: [ChangeSinceOffense] - Concrete support you will provide: job offer, housing, rides to treatment, supervision help: [SupportPlan] - Anything the attorney said to include or avoid, including whether to mention a sentence: [AttorneyNotes] - Output format: [Format] Generate: 1. A fact intake check listing each item from CharacterEvidence and ChangeSinceOffense, marked seen by writer or heard from someone else. Letters should rely on what the writer saw. 2. The letter addressed to the judge using the exact title and name in CaseBasics (for example The Honorable Jane Doe), with a reference line for the defendant's name and case number if given. 3. An opening paragraph: who the writer is, their work and community ties, how they know the defendant, and for how long. 4. An acknowledgment paragraph: the writer knows the offense of conviction and does not excuse it. No retrying the case, no claims of innocence, no blame on the victim, police, or prosecutor. 5. Two or three character paragraphs, each built on one specific memory from CharacterEvidence with what the defendant did and why it matters. 6. A change and support paragraph: what the writer has seen since the offense and the concrete SupportPlan, with names, schedules, or commitments the writer can keep. 7. A closing that asks the court to consider these points, follows AttorneyNotes on whether to mention any sentence, and gives the writer's signature block and contact details. 8. A pre submission checklist for the defense attorney: length near one page, accurate facts, no statements about the case the attorney did not approve, signed and dated, sent to the attorney rather than directly to the judge unless instructed. Constraints: - Never invent facts, dates, achievements, or offers of support. Everything in the letter must be true and something the writer is willing to stand behind. - Respectful, plain language; no legal arguments; no em dashes.
Vehicle Wrap Artwork Spec Writer for Fleet and Service Vans: Template Scale and Resolution, Real Vehicle Measurements, Bleed per Panel, Body Line and Door Handle Keep Out Zones, Print Panel Seams, Window Perf, and a Proof Sheet
Write the production spec a wrap shop needs before printing a van or truck wrap: vehicle template and scale, raster resolution at full size, measurements taken from the real vehicle, bleed per panel, keep out zones over handles, seams, and deep body lines, how the art splits into print panels with overlaps, perforated window film, and a proof sheet for customer sign off.
Act as a vehicle wrap designer and production manager who has prepared hundreds of fleet van and box truck wraps for large format print, knows that vehicle templates are only a starting point, and has reprinted panels because a phone number landed on a door handle or a logo was split across a seam. Inputs: - Vehicle year, make, model, roof height, wheelbase, and any ladder racks, shelving, or trim that stays on: [VehicleSpec] - Coverage: full wrap, partial wrap, or spot graphics, and which sides, hood, roof, and rear doors: [Coverage] - The design brief: brand colors with any Pantone references, logo files available, required content such as phone, website, license or DOT number, and services list: [DesignBrief] - Measurements taken on the actual vehicle (length, height at several points, door and window sizes): [Measurements] - Print setup at the shop: printer and media width, vinyl and laminate (for example cast wrap film with matching laminate), and the scale they want files in: [PrintSetup] - Window plan: perforated window film on rear windows or none, and any local rules the owner pasted: [WindowPlan] - Output format: [Format] Generate: 1. A file setup block: template source and version, working scale from PrintSetup (for example 1:10 or 1:20), resulting resolution at full size, color mode, how spot colors are specified, and which elements stay vector. 2. A measurement reconciliation table comparing the template to Measurements for each side, with the adjustment to make and a note to remeasure anything off by more than an inch. 3. Bleed per panel: extra art beyond each panel edge so installers can wrap into recesses and trim, stated in inches at full size. 4. Keep out zones per side: door handles, fuel door, seams between body panels, deep body lines, rivets, rub strips, lights, and the sliding door track. Nothing critical (phone, logo, website, DOT number) goes in a keep out zone. 5. A content hierarchy with minimum sizes for readability at a distance, plus placement of the DOT number or license text where required. 6. Print panel layout: how each side splits into vertical panels at the media width, the overlap between panels, and seam placement that avoids faces, logos, and text. 7. A window section from WindowPlan: perforated film coverage and any visibility limits, or a note that window graphics are left out. 8. A customer proof sheet: four side views, a list of what the customer must confirm (spelling, phone, colors are approximations on screen), and the sign off line. Constraints: - Use only dimensions in Measurements or VehicleSpec; mark any template value you could not verify as CHECK. - Never print or design over damaged paint without noting it on the proof. No em dashes.
International Pet Travel Planner for Dogs and Cats Leaving the US: Destination Rules, ISO Microchip Before Rabies Vaccine, Wait Periods and Titer Tests, USDA APHIS Endorsed Health Certificate Timing, and Return Entry Rules
Plan a dog or cat move abroad without a missed step: destination entry rules from official sources, ISO microchip timing relative to rabies vaccination, waiting periods and titer tests, the USDA accredited vet visit and APHIS endorsement window, airline cabin or cargo checks, and the paperwork needed if the pet comes back to the US.
Act as a pet relocation coordinator who has moved dogs and cats from the United States to Europe, the UK, and rabies free countries, works with USDA accredited veterinarians every week, and has seen pets turned away for a microchip implanted after the rabies shot or a health certificate signed a day too early. Inputs: - Pet details: species, breed, age, weight, crate size if known, microchip number and standard if known: [PetProfile] - Vaccination history: rabies vaccine dates, vaccine type and duration, and whether the microchip was implanted before or after: [VaccineRecord] - Destination country, arrival airport, and whether the pet flies in cabin, as checked baggage, or as manifest cargo: [Destination] - Travel date and how firm it is: [TravelDate] - Rules text you pasted from the APHIS pet travel page for this destination, the destination government site, and the airline pet policy: [OfficialRules] - Whether the pet may return to the US later and from which countries: [ReturnPlan] - Output format: [Format] Generate: 1. A rules summary from OfficialRules only: microchip standard, rabies vaccination rules, wait periods, titer test needs, parasite treatments, health certificate form, endorsement method, and import permit or notice requirements. Anything not in OfficialRules is marked CHECK. 2. A microchip and rabies sequence check from VaccineRecord: if the chip is not ISO 11784/11785 or was implanted after the current rabies vaccine, say what the destination rules require (a new vaccine after chipping, a scanner, or a new wait) and what it does to TravelDate. 3. A backward timeline from TravelDate: earliest valid travel date after any wait period or titer blood draw, the USDA accredited vet visit date that fits the certificate window, the APHIS endorsement date, and any parasite treatment window before arrival. 4. An airline and crate checklist: cabin or cargo rules from OfficialRules, breed or temperature restrictions, crate sizing method, and booking the pet before buying your own ticket where the airline requires it. 5. A document pack list: what travels with the pet in original, what is uploaded or endorsed electronically, and copies to keep. 6. A return to the US section from ReturnPlan, covering current CDC dog import requirements for the countries visited and any form that must be completed before leaving the US. 7. A risk list: the three mistakes most likely to cause denied boarding or quarantine for this specific trip, and how to prevent each. Constraints: - Never guess a rule or a day count; quote OfficialRules or mark CHECK. This is planning help, not veterinary advice. - Dates in plain calendar form; no em dashes.
Meta Business Suite Insights Export Analyst for Instagram and Facebook: Content CSV Cleanup, Views vs Reach Definitions, Organic vs Boosted Split, Per Format Medians, Saves and Shares Rates, and a Next Month Test Plan
Turn a Meta Business Suite or Instagram Insights content export into decisions: clean the CSV, define views, reach, and interactions the way Meta reports them, separate boosted posts from organic, compare formats with medians from your own data, read saves and shares per reach, and leave with a small test plan instead of borrowed industry benchmarks.
Act as a social media analyst who reads Meta Business Suite and Instagram professional dashboard exports every month for small businesses, knows that Meta now reports views where it used to report impressions, and refuses to compare a client against industry averages nobody can source. Inputs: - The exported content rows as pasted CSV: post ID or date, publish time, post type (Reel, carousel, image, story), reach, views, likes, comments, shares, saves, and any boost or ad flag: [ExportRows] - Account, platform, date range of the export, and the time zone the export uses: [AccountContext] - What the business wants from the account (class sign ups, store visits, DMs, link clicks): [BusinessGoal] - Anything unusual in the period (holiday, a paid boost, a collab post, a viral moment): [PeriodNotes] - Output format: [Format] Generate: 1. An export hygiene check: confirm date range and time zone from AccountContext, count rows by post type, flag duplicates, missing metrics, and any row that is a boosted or paid post using PeriodNotes and the boost flag. 2. Metric definitions in plain words: reach as unique accounts, views as total times content was played or shown, interactions as likes plus comments plus shares plus saves. Note that metric names in the export can change, so mark any column whose meaning is unclear as CHECK. 3. An organic only table that excludes boosted rows, with per post interactions per reach, saves per reach, and shares per reach as percentages, rounded to one decimal. 4. Per format medians (not averages) for reach, views, and each rate, with the number of posts behind each median and a warning when a format has fewer than five posts. 5. Top and bottom posts by the rate that best matches BusinessGoal, with one line on what the content was if ExportRows includes it. 6. A posting time read that only describes what the data shows, with sample size, and does not declare a best time from a handful of posts. 7. The boosted post section: report it separately and explain why its reach should not be compared with organic posts. 8. A next month test plan: two or three tests, each with one variable changed, how many posts it needs, and which metric decides it. Constraints: - Use only numbers in ExportRows and show the arithmetic for any rate. Never quote industry benchmarks or follower growth not in the Inputs. - Keep it to what a small business owner can act on; no em dashes.
Themed Crossword Constructor for American Style 15x15 Grids: Theme Set and Revealer, Rotational Symmetry Placement, Black Square and Word Count Budget, Fill Quality Pass, Clue Writing Rules, and a Submission Checklist
Build a publishable American style themed crossword from an idea: a tight theme set with a revealer, matched entry lengths placed with 180 degree rotational symmetry, a black square and word count budget, a fill pass that removes crosswordese and duplicates, clues that follow standard conventions, and a submission checklist for the venue you are targeting.
Act as a published crossword constructor who builds American style themed 15x15 grids for newspaper and indie venues, works in Crossfire or Ingrid with a scored word list, and has had puzzles rejected for loose themes, unchecked squares, and tired fill. Inputs: - Theme idea in one sentence, plus any entries you already like: [ThemeIdea] - Target venue and day or difficulty (Monday easy, Wednesday medium, themeless Saturday, an indie weekly): [Venue] - Grid size and any special rules the venue publishes (word count cap, minimum entry length, pangram or no): [GridRules] - Your word list and scoring scale, for example a 1 to 60 score where 50 is lively: [WordList] - Entries or clue topics to avoid (brand names, grim subjects, words the editor dislikes): [AvoidList] - Output format: [Format] Generate: 1. A theme set audit: list candidate entries with exact letter counts, state the single rule every theme entry follows, and cut any entry that fits the rule loosely or uses the theme word in a different sense. 2. A revealer: one in-language phrase that explains the theme, with its letter count, and where it should sit (usually last theme slot or the center row). 3. Symmetry placement: assign each theme entry a row and column span so the grid keeps 180 degree rotational symmetry. Matching slots must have equal lengths, and a center entry must have an odd length and sit centered. 4. A grid budget from GridRules: theme squares, target word count, target black square count, minimum entry length of 3, every white square checked by an across and a down, and the whole grid connected. 5. A fill pass plan: the hardest crossing areas around theme entries, cheater squares that are allowed, and a list of crosswordese, obscure abbreviations, partials, and duplicate roots to replace, each with a better option scored from WordList. 6. Clues for every theme entry and the revealer, plus sample fill clues that show the conventions: tense and number agreement, abbreviation signals for abbreviated answers, a question mark on wordplay, and fill in the blank format. 7. A dupe and sensitivity check: no answer word repeated in another answer or clue, nothing from AvoidList, and no clue that could read as offensive. 8. A submission checklist for Venue: file type, grid and clue sheet format, byline, and a note to confirm current guidelines on the venue's own page. Constraints: - Count every letter twice. Never claim a grid is legal or a word is in a list unless the Inputs show it. - Keep theme entries in the language and not forced; no em dashes.