agentsclimarketplace

Bowen faculty operations

Skill allenlee0430/bowen-ai-skills/skills/bowen-faculty-operations

Reusable Codex and Claude Code skills for research operations, grants, evidence synthesis, lab-in-the-loop planning, file curation, and faculty workflows.

Install
npx -y skills add allenlee0430/bowen-ai-skills --skill bowen-faculty-operations

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.

What its author says it does

Copied from the file, not written here

Coordinate Bowen Li's faculty and principal-investigator operations across mentoring, reference letters, teaching, committees, lab administration, reimbursements, procurement, consulting, travel, and institutional deadlines. Use for daily briefs, weekly reviews, task extraction, delegation plans, meeting preparation, or converting mixed files, email, Teams, and calendar evidence into a controlled action queue.

SKILL.md

2.2 KB, 354 tokens by cl100k_base, as published. Nobody here has run it

Bowen Faculty Operations

Workflow

  1. Read references/operating-rhythm.md.
  2. Define the time horizon and data sources. Use connected calendar, email, Teams, and files only when available and relevant.
  3. Review Gmail, Outlook, and Teams as one cross-channel commitment surface. When an email looks unanswered or unresolved, check relevant Teams chats, recent threads, mentions, or named channels before marking it as open.
  4. Extract commitments with owner, deadline, dependency, next action, resolution status, and evidence.
  5. Classify into mentoring, teaching, committees, lab operations, finance, travel, consulting, and personal administration.
  6. Rank by deadline, consequence, dependency, and delegability.
  7. Return an action queue, delegation queue, waiting-for list, meeting-prep list, cross-channel closed-loop items, and items requiring the user's judgment.

Rules

  • Separate research strategy from administrative throughput.
  • Draft communications when asked; do not send or modify external systems without authorization.
  • Treat Teams replies, decisions, delegations, and acknowledgments as valid closure evidence for mail-derived follow-ups. Mark these as closed or answered via Teams with the chat/channel/source when available.
  • Keep Teams scanning read-only by default. Do not send Teams messages, create Planner tasks, mark items read, or modify chats/channels unless explicitly authorized.
  • Scope Teams reads tightly by the time horizon, named people, named workstreams, unread chats, recent threads, or mentions. Note coverage limits, especially that channel unread markers may not be exposed.
  • Keep financial currencies separate unless conversion is requested.
  • For receipt breakdowns, include dates when available.
  • Protect student, personnel, health, identity, and financial information.

Keep looking

Skills are one crate of 328,083. 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.