My main focus

• Current research work (hopefully PhD): Muti-agent Simulation, MedVoice.
• Open source contributor: OpenBMB/ChatDev 2.0, HKUDS/RAG-Anything.

🤖 Hermes Skills

Auto-synced daily from my-hermes-skills · docs

Systematic Review (Covidence)

• covidence-full-text-retrieval — Autonomously retrieve full-text PDFs for references in the full-text review stage of a Covidence systematic review, in the user's Chrome session via CDP. Looks up open-access copies via Unpaywall, Semantic Scholar, and arXiv, with an optional NotebookLM-assisted last-resort web search, then uploads any PDF it finds through Covidence's "Upload full text" action. References with no locatable full text get a note logged for manual follow-up. Never casts an Include/Exclude decision -- that stays manual. (v1.2.0)
• covidence-full-text-review — Review full-text papers in a Covidence systematic review. Mode 1 (websearch_queue): walks the Covidence queue, web-searches each title, opens the first result in the papers-access browser profile, reads the full text, and reports verdicts in chat (no Covidence writes). Mode 2 (secondary_reviewer): receives a URL from the user, reads the paper, returns a structured Include/Exclude verdict with rationale, and optionally casts the vote in Covidence when a ref_id is supplied. (v2.0.0)
• covidence-screening — Autonomously screen references at the title & abstract stage of a Covidence systematic review in the user's Chrome session via CDP. Votes Yes/Maybe/No per the user's PICO criteria, writes a one-line rationale for Maybe votes, and runs unattended after an approve-first-N onboarding phase. (v1.0.0)

Productivity

• i-have-adhd — Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
• memory-ui — Launch the Mnemosyne browser UI to inspect stored memory.
• pbcopy-word-delivery — Deliver structured text content (verdicts, reports, summaries) directly to the macOS clipboard via pbcopy so the user can Cmd+V into Word without Warp terminal soft-wrap artifacts. (v1.0.0)
• session-handoff — Use when ending or pausing a session, switching between sessions, or asked to save/compress session state with TODOs - compresses the current session into a handoff file, updates a task index, and creates Apple Reminders for follow-up. Also used by the daily reminder cron in review mode to pick up leftover tasks. (v1.2.0)
• tldr — Use when the user asks for a TL;DR or before/after summary. (v1.0.0)

Slack

• slack-scan — Summarize today's Slack activity on demand -- one channel or every channel/DM the bot is in. (v1.0.0)

ilearning-autoadvance

• ilearning-autoadvance — Autonomously advance HCL iLearning / SAP SuccessFactors compliance courses (Articulate Storyline SCORM, Ethena GoEthena, or direct-HTML SVG players) via raw CDP on port 9222. Resumes paused audio, clicks interactive slide topics/cards, answers quizzes, navigates to the next slide. (v5.0.0)

superpowers

• superpowers-brainstorming — You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. (v1.0.0)
• superpowers-dispatching-parallel-agents — Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies (v1.0.0)
• superpowers-executing-plans — Use when you have a written implementation plan to execute in a separate session with review checkpoints (v1.0.0)
• superpowers-finishing-a-development-branch — Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup (v1.0.0)
• superpowers-receiving-code-review — Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation (v1.0.0)
• superpowers-requesting-code-review — Use when completing tasks, implementing major features, or before merging to verify work meets requirements (v1.0.0)
• superpowers-slash-commands — Index and invocation guide for the Superpowers skills. Use when the user asks for a Superpowers skill by name or wants to know which skills exist. (v1.0.0)
• superpowers-subagent-driven-development — Use when executing implementation plans with independent tasks in the current session (v1.0.0)
• superpowers-systematic-debugging — Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes (v1.0.0)
• superpowers-test-driven-development — Use when implementing any feature or bugfix, before writing implementation code (v1.0.0)
• superpowers-using-git-worktrees — Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification (v1.0.0)
• superpowers-using-superpowers — Use when starting any conversation - establishes how to find and use skills, requiring skill loading (skill_view) before ANY response including clarifying questions (v1.0.0)
• superpowers-verification-before-completion — Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always (v1.0.0)
• superpowers-writing-plans — Use when you have a spec or requirements for a multi-step task, before touching code (v1.0.0)
• superpowers-writing-skills — Use when creating new skills, editing existing skills, or verifying skills work before deployment (v1.0.0)

🤖 Daily Byte of Humor

What did the cell say when his sister cell stepped on his foot?

Mitosis.