Menu

Individual skill

wealth-advisory

Private wealth tax and estate planning analysis via advisory API. Use when a prompt asks you to prepare structured wealth planning JSON output for a client engagement using an advisory API base URL (usually API_BASE). Covers Roth conversion RMD analysis, ILIT Crummey funding, GRAT vs CRAT trust comparison, and estate liquidity action plans. The advisory environment provides client records, source documents, retirement accounts, life insurance policies, trust candidates, tax policy constants, and RMD factors accessible via REST endpoints.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_008/fewshot/codex/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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

Prepare structured JSON planning outputs for private wealth advisory engagements. The harness supplies an API base URL (typically `API_BASE`). Use `curl` to call the endpoints listed in [API Reference](references/api_reference.md).

## Workflow

1. Read `input/payloads/request_memo.md` to identify the client ID and engagement type.
2. Read `input/payloads/answer_template.json` to learn the required output schema.
3. Fetch all relevant API data for the client. Start with these calls in parallel:
   - `GET {API_BASE}/api/clients/{client_id}`
   - `GET {API_BASE}/api/source-documents` (filter by client_id)
   - `GET {API_BASE}/api/retirement-accounts` (filter by client_id)
   - `GET {API_BASE}/api/life-insurance` (filter by client_id)
   - `GET {API_BASE}/api/trust-candidates` (filter by client_id)