teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
using-proton-pass-cli
Interact with Proton Pass via the `pass-cli` command-line tool. Use this skill when the user wants to manage passwords, vaults, items, SSH keys, secret injection, or any credential management through the Proton Pass CLI. Triggers on mentions of pass-cli, proton pass, secret references, pass:// URIs, vault management, or SSH agent integration with Proton Pass.
godmode
Jailbreak LLMs: Parseltongue, GODMODE, ULTRAPLINIAN.
arxiv
Search arXiv papers by keyword, author, category, or ID.
domain-intel
Passive domain reconnaissance using Python stdlib. Subdomain discovery, SSL certificate inspection, WHOIS lookups, DNS records, domain availability checks, and bulk multi-domain analysis. No API keys required.
duckduckgo-search
Free web search via DuckDuckGo — text, news, images, videos. No API key needed. Use the Python DDGS library or CLI to search, then web_extract for full content.
experiment-log-interview
Conducts a structured Socratic interview to produce or update a single experiment log entry — the durable record of what was run, what it showed, and what it means. Use this skill whenever the user wants to log an experiment, write up results, record a backtest, capture a finding, pre-register a run, document a study, or update an existing entry with new results or a revised interpretation. Trigger on phrases like "log this experiment," "write up the results of...", "I ran X, help me document it," "pre-register this," "update the entry for...", or when the user shares results and asks for help interpreting and recording them. The skill enforces the four-way separation between what happened, what it means, what it implies, and what comes next; challenges the user's interpretations with evidence requests and alternative explanations; and writes incrementally to keep context clean and the entry always grounded.
experiment-log-structure
Use when an agent needs to produce, update, validate, or normalize a standardized experiment-log entry without running an interview. Defines the canonical structure, pre-registration rules, evidence/interpretation split, calibration tags, and append-only revision model for durable experiment records.
llm-wiki
Karpathy's LLM Wiki: build/query interlinked markdown KB.
ml-paper-writing
Write publication-ready ML/AI papers for NeurIPS, ICML, ICLR, ACL, AAAI, COLM. Use when drafting papers from research repos, structuring arguments, verifying citations, or preparing camera-ready submissions. Includes LaTeX templates, reviewer guidelines, and citation verification workflows.
polymarket
Query Polymarket: markets, prices, orderbooks, history.
research-paper-writing
Write ML papers for NeurIPS/ICML/ICLR: design→submit.
research-proposal-interview
Conducts a structured Socratic interview to produce a comprehensive markdown research proposal that handles cascading uncertainty (fixed end-question, branching experiments). Use this skill whenever the user wants to write a research proposal, research plan, study design, experiment plan, thesis proposal, RFC, or "spec out" a research direction — even if they don't explicitly say "interview me." Trigger when the user says things like "help me plan this research", "I want to design experiments for X", "draft a proposal for...", "think through a research direction", or shares a half-formed research idea and asks for help structuring it. The skill interviews the user, challenges their priors with evidence requests and falsifiers, optionally uses sub-agents to explore prior art, and builds the proposal markdown incrementally so context stays clean and the document is always grounded.
research-proposal-structure
Use when an agent needs to produce, update, validate, or normalize a standardized research proposal artifact without running an interview. Defines the canonical structure, confidence-tag semantics, decision logic, and completion checks for proposal.md-style research plans.
openhue
Control Philips Hue lights, scenes, rooms via OpenHue CLI.
xurl
X/Twitter via xurl CLI: post, search, DM, media, v2 API.
yuanbao
Yuanbao (元宝) groups: @mention users, query info/members.
simplify-code
Parallel 3-agent cleanup of recent code changes.
hermes-agent-skill-authoring
Author in-repo SKILL.md: frontmatter, validator, structure, and writing-quality principles.
hermes-tui-development
Inspect and extend Hermes Agent TUI capabilities, launch flags, hotkeys, composer input, and terminal behavior.
package-skill
Package a Claude Code skill directory into a distributable .skill file. Use when the user wants to export, package, bundle, zip, or distribute a skill. Triggers on mentions of .skill files, packaging skills, exporting skills, or sharing skills.
subagent-driven-development
Execute plans via delegate_task subagents (2-stage review).
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
debugging-hermes-tui-commands
Debug Hermes TUI slash commands: Python, gateway, Ink UI.
linux-system-debugging
Class-level Linux debugging workflow for authentication/PAM lockouts, desktop hardware/device stacks, and RAM/swap/CPU/process resource pressure.
node-inspect-debugger
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
hermes-s6-container-supervision
Modify, debug, or extend the s6-overlay supervision tree inside the Hermes Agent Docker image — adding new services, debugging profile gateways, understanding the Architecture B main-program pattern.
brainstorm
>-
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.
feature-brainstorm
Multi-phase brainstorming for complex feature implementations using parallel sub-tasks. Use when the user asks to brainstorm, design, or plan a complex feature, wants to explore implementation approaches, or needs architectural analysis before coding. Triggers on phrases like "brainstorm feature", "design implementation", "explore approaches", "plan architecture", or "how should we implement".
plan
Plan mode: write an actionable markdown plan to .hermes/plans/, no execution. Bite-sized tasks, exact paths, complete code.
spike
Throwaway experiments to validate an idea before build.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
code-review
Guidelines for performing thorough code reviews with security and quality focus
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
nix-flake-dotfiles-maintenance
Use when modifying a multi-host Nix flake or dotfiles repo, especially host-specific inputs, overlays, lockfile scope, and evaluation checks.
terminal-multiplexer-workflows
Use when answering, configuring, or troubleshooting terminal multiplexer workflows such as Zellij/tmux pane, tab, floating pane, grouping, keybinding, and CLI-action behavior.
conventional-commits
Commit changes in a git workspace using the Conventional Commits specification. Use when the user asks to commit, stage, or save changes to git, or mentions "conventional commits". Analyzes staged/unstaged changes, groups related modifications, generates properly formatted commit messages, and commits files separately or together as appropriate. Confirms with user when commit ordering is ambiguous.
safe-git-rebase-with-guards
Perform a git rebase safely when the branch may have uncommitted WIP, poisoned rerere cache, or a concurrent actor. Use for any non-trivial rebase/linearization in a shared repo or git worktree where conflict markers, WIP loss, or baked-in corruption are risks.
stacked-issues
Implement multiple GitHub issues sequentially as stacked branches in separate worktrees, with an implementer sub-agent and an independent reviewer sub-agent per issue. Use when the user gives you two or more dependent issues and asks for them to be implemented in order, or says "stacked branches", "sequential issues", "issue chain", "do these in worktrees", or describes a parent epic with child issues that build on each other. Also reach for this whenever the user wants implementation and verification done by separate agents.
stacked-prs
Push local branches and create stacked PRs. Analyzes branch topology, pushes, creates PRs with correct base branches, and resolves merge conflicts. Use when you have a chain of local branches to turn into stacked PRs.
Page 4 of 4 · 194 results