agentleFS
sebssebs/rewelo/.claude/skills/portfolio/SKILL.md

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

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.
  • OlayeeeyoSkill

    risk

    评估当前整体持仓的风险敞口。当用户输入 /risk 时触发。适用场景:"我的持仓有什么风险?" "期权 assignment 风险大吗?" "持仓集中度怎样?

    Also in 3 projects that use this

  • dubwoahSkill

    ask

    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

  • AnthropicSkill

    architecture

    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

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
  1. Very specific:

    Use project_list to get all projects

    line 13
  2. Very specific:

    Use report_summary for each project

    line 15

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Multi-Project Portfolio View

Generate a cross-project portfolio analysis.

Data collection

  1. Use project_list to get all projects
  2. For each project, get the active tickets with ticket_list and excludeTags: ["state:done"]: its items carry value, cost and priority (ticket_list returns 100 tickets per call: page with offset until you have total of them). calc_priority ranks done tickets too, so don't take the metrics below from it
  3. Use report_summary for 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

ProjectTicketsTotal ValueTotal CostAvg PriorityDone %

Value vs. Cost chart (text-based)

Show a simple bar comparison for each project:

ProjectA: Value ████████████ 120  Cost ██████ 60
ProjectB: Value ████ 40         Cost ████████ 80

Imbalance 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."

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.