Individual skill

wealth-advisory-json

Use this skill whenever the user asks for a client-specific private wealth advisory JSON output using a request memo, answer_template.json, and an advisory API. It is for estate liquidity plans, Roth conversion and RMD projections, ILIT/Crummey administration, GRAT versus CRAT comparisons, trust-transfer recommendations, and similar wealth-planning tasks. Use it even when the user only says to prepare the structured planning output or return the final JSON.

experiments/codex_skill_creator_comparison_gpt5_5_xhigh/reports/skills/task_group_008/fewshot/opencode/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 JSON

Use this skill to produce a final JSON object for private wealth advisory planning tasks. The local `answer_template.json` is the output contract; the API data and local request memo are the evidence. The answer should be client-specific and numerical, not a generic planning memo.

## First Pass

1. Read the task prompt, the request memo, and `input/payloads/answer_template.json`.
2. Extract `client_id`, engagement/topic, planning year, and any horizon year from the memo. If the memo gives a horizon, use it for projection fields.
3. Use the task-provided API base URL, usually `API_BASE`, and fetch only the advisory endpoints made available by the task environment.
4. Build a client data packet before calculating. You may use the bundled helper:

```bash
python scripts/fetch_case_data.py CLIENT_ID --out /tmp/advisory_case.json
```