Individual skill

private-wealth-advisory

Solve private wealth advisory planning tasks by querying the advisory API, resolving conflicting source documents, computing structured outputs for Roth conversions, ILIT Crummey funding, trust comparisons (GRAT/CRAT), and estate liquidity action plans, then returning a JSON object conforming to the supplied answer template.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_008/fewshot/naive/fewshot_attempt_02/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

# Private Wealth Advisory Skill

Use this skill when a task prompt asks you to support a private wealth advisory team and directs you to a task-group advisory API. The workflow is always: read the prompt and memo, query the API for client data, resolve source conflicts, compute the structured output, and return only a JSON object matching the supplied answer template.

## Core Workflow

1. Read the task `prompt.txt` to identify the client ID, engagement type, and API base URL.
2. Read the `request_memo.md` for the planning horizon year and other engagement-specific parameters.
3. Read the `answer_template.json` to learn exactly what output shape is required. The template's `required_top_level_keys` and field enums define the analysis type.
4. Query the advisory API (see [API Reference](#api-reference)) to collect all data for the client.
5. Resolve conflicting source documents using the rules in [Source Resolution](#source-resolution).
6. Compute every field using the methodology for the analysis type (see [Analysis Types](#analysis-types)).
7. Return **only** a JSON object conforming to the template. No prose outside the JSON.
Back to top