AI Agent Skills

GitHub PR lifecycle: branch, commit, open, CI, merge.

Run 150+ AI applications in the cloud via the inference.sh platform. Triggers on "generate image with FLUX", "create video", "use Veo/Seedance", "run inference.sh", "infsh CLI", "single key for image+video+LLM". One API key covers image generation (FLUX, Reve, Seedream, Grok, Gemini), video (Veo, Wan, Seedance, OmniHuman, HunyuanVideo), LLMs (Claude, Gemini, Kimi, GLM-4), search (Tavily, Exa), 3D (Rodin), social (Twitter/X), and audio (TTS, voice cloning).

llama.cpp local GGUF inference + HF Hub model discovery.

Plan mode: write markdown plan to .hermes/plans/, no exec.

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.

Use when you have a spec or requirements for a multi-step task, before touching code

Delegate coding to OpenAI Codex CLI (features, PRs).

Infographics: 21 layouts x 21 styles (信息图, 可视化).

Generate project ideas via creative constraints.

Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.

Build monitoring bots that poll APIs and send notifications on state changes (new listings, price alerts, status updates)

Decomposition playbook + specialist-roster conventions + anti-temptation rules for an orchestrator profile routing work through Kanban. The "don't do the work yourself" rule and the basic lifecycle are auto-injected into every kanban worker's system prompt; this skill is the deeper playbook when you're specifically playing the orchestrator role.

Inspect codebases w/ pygount: LOC, languages, ratios.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

Throwaway experiments to validate an idea before build.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Integrate TinyFish web toolkit (search, fetch, browser automation) into Hermes Agent

Create production-ready public GitHub repositories with comprehensive documentation, automated setup, and quality assurance

OBLITERATUS: abliterate LLM refusals (diff-in-means).

Use when you have a written implementation plan to execute in a separate session with review checkpoints

54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.

Webhook subscriptions: event-driven agent runs.

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

Delegate coding to OpenCode CLI (features, PR review).

Dark-themed SVG architecture/cloud/infra diagrams as HTML.

Clone/create/fork repos; manage remotes, releases.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

SAM: zero-shot image segmentation via points, boxes, masks.

Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

TRL: SFT, DPO, PPO, GRPO, reward modeling for LLM RLHF.

Extract text from PDFs/scans (pymupdf, marker-pdf).

Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.

Use cloud browser services (Browserbase) for Cloudflare bypass, JavaScript rendering, and stealth scraping when local tools fail

Host modded Minecraft servers (CurseForge, Modrinth).

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Delegate coding to Claude Code CLI (features, PRs).

Iterative Python via live Jupyter kernel (hamelnb).

Create professional visual assets for GitHub repositories — architecture diagrams, social cards, and README banners.

Build a throwaway prototype to flush out a design before committing to it. Routes between two branches — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route. Use when the user wants to prototype, sanity-check a data model or state machine, mock up a UI, explore design options, or says "prototype this", "let me play with it", "try a few designs".

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

Setup Obsidian mobile sync via GitHub (free) or Obsidian Sync (paid). Includes GitHub CLI automation, MGit/Working Copy setup, and Mnemosyne integration patterns.

REST/GraphQL API testing with automated validation — test endpoints, validate responses, check status codes, and ensure API contracts

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

Configure, extend, or contribute to Hermes Agent.

Songwriting craft and Suno AI music prompts.

Generate visual assets (ASCII art, diagrams, banners) for repos and documentation

Evaluate and maximize GitHub repo quality from 7/10 to 10/10 perfect

Discover and analyze trending GitHub repositories from TrendShift and other sources — evaluate usefulness, extract learnings, and identify valuable skills/tools

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

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.