portfolio
Skill2 starsChanged 51 days agoMITView on GitHub
Cross-project portfolio view comparing value distribution and effort allocation
23 other projects use a version of this.
Adopted by
Most recently taken up by
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- thesun4sky/jobstacktheir own version, first seen Nov 10, 2026
- markbaindesign/bain-studiotheir own version, first seen Nov 8, 2026
- fainir/agent-harnesstheir own version, first seen Nov 1, 2026
- ahmetenesdur/starkfitheir own version, first seen Oct 25, 2026
- Seth090502/osanwe-publictheir own version, first seen Oct 20, 2026
Used with
Projects with it also use risk, ask and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OlayeeeyoSkillrisk
评估当前整体持仓的风险敞口。当用户输入 /risk 时触发。适用场景:"我的持仓有什么风险?" "期权 assignment 风险大吗?" "持仓集中度怎样?
Also in 3 projects that use this
dubwoahSkillask
Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.
Also in 3 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- anthropics/claude-for-legal★ 9.5ksame name
- gauss314/skills★ 242same name
- thesun4sky/jobstack★ 216same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- Kanevry/session-orchestrator★ 53same name
- RaoHai/ClaudeQuant★ 8same name
- davidromeo/tradeblocks-skills★ 4same name
- ExarLabs/paros-advisor★ 4same name
- tradeblocks-org/tradeblocks-skills★ 4same name
13 more not listed
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 repository8 other files it gives its agents.
- flow-metricsSkill
- intakeSkill
- plan-sprintSkill
- reprioritizeSkill
- retro-accuracySkill
- sliceSkill
- standupSkill
- what-ifSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Use project_list to get all projects
- Very specific: line 15
Use report_summary for each project
“Common” is measured: kept by at least 6 in 10 of the 18 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
Multi-Project Portfolio View
Generate a cross-project portfolio analysis.
Data collection
- Use
project_listto get all projects - For each project, get the active tickets with
ticket_listandexcludeTags: ["state:done"]: its items carry value, cost and priority (ticket_listreturns 100 tickets per call: page withoffsetuntil you havetotalof them).calc_priorityranks done tickets too, so don't take the metrics below from it - Use
report_summaryfor each project
Portfolio metrics
For each project, calculate:
- Total Value: sum of (benefit + penalty) across active tickets
- Total Cost: sum of (estimate + risk) across active tickets
- Average Priority: mean priority of the active tickets
- Ticket Count: total active tickets
- Completion Rate: tickets tagged
state:done/ total tickets
Output
Project comparison table
| Project | Tickets | Total Value | Total Cost | Avg Priority | Done % |
Value vs. Cost chart (text-based)
Show a simple bar comparison for each project:
ProjectA: Value ████████████ 120 Cost ██████ 60
ProjectB: Value ████ 40 Cost ████████ 80Imbalance analysis
Identify projects where:
- High value but low effort allocated (under-invested)
- Low value but high effort allocated (over-invested)
- High average priority (urgent backlog)
- Low completion rate (execution problems)
Recommendations
Suggest rebalancing actions:
- "Project Alpha has 60% of total value but only 30% of effort. Consider shifting resources."
- "Project Beta has low value and high cost. Evaluate whether to continue or descope."
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.

