hermes-tenant-providers
NaoUse when adding Hermes providers, keys, or aliases.
The Gab44 agent library
Every skill installed in Hermes, Nao's autonomous agent — what each one does, whether it works on this machine, and a direct line to ask about any of them.
An agent skill is a written procedure. Not code that runs by itself — a recipe the AI loads when a task matches it: exact commands, decision rules, pitfalls already learned the hard way. When Nao asks Hermes to do something, Hermes scans this library, loads the matching skills, and works from them.
This page is the whole library, in the open. Each card is one skill: the name, what it's for, whether its requirements check out on the real machine, and how many times it has actually been loaded. Nothing curated for show — it is generated straight from the live inventory.
And below, you can ask. One question box, no login. It lands in Nao's inbox and gets a real answer.
Skills are how an agent stays consistent: same research method, same deploy pipeline, same quality bar, every time.
A green dot means the skill's required tools and keys were verified on the server today. No dot, no claim.
Skills get added, merged, and retired through audits. This page reflects the library as it stands now.
Your question
Curious how one of these works, want one for your own project, or just want to test the agent? One box, straight to Nao.
“The world is perfect. Health is a result. Love is the cause.”
The library serves one brand, Gab44 — astrology, energy, and the engineering underneath it. Skills about charts sit next to skills about Cloudflare. That is the point.
Use when adding Hermes providers, keys, or aliases.
Route a grok.com / SuperGrok subscription into Hermes using the Grok CLI's OAuth token and a local OpenAI-compatible bridge — for when the xai-oauth device flow stalls or api.x.ai rejects CLI tokens. Covers proxy endpoint + handshake headers, Hermes custom-provider wiring, quota/vision limits, restart procedure, and no-vision-model image fallbacks (rootless tesseract OCR + PIL triage).
Use, configure, theme, extend, and orchestrate Hermes Agent.
Use when driving OpenHands CLI headless or as a chat relay.
Delegate coding to OpenCode CLI (features, PR review).
Delegate coding to OpenAI Codex CLI (features, PRs).
Agent Canvas (perso.gab44.com): stack layout, subscription auth model, profiles API, e2e test recipe.
Delegate coding to Claude Code CLI (features, PRs).
Use when tuning Hermes context compression and handoffs.
Drive the desktop in the background without stealing focus.
Use when researching the live internet across X, Reddit, YouTube, GitHub, RSS, or any URL. Agent Reach v1.5.0 is the installer/doctor/router; call upstream tools directly.
Neutral third-party resolution of agent merge conflicts.
Use for nao.gab44.com dashboard changes and debugging.
Use when resuming an interrupted thread or lost message.
Write desktop app plugins that add UI panes and commands.
Author a Hermes color theme that skins every surface.
Build and operate a personal brand across content platforms — strategy, voice, deliverables, and safe framing for health/wellness/spirituality knowledge.
54 real design systems (Stripe, Linear, Vercel) as HTML/CSS.
Design one-off HTML artifacts (landing, deck, prototype).
Humanize text: strip AI-isms and add real voice.
Generate images, video, and audio via diffusion workflows.
Author/validate/export Google's DESIGN.md token spec files.
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
ASCII art: pyfiglet, cowsay, boxes, image-to-ascii.
ASCII video: convert video/audio to colored ASCII MP4/GIF.
Infographics: 21 layouts x 21 styles (信息图, 可视化).
Hermes workflow skill.
Hand-drawn Excalidraw JSON diagrams (arch, flow, seq).
Manim CE animations: 3Blue1Brown math/algo videos.
p5.js sketches: gen art, shaders, interactive, 3D.
Build creative browser demos with DOM-free text layout.
Throwaway HTML mockups: 2-3 design variants to compare.
Songwriting craft and Suno AI music prompts.
Iterative Python via live Jupyter kernel (hamelnb).
Self-host persistent services (AI agent platforms, web apps, APIs) on the headless Hermes server without root — userland binary installs from .deb packages, pinned secrets that survive restarts, password-auth gateways in front of token-auth backends, docker-subnet service discovery, and Cloudflare tunnel/domain exposure. Use whenever Nao wants something "hosted on the server" with a real login ins
Complete OAuth/browser-approval flows for chat-only users on headless servers — device-code flows (send link instantly, ~15min expiry), localhost-callback flows (user pastes the dead redirect URL, agent curls the listener), rclone loopback-proxy flows (Google Drive etc.), stale-credential triage, and the accountability nag-cron. Use whenever a login/authorization needs the user's browser but the u
Use when changing Relay. Decision model, not more CMS.
Use for cPanel hosting, DNS, DB, email tasks.
Build, run, and E2E-test Telegram bots on host Anouf.
Use when linking Termius or phone SSH to Anouf CLIs.
Use for Firebase Hosting deploys and Auth/Storage wiring.
Verify card/bank charges against real cloud usage (GCP).
Review Kanban handoffs and route verified outcomes.
Use when auditing Claude skills and commands for quality. Supports Quick Scan (changed skills only) and Full Stocktake modes with sequential subagent batch evaluation.
Run a six-phase verification of a Claude Code session's work — build, type check, lint, tests with coverage, security grep, and diff review — then produce a PASS/FAIL verification report. Use when verifying work after completing a feature or refactor, before creating a PR, or when quality gates must pass.
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.
Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.
Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before s
Trace every user-facing button/touchpoint through its full state change sequence to find bugs where functions individually work but cancel each other out, produce wrong final state, or leave the UI in an inconsistent state. Use when: systematic debugging found no bugs but users report broken buttons, or after any major refactor touching shared state stores.
Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.
Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring, checking if AI changes degraded a file, or before commit/PR.
Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination. Use when capturing lessons from a session, managing instincts, or promoting them into skills, commands, or agents.
Convene a four-voice council for ambiguous decisions, tradeoffs, and go/no-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
Answer questions about ECC by reading the live repo surface — agents, skills, commands, hooks, rules, install profiles, and docs — instead of memory. Use when the user asks what ECC includes, how to install or reset it, which skill or command fits a task, or how project onboarding works.
Patterns for robust error handling across TypeScript, Python, and Go. Covers typed errors, error boundaries, retries, circuit breakers, and user-facing error messages. Use when designing error types, retries, circuit breakers, or user-facing failure messages in TypeScript, Python, or Go.
Eval-driven development (EDD) framework for AI coding sessions — define capability and regression evals before coding, grade with code-based, model-based, rule, or human graders, and track pass@k and pass^k reliability. Use when defining pass/fail criteria for agent tasks, measuring agent reliability, building regression suites for prompt or agent changes, or benchmarking across model versions.
Git workflow patterns including branching strategies, commit conventions, keeping history clean and readable, tidying local commits before merging, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes. Use when choosing a branching strategy, writing commit conventions, cleaning up history before a pull request, deciding merge versus rebase, or r
Write growth log entries that extract reusable patterns from completed work — root cause, transferable rule, and a recognizable signal — instead of diary-style event narration, with a 4-8 sentence template and merge-duplicates discipline. Use when capturing what was learned after a complex task, debugging session, failure, or rollback, when reviewing progress over a period, or when a delivery gate
Create and configure hookify rules — markdown files with YAML frontmatter that match bash, file, prompt, or stop events by regex or conditions and show warn/block messages to the agent. Use when creating a hookify rule, writing hook rule syntax, configuring hookify, or adding pattern guardrails such as blocking dangerous commands, .env edits, or debug code.
Prevent AI style drift on legacy projects by scanning the codebase for implicit conventions, resolving conflicts with the operator one at a time, and writing an enforceable .ai-style-rules.md (Golden Files, naming rules, DONTs) plus an optional CLAUDE.md hook. Use when onboarding an AI agent onto a hand-written legacy codebase or extracting a project's unwritten coding rules.
Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straight
Pattern for progressively refining context retrieval to solve the subagent context problem. Use when a subagent lacks the context it needs and retrieval must be refined across passes.
Keep a long-lived project's documentation from rotting by assigning existing project docs clear constitution, map, status, and history roles, then wiring the active agent harness to those canonical sources. Use in the maintain phase when docs drift from code, agents lose context between sessions, or intentional removals keep being recreated. Prefer adopting the repository's current docs structure
Design a goal-oriented agent loop or review one for failure modes: spinning, Goodhart-gaming the verifier, or running a wrong answer to completion. Covers machine-decidable goals, loop types, plan/build/judge skeletons, and runaway prevention; mechanism wiring lives in autonomous-loops. Use when designing, writing, or checking an agent loop. 中文触发:写 loop、设计 loop、做一个 loop、检查 loop 对不对、loop 体检、loop 会不
Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.
Write-time code quality enforcement using Plankton — auto-formatting, linting, and Claude-powered fixes on every file edit via hooks. Use when setting up write-time formatting, linting, or auto-fix hooks on file edits.
Validate the why before building through four product diagnostics — a YC-style product diagnostic that produces PRODUCT-BRIEF.md with a go/no-go recommendation, a founder review scoring product-market-fit signals, a user journey audit measuring time-to-value, and ICE feature prioritization. Use when pressure-testing product direction, choosing between features, sanity-checking a launch, or convert
Local-evidence production readiness audit for shipped apps, pre-launch reviews, post-merge checks, and "what breaks in prod?" questions without sending repo data to an external audit service. Use when auditing production readiness before launch, after a merge, or when asked what breaks in prod.
Scan skills to extract cross-cutting principles and distill them into rules — append, revise, or create new rule files. Use when the same principle keeps recurring across skills and belongs in a rule file instead.
Multi-agent adversarial verification: two independent reviewers with the same rubric must both pass before output ships, with a fix-and-re-review convergence loop and human escalation cap. Use when gating publishing, production deploys, compliance or brand-sensitive content, or hallucination-prone claims before they ship.
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines. Use when checking whether agents actually follow the skills, rules, and definitions they were given, rather than assuming they do.
Search existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow.
Test-driven development workflow: write a failing test first, watch it fail, implement the smallest change to green, then refactor with 80%+ coverage across unit, integration, and E2E tests. Use when writing a new feature, fixing a bug, refactoring, or when told to write failing tests first.
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
Himalaya CLI: IMAP/SMTP email from terminal.
Triage an inbox: prioritize threads, draft replies safely.
Clone/create/fork repos; manage remotes, releases.
GitHub auth setup: HTTPS tokens, SSH keys, gh CLI login.
Inspect codebases w/ pygount: LOC, languages, ratios.
GitHub PR lifecycle: branch, commit, open, CI, merge.
Review PRs: diffs, inline comments via gh or REST.
Carry a GitHub issue to a verified PR with honest CI state.
Nao's personalized health & supplement framework — strict evaluation criteria for bioavailability, purity, excipients. Integrates Gary Brecka protocols with holistic dental health. Use when recommending supplements, evaluating products, or discussing Nao's biological optimization.
Critical evaluation and personalization of health/wellness protocols — cross-references modern biohacking (Brecka, etc.) against 4,000+ year medical traditions (TCM, Ayurveda, Greco-Arabic) with mandatory sex differentiation. Use when analyzing ANY health claim, supplement, or protocol for truth and precision. Challenge claims; don't just accept them.
Use when products interpret symptoms or body meaning safely.
YouTube transcripts to summaries, threads, blogs.
Use when generating images for Nao. Proven host recipes.
Use for rendering hours-long healing frequency audio.
Search/download GIFs from Tenor via curl + jq.
HeartMuLa: Suno-like song generation from lyrics + tags.
Audio spectrograms/features (mel, chroma, MFCC) via CLI.
llama.cpp local GGUF inference + HF Hub model discovery.
Use for local text/image generation on Anouf (CPU-only).
AudioCraft: MusicGen text-to-music, AudioGen text-to-sound.
HuggingFace hf CLI: search/download/upload models, datasets.
SAM: zero-shot image segmentation via points, boxes, masks.
Read, search, create, and edit notes in the Obsidian vault.
Use when Nao's Drive/Sheets go through Composio.
Turn a markdown report into a styled A4 PDF and deliver it (with source) via Telegram. Use whenever producing long-form study reports for Nao (his standard: 30+ page deep dives). Companion to deep-research-process (methodology) — this skill is the document-production mechanics.
Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.
Use when drafting or revising client service proposals.
Use for recurring data-driven marketing report decks.
Extract text from PDFs/scans (pymupdf, marker-pdf).
Nao's development and workflow protocols — AI-centric 'God Mode' development, external team handoff documentation, automated financial strategies. Use when working on Gab44/NatalTruth projects, crypto bots, or coordinating with external teams.
Create, read, merge, fill, and secure PDF files.
Create, read, edit Excel .xlsx workbooks and CSVs.
Cross-verify health/spirituality/development claims by querying multiple LLMs (Manus, Grok, Kimi, Gemini) as independent second opinions. Use when Nao asks for 'second opinion' or wants to send files to another LLM for unbiased analysis.
Sell services with warmth, truth, and clear boundaries.
Create, read, edit .pptx decks with python-pptx.
Use when restyling a multi-page journal PDF font/size.
Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.
Edit text in existing PDFs via natural-language prompts.
Organize sessions by prompt: find, rename, archive, prune.
Weekly reset: commitments, stalled work, next-week plan.
Airtable REST API via curl. Records CRUD, filters, upserts.
Box manages cloud files, sharing, search, and metadata.
Extract cited obligations, deadlines, tasks from documents.
Create, read, edit, template, and review Word .docx files.
Notion API + ntn CLI: pages, databases, markdown, Workers.
Install and select animated petdex mascots for Hermes.
Watch product, flight, or listing prices; alert on target.
Author live widget apps for the Hermes TUI dock.
Locate and download free full texts of books (esp. out-of-print / underground / esoteric titles) via the Internet Archive JSON APIs, verify completeness, and extract structured quotes. Use whenever a research task needs the actual primary text of a book, not secondary summaries.
Ground answers and documents in cited, verifiable sources.
Use the Manus autonomous agent API for deep research, second-opinion queries, and retrieval of Nao's personalized knowledge from Manus's environment. Use whenever Nao says 'ask Manus', 'get it from Manus', or when a deep research task would benefit from Manus's autonomous agent capabilities.
Use when weather may disrupt homes, deliveries, or routes.
Recover blocked/paywalled/WAF'd pages via fallbacks.
Search arXiv papers by keyword, author, category, or ID.
Monitor blogs and RSS/Atom feeds via blogwatcher-cli tool.
Watch named companies for material news; cited digests.
Karpathy's LLM Wiki: build/query interlinked markdown KB.
Query Polymarket: markets, prices, orderbooks, history.
Control Philips Hue lights, scenes, rooms via OpenHue CLI.
Marky social-media dispatcher API (mymarky.ai): create/schedule/publish posts across connected platforms (Facebook, Instagram, LinkedIn, TikTok, ...), list businesses and integrations, fetch post stats. Use for any multi-platform social publishing/scheduling task for Nao's brands.
Run an autonomous multi-platform brand content engine: cron-driven post generation, X direct posting, Marky API dispatch to LinkedIn/Instagram/Facebook/TikTok, engagement loops, and cheap-model pinning. Use when Nao (or any brand) wants 'publish as you wish, bring visitors' — live ugly but live.
X/Twitter via xurl CLI: raw post search, posting, DM, media.
Standards for any website/web project built for Nao — love-based design, mandatory light theme, mission-aligned content pillars, live preview deployment pattern, verification loop.
Scaffold a content website and put it LIVE publicly in minutes — zero-dependency vanilla-JS SPA + JSON CMS + node static server + cloudflared tunnel. Use whenever Nao (or anyone) wants to 'see it live', build a knowledge/content site, or iterate on a web project with instant public URLs.
Publish sites, apps, and APIs to Cloudflare Workers from a headless server — token minting from a token-manager key, wrangler assets+worker+KV config, Expo/React static export deploys, secrets handling, and the deploy pipeline that keeps API endpoints and custom routing alive next to static assets. Use whenever deploying to Cloudflare Workers/Pages, minting scoped CF API tokens, or wiring a Worker
Use for every coding task. Three rules only.
Use for ANY web task for Nao — routes to the right skill.
Extract complete business catalogs — services, products, prices, hours, policies, branding, payment config — from hosted SaaS platforms (Acuity/Squarespace Scheduling, Shopify storefronts) as public JSON, and pipe them into a site rebuild with zero hand-transcription.
Use for any build task. Orchestrate, never code directly.
Use before any web build. Enforced UI/UX design rules.
Use for Astro client sites. Enforced research before code.
Use when building or changing any Nao web app (NatalTruth, Gab44, AdamCareer, personal). Default architecture: POLYTHEISM — one family, separate gods. Shared standards, never shared monoliths.
Exploratory QA of web apps: find bugs, evidence, reports.
Use when hosting or publishing a Nao live site.
Deep audit of an external repo against its live production: read every file, verify API claims against the real backend, score KPIs, flag dishonest/fake/dead pages.
TDD: enforce RED-GREEN-REFACTOR, tests before code.
4-phase root cause debugging: understand bugs before fixing.
Nao's expected deep research methodology — the Hawkins deep dive quality bar. Use for ANY research, analysis, or study task Nao assigns. This is the standard.
Complete OAuth authorization (device-code and PKCE authorize flows) from a headless server with the user approving on their phone. Covers link-handoff timing, the dead-localhost-URL copy trick, dashboard misconfig diagnosis, confidential-client exchange failures, and token storage/rotation. Use for X, Grok/xAI, or any OAuth provider when the agent runs on a server with no browser.
Use when Nao wants COD ecom. Astro markdown shop.
Use when building a luxury client marketing site for Nao.
Write a markdown plan to .hermes/plans/; no execution.
Author in-repo SKILL.md files: frontmatter and structure.
Operational playbook for executing deep research: delegating long documents safely, driving the Manus API, verifying subagent output before delivery. Pairs with deep-research-process (methodology) — this skill is the execution layer.
Pre-commit review: security scan, quality gates, auto-fix.
Read the live Hermes desktop DOM/CSS over CDP.
Debug Node.js via --inspect + Chrome DevTools Protocol CLI.
Debug Python: pdb REPL + debugpy remote (DAP).
Parallel 4-agent cleanup of recent code changes.
Throwaway experiments to validate an idea before build.
Official NatalTruth premium report: Bright Signal, 18 chapters, one named chart. Use this, not the retired v3-v6 templates, whenever generating or debugging a paid individual reading.
Compute and deliver astrological readings for Nao — synastry/compatibility between two charts (the 'soulmate or twin flame' request class) and the daily 'energy + leçon du jour' morning reading. Includes ready-to-run Swiss Ephemeris scripts, the DD/MM date pitfall, noon-chart Moon brackets, interpretation criteria bank, and Nao's delivery format rules.
Nao's astrological methodology — multi-layered interpretation integrating elemental analysis, parental dynamics, gematria, and practical timing. Use for chart interpretation, name analysis, or astrological guidance for Nao or others.
Decode number sequences ('angel numbers' like 13 13 33), life paths, and name numbers — layered arithmetic + tarot mapping + the moment-as-content frame. Use when the user reports seeing repeated numbers or asks for numerology calculations.
Nao's personalized framework for self-sovereignty — integrates Hawkins Map of Consciousness, the Physics of Being (subtle bodies), Bourbeau soul wounds, and astrocartography. Use when discussing Nao's spiritual development, consciousness levels, energetic alignment, or relocation guidance.
pyswisseph workflows beyond the single natal chart: noon charts without birth time, synastry cross-aspects, live transit reports mapped to natal houses, and personal-year numerology — the full script patterns for recurring astrology requests.
Numerology, gematria, and angel-number alignment coaching.
Lise Bourbeau's 5 soul wounds framework — rejection, abandonment, humiliation, betrayal, injustice — and their personality masks, behaviors, and health correlations. Use when analyzing personality through the Bourbeau lens or when someone references 'les blessures de l'âme'.
Decode body symptoms (pain zones, side-of-body, sleep patterns) into energetic/Bourbeau/Sarno meaning for Nao, with the validated reframe and practice protocols — anger extraction, warm-wall boundaries, energy-vampire contradiction check, 3am protocol, receiving-edge work.
Decode synchronicities (animals, omens, numbers) as mail.
Nothing matches that search.