portfolio-manager
Skill91 starsChanged 2 months agoMITView on GitHub
Inspect all configured fantasy teams, saved players, lineup analysis, and transaction proposals through the portfolio MCP. Open the local dashboard for visual review and exact proposal approval.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- jwd2a/claude-skillstheir own version, first seen Oct 13, 2026
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- ntaffzii/Skill-Agentstheir own version, first seen Sep 2, 2026
- darker2016/WorkbuddySkillGroups4DSHtheir own version, first seen Aug 14, 2026
- 9thLevelSoftware/legiontheir own version, first seen May 5, 2026
- finskills/portfolio-managertheir own version, first seen May 4, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- 9thLevelSoftware/legion★ 76same name
- ancs21/ai-sub-invest★ 19same name
- darker2016/WorkbuddySkillGroups4DSH★ 6same name
- ntaffzii/Skill-Agents★ 4same name
- finskills/portfolio-manager★ 0same name
- IngAs8/ClaudeSkill★ 0same name
- jwd2a/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- draft-assistantSkill
- espn-automationSkill
- season-managerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 6 are distinctive, and 11 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use the portfolio MCP for requests that span managed teams.
- Distinctive: line 10
Use the manager and ESPN companion for operations on one selected team.
- Very specific: line 14
Call list_managed_teams to discover configured team keys.
- Very specific: line 15
Call get_managed_team for the selected roster, policy, and limits.
- Very specific: line 16
Call get_managed_analysis for a calculation from its saved snapshot.
- Very specific: line 17
Call search_managed_players to search owned players or the saved player pool.
- Very specific: line 18
Call list_managed_proposals to inspect saved transaction status.
- Very specific: line 21
Use FFM_PORTFOLIO_MANIFEST or the command's --manifest argument to select a private configuration.
- Distinctive: line 26
Check source age, completeness, verified locks, and proposal revisions before describing an action as ready.
- Very specific: line 28
Keep calculated recommendations separate from prepared proposals.
- Very specific: line 29
Keep synthetic results separate from live confirmations.
- Very specific: line 31
Check truncated before describing proposal history as complete.
- Very specific: line 36
Run fantasy-football-dashboard --demo for a fictional workspace.
- Very specific: line 37
Run the dashboard with the private manifest to inspect actual saved teams.
- Distinctive: line 41
Do not treat a read request or dashboard setup as permission to submit a live transaction.
- Distinctive: line 45
Use the season-manager workflow for HTTP transactions and draft-assistant for drafts.
- Distinctive: line 46
Do not start a browser to service portfolio reads or HTTP season submissions.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Portfolio manager
Use the portfolio MCP for requests that span managed teams. Use the manager and ESPN companion for operations on one selected team.
Read the portfolio
- Call
list_managed_teamsto discover configured team keys. - Call
get_managed_teamfor the selected roster, policy, and limits. - Call
get_managed_analysisfor a calculation from its saved snapshot. - Call
search_managed_playersto search owned players or the saved player pool. - Call
list_managed_proposalsto inspect saved transaction status.
These five tools read local state. They do not contact ESPN or submit transactions.
Use FFM_PORTFOLIO_MANIFEST or the command's --manifest argument to select a private configuration.
An existing server coordinator manifest is accepted. The tools do not search disks for team stores.
Interpret results
Check source age, completeness, verified locks, and proposal revisions before describing an action as ready.
Unknown projections remain unknown. Saved pool membership does not prove current player availability.
Keep calculated recommendations separate from prepared proposals.
Keep synthetic results separate from live confirmations.
pending_waiver means ESPN accepted a queued claim. It does not establish player ownership.
Check truncated before describing proposal history as complete.
The first implementation supports football. Provider and sport fields do not establish support for other sports.
Dashboard and submissions
Run fantasy-football-dashboard --demo for a fictional workspace.
Run the dashboard with the private manifest to inspect actual saved teams.
The dashboard requires --enable-actions before it permits submissions.
Its review flow binds approval to one exact saved HTTP season proposal.
It applies the existing team policy and HTTP transaction checks.
Do not treat a read request or dashboard setup as permission to submit a live transaction.
For actions through MCP, select the existing ESPN companion for the exact team context. Preserve saved modes, limits, protected players, and pending commitments. Use the season-manager workflow for HTTP transactions and draft-assistant for drafts. Do not start a browser to service portfolio reads or HTTP season submissions. An uncertain result requires reconciliation. Do not submit the same transaction again.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.