agentleFS
allenlee0430allenlee0430/allenlee-lab-skills/.claude/skills/manage-research-portfolio/SKILL.md

manage-research-portfolio

Skill0 starsChanged 5 months agoMITView on GitHub

Build and maintain a PI-level command view of Bowen Li's grants, manuscripts, experiments, trainees, collaborations, talks, deadlines, decisions, and risks. Use for weekly planning, deadline radar, project prioritization, workload balancing, status reporting, and converting scattered files or notes into an actionable research portfolio.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create one row per outcome-bearing project, not one row per file.

    line 9
  2. Distinctive:

    Never infer a commitment from an early draft or old file.

    line 14
  3. Very specific:

    Read references/portfolio-schema.md before creating or revising the tracker.

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “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

Manage research portfolio

  1. Gather current evidence from 00_Active_Now, recent files, calendar or email when authorized, and existing trackers.
  2. Create one row per outcome-bearing project, not one row per file.
  3. Record objective, current stage, next irreversible decision, next action, owner, deadline, dependency, risk, confidence, and source evidence.
  4. Distinguish hard external deadlines from internal targets and undated aspirations.
  5. Rank work by scientific or strategic value, deadline pressure, dependency leverage, and PI attention required.
  6. Produce a weekly command brief: wins, deadlines in 14/30/90 days, blocked items, decisions only Bowen can make, delegated actions, and projects to pause.
  7. Never infer a commitment from an early draft or old file. Mark stale or conflicting evidence.
  8. Maintain a decision log so the same issue is not repeatedly reopened without new evidence.

Read references/portfolio-schema.md before creating or revising the tracker.

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.