Hermes Nightly Self Check Decisions
hermes-nightly-self-check-decisions — Record decisions from nightly self-check findings so behavior is consistent.
Install
$ agentstack add skill-atlasomnia-donna-starter-hermes-nightly-self-check-decisions ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-atlasomnia-donna-starter-hermes-nightly-self-check-decisions) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Hermes Nightly Self-Check — Decisions Log
Purpose: Record decisions made from hermes-nightly-self-check findings so behavior is consistent across sessions.
How to record
Each entry captures one finding and the decision it produced. Use this format:
### YYYY-MM-DD — Short issue title (Issue #N)
- Issue: What the self-check flagged — the symptom, where it came from, and why it happened.
- Decision: The rule or fix chosen, stated so a future session can apply it without re-litigating.Rules:
- One entry per finding; append chronologically under Decision history.
- Write the decision as an executable rule (what to do), not a description of what was done.
- If the finding is resolved by a change to config, skills, or process, note where that change lives so the next check can verify it.
- Do not record credentials, tokens, or private paths in the log — reference locations by role (for example "the primary model endpoint" or "the profile config") instead.
- If the same class of finding recurs, the decision should tighten the check or the rule, not just repeat the note.
Decision history
Starter template (Example #1)
- Issue: Nightly check flagged a mismatch between two config locations for the same setting.
- Decision: Keep one location canonical; document the relationship so future checks do not flag it as a conflict.
Setup flow (Example #2)
- Issue: A tool call failed because an argument was passed as null.
- Decision: Always specify an explicit value; never pass null or omit the argument. Default to the safest explicit value when unsure.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: AtlasOmnia
- Source: AtlasOmnia/donna-starter
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.