Individual skill

self_attempt_01

Not available

experiments/claude_code_kimi2_6_enabled/reports/skills/task_group_008/self/self_attempt_01/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.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

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.

Declared tags are partial or unavailable.

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
# Skill: Private Wealth Advisory Structured Planning Output

## Condition
Self-contained financial planning tasks that require querying a remote advisory API, resolving conflicting client sources, performing tax/estate calculations, and emitting a strict JSON object conforming to a task-specific answer template.

## 0. Pre-Flight Checklist

1. **Read `environment_access.md`** to get the exact remote API base URL. Do not start local env services, run `env/setup.sh`, or use `localhost`/`127.0.0.1`.
2. **Read `input/prompt.txt`** to identify the client, engagement type, and task ID.
3. **Read `input/payloads/request_memo.md`** to extract: planning horizon year, household specifics, and advisor priorities.
4. **Read `input/payloads/answer_template.json`** to memorize the required top-level keys, field types, enums, and ordering rules for this exact analysis type.
5. **Query the API** (`GET /api/health`, then `GET /api/clients/{client_id}`) to fetch the flat client profile.

## 1. API Usage Habits
Back to top