Track several parallel businesses, ventures or long-running ideas as one portfolio, with one card type per business and a generated overview; modes card, pulse, review and strategy. Use when the person asks "how are my businesses doing", "what moved this week", "weekly pulse", "monthly review of X", "quarterly strategy", "add this idea to the portfolio", or "which one next".
Installs into .claude/skills of the current project.
Are you the author of Portfolio?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/exarlabs-portfolio)
---
name: portfolio
description: Track several parallel businesses, ventures or long-running ideas as one portfolio, with one card type per business and a generated overview; modes card, pulse, review and strategy. Use when the person asks "how are my businesses doing", "what moved this week", "weekly pulse", "monthly review of X", "quarterly strategy", "add this idea to the portfolio", or "which one next".
---
# portfolio
Thin entry (PAROS P04). The knowledge lives in a live definition; this file only finds it.
1. Locate the live definition, first match wins:
- where the vault entry file (`AGENTS.md` or `CLAUDE.md`) says skills live: `<skills folder>/portfolio/CURRENT.md`;
- `<vault>/PAROS/skills/portfolio/CURRENT.md`;
- the PAROS reference copy: `<paros repo>/skills/portfolio/CURRENT.md`.
2. Read it in full, and the `LOCAL.md` next to it if present. Read its `version:` field.
3. Report one line before working:
- from the vault: `Running portfolio v<X> from your vault`;
- from the reference copy: `Running portfolio v<X> from the PAROS reference, not yet adopted`.
4. Follow it. Its `## Constitution` always wins.
5. If the person corrects the result, write a learning packet to the skill's `observations/` folder (P05).