[Ubuntu 22.04][Agent&Skills] Hermes cannot run contributor plan-issue from a workspace checkout

## Description

On NemoClaw v0.0.106, a Hermes agent started from a repository workspace does not discover the repository-level `nemoclaw-contributor-plan-issue` skill under `.agents/skills`. The documented `plan issue` trigger therefore cannot begin the required workflow. After the same skill is manually deployed into the Hermes profile, GitHub issue discovery still cannot complete with the shipped sandbox toolchain, and the agent does not honor the Git/GitHub access hard-stop.

Platform scope: Reproduced on Ubuntu 22.04 only; other platforms not tested
Regression: Unknown — earlier versions not tested

## Environment

```text
Device: x86_64 virtual machine
OS: Ubuntu 22.04.5 LTS
Architecture: x86_64
Node.js: v22.23.2
npm: 10.9.8
Docker: 29.6.1
OpenShell CLI: 0.0.85
NemoClaw: v0.0.106
OpenClaw: N/A (Hermes Agent 0.19.0 runtime)
```

## Steps to Reproduce

1. Install NemoClaw v0.0.106 and start a Ready Hermes sandbox with a valid inference provider.
2. Check out the NemoClaw v0.0.106 repository in the Hermes workspace.
3. Confirm that `.agents/skills/nemoclaw-contributor-plan-issue/SKILL.md` exists in that workspace.
4. From the repository checkout, run:
```bash
hermes --yolo -z "plan issue {public-github-issue-url}"
```
5. Inspect the skills exposed to the agent and the final response.
6. As a diagnostic only, manually copy the skill into the Hermes profile skills directory and repeat the same trigger.

## Expected Result

Hermes automatically discovers the repository-level skill, loads `nemoclaw-contributor-plan-issue` for the documented trigger, reads the public GitHub issue through the supported credential and policy boundary, and returns the exact structured plan report. Planning remains read-only and performs no GitHub writes.

## Actual Result

The first Hermes session does not expose `nemoclaw-contributor-plan-issue` in its available skills, so it never loads the workflow and does not produce the required report.

After the skill is manually deployed into the Hermes profile, `skill_view` succeeds, but the shipped environment cannot find `gh`. The agent then attempts unauthenticated `curl` access, receives a GitHub API rate-limit response, and continues trying alternate discovery operations instead of stopping on the Git/GitHub access error. No structured plan report is produced.

## Logs

```text
Before manual deployment:
Skill nemoclaw-contributor-plan-issue is absent from the available skill list.

After manual deployment:
skill_view: success=true, name=nemoclaw-contributor-plan-issue
which gh: no output, exit code 1
GitHub API: rate limit exceeded for the shared public egress address
The agent continues with repository searches and an alternate curl attempt instead of stopping.

No GitHub labels, comments, child issues, or relationship changes were created.
```