Update to SS33 Skill Store

{
  "description": "Finds a proven step-by-step procedure in the SS33 Skill Store (about 60,000 skills written by practitioners and organisations) and follows it. Use before producing a plan, schedule, procedure, document, configuration or code in a specialised area, such as legal, finance, tax, healthcare admin, trades, animal care, home, data, security or a library you are unsure of, where house rules, standards or exact numbers matter. Not for chat, one-line answers or work the open project already explains.",
  "included_files": [],
  "name": "ss33-skill-store",
  "skill_md_contents": "---\nname: ss33-skill-store\ndescription: Finds a proven step-by-step procedure in the SS33 Skill Store (about 60,000 skills written by practitioners and organisations) and follows it. Use before producing a plan, schedule, procedure, document, configuration or code in a specialised area, such as legal, finance, tax, healthcare admin, trades, animal care, home, data, security or a library you are unsure of, where house rules, standards or exact numbers matter. Not for chat, one-line answers or work the open project already explains.\n---\n\n# SS33 Skill Store\n\nThe SS33 Skill Store is a library of about 60,000 skills: step-by-step\nprocedures with the rules, numbers and common mistakes for a task. Hundreds\nare Verified, meaning they were tested on blind questions and measurably\nimproved a model's answers. The store is reached through three tools:\n`search_skill_store`, `get_skill` and `report_skill_outcome`.\n\n## When to search\n\nSearch when the task needs knowledge you may not have exactly right:\n\n- A document, plan or procedure in a professional field (a lease clause, a\n  payroll run, a medical billing change, a building quote).\n- A schedule or care plan where specific numbers matter (feeding, dosing by\n  weight, training loads, planting dates).\n- A configuration or code task for a tool, API or standard you are unsure\n  of, or one newer than your training.\n\nSkip the search for casual conversation, one-line facts, translation, and\ncoding work the project's own code and docs already explain.\n\n## Steps\n\n1. **Search.** Call `search_skill_store` with `query`: one or two sentences\n   describing the task in plain words, for example \"Write a job quote for a\n   kitchen remodel with materials, labour, markup and a deposit schedule\".\n   Pass `area` when one fits: Software Development; AI & Agents; Data &\n   Analytics; Security; Business; Finance & Markets; Betting & Prediction\n   Markets; Legal; Health & Life Sciences; Creative & Media; Science &\n   Education; Personal & Home.\n2. **Choose.** Read each candidate's summary and why it matched. Prefer a\n   Verified skill that fits the whole task. When the search says nothing\n   fits (`found` is false), carry on without a skill.\n3. **Fetch.** Call `get_skill` with the chosen `ref`. Read the SKILL.md and\n   any supporting files it points to.\n4. **Follow it.** Use the skill's procedure, rules and numbers, adapted to\n   the user's situation. Tell the user which skill you used, by name.\n5. **Report.** After the work is done, call `report_skill_outcome` with\n   `worked` (true or false) and short `notes` on what helped or what was\n   missing.\n\n## Privacy\n\nSend only a short description of the task. Never paste the user's whole\nmessage, names, contact details, account numbers, health details or other\npersonal data into a search.\n\n## Limits\n\nNo account is needed. Searches are limited per conversation (30 a minute).\nA skill whose licence does not allow it to be shared comes back with a link\nto its author instead of its text.\n"
}