5 days ago I had zero Hermes experience. Today: → Built a skill that generates content in a specific brand voice → Connected it to Notion automatically → Set up cron jobs for daily delivery → Built an accountability bot that checks my progress 3x a day Not a demo. Running live. Still have things to fix. Morning cron failed. Voice needs tightening. But it ships. That's what matters. Thank you Johann, for the support @johann_sath

I built a tool that automates cold DMs Would love to hear your feedback

Get leads on auto-pilot with DMpro Automated Cold DMs at scale While keeping accounts safe

whattt!

Got your hands on Claude Fable 5? The first thing you should do is to upgrade your main projects with it, so it drastically impoves everything you've been working on. Run this Audit & Project Improvement Prompt on each repo that's important to you (simply copy-paste it): Repo Audit & Improvement Plan: Prompt made by Claude Fable 5 You are a world-class principal-level software engineer and technical auditor. Your job is to deeply analyze this repository, produce an honest audit, and deliver a prioritized, actionable improvement plan. Work in the four phases below, in order. Do not skip ahead. Ground every claim in actual files: cite file paths and line numbers. If you can't verify something, say so explicitly rather than guessing. Phase 1 / Discovery & Mapping (read before judging) Explore the repository systematically before forming any opinions: Map the directory structure and identify the project type, language(s), frameworks, and runtime targets. Identify entry points, core modules, and the main data/control flow through the system. Read the package manifest(s), lockfiles, build config, CI config, environment/config files, and any docs (README, CONTRIBUTING, ADRs). Determine what the project is for: its purpose, intended users, and apparent maturity (prototype, internal tool, production service, library). Note conventions already in use (naming, module boundaries, error handling patterns, test style) so recommendations fit the existing culture rather than fighting it. Output for this phase: a concise "Repo Map" purpose, stack, architecture sketch, key directories with one-line descriptions, and anything that surprised you. Phase 2 / Audit (evidence-based, severity-rated) Audit each dimension below. For every finding, record: (a) what you found, (b) where (file:line), (c) why it matters (concrete consequence, not vague principle), (d) severity: Critical / High / Medium / Low. • Architecture & design: module boundaries, coupling/cohesion, circular dependencies, leaky abstractions, god objects/files, layering violations, scalability bottlenecks. • Code quality: duplication, dead code, complexity hotspots (longest/most-branched functions), inconsistent patterns, error handling gaps (swallowed exceptions, missing edge cases), type safety holes. • Security: hardcoded secrets or credentials, injection risks, unsafe deserialization, missing input validation, auth/authz weaknesses, outdated dependencies with known CVEs, overly permissive configs. • Testing: coverage gaps (especially around core business logic), test quality (do tests assert behavior or just execution?), missing test types (unit/integration/e2e), flaky patterns, untestable code. • Performance: N 1 queries, unnecessary allocations or copies, blocking calls in async paths, missing caching/indexing, unbounded growth (memory, files, queues). • Dependencies: outdated, unmaintained, duplicated, or unnecessarily heavy packages; license risks; lockfile hygiene. • DevEx & operations: build/setup friction, CI/CD gaps, missing linting/formatting enforcement, logging/observability quality, error reporting, deployment story. • Documentation: README accuracy, onboarding path, undocumented critical behavior, stale docs that contradict code. Rules for this phase: Prefer 15 high-confidence findings over 50 speculative ones. Distinguish facts ("this function has no error handling: src/api/client.ts:142") from judgments ("this module's responsibilities feel unclear") and label which is which. Also list what the repo does well: strengths matter for deciding what to preserve. Output for this phase: an "Audit Report": findings grouped by dimension, sorted by severity, plus a Strengths section. Don't forget to mention all the ugly parts that need utmost priority. Phase 3 / Improvement Strategy Synthesize the audit into a strategy: Identify the 3–5 themes that explain most of the findings (e.g., "no enforced boundaries between layers," "error handling is ad hoc"). For each theme, propose a target state and the principle behind it. State explicit trade-offs: what you're recommending NOT to fix and why (effort vs. payoff, risk, project maturity). Define what "done" looks like — measurable signals (e.g., "CI fails on lint errors," "core module test coverage ≥ 80%," "zero Critical findings"). Phase 4 / Detailed Task Plan Convert the strategy into an execution plan: Break work into discrete tasks. Each task must include: Title and one-paragraph description Files/areas affected Acceptance criteria (how we verify it's done) Effort estimate (S = <2h, M = half-day, L = 1–2 days, XL = needs breakdown) Risk of the change itself (could it break things?) Dependencies on other tasks Order tasks into milestones: Milestone 0 Safety net: anything needed before refactoring safely (tests around critical paths, CI gates, backups). Milestone 1 Critical fixes: security and correctness issues. Milestone 2 High-leverage improvements: changes that make all future work easier. Milestone 3 Quality & polish: remaining medium/low items worth doing. Flag quick wins (high impact, S effort) separately so they can be done immediately. For the top 3 tasks, include a brief implementation sketch (approach, key steps, gotchas). Final Deliverable Format • Produce a single document with these sections: • Executive Summary (≤10 sentences: overall health grade A–F with justification, top 3 risks, top 3 opportunities) • Repo Map • Audit Report • Improvement Strategy • Task Plan (milestones task table quick wins) • Open Questions: anything you need from a human to decide (product intent, deprecation candidates, performance targets) Constraints Do NOT modify any code during this audit. Analysis only. Do not pad the report. If a dimension is healthy, say so in one sentence and move on. Calibrate to the project's maturity. Don't recommend enterprise-grade infrastructure for a weekend prototype unless the owner's goals demand it. Analyze the project's needs and provide recommendations in the most effective ways. If the repo is large, prioritize depth in the core 20% of code that does 80% of the work, and note which areas received lighter review.

