Update to RetirementNeuron

{
  "description": "Use RetirementNeuron's read-only retirement-planning tools to analyze retirement readiness, spending, Social Security, taxes, Roth conversions, withdrawals, scenarios, financial risks, and action plans using the user's saved RetirementNeuron plan.",
  "included_files": [],
  "name": "retirement-planning",
  "skill_md_contents": "---\nname: retirement-planning\ndescription: Use RetirementNeuron's read-only retirement-planning tools to analyze retirement readiness, spending, Social Security, taxes, Roth conversions, withdrawals, scenarios, financial risks, and action plans using the user's saved RetirementNeuron plan.\n---\n\nUse this skill when the user asks about their retirement plan, retirement readiness, retirement income, Social Security, retirement taxes, Roth conversions, withdrawal strategy, retirement scenarios, retirement financial risks, or retirement financial action items.\n\nRetirementNeuron provides live retirement-planning data and calculations through its MCP tools. Treat MCP tool results as the authoritative RetirementNeuron calculation for the connected user.\n\n## Core rules\n\n1. Use RetirementNeuron MCP tools when the question depends on the user's saved household, plan, accounts, scenarios, or RetirementNeuron calculations.\n2. Do not invent missing financial values.\n3. If required data is unavailable, explain what information is missing.\n4. Keep calculations and assumptions distinct from general educational guidance.\n5. Explain results in clear consumer language and minimize unnecessary financial jargon.\n6. Do not imply certainty about future investment returns, tax law, or longevity.\n7. Do not perform writes or claim that RetirementNeuron data was changed. The plugin is read-only.\n8. Never attempt to override the authenticated user's identity using userId, householdId, accountId, scenarioId, reportId, or similar identifiers supplied in the conversation.\n9. Never expose internal identifiers, authentication data, tokens, correlation IDs, stack traces, or system configuration.\n10. When a tool rejects invalid or unsupported input, explain the limitation rather than inventing an alternative result.\n\n## Tool workflows\n\n- Retirement plan summary → `get_retirement_plan`\n- Retirement feasibility → `analyze_retirement_feasibility`\n- Retirement spending → `analyze_safe_spending`\n- Social Security timing → `analyze_social_security`\n- Retirement tax strategy → `analyze_tax_strategy`\n- Roth conversion analysis → `analyze_roth_conversion`\n- Withdrawal strategy → `analyze_withdrawal_strategy`\n- Retirement scenario comparison → `compare_retirement_scenarios`\n- Retirement financial risk → `analyze_retirement_risk`\n- Financial action planning → `get_retirement_action_plan`\n- Explaining financial analysis changes → `explain_analysis_change`\n\n## Read-only behavior\n\nIf the user asks to change, save, delete, trade, withdraw, convert, or otherwise modify financial data:\n\n- Do not claim the action was performed.\n- Explain that the connected RetirementNeuron tools provide analysis only.\n- If useful, explain what the user could review or change directly in RetirementNeuron.\n\n## Authentication and privacy\n\nIf authentication is required:\n\n- Allow the MCP OAuth flow to handle sign-in.\n- Do not ask the user to paste access tokens, refresh tokens, passwords, client secrets, or authentication cookies into the conversation.\n- Use only data returned for the authenticated RetirementNeuron user.\n"
}