helix4u/wiki-upkeep
skills/productivity/wiki-upkeep/SKILL.md
Maintain a local Hermes/knowledge wiki — link checks, index pages, stale sections, and safe edits.
$ install --global
skillsauthnpx skillsauth add helix4u/hermes-agent wiki-upkeepInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 7:46 AM11.6s1 file scanned
SKILL.md
- name:
- wiki-upkeep
- description:
- Maintain a local Hermes/knowledge wiki — link checks, index pages, stale sections, and safe edits.
Wiki upkeep
Use when the user wants to clean up, validate, or reorganize a wiki served by Hermes (/wiki-host) or a static HTML/Markdown wiki tree under their workspace.
Principles
- Read before write: map structure with
search_files/read_filebefore patching. - Small patches: prefer
patchover rewriting large files. - No secrets: do not embed API keys or tokens in wiki pages.
- Paths: use the user’s wiki root (ask if unknown). Typical gateway entry is
knowledge_wiki.htmlat the wiki host root.
Checklist
- Index / navigation: landing page links to major sections; fix broken relative URLs.
- Stale markers: pages with
TODO,FIXME, or dated “last updated” lines — confirm or refresh. - Orphans: pages not linked from the index (optional report to the user).
- Consistency: titles, heading levels, and shared templates (sidebar, footer) match across pages.
Suggested flow
- Identify wiki root (env, user message, or
HERMES_HOME/ workspace convention). search_filesfor*.html,*.mdunder that root (respect.gitignore/ project layout).- Sample
read_fileon index and high-traffic pages. - Apply
patchfor fixes; usewrite_fileonly for new small pages. - Summarize what changed and what to verify in the browser (reload wiki URL).
Optional automation
If the gateway hosts the wiki, remind the user that CHANGELOG.md (repo root) and user-facing behavior notes should stay in sync when wiki content documents product behavior.
Related Skills
helix4u/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
4SKILL.mdUpdated Apr 18, 2026
helix4u/test-driven-development
development
VerifiedTrustedCommunity
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
4SKILL.mdUpdated Apr 18, 2026
helix4u/systematic-debugging
development
VerifiedTrustedCommunity
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
4SKILL.mdUpdated Apr 18, 2026
helix4u/subagent-driven-development
development
VerifiedTrustedCommunity
Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).
4SKILL.mdUpdated Apr 18, 2026