ownex-vault
Skill1 starsChanged 3 months agoMITView on GitHub
Goal: Ensure data integrity — verify database consistency, validate backups, and manage credential rotation schedules. App: vault · Cadence: 6h · Risk: low discover → triage → act → verify → notify
- Reads credentials
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- graftSkill
- loop-triageSkill
- ownex-atlasSkill
- ownex-forgeSkill
- ownex-odysseySkill
- ownex-pulseSkill
- ownex-securitySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Goal: Ensure data integrity — verify database consistency, validate backups, and manage credential rotation schedules.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OWNEX Vault Cycle — Data Vault
Goal: Ensure data integrity — verify database consistency, validate backups, and manage credential rotation schedules.
App: vault · Cadence: 6h · Risk: low
Default Phases
discover → triage → act → verify → notify
Human Gates
- Credential rotation (API keys, tokens)
- Data restoration events
- Schema migration validation
Required Skills
integrity-check— Verify database integrity and consistencybackup-verify— Validate recent backup completeness and freshnesscredential-rotate— Detect and manage expiring credentials
Checks
- Database WAL integrity
- Backup file age (<24h for daily, <1h for WAL)
- Credential expiry dates
- Encryption key rotation schedule
- Configuration file consistency
State File
# Vault Cycle State
Last run: <timestamp>
Backups:
daily: ✅ complete (last: 2026-07-28 02:00)
WAL: ✅ streaming (last: 2026-07-28 10:30)
Credentials:
API_KEY_PROD: 🔴 expires in 3 days — ROTATE
DB_PASSWORD: 🟢 expires in 60 days
JWT_SECRET: 🟢 expires in 180 days
Integrity:
DB check: ✅ passed (no corruption)
Schema: ✅ up to dateSuccess Metrics
- Backup freshness (% within SLA)
- Credential expiry lead time
- DB integrity check pass rate
- Time to detect data inconsistency
Budget
- Daily cap: 30k tokens
- Max runs: 4/day
- L1: report + alert
- L2: auto-rotate credentials (with confirmation gate)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