introducing cursor profiles! go claim your handle at cursor.com/profile

Get your ai employee now

we shipped the cyndra platform first thing we did? opened a bug bounty let the community test it, break it & help us make it better that's how you build in public link below

winners fail more than losers ever will so keep building, failing & learning

JUST IN 🔥 Hermes just added an optional OpenHands skill this changes quite a bit how agents work You can now route a coding task from Hermes into a headless OpenHands run, pick the model/provider yourself, and keep the workflow as a reusable skill instead of manually remembering all the CLI weirdness this basically means you can now have Hermes send a coding task to OpenHands, choose which AI model runs it, and save the setup as a skill so you do not have to remember all the command line details remember to do hermes update in your CLI to get this

This is my daily routine before sleeping.

Hermes Agent is the most powerful AI tool right now The issue is, almost nobody knows how to use it properly In this video I show you 6 use cases for Hermes I promise will completely change how you work:

i use claude ~12 hours a day and never hit the limit. here's how:

I need to change my for you posts let's talk about ai agents and models better

MASSIVE Hermes Agent update this week. 7 new features you need to be taking advantage of immediately: 1. Improved memory/session search. Hermes now automatically logs every session from every day into memory. Meaning you can ask "what did we work on on April 15th?" 2. Background tasks: use /background at anytime to give a task to Hermes that it will complete in the background. Meaning you can give a bunch of background tasks and still have it perform a main task simultaneously. Perfect for multitasking. 3. xAI oath: login with your existing Grok account and use that as your orchestrator. No need to pay extra for other AI accounts. Awesome of xAI to allow this. 4. X posting and fetching. If you use your Grok oauth, you can now use Hermes to search, find, and create posts. Really nice X integration for your agent 5. Codex CLI. Your agent can now natively use Codex CLI. Meaning you can give your agent a coding task and it will spin up Codex CLI by itself to vibe code for you. Very powerful 6. Native AI videos. Hermes agent can now use a number of tools to generate its own AI videos. This includes the Grok oauth from earlier. So if you plug that in you can now use Grok Imagine to build videos in seconds. 7. Auto Kanban tasks. If you open up your Hermes kanban board ('hermes dashboard' in your terminal) you can drop goals into the triage category and Hermes will automatically break it down into tasks and assign to subagents. Really powerful way to get big tasks done quickly Highly recommend taking advantage of all of these immediately if you want to stay on the cutting edge

Yesterday, collaboration Grok with Hermes. Today, Telegram made it so that the bots can communicate with each other. Tomorrow, nobody knows.

that's literally insane Let's building cool stuff 🔥

What's the better free model for hermes planing?

Is anyone still learning from YouTube or videos, or are you okay with AI?