How do I install the Portfolio skill?

Run npx skillmds@latest add sd0xdev/portfolio in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Portfolio safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Portfolio?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Portfolio free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Portfolio?

sd0xdev (@sd0xdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Portfolio by sd0xdev — Agent Skill

Name: Portfolio
Author: sd0xdev

Portfolio

Portfolio system knowledge base. Use when: position queries, routing strategy questions, provider integration. Not for: general code exploration (use code-explore), code review (use codex-code-review). Output: domain-specific analysis + recommendations.

sd0xdev Updated Sep 17, 2026

File contents

Portfolio Skill

Trigger

Keywords: Portfolio, portfolio, position, {PRIMARY_PROVIDER}, protocol, lending, staking, liquidity

When NOT to Use

General token queries (not Portfolio positions)
Transaction building (use corresponding provider)
Non-portfolio related API issues

Core Files

Type	File	Purpose
Controller	`src/entity/portfolio/portfolio.controller.ts`	REST API
Router	`src/service/portfolio/source-router/*.service.ts`	Routing orchestration
Client	`src/service/portfolio/providers/{provider}/*.ts`	{PRIMARY_PROVIDER} integration
Aggregator	`src/service/portfolio/aggregation/*.service.ts`	Aggregation computation
DTO	`src/dto/portfolio/position.types.ts`	Position model

API Overview

Base: /onchain/v1/portfolio

Endpoint	Method	Purpose
`/positions`	POST	Get portfolio positions
`/chains`	GET	Supported chains list
`/protocols`	GET	Supported protocols list

Output

Domain-specific query results with code references
Analysis and recommendations based on current architecture

Verification

Position data correctly normalized
Cache hit/miss working properly
Aggregation calculations accurate

Development Guide

Add Protocol Support

Check if {PRIMARY_PROVIDER} supports it
If custom build needed: implement PortfolioPositionExtractor + register + configure routing

Add Data Source

Implement ProviderClient + Adapter
Register with SourceRouter
Configure routing strategy

Debug

redis-cli keys "portfolio:{provider}:*"
redis-cli get "portfolio:{provider}:positions:0x...:v2:..."
curl -X POST /positions -d '{"isForceRefresh": true, ...}'

References

references/architecture.md - System architecture + cache strategy
references/api.md - API reference + data models
@docs/features/portfolio/ - Detailed documentation

Tests

Type	Location
Unit	`test/unit/service/portfolio/`
Integration	`test/integration/portfolio/`

Examples

Input: How to query portfolio positions?
Action: Explain POST /positions API + routing strategy

Input: How does {PRIMARY_PROVIDER} integration work?
Action: Explain {PRIMARY_PROVIDER}Client + {PRIMARY_PROVIDER}Adapter flow

---name: portfoliodescription: Portfolio system knowledge base. Use when: position queries, routing strategy questions, provider integration. Not for: general code exploration (use code-explore), code review (use codex-code-review). Output: domain-specific analysis + recommendations.---# Portfolio Skill## Trigger- Keywords: Portfolio, portfolio, position, {PRIMARY_PROVIDER}, protocol, lending, staking, liquidity## When NOT to Use- General token queries (not Portfolio positions)- Transaction building (use corresponding provider)- Non-portfolio related API issues## Core Files| Type | File | Purpose || ---------- | -------------------------------------------------- | ----------------------- || Controller | `src/entity/portfolio/portfolio.controller.ts` | REST API || Router | `src/service/portfolio/source-router/*.service.ts` | Routing orchestration || Client | `src/service/portfolio/providers/{provider}/*.ts` | {PRIMARY_PROVIDER} integration || Aggregator | `src/service/portfolio/aggregation/*.service.ts` | Aggregation computation || DTO | `src/dto/portfolio/position.types.ts` | Position model |## API Overview**Base**: `/onchain/v1/portfolio`| Endpoint | Method | Purpose || ------------ | ------ | --------------------- || `/positions` | POST | Get portfolio positions || `/chains` | GET | Supported chains list || `/protocols` | GET | Supported protocols list |## Output- Domain-specific query results with code references- Analysis and recommendations based on current architecture## Verification- Position data correctly normalized- Cache hit/miss working properly- Aggregation calculations accurate## Development Guide### Add Protocol Support1. Check if {PRIMARY_PROVIDER} supports it2. If custom build needed: implement `PortfolioPositionExtractor` + register + configure routing### Add Data Source1. Implement `ProviderClient` + `Adapter`2. Register with `SourceRouter`3. Configure routing strategy### Debug```bashredis-cli keys "portfolio:{provider}:*"redis-cli get "portfolio:{provider}:positions:0x...:v2:..."curl -X POST /positions -d '{"isForceRefresh": true, ...}'```## References- `references/architecture.md` - System architecture + cache strategy- `references/api.md` - API reference + data models- @docs/features/portfolio/ - Detailed documentation## Tests| Type | Location || ----------- | ------------------------------ || Unit | `test/unit/service/portfolio/` || Integration | `test/integration/portfolio/` |## Examples```Input: How to query portfolio positions?Action: Explain POST /positions API + routing strategy``````Input: How does {PRIMARY_PROVIDER} integration work?Action: Explain {PRIMARY_PROVIDER}Client + {PRIMARY_PROVIDER}Adapter flow```

Frequently asked questions