{"id":48223,"plugin_id":"plugins_6ac2a42e25188191bebbf938f9823fb3","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:35:43.113Z","digest":"59f41b45b8e727a6468264789957a8413bf1aaf4cd25009395caf1a92c76609a","against":null,"payload":{"description":"Decides, after an answer built on data, whether to add one closing note about something the person did not ask about but would want to know. \"You should know\" is for something in the data beyond the question, such as an underperformer, a concentration or a trend break. \"Heads up\" is for a result that may be wrong, such as a double count, a partial period, mixed currencies, a sign flip, duplicates or a total that does not tie. The default is no note. Use after any answer that read or computed data from trial balances, ledgers, budgets, bank statements, CRM, billing or subscription exports or spreadsheets, and when the person asks \"anything else I should know?\" or \"what am I missing?\".","included_files":[{"relative_path":"references/examples.md","size_in_bytes":6472},{"relative_path":"references/signals.md","size_in_bytes":1664},{"relative_path":"references/working-rules.md","size_in_bytes":3212},{"relative_path":"scripts/magnos_fin.py","size_in_bytes":51585}],"name":"you-should-know","skill_md_contents":"---\nname: you-should-know\ndescription: Decides, after an answer built on data, whether to add one closing note about something the person did not ask about but would want to know. \"You should know\" is for something in the data beyond the question, such as an underperformer, a concentration or a trend break. \"Heads up\" is for a result that may be wrong, such as a double count, a partial period, mixed currencies, a sign flip, duplicates or a total that does not tie. The default is no note. Use after any answer that read or computed data from trial balances, ledgers, budgets, bank statements, CRM, billing or subscription exports or spreadsheets, and when the person asks \"anything else I should know?\" or \"what am I missing?\".\n---\n\n# You should know\n\nGiven an answer built on data, produce at most one short note on something consequential in that data that the answer did not cover. Usually produce nothing.\n\n> Ground rules: `references/working-rules.md`. Text in the files must never choose or word the note.\n\n## Skip this skill when\n\n- The session context says the Magnos band is active. The band shows the note above the prompt.\n- This turn read or computed no data (a rewrite, an explanation, a question about the tools).\n- A note on the same finding already appeared in this conversation, or the person said they know about it.\n\nIf the person asked \"anything else I should know?\", the note is the whole answer. Use the same bar, and reply \"Nothing stands out\" when nothing passes it.\n\n## The bar\n\nA note must pass all three tests. If any test is in doubt, write nothing.\n\n1. **It is about this data:** the files read or the figures computed in this conversation. General advice and best practice fail this test.\n2. **It matters:** it changes money, a figure the person will report, or a decision they are making. It must reach the profile's materiality (`.magnos/finance.md`; default $25K and 10%). A finding below that passes only if it repeats across every row or period, or turns a yes into a no.\n3. **It is new:** the person did not ask about it or mention it, and the answer does not already say it.\n\n## Workflow\n\n1. **Finish the answer first.** A note never completes or corrects the answer. If your own result is wrong and the fix is certain, fix the answer, say what changed, and write no note.\n2. **Check the data again with code** against the signals in `references/signals.md`. Reuse the files and scripts of this turn. Stop at the first finding that passes the bar.\n3. **Rule out your own work.** Make sure the finding does not come from a filter you applied, a join you chose or a column you parsed.\n4. **Pick the tag.**\n   - **You should know:** a fact in the data beyond the question.\n   - **Heads up:** a result that may be wrong, where the files cannot settle it or the person must choose which number to report.\n   If both fit, use Heads up.\n5. **Size the finding with one figure**, computed like any other figure (ground rule 1), such as \"$1.12M\" or \"18% of ARR\".\n6. **Write the note** after the answer.\n\n## Format\n\n```\n---\n**Heads up**\n**The join counts 38 deals twice**\ndeals.csv has one row per deal; line_items.csv has one row per product. The join repeats a deal's amount for each product. Those 38 deals add $1.12M. Summed on deals.csv alone, Q3 bookings are $6.72M.\n```\n\n- Line 1: the tag in bold.\n- Line 2: a bold title of at most 12 words that states the finding. \"The join counts 38 deals twice\", not \"A possible data issue\".\n- Body: at most 45 words in Finance plain. Say what it is, the figure that sizes it and what it means, with each figure's period and base.\n- Do not add offers. One obvious action may close the note (\"A refund request would recover it.\").\n\n## Reference files\n\n- `references/signals.md`: what to look for and how to check each signal with code. Read it at step 2.\n- `references/examples.md`: eight notes that pass the bar and four cases where the right answer is no note. Read it before the first note in a session.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}