APromptAura

Prompts for Any

Ranked by votes, with verified run counts from the community.

0
p/metaAauraNovice4 days agohas example⁂auto-checked

How verification works here, and why a failed report is worth as much as a good one

Read this before you use the site, it explains the one thing PromptAura does that other prompt libraries do not. THE PROBLEM Prompts do not age well. They are written against a specific model, at a specific moment, and models change underneath them constantly. Every prompt library on the internet is full of instructions that stopped working a year ago, and none of them can tell you which ones. A list of prompts with upvotes cannot solve this. Upvotes measure whether an idea sounds good. They do not measure whether it still runs. WHAT WE DO INSTEAD When you run a prompt from this site, tell us what happened. You pick the model and the version, and you say whether it did what it claimed. That single dated claim drives everything: - The freshness badge on every prompt, so you can see at a glance whether anyone has confirmed it lately - The compatibility table, showing which models a prompt has actually been run on - The "still works" sort, which ranks by verified runs and pushes reported breakage down - The model watch pages, which show what stopped working after a release WHY FAILURES MATTER MORE THAN YOU THINK Most people will only click the button when something works. That is human, and it is also how the dataset becomes useless. If a prompt fails for you, say so. It costs you ten seconds and it is the single most valuable thing you can contribute here. A library where nothing is ever marked broken is just a list with extra steps. Reporting a failure does not attack the author. Models moved; that is nobody's fault. The prompt gets flagged, the author can revise it, and the next person does not waste their time. AUTOMATED VERIFICATION You will see verifications from an account called aura-bot. That is automation: it runs prompts against current models and records the result. Its bio says so, and its reports are labeled. It is a smoke test, not a human saying a prompt is good. Treat it as a floor, not a recommendation. FROM YOUR EDITOR If you connect the MCP server, you can verify without visiting the site at all. Run a prompt in Claude Code or Cursor, then tell your assistant it worked, and it records the result with the model version filled in automatically. See /connect.
Any#site-guide#verification#freshness
0
0
p/metaAauraNovice4 days agohas example⁂auto-checked

Weekly challenge: turn meeting notes into action items nobody argues about

This is the first PromptAura weekly challenge. Post your entry as a prompt in p/productivity, tag it `weekly-challenge`, and include an example output. THE BRIEF Write a prompt that takes raw, messy meeting notes and produces a list of action items that survives contact with the people who were in the room. That means: - Every item has exactly one owner, named - Every item has a date or an explicit "no date agreed" - Anything that was discussed but not decided is listed separately as open, not silently promoted into a task - Nothing is invented. If the notes do not say who owns something, the prompt must say so rather than guessing Test it on your own real notes, not on a clean sample. The whole point is handling the mess. HOW ENTRIES ARE JUDGED Verified runs decide it, not upvotes. Whoever's entry collects the most "worked for me" verifications by the end of the week wins. That means you should run other people's entries and report honestly, including when they fail. WINNER GETS A pinned spot on the p/meta feed for the following week, and the founder flair on their profile. THE PROMPT BELOW IS THE BASELINE TO BEAT You are turning raw meeting notes into action items. Notes: meeting_notes Rules: - One owner per item, named exactly as they appear in the notes - If no owner is identifiable, put the item under Unassigned and do not guess - If no date was agreed, write "no date agreed" rather than inventing one - Anything discussed without a decision goes under Open questions, never under Actions - Do not add items that are not supported by the notes Output format: Actions - [owner] [action] [date or "no date agreed"] Unassigned - [action] Open questions - [question]
ClaudeGPTAny#weekly-challenge#meeting-notes#action-items
0