Agent skill

Omh Files

[omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search…

MITAuto-check passed

Install Omh Files

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-files -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-files --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-files .claude/skills/omh-files && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "omh-files" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-files into .claude/skills/omh-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-files", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-files

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-files -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-files --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omh-files .agents/skills/omh-files && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "omh-files" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-files into .agents/skills/omh-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-files", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-files -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-files --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omh-files .cursor/skills/omh-files && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "omh-files" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-files into .cursor/skills/omh-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-files", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/rlaope/oh-my-hermes.git --path skills/omh-files

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-files -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-files --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omh-files .gemini/skills/omh-files && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "omh-files" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-files into .gemini/skills/omh-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-files", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-files

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-files -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omh-files .github/skills/omh-files && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "omh-files" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-files into .github/skills/omh-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-files", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-files -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-files --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omh-files .opencode/skills/omh-files && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "omh-files" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-files into .opencode/skills/omh-files/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-files", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: omh-files
GitHub stars: 3.2k
Token cost: ~1.9k tokens
SKILL.md length: 880 words
Files: 1
Skills in repo: 143
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

[omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search…

The user says: workspace-file-operator
SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Workspace file operator

What it does

Omh Files is an agent skill from rlaope/oh-my-hermes. [omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions. Use when the user says: workspace-file-operator, workspace file operator, file operator, file operation, file operations, filesystem task, filesystem operation, file system task.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.

When your agent uses it

The user says: workspace-file-operator
Workspace file operator
File operations
Filesystem task

Example prompts

“/omh-files”

What it can do on your machine

Read from SKILL.md and the folder at commit 41de9dc. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omh Files loads about 1.9k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 880 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~105
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rlaope/oh-my-hermes at commit 41de9dc, republished under its MIT licence (© rlaope). 880 words, ~1,934 tokens.

Download SKILL.mdSave it as .claude/skills/omh-files/SKILL.md (or your agent's skills folder).

name: omh-files
description: [omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions. Use when the user says: workspace-file-operator, workspace file operator, file operator, file operation, file operations, filesystem task, filesystem operation, file system task.

Workspace File Operator

This is a Hermes-native workspace-file-operator workflow skill.

Why This Exists

workspace-file-operator exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.

Do Not Use When

The request is already handled by a narrower explicit skill with stronger evidence.
The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.

Examples

Good example:

Prompt: workspace-file-operator list files in the reports folder and move old PDFs into archive after confirmation.
Expected behavior: Produce prepare_workspace_file_operator_card with required context, wrapper actions, and not-evidence boundaries.
Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.

Bad example:

Prompt: workspace-file-operator delete every matching file without path scope or confirmation.
Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.
Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.

Completion Checklist

The path root, allowed file operations, excluded paths, destructive-operation policy, and stop condition are explicit.
Delete, overwrite, move, rename, permission change, archive mutation, upload, and download are gated or marked missing.
Directory listings, file contents, hashes, diffs, and operation results are reported only from observed file evidence.

Recovery Notes

If the target path or folder is missing, ask for the smallest path scope needed before preparing the operation.
If delete, overwrite, move, rename, chmod, or irreversible cleanup is requested, require an explicit confirmation gate.
If the request is file conversion, deck/PDF export, or attachment delivery, route to materials-package or deliverable-package instead.

Workflow Lane

Current lane: Automation and status (achievements, workspace-audit, production-audit, live-incident-response, automation-blueprint, github-event-ops, github-issue-intake, buzz, +39 more) - schedules, status, health, and ops review.
If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Use When

Use when Hermes should prepare or supervise local workspace/file-system operations such as listing, searching, organizing, copying, moving, renaming, archiving, or deleting files without claiming the operation ran.

Strong routing signals: `workspace-file-operator`, `workspace file operator`, `file operator`, `file operation`, `file operations`, `filesystem task`, `filesystem operation`, `file system task`, `file system operation`, `list files`, `list folder`, `list directory`, `find local files`, `search files`, `organize files`, `organize folder`, `move file`, `move files`, `copy file`, `copy files`, `rename file`, `rename files`, `delete file`, `delete files`, `remove file`, `remove files`, `archive files`, `downloads folder`, `reports folder`, `folder cleanup`, `file cleanup`, `파일 작업`, `파일 조작`, `파일 정리`, `파일 검색`, `파일 찾아`, `파일 이동`, `파일 복사`, `파일 이름 변경`, `파일 삭제`, `폴더 정리`, `다운로드 폴더`, `디렉터리 목록`

Catalog Metadata

Category: filesystem Phase: file-task Hermes role: guide Quality tier: workflow-surface-gated Reasoning demand: standard

Quality bar:

Name the user-facing workflow objective, required context, next action, and stop condition.
Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.
Expose missing tools, credentials, targets, or observations as user-visible gaps.

Handoff policy:

Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded.

Required inputs:

user request
target context
delivery or status expectation
known missing evidence

Expected outputs:

workspace_file_task_card/v1
file_operation_scope/v1
file_observation_manifest/v1 when observed
file_confirmation_gate/v1 when destructive
next action
prepared-vs-observed boundary

Artifact expectations:

workspace_file_task_card/v1 metadata-only wrapper card when prepared
file_operation_scope/v1 with path root, allowed operations, excluded paths, and stop condition
file_observation_manifest/v1 only when directory listings, file stats, hashes, diffs, or operation output are observed
session_file_activity/v1 (omh quality-evidence file-activity --hermes-session <id> --json) cited in that manifest for which workspace files a Hermes session's read_file, write_file, and patch calls named and the outcome Hermes recorded; never as file-content, hash, diff, test, review, CI, or merge evidence
file_confirmation_gate/v1 for delete, overwrite, move, rename, chmod, archive mutation, or irreversible cleanup

Show full SKILL.md (241 more words)Show less

Safety rules:

A workspace file operator card is not file read, file write, copy, move, rename, delete, archive, upload, download, permission change, or destructive filesystem evidence unless observed file-operation output records it.
Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.

Runtime Evidence

Preferred harness for this skill: workspace-file-operator.

omh runtime record --skill workspace-file-operator --harness workspace-file-operator --status started

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.

Files

Just SKILL.md in skills/omh-files of rlaope/oh-my-hermes.

Open the folder on GitHubat commit 41de9dc

Compare with similar skills

Omh Files next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omh Files compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Omh Files this skillrlaope/oh-my-hermes	3.2k	—	~1.9k	Automated safety check: Pass	MIT	yesterday
Implementing Policy As Code With Open Policy Agentmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.6k	Automated safety check: Notes	Apache-2.0	1 mo ago
Cleanupsimstudioai/sim	30k	—	~1.4k	Automated safety check: Pass	Apache-2.0	today
Policy Acknowledgementsickn33/agentic-awesome-skills	47k	1 repos	~3.4k	Automated safety check: Pass	MIT	today
Privacy Policythedaviddias/Front-End-Checklist	74k	—	~617	Automated safety check: Pass	MIT	3 days ago
Editorial Policythedaviddias/Front-End-Checklist	74k	—	~763	Automated safety check: Pass	MIT	3 days ago

Similar skills

Implementing Policy As Code With Open Policy Agent
mukul975/Anthropic-Cybersecurity-Skills
Implements policy-as-code enforcement with Open Policy Agent (OPA) and Gatekeeper for Kubernetes and CI/CD pipelines, covering writing Rego policies, deploying OPA Gatekeeper as a Kubernetes…
34k GitHub stars~2.6k tokensUpdated 1 mo ago
DevOps & CloudAuto-check: notes
Cleanup
simstudioai/sim
Run all code quality skills — effects, memo, callbacks, state, React Query, emcn design review, url-state, comments, and test-audit — analyzing in parallel, then applying fixes sequentially
30k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed
Policy Acknowledgement
sickn33/agentic-awesome-skills
Policy acknowledgement register: employee, policy and version, sent and due dates, acknowledged date and flag, days overdue, reminder sent and status.
47k GitHub starsUsed in 1 repo~3.4k tokens
Auto-check passed
Privacy Policy
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing whether a website has a visible, accessible privacy policy link, particularly in the footer navigation.
74k GitHub stars~617 tokensUpdated 3 days ago
Legal & ComplianceAuto-check passed
Editorial Policy
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater…
74k GitHub stars~763 tokensUpdated 3 days ago
Auto-check passed
Policy Drafting
anthropics/claude-for-legal
Official
Draft an employment policy with state supplements where law differs across the jurisdictional footprint.
9.6k GitHub starsUsed in 2 repos~1.4k tokens
Legal & ComplianceAuto-check passed

More from rlaope/oh-my-hermes

All 143 skills in this repo

Omh Accessibility Audit
rlaope/oh-my-hermes
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.
3.2k GitHub stars~2.8k tokensUpdated yesterday
Auto-check passed
Omh Agent Evaluation
rlaope/oh-my-hermes
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.
3.2k GitHub stars~2.1k tokensUpdated yesterday
Auto-check passed
Omh Agent Instructions
rlaope/oh-my-hermes
[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…
3.2k GitHub stars~2.2k tokensUpdated yesterday
Auto-check passed
Omh Agent Ops Review
rlaope/oh-my-hermes
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.
3.2k GitHub stars~1.9k tokensUpdated yesterday
Auto-check passed
Omh AI Slop Cleaner
rlaope/oh-my-hermes
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.
3.2k GitHub stars~2.7k tokensUpdated yesterday
Auto-check passed
Omh App Debugging
rlaope/oh-my-hermes
[omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the…
3.2k GitHub stars~2.3k tokensUpdated yesterday
Auto-check passed

Questions about Omh Files

What does Omh Files do?

[omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search…. Omh Files is an agent skill from rlaope/oh-my-hermes. [omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions.

When should I use Omh Files?

Omh Files fits situations like: the user says: workspace-file-operator; workspace file operator; file operations; filesystem task.

How do I install Omh Files in Claude Code?

Run `npx skills add rlaope/oh-my-hermes --skill omh-files -a claude-code`. Or copy the skill folder (skills/omh-files in rlaope/oh-my-hermes) into .claude/skills/omh-files in your project. Claude Code loads it when a task matches its description.

How do I install Omh Files in Codex?

Run `npx skills add rlaope/oh-my-hermes --skill omh-files -a codex`. Or copy the skill folder (skills/omh-files in rlaope/oh-my-hermes) into .agents/skills/omh-files in your project. Codex loads it when a task matches its description.

Can I use Omh Files in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-files -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-files, .gemini/skills/omh-files, .github/skills/omh-files and .opencode/skills/omh-files in your project.

What does Omh Files need to run?

SKILL.md names no scripts, command-line tools or credentials: Omh Files is instructions for the agent only.

Does Omh Files access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Omh Files safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omh Files use?

Omh Files is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omh Files use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Omh Files?

Skills that share tags, products or a category with Omh Files: Implementing Policy As Code With Open Policy Agent (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Cleanup (simstudioai/sim, 30k stars), Policy Acknowledgement (sickn33/agentic-awesome-skills, 47k stars) and Privacy Policy (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Files?

rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,233 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 8, 2026.

Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Omh Files

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Workspace File Operator

Why This Exists

Do Not Use When

Examples

Completion Checklist

Recovery Notes

Workflow Lane

Use When

Catalog Metadata

Runtime Evidence

Files

Compare with similar skills

Similar skills

More from rlaope/oh-my-hermes

Questions about Omh Files