Menu

Individual skill

advisory-planning-json

0upvotes

Produce private wealth advisory planning JSON from a task memo, answer template, and the advisory API. Use for Roth conversion/RMD summaries, ILIT Crummey funding cycles, GRAT versus CRAT comparisons, and estate liquidity action plans that require resolving conflicting client records and returning only structured JSON.

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

# Advisory Planning JSON

Use this skill when a private wealth advisory task asks for a JSON object based on a local memo/template and the advisory API.

## Workflow

1. Read the task prompt, `input/payloads/request_memo.md`, and `input/payloads/answer_template.json`.
2. Get the API base from `API_BASE` when present. Otherwise use the base URL supplied by the task harness.
3. Extract `client_id`, planning horizon if present, and `task_id` from the task directory name or pass it explicitly.
4. Query records with client filters instead of broad collection reads:
   - `/api/clients/{client_id}`
   - `/api/source-documents?client_id={client_id}`
   - `/api/retirement-accounts?client_id={client_id}`
   - `/api/life-insurance?client_id={client_id}`
Back to top