Productivity
239 prompts in this category · Page 2 of 20
Note Taking Prompt: Clean Up Raw Notes Into Cornell Notes
Paste raw notes from a lecture, meeting, or book and get Cornell notes: cue questions, tidy main notes, a short summary, follow ups, and gaps to check.
Act as a learning coach and note taking specialist who restructures messy raw notes into the Cornell format, keeping every fact from the notes and adding nothing that is not in them. Inputs: - My raw notes, pasted as typed, fragments and all: [RawNotes] - Where they came from: lecture, meeting, book chapter, podcast, or video: [SourceType] - What I will use them for: exam, project, decision, or writing: [NotesPurpose] - Where my notes live: Notion, Obsidian, OneNote, Google Docs, or paper: [NoteApp] - Terms or names I know are spelled right: [KnownTerms] Generate: 1. Clean main notes: grouped under short topic headings, one idea per bullet, numbers and terms kept exactly as written, abbreviations expanded only when the meaning is certain. Mark anything unclear as [UNCLEAR: original fragment]. 2. A cue column: one recall question for each main idea, worded so I can test myself with the notes covered. 3. A summary of three to five sentences in plain words, written for NotesPurpose. 4. Follow ups: action items with owners and dates for a meeting, or things to look up for a lecture, book, or podcast. 5. Key terms with definitions taken only from RawNotes. When the notes do not define a term, write [DEFINE FROM SOURCE]. 6. The finished Cornell page formatted for NoteApp: a two column table for Notion, Obsidian, or Google Docs, a cue and notes layout for OneNote, or a ruled page sketch for paper. 7. Five self test questions drawn from the cue column, each pointing to the heading where the answer sits. Rules: - Do not add facts, examples, or explanations from outside RawNotes. - Keep my wording where it is clear.
Program Manager Prompt: Weekly Status, RAID Log, and Asks
Turn workstream updates into a program status report: RAG status with reasons, milestone table, updated RAID log, cross team dependencies, and steering asks.
Act as a senior technical program manager who runs a multi team program and writes the weekly status that executives read in two minutes and workstream leads trust. Inputs: - Program name, goal, and the date of this report: [ProgramContext] - Workstream updates from each lead, pasted as written: [WorkstreamUpdates] - Milestone plan with baseline dates and current forecast dates: [MilestonePlan] - Current RAID log (risks, assumptions, issues, dependencies) with owners: [RaidLog] - Budget or capacity notes, if any: [BudgetCapacity] - Who reads this report and what they decide: [Audience] - RAG definitions my company uses: [RagRules] Generate: 1. A program RAG status with a one sentence reason, applying RagRules exactly. If a workstream update conflicts with the forecast dates, flag it rather than picking one. 2. A three line executive summary: what moved, what is at risk, and what we need. 3. A workstream table: workstream, RAG, progress this week, next week, and the lead. 4. A milestone table: milestone, baseline date, forecast date, variance in days, and status. Compute variance only from MilestonePlan. 5. An updated RAID log: new items found in WorkstreamUpdates, changed items, and items to close, each with owner, due date, and the next action. 6. A dependency map in text: which workstream waits on which, and the date each dependency must land to protect the next milestone. 7. Steering committee asks: decisions or help needed, each with options and the impact of waiting a week. 8. Follow up questions for any lead whose update was vague. Rules: - Do not soften or upgrade a status the data does not support. - Use only dates and numbers from the Inputs; write [NEED UPDATE] where missing. - Keep the summary readable by Audience without program jargon.
YouTube Transcript Summary Prompt: Timestamped Notes
Turn a pasted YouTube transcript into a summary you can trust: a TL;DR, timestamped key points, claims to verify, action steps, and quotes from the text.
Act as a research note taker who summarizes long YouTube videos from their transcripts for busy professionals, keeping every point tied to a timestamp so the viewer can jump back and check it. Inputs: - Video title, channel, and length as shown on YouTube: [VideoDetails] - The full transcript with timestamps, copied from YouTube's Show transcript panel: [Transcript] - Why I am watching and what I need from it (a decision, a skill, a talk I must discuss): [MyPurpose] - What I already know about the subject, so you can skip basics: [PriorKnowledge] - Summary length I want (one minute read, five minute read): [Length] - Output format: [Format] Generate: 1. A transcript check: whether the transcript looks auto generated, where it seems garbled or cut off, and any sections with no timestamps. Never fill a gap with what the speaker probably said. 2. A TL;DR of three sentences aimed at MyPurpose. 3. A timestamped outline: each major section with its start time from Transcript, a short heading, and two or three bullet points. 4. Key points ranked by usefulness for MyPurpose, each with its timestamp, skipping what PriorKnowledge already covers. 5. Claims to verify: factual or numerical claims the speaker makes, each with its timestamp, labeled as stated by the speaker, plus what kind of source would confirm it. 6. Action steps: concrete things to do, try, or decide, only if the video actually suggests them; otherwise say there are none. 7. Up to five exact quotes copied word for word from Transcript with timestamps. If a quote spans a garbled area, leave it out. 8. What the video does not cover that MyPurpose still needs, as open questions. Constraints: - Use only the transcript. Do not add facts from outside knowledge; if you add context, label it "Outside context" and keep it to one line. - Keep to Length. - If the transcript is missing or shorter than the video length suggests, say so before summarizing. - No em dashes.
Microsoft Bookings Booking Page Setup Planner: Service Durations and Buffer Times, Staff Availability, Scheduling Policy Lead Times, Custom Booking Questions, Reminder Emails, and a Break It Test Plan
Plan a Microsoft Bookings page before you click through the settings: turn your services into durations with buffer times, map staff hours, pick lead times and time increments, write custom booking questions that keep sensitive details out of the form, size reminders to your no show pattern, and test it with bookings designed to break it.
Act as a Microsoft 365 administrator who configures Microsoft Bookings booking pages for small service teams so customers can self book without double bookings, no shows, or missing intake details. Inputs: - Business name, booking page type (shared booking page or personal page), and time zone: [BookingPageBasics] - Services: name, length, price or free, in person or Teams meeting, group size, and prep or cleanup time needed: [ServiceList] - Staff: names, roles, which services each delivers, working hours, and regular days off: [StaffRoster] - Booking rules: shortest notice you accept, how far ahead customers may book, cancellation window, and slot increments: [BookingRules] - Details you must collect before the appointment, and anything that must never go in a booking form: [IntakeNeeds] - Reminder preferences and your current no show pattern: [NoShowHistory] - Output format: [Format] Generate: 1. A booking page decision from BookingPageBasics: shared or personal page, who can book (anyone or only people in your organization), and whether customers may choose a particular staff member. 2. A Bookings service table from ServiceList: default duration, buffer time before and after, price display, location or Teams meeting toggle, maximum attendees for group services, and the staff assigned from StaffRoster. 3. Staff availability: for each person in StaffRoster, business hours or custom hours, blocked days, and a flag for anyone assigned to a service they cannot fit inside their hours. 4. A scheduling policy from BookingRules: minimum lead time, maximum lead time, time increments, and cancellation and reschedule notice, each with one line on why it fits the service table. 5. Custom booking questions from IntakeNeeds: exact question text, answer type, required or optional, and which services show it. Move anything sensitive out of the form into a secure follow up step. 6. Confirmation, reminder, and follow up emails per service: timing and the custom reminder text, sized to NoShowHistory. 7. A break it test plan: five test bookings that try back to back slots, buffer overlap, too short notice, a staff day off, and a full group class, with the expected result for each. 8. A launch checklist: where to link the booking page, what to tell staff, and what to review after the first two weeks. Constraints: - Use only services, staff, and hours from the inputs; mark any missing value NEEDS DECISION instead of guessing. - Bookings menu labels change over time; tell the user to confirm each setting name in their own tenant. - No em dashes.
Apartment Unit Turn Make-Ready Scheduler: Move-Out Inspection, Trade Sequencing for Paint, Flooring, and Cleaning, Vendor Calendar, Days Vacant Targets, and a Final Punch Walk
Plan apartment unit turns for a property management team: a day by day make-ready schedule per unit from move-out to move-in, trades in the right order (repairs, paint, flooring, clean), a vendor calendar that avoids double booking, risk flags for tight move-ins, and a punch walk checklist.
Act as an apartment maintenance supervisor who runs unit turns for a multifamily community, sequences in-house techs and outside vendors, and hands leasing a ready date they can promise. Inputs: - Units turning, with move-out date, scheduled move-in date (or none yet), floor plan, and condition notes from the pre-move-out walk: [UnitList] - Turn standards for this community (what always gets done, for example full paint every turn or touch-up only, carpet clean vs replace rules): [TurnStandards] - In-house team and hours, plus outside vendors with their available days and lead times: [VendorRoster] - Days vacant target and any turn budget per unit: [TurnTargets] - Constraints such as holidays, office hours, elevator reservations, or parts on order: [Constraints] - Output format: [Format] Generate: 1. A turn scope per unit from UnitList and TurnStandards: trash-out, repairs, paint level, flooring action, appliance work, clean, and keys or lock change. 2. Trade sequencing rules used for every unit: repairs and drywall first, then paint, then flooring install or carpet clean, then final clean, then punch, then lock change. 3. A day by day make-ready schedule per unit with the trade, the crew from VendorRoster, and the ready date. 4. A vendor calendar that groups units by trade per day and avoids booking one vendor in two places, honoring lead times and Constraints. 5. A risk list: units whose ready date falls less than one day before move-in, parts on order, and what leasing should be told. 6. A days vacant check against TurnTargets with the units over target and one way to pull each back. 7. A punch walk checklist the supervisor signs before the unit is marked ready. Constraints: - Use only units, dates, and vendors listed in the inputs; mark any missing date as NEED. - Do not promise a ready date that skips a sequencing step. - Keep each unit schedule to one line per day. No em dashes.
Construction Superintendent Daily Report Writer: Weather, Manpower by Trade, Work Completed by Area, Deliveries, Inspections, Delays with Cause, and Photo Log
Turn a superintendent's voice notes and texts from the field into a clean daily construction report: weather and site conditions, crew counts by subcontractor, work done by area, deliveries, inspections, safety notes, delays tied to a cause, and a photo log the project manager can rely on later.
Act as a general contractor superintendent who has kept daily reports on commercial jobs for years and writes them so they hold up later in delay claims, change order disputes, and owner meetings. Inputs: - Project and date: project name, job number, report number, superintendent, shift hours: [ProjectAndDate] - Weather and site conditions, with times (rain start and stop, temperature, wind, ground conditions): [WeatherLog] - Crew counts by subcontractor and trade, with foreman names and hours: [ManpowerBySub] - Work performed, in rough notes by building area, level, or grid line: [WorkByArea] - Deliveries, equipment on site, inspections, and visitors: [DeliveriesAndInspections] - Safety observations, incidents, and toolbox talk topic: [SafetyNotes] - Problems, delays, RFIs, and directives received in the field: [IssuesAndDelays] - Photo file names with what each shows: [PhotoList] - Output format: [Format] Generate: 1. A header block from ProjectAndDate. 2. A weather section from WeatherLog with times, and whether weather stopped or limited any work, stated as fact. 3. A manpower table from ManpowerBySub: company, trade, foreman, headcount, hours, and a total. 4. Work completed by area from WorkByArea, written as specific, measurable statements (for example "Level 2 grid C to F, 4,200 sq ft slab on deck placed"). 5. Deliveries, equipment, inspections, and visitors from DeliveriesAndInspections, with inspection results (passed, failed, partial) and inspector name if given. 6. A safety section from SafetyNotes: toolbox talk topic, observations, and any incident with time and immediate action. 7. A delays and issues section from IssuesAndDelays: what happened, time lost, crews affected, cause (weather, owner, design, sub, inspection), RFI or directive number, and whether notice to the owner may be needed under the contract [PM to confirm]. 8. A photo log from PhotoList keyed to the sections above. 9. Tomorrow's plan and open items in three to five lines. Constraints: - Facts only from the inputs; no opinions about blame. Mark anything uncertain as [verify]. - Use numbers and times, never "a lot of rain" or "a while". - Short, plain sentences. No em dashes.
On-Call Shift Handoff Note Writer: Open Incidents, Silenced Alerts, Pending Changes, Watch Items, and Escalation Contacts for the Next Engineer
Turn the end of an on-call shift into a handoff note the next engineer can act on in five minutes: open incidents with status and next action, silences that will expire, pending changes and freezes, things to watch, and who to call.
Act as a site reliability engineer who has run many on-call rotations and writes shift handoff notes that the incoming engineer can read in five minutes and act on without asking a single follow up question. Inputs: - Rotation details: team, shift window and time zone, outgoing and incoming engineer: [RotationDetails] - Open and recently resolved incidents with ticket IDs, severity, current status, and what was tried: [Incidents] - Alerts that are silenced, acknowledged, or flapping, with silence expiry times: [AlertState] - Deploys, migrations, maintenance windows, or change freezes in the next shift: [PendingChanges] - Rough notes, chat excerpts, or anything the outgoing engineer is worried about: [ShiftNotes] - Escalation paths and contacts for dependent teams and vendors: [EscalationContacts] - Output format: [Format] Generate: 1. A three line top summary: overall state, the single most important thing to do first, and any time sensitive deadline in the incoming shift. 2. An open incidents table from Incidents: ID, severity, status, what was tried, next action, and owner. 3. A silences and alerts section from AlertState: every silence with exact expiry in the shift time zone, and what to do if the alert fires again after expiry. 4. A changes calendar from PendingChanges in time order, with who is driving each change and a rollback note. 5. Watch items pulled from ShiftNotes: things that are not incidents yet, with the metric or dashboard to check and the threshold that should trigger action. 6. An escalation block from EscalationContacts in the order to call, with when to use each. 7. Loose ends: tickets to update, postmortems to schedule, and questions for the team lead. 8. A short handoff checklist the incoming engineer confirms out loud or in chat. Constraints: - Use only facts from the inputs; mark anything unclear as [confirm with outgoing]. - Write times with time zone, never "later" or "soon". - No blame language. Plain, terse tone. No em dashes.
Jira JQL Saved Filter and Dashboard Builder: Team Queries for My Open Work, Blocked and Aging Issues, Sprint Carryover, Filter Subscriptions, and Gadget Layout
Turn the questions a team lead asks every morning into working JQL saved filters, a dashboard gadget layout, and email subscriptions, with field names checked against your Jira site and notes on what each query will miss.
Act as a Jira administrator who writes JQL saved filters and dashboards for delivery teams, uses the real field and status names from the site, and explains what each query includes and leaves out. Inputs: - Project keys, issue types, and workflow statuses with their status categories (To Do, In Progress, Done): [ProjectsAndStatuses] - Custom fields the team uses (for example Story Points, Team, Flagged, Blocked Reason) and whether they are company managed or team managed: [CustomFields] - The questions the team wants answered each day or week, in plain words: [TeamQuestions] - Sprint and board setup (Scrum or Kanban, sprint length, board filter): [BoardSetup] - Who needs which view, and whether they want an email subscription: [Audience] - Output format: [Format] Generate: 1. A JQL saved filter for each item in TeamQuestions: filter name, the JQL, and one line on what it returns. 2. Field name checks from CustomFields: where a custom field name has spaces or clashes, show the quoted form or cf[ID] form, and flag team managed fields that may not be searchable across projects. 3. Aging and blocked queries that use functions like statusCategory, status changed, updated, Flagged, and openSprints() correctly, with the date window stated. 4. A sprint carryover filter using sprint in openSprints() and sprint in closedSprints() based on BoardSetup. 5. A dashboard gadget layout: which gadget (Filter Results, Two Dimensional Filter Statistics, Created vs Resolved, Pie Chart) uses which filter, and the column order. 6. Filter subscriptions per Audience: schedule, recipients, and whether to send when empty. 7. Sharing permissions for each filter and dashboard (project role, group, or private). 8. A pitfalls list: what each filter will miss, such as issues without a sprint or statuses outside the expected category. Constraints: - Use only statuses and fields given in ProjectsAndStatuses and CustomFields; mark anything else [confirm field name]. - Prefer statusCategory over long status lists when it gives the same answer. - Plain admin tone. No em dashes.
Obsidian Dataview Query Builder: TABLE LIST TASK Views from Folder and YAML Frontmatter Fields for a Weekly Review Dashboard
Design Obsidian Dataview TABLE, LIST, and TASK queries from your real folder layout and YAML frontmatter fields, then assemble a weekly review dashboard that surfaces open tasks, stale notes, and projects waiting on others without inventing fields you do not use.
Act as an Obsidian power user who writes Dataview TABLE, LIST, and TASK queries from a real vault schema, respects existing YAML frontmatter fields, and builds a weekly review dashboard that stays honest about missing metadata. Inputs: - Folder map (projects, areas, daily notes, templates paths): [FolderMap] - YAML frontmatter fields you actually use (status, due, project, area, priority, up): [YamlFields] - Weekly review goals (find stale, open tasks by project, waiting on): [ReviewGoals] - Dataview plugin flavor (Dataview queries vs DataviewJS) and any bans: [PluginConstraints] - Sample note paths and frontmatter snippets: [SampleNotes] - Output format: [Format] Generate: 1. A schema echo: list YamlFields and FolderMap as understood; refuse to invent new keys unless marked optional proposal. 2. Three TABLE queries aligned to ReviewGoals (for example open projects, due this week, stale notes where up older than N days). 3. Two LIST queries for lightweight indexes (areas, waiting on people). 4. Two TASK queries that pull unfinished tasks from daily notes and project notes with FROM folder limits. 5. A weekly review note outline that embeds those queries in order with human checklist steps between them. 6. A troubleshooting card: DQL typos, WHERE on missing fields, calendar date formats, and tasks in callouts. 7. A migration tip if SampleNotes show inconsistent field names (status vs State). 8. A paste ready code block set labeled so users copy one query at a time. Constraints: - Never invent result counts, fake note titles beyond SampleNotes, or frontmatter fields not in YamlFields without labeling them as optional proposals. - Prefer DQL over DataviewJS unless PluginConstraints asks otherwise. - No em dashes.
Apple Reminders Smart Lists Planner: Tag Taxonomy, Date Filters, Location and Messaging Triggers, Shared List Rules, and a Weekly Review Checklist
Design an Apple Reminders system that uses tags, smart lists, and triggers instead of a pile of manual lists: a tag taxonomy, smart list filter recipes for iOS and macOS, location and Messages triggers, shared list etiquette, and a weekly review so nothing sits unmarked.
Act as an Apple Reminders power user who designs tag based systems on iOS and macOS, writes exact smart list filters, and keeps shared household lists from becoming noise. Inputs: - Roles and contexts you juggle (work, home, errands, kids, side project): [LifeContexts] - Devices and OS versions you use Reminders on: [Devices] - People you share lists with and what they may edit: [SharingMap] - Current pain (too many lists, forgotten grocery items, no weekly review): [PainPoints] - Preferred review day and how many minutes you will spend: [ReviewBudget] - Output format: [Format] Generate: 1. A list inventory: which ordinary lists to keep (one per shared household or project) versus what should be tags instead. 2. A tag taxonomy of 8 to 12 tags with naming rules (#errand, #waiting, #deep) and when to apply each. 3. Smart list recipes: for each, the exact filter logic using date, tags, priority, and flagged, written so someone can recreate it in Reminders > New Smart List. 4. Trigger patterns: location arrive/leave for errands, when messaging a person for #waiting, and time based daily flags; mark any menu path you are unsure of as [confirm in Reminders help for your OS]. 5. Sharing rules from SharingMap: who is invited, default list assignment for Siri adds, and a "no dumping" etiquette note. 6. A capture cheat sheet: Siri phrases and keyboard shortcuts that land tasks in the right list with tags. 7. A weekly review checklist sized to ReviewBudget that clears completed, retags #waiting, and empties the Inbox list. 8. A migration plan from PainPoints: which old lists to archive first and how to bulk retag. Constraints: - Do not invent iCloud storage quotas or unreleased OS features. - Prefer tags plus few lists over dozens of lists. - Plain checklists. No em dashes.
Todoist Filter Query Builder: Saved Filters with today, overdue, p1, #Project and ##Subprojects, @Labels, /Sections, assigned to, created before, AND OR NOT Operators, Comma Split Lists, and a Weekly Review Set
Turn how you actually work into a small set of Todoist filters that answer one question each: what to do now, what is waiting on others, what is stale, and what needs a weekly review, with each query written in Todoist's filter syntax, explained piece by piece, tested against sample tasks, and paired with a label plan so the filters keep working.
Act as a Todoist power user and productivity coach who sets up task systems for professionals, writes filter queries in Todoist's own syntax, and keeps the number of saved filters small enough to use every day. Inputs: - Role and the kinds of work that compete for attention: [WorkContext] - Current projects and sub projects as named in Todoist, and sections inside them: [ProjectTree] - Labels in use or wanted (contexts, energy, waiting, people): [LabelPlan] - Shared projects and who assigns tasks to whom: [Collaboration] - Questions the filters must answer, such as "what now", "waiting on others", "stale tasks", "this week by area": [FilterQuestions] - Output format: [Format] Generate: 1. A label plan from LabelPlan: keep or rename each label, mark the one waiting label and any context labels, and drop labels that no filter will use. 2. One saved filter per item in FilterQuestions: name, query, color, and a plain reading of the query. Use Todoist syntax such as today, overdue, no date, 7 days, p1 to p4, #Project, ##Project to include sub projects, @label, /Section, assigned to: me, assigned to: others, due before: +3 days, created before: -30 days, search: word, and the operators & (and), | (or), ! (not), and parentheses. 3. Where one view should show stacked lists, use commas to split the query into separate sections, for example (today | overdue) & #Work, @waiting. 4. A test table: five sample tasks built from ProjectTree and LabelPlan, and which filters each task should appear in. Point out any task that shows up nowhere. 5. Edge cases: tasks with no date, recurring tasks, sub tasks, tasks in shared projects from Collaboration, and how each filter handles them. 6. A daily and weekly routine: which filter to open first each morning, and a weekly review sequence of three or four filters with what to do in each. 7. Setup steps: where to create filters, how to favorite them, and where to put them in the sidebar. 8. If a query relies on syntax you are not sure Todoist supports, label it "test in Todoist" and give a simpler fallback. Constraints: - No more than seven saved filters. Each name under four words. - Exact query strings in code style. No em dashes.
Raycast Script Commands and Snippets Builder for a Mac IT Helpdesk: Scripts with @raycast Metadata, Output Modes, Typed Arguments, Confirmation for Risky Actions, Keychain Secrets, Snippet Placeholders, Quicklinks, and a Shared Repo
Turn the repetitive work of a small Mac support or IT team into Raycast tools: sort each task into a script command, a snippet, a quicklink, or a job for your MDM, then write ready to save Bash or Python script commands with correct @raycast metadata, the right output mode, typed arguments, confirmation on risky actions, tokens read from the macOS Keychain, snippet keywords with dynamic placeholders, and a shared repo with a test checklist.
Act as a Mac IT support lead who builds Raycast Script Commands, snippets, and quicklinks for a small helpdesk, and has cleaned up scripts that leaked API tokens into a shared repo or ran a destructive command on one stray keystroke. Inputs: - Team size, who uses the tools, and the tasks repeated every day: [TeamAndTasks] - Systems the scripts may touch, with base URLs and what needs admin rights: [ToolsAndAPIs] - Allowed script languages and installed command line tools (for example bash, python3, jq): [ScriptLanguage] - Where secrets live and what may never be committed: [SecretsPolicy] - Canned replies and text the team retypes: [SnippetLibrary] - Output format: [Format] Generate: 1. A triage table for TeamAndTasks: each task becomes a script command, a snippet, a quicklink, or "not a Raycast job" when it needs admin rights or belongs in MDM or Self Service per ToolsAndAPIs. One line of reason each. 2. For each script command, a complete file: kebab case filename, shebang, then the metadata comment block with @raycast.schemaVersion 1, @raycast.title (verb first), @raycast.mode, @raycast.packageName to group commands, @raycast.icon, and @raycast.description. 3. Pick the mode on purpose: silent for fire and forget, compact when one result line is enough, fullOutput for multi line results, inline only for a status line and only with @raycast.refreshTime. State the reason in a comment. 4. Arguments: at most three @raycast.argument lines with JSON type text, password, or dropdown, a placeholder, and optional when it truly is. Read them as $1 or sys.argv, validate, and on bad input print one plain line and exit 1 so Raycast shows the failure. 5. Risky actions (cancel, delete, restart, post to a system): add @raycast.needsConfirmation true and print exactly what will change before doing it. 6. Secrets per SecretsPolicy: never hard code a token. Read it with security find-generic-password -s name -w, and give each teammate the one line setup with security add-generic-password. If the item is missing, exit 1 with the setup hint. 7. Output discipline: last line is the human message in compact and silent modes, results that agents paste go to pbcopy, and no sudo inside any script. 8. Snippets from SnippetLibrary: a keyword scheme with a prefix such as ;; so words never expand by accident, then each snippet with dynamic placeholders like {cursor}, {clipboard}, or a date with an offset. Note that date offsets count calendar days. 9. Quicklinks for lookups by ID, using an argument placeholder in the URL. 10. Shared repo setup: folder layout, chmod +x, adding the folder with Add Script Directory in Raycast settings, a README line per command, and a test checklist (empty argument, bad argument, offline, missing Keychain item). Constraints: - Only call systems listed in ToolsAndAPIs. Mark any endpoint you did not get as "confirm in the API docs". - Placeholder and metadata syntax can change between Raycast versions; mark anything uncertain "check the current Raycast manual". No em dashes.