chore(skills): standards sweep — bring 42 bundled/optional skills up to hardline
Audited all 191 in-repo skills (77 bundled, 114 optional) against the authoring standards (AGENTS.md hardline + PR #80800). Fixed 42: - 8 overlong descriptions rewritten to <= 60 chars, one sentence, period (one-three-one-rule 525ch, drug-discovery 405ch, web-pentest 358ch, fitness-nutrition 352ch, neuroskill-bci 332ch, oss-forensics 320ch, computer-use 307ch, memento-flashcards 252ch) - 24 skills with missing frontmatter fields: author (credited from git history: f-trycua, SHL0MS, teyrebaz33, haileymarshall, FurkanL0, teknium1), license, version, platforms, tags - 7 machine-local paths scrubbed (/home/bb, /home/user, /home/ubuntu -> portable placeholders) - 11 marketing-word intros reworded (Comprehensive/state-of-the-art) - docs catalogs + per-skill pages regenerated, scope-disciplined Deferred (not in this PR): - 14 frontmatter/dir name mismatches — open PR #42788 already proposes the dir-rename approach for 4 of them; resolve there as one class - 2 skills over 100k chars (pytorch-fsdp 159k, research-paper-writing 103k) — need content splits into references/, separate PRs - comfyui dangling related_skill resolves after the name-mismatch class
This commit is contained in:
@@ -2,6 +2,8 @@
|
||||
name: dogfood
|
||||
description: "Exploratory QA of web apps: find bugs, evidence, reports."
|
||||
version: 1.0.0
|
||||
author: Teknium (teknium1), Hermes Agent
|
||||
license: MIT
|
||||
platforms: [linux, macos, windows]
|
||||
metadata:
|
||||
hermes:
|
||||
|
||||
@@ -183,7 +183,7 @@ The TUI is built Ink + tsx. Two common scenarios:
|
||||
`ui-tui/package.json` has `npm run dev` (tsx --watch). Add `--inspect-brk` by running tsx directly:
|
||||
|
||||
```bash
|
||||
cd /home/bb/hermes-agent/ui-tui
|
||||
cd <hermes-agent-repo>/ui-tui
|
||||
npm run build # produce dist/ once so transpile isn't needed on first load
|
||||
node --inspect-brk dist/entry.js
|
||||
# In another terminal:
|
||||
@@ -227,7 +227,7 @@ Those are Python, not Node — use the `python-debugpy` skill for them. Only Nod
|
||||
## Running Vitest Tests Under the Debugger
|
||||
|
||||
```bash
|
||||
cd /home/bb/hermes-agent/ui-tui
|
||||
cd <hermes-agent-repo>/ui-tui
|
||||
# Run a single test file paused on entry
|
||||
node --inspect-brk ./node_modules/vitest/vitest.mjs run --no-file-parallelism src/app/foo.test.tsx
|
||||
```
|
||||
|
||||
@@ -149,7 +149,7 @@ For long-lived processes: Hermes gateway, tui_gateway, a daemon, a process that'
|
||||
### Setup
|
||||
|
||||
```bash
|
||||
source /home/bb/hermes-agent/.venv/bin/activate
|
||||
source <hermes-agent-repo>/.venv/bin/activate
|
||||
pip install debugpy
|
||||
```
|
||||
|
||||
@@ -246,7 +246,7 @@ This is fine for one-off automation but painful as an interactive UX.
|
||||
"connect": { "host": "127.0.0.1", "port": 5678 },
|
||||
"justMyCode": false,
|
||||
"pathMappings": [
|
||||
{ "localRoot": "${workspaceFolder}", "remoteRoot": "/home/bb/hermes-agent" }
|
||||
{ "localRoot": "${workspaceFolder}", "remoteRoot": "<hermes-agent-repo>" }
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
Reference in New Issue
Block a user