← Back to list
tax-loss-harvesting Checked
Tax-loss harvesting opportunity identification, scoring, and planning with wash sale compliance a…
8.1Overall rating
Installation
🤖 Install via AI
Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.
Install the "tax-loss-harvesting" skill by following the instructions at https://skill123.me/install/tax-loss-harvesting.
⌨️ Command line install
Run in your terminal — downloads and installs to ~/.claude/skills/.
curl -fsSL https://skill123.me/install/tax-loss-harvesting.sh | bash
📦 Download ZIP
Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.
⬇ Download v1.0.0 · 14 KBAbout this skill
Overview
Tax-loss harvesting opportunity identification, scoring, and planning with wash sale compliance and annual carryforward tracking
Source
- Repo: https://github.com/agiprolabs/claude-trading-skills
- Path: skills/tax-loss-harvesting
Score breakdown
Trigger
4.0
Description covers What (opportunity identification, scoring, planning, wash sale compliance, carryforward) but no When/When-Not or trigger variants: 3+2+3+0=8/20
Structure
9.3
294-line SKILL.md, one reference and one script, clean Files table: 4+5+3+2=14/15
Workflow
7.6
Task-oriented use cases and quick-start scoring code; deterministic formulas; single-tool design limits pattern richness; verification light: 5+4+5+3+2=19/25
Content
10.0
Concise, worked numeric examples, consistent tables: 10/10
Engineering
10.0
Valid extended frontmatter; script has shebang and stdlib-only deps; all paths exist: 10/10
Security
10.0
Fully offline; no eval/base64/destructive ops, no secrets, no injection; prominent tax disclaimers; capabilities match declared scope: 20/20
Tax-loss harvesting planner: TLH opportunity scoring, net-benefit calculation, wash-sale interaction, carryforward tracking, year-end strategies; offline stdlib-only demo scanner. Strong compliance posture: 'NOT tax advice' disclaimer appears in header and footer, jurisdiction caveats throughout. Capability manifest: no file/env/credential reads, no writes, no network egress, no persistence — capabilities match declared scope. Reference file again misnamed 'planned_features.md'.