hermes-project-discovery

Locate real user projects outside sandboxed workspaces by scanning home-adjacent paths.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/photonics-dhl/Hermes --skill hermes-project-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hermes-project-discovery
Source: https://github.com/photonics-dhl/Hermes/tree/main/hermes-home/skills/productivity/hermes-project-discovery
Command: npx skills add https://github.com/photonics-dhl/Hermes --skill hermes-project-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hermes Project Discovery helps users locate and access real project directories that reside outside sandboxed working directories, enabling seamless code and data work without manual path guessing.

Core Features & Use Cases

  • Sandbox-aware location: Detects when the current working directory is a sandbox and guides navigation to the actual project path.
  • Home-adjacent search: Scans common base locations such as /data/home/<username>/, /home/<username>/, and ~/.hermes/ to locate the user project.
  • Gateway state extraction: Reads gateway_state.json to extract the real project path from argv.
  • Path reconstruction: Derives the user home from argv and locates the real project in the correct directory (e.g., /data/home/<user>/321/DHL/...).
  • Use Case: When you request to explore a named project like "Scholar's Tea" or "Project X" while in a sandbox, Hermes locates the actual codebase for direct work.

Quick Start

Ask Hermes to locate a named project outside the sandbox and open its real directory for work.

Frequently Asked Questions about hermes-project-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find my real project directory when working inside a sandbox?

A sandbox-aware project locator detects the sandbox state, scans home-adjacent paths like /data/home/<username>/, and extracts the real project path from gateway_state.json to reconstruct the actual directory location for seamless access.

How does gateway_state.json help locate user projects outside the sandbox?

Gateway state extraction reads gateway_state.json to derive the user home from argv, enabling the discovery process to locate the real project in the correct directory such as /data/home/<user>/321/DHL/ instead of guessing paths manually.

What is the best way to access a named codebase from a sandboxed working directory?

The best way to access a named codebase from a sandboxed working directory is to request a sandbox-aware locator to scan common base locations and home-adjacent paths, reconstructing the true project path from gateway state data for immediate work.

Can I access real filesystem projects in HPC environments without manual path guessing?

Yes, you can access real filesystem projects in HPC environments without manual path guessing by scanning home-adjacent paths such as /home/<username>/ and ~/.hermes/, then extracting the actual project path from gateway_state.json to navigate directly.

What are the limitations of sandbox-aware project discovery for home-adjacent paths?

Limitations of sandbox-aware project discovery include reliance on the presence and correct parsing of gateway_state.json, and the assumption that real user projects reside in predefined home-adjacent paths like /data/home/<username>/ or ~/.hermes/ for successful location.