Menu

Individual skill

wealth-advisory-planning-json

0upvotes

Solve private wealth advisory planning tasks that require JSON outputs from the advisory API, including Roth/RMD projections, ILIT Crummey funding checks, GRAT/CRAT comparisons, and estate liquidity action plans.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_008/fewshot/naive/fewshot_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Wealth Advisory Planning JSON

Use this skill when a task asks for a structured JSON planning output for a private wealth advisory client and provides an advisory API base URL, request memo, and `answer_template.json`.

## Required Workflow

1. Read the task prompt, `input/payloads/request_memo.md`, and `input/payloads/answer_template.json`.
2. Extract `client_id`, engagement type, planning horizon if stated, and the output schema.
3. Use the API base supplied by the harness, usually `$API_BASE`. Query only business-data endpoints needed for the current `client_id`; do not call judge or evaluator endpoints.
4. Fetch:
   - Always: `GET /api/clients/{client_id}`, `GET /api/source-documents?client_id={client_id}`, `GET /api/policies/tax`.
   - Roth/RMD: `GET /api/retirement-accounts?client_id={client_id}` and `GET /api/rmd-factors`.
   - ILIT: `GET /api/life-insurance?client_id={client_id}`.
   - GRAT/CRAT or estate liquidity: `GET /api/trust-candidates?client_id={client_id}`; estate liquidity also needs life-insurance.
Back to top