agentsclimarketplace
Sign in

Bowen research command center

Skill allenlee0430/bowen-ai-skills/skills/bowen-research-command-center

Build an evidence-backed daily or weekly command view of Bowen Li's active research, manuscripts, grants, talks, collaborations, and decisions. Use when asked what to prioritize, what changed recently, what is blocked, what deadlines are approaching, or how to coordinate multiple research workstreams from local files and connected calendars, mail, or Teams.From its SKILL.md

Install
npx -y skills add allenlee0430/bowen-ai-skills --skill bowen-research-command-center

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 402 tokens by cl100k_base, as published. Nobody here has run it

Bowen Research Command Center

Workflow

  1. Read references/operating-map.md before scanning.
  2. Establish the time horizon: today, this week, this month, or a named deadline.
  3. Gather only relevant evidence. Start with recent metadata in the mapped research roots; use connected calendars, email, and Teams only when they can clarify status, commitments, blockers, or decisions.
  4. Cross-check mail-derived blockers against Teams chats, recent threads, mentions, or named project channels. If Teams shows a reply, decision, delegation, or resolution, record the item as resolved or delegated via Teams rather than treating email silence as an open blocker.
  5. Convert evidence into a portfolio table with: workstream, desired outcome, stage, next decision, blocker, deadline, owner, and evidence path or connected-source item.
  6. Rank work by deadline risk, scientific leverage, dependency blocking, and evidence freshness. Do not equate file recency with importance without corroboration.
  7. Return:
    • top three outcomes;
    • decision queue;
    • blocked/delegatable items;
    • deadlines and follow-ups;
    • cross-channel closure notes for items resolved outside email;
    • a short stop-doing list.

Rules

  • Separate verified facts, file-derived inferences, and recommendations.
  • Prefer decisions and outcomes over activity counts.
  • Do not read credentials, identity documents, or private finance records.
  • Treat Teams replies, decisions, delegations, and acknowledgments as valid evidence for closing mail-derived research follow-ups. Preserve the Teams source and timestamp when available.
  • Scope Teams reads tightly by horizon, workstream, named collaborators, unread chats, recent threads, or mentions. Report coverage limits when Teams access is broad, incomplete, or unavailable.
  • Do not send messages, change calendars, create Planner tasks, mark Teams items read, or move files unless explicitly asked.
  • Link each important claim to a local path or connected-source item.

What ships with it: 2 files

2.2 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.