Update to MayRetire
Snapshot Oct 28, 2026 · 13:08 UTC · version 0.3.0
Collection source: downloaded plugin package.
Instructions updated for mayretire-create-plan
Skill instructions — Now says: For interface guidance, consult the bundled [MayRetire tutorial](../mayretire-app-assistant/references/MayRetire_Tutorial.md) and its relevant screenshots....
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 25, 2026 · 12:05 UTC
No removed lines (ordering may have changed)
Oct 28, 2026 · 13:08 UTC
For interface guidance, consult the bundled [MayRetire tutorial](../mayretire-app-assistant/references/MayRetire_Tutorial.md) and its relevant screenshots. For the new JSON plan, rely on `describe`, `inspect_plan_payload`, and calculatio...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -23,6 +23,12 @@ user wants to keep or import it; the remote service does not save it to an account. Use `plan_handoff_url` only when the user asks to view it in MayRetire. +For interface guidance, consult the bundled +[MayRetire tutorial](../mayretire-app-assistant/references/MayRetire_Tutorial.md) +and its relevant screenshots. For the new JSON plan, rely on `describe`, +`inspect_plan_payload`, and calculation results to decide which fields actually +apply. Link the public tutorial when explaining where users enter a setting. + For detailed interpretation after creation, use the `mayretire` skill's topic-specific references. Do not present projections as personalized financial, tax, or legal advice.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: mayretire-create-plan\ndescription: Create a Canadian retirement plan through a guided interview and MayRetire MCP when the user has no exported plan or asks to build a new one.\n---\n\n# Create a MayRetire plan\n\nThe remote MayRetire MCP cannot read a user's account, browser storage, or local\nfiles. Explain that supplied financial data is sent through the assistant to\nMayRetire's server for processing. Do not request credentials, government IDs,\npayment-card details, or health information. Ask the user for missing material\nfacts in short batches; distinguish unknown values from real zeros. Engine\ndefaults and templates are not recommendations.\n\nRead [the guided interview](references/creating-a-plan.md) before constructing\na plan. Use `describe` for unfamiliar fields and collections. Call\n`create_plan_payload` with the answers, then `validate_plan_payload` and\n`inspect_plan_payload` on the returned complete plan. Review the household,\ntimeline, goals, benefits, accounts, employment, portfolios, and material\nassumptions with the user. Do not calculate while material amounts remain\nunknown. Once the baseline is confirmed, use `calculate_plan_payload` and\nexplain its active success criteria. Return the complete plan JSON when the\nuser wants to keep or import it; the remote service does not save it to an\naccount. Use `plan_handoff_url` only when the user asks to view it in MayRetire.\n\nFor detailed interpretation after creation, use the `mayretire` skill's\ntopic-specific references. Do not present projections as personalized\nfinancial, tax, or legal advice.\n"
"---\nname: mayretire-create-plan\ndescription: Create a Canadian retirement plan through a guided interview and MayRetire MCP when the user has no exported plan or asks to build a new one.\n---\n\n# Create a MayRetire plan\n\nThe remote MayRetire MCP cannot read a user's account, browser storage, or local\nfiles. Explain that supplied financial data is sent through the assistant to\nMayRetire's server for processing. Do not request credentials, government IDs,\npayment-card details, or health information. Ask the user for missing material\nfacts in short batches; distinguish unknown values from real zeros. Engine\ndefaults and templates are not recommendations.\n\nRead [the guided interview](references/creating-a-plan.md) before constructing\na plan. Use `describe` for unfamiliar fields and collections. Call\n`create_plan_payload` with the answers, then `validate_plan_payload` and\n`inspect_plan_payload` on the returned complete plan. Review the household,\ntimeline, goals, benefits, accounts, employment, portfolios, and material\nassumptions with the user. Do not calculate while material amounts remain\nunknown. Once the baseline is confirmed, use `calculate_plan_payload` and\nexplain its active success criteria. Return the complete plan JSON when the\nuser wants to keep or import it; the remote service does not save it to an\naccount. Use `plan_handoff_url` only when the user asks to view it in MayRetire.\n\nFor interface guidance, consult the bundled\n[MayRetire tutorial](../mayretire-app-assistant/references/MayRetire_Tutorial.md)\nand its relevant screenshots. For the new JSON plan, rely on `describe`,\n`inspect_plan_payload`, and calculation results to decide which fields actually\napply. Link the public tutorial when explaining where users enter a setting.\n\nFor detailed interpretation after creation, use the `mayretire` skill's\ntopic-specific references. Do not present projections as personalized\nfinancial, tax, or legal advice.\n"
Full snapshot data
{
"description": "Create a Canadian retirement plan through a guided interview and MayRetire MCP when the user has no exported plan or asks to build a new one.",
"included_files": [
{
"relative_path": "references/creating-a-plan.md",
"size_in_bytes": 2676
}
],
"name": "mayretire-create-plan",
"skill_md_contents": "---\nname: mayretire-create-plan\ndescription: Create a Canadian retirement plan through a guided interview and MayRetire MCP when the user has no exported plan or asks to build a new one.\n---\n\n# Create a MayRetire plan\n\nThe remote MayRetire MCP cannot read a user's account, browser storage, or local\nfiles. Explain that supplied financial data is sent through the assistant to\nMayRetire's server for processing. Do not request credentials, government IDs,\npayment-card details, or health information. Ask the user for missing material\nfacts in short batches; distinguish unknown values from real zeros. Engine\ndefaults and templates are not recommendations.\n\nRead [the guided interview](references/creating-a-plan.md) before constructing\na plan. Use `describe` for unfamiliar fields and collections. Call\n`create_plan_payload` with the answers, then `validate_plan_payload` and\n`inspect_plan_payload` on the returned complete plan. Review the household,\ntimeline, goals, benefits, accounts, employment, portfolios, and material\nassumptions with the user. Do not calculate while material amounts remain\nunknown. Once the baseline is confirmed, use `calculate_plan_payload` and\nexplain its active success criteria. Return the complete plan JSON when the\nuser wants to keep or import it; the remote service does not save it to an\naccount. Use `plan_handoff_url` only when the user asks to view it in MayRetire.\n\nFor interface guidance, consult the bundled\n[MayRetire tutorial](../mayretire-app-assistant/references/MayRetire_Tutorial.md)\nand its relevant screenshots. For the new JSON plan, rely on `describe`,\n`inspect_plan_payload`, and calculation results to decide which fields actually\napply. Link the public tutorial when explaining where users enter a setting.\n\nFor detailed interpretation after creation, use the `mayretire` skill's\ntopic-specific references. Do not present projections as personalized\nfinancial, tax, or legal advice.\n"
}SHA-256 of public snapshot: a38b127a06bd6fcd0a6f230cb1f665d1bbbf932ae0cf921b02d822238af800ff