Audit knowledge base consistency for frontmatter issues, stale projects, and outdated references.
npx skills add https://github.com/BEKO2210/Firstbrain --skill maintain-beko2210
Please help me install this Agent Skill. Skill: maintain Source: https://github.com/BEKO2210/Firstbrain/tree/main/.agents/skills/maintain Command: npx skills add https://github.com/BEKO2210/Firstbrain --skill maintain-beko2210
This Skill automates the tedious and error-prone process of auditing your knowledge base for inconsistencies, stale information, and outdated references, ensuring your second brain remains accurate and reliable.
/maintain regularly to catch notes with missing created dates, ensure all tags are lowercase, and identify projects that have been inactive for over 60 days, prompting you to archive them.Run the maintain skill to audit your vault for any inconsistencies and apply safe fixes.
High-intent search queries and answers about installing and using this skill.
Stale project detection identifies notes or projects that haven't been updated in a configurable period. You can set custom staleness thresholds, such as flagging projects inactive for over 60 days, to prompt archiving and maintain vault consistency.
The best way to fix tag casing issues and type/folder mismatches is through automated vault maintenance. The system automatically corrects safe issues in the AUTO zone and proposes solutions for complex inconsistencies in the PROPOSE zone for user review.
Yes, you can automatically fix links to archived notes. The reference checking feature flags links pointing to archived or completed notes, automatically correcting safe issues and proposing corrections for outdated references to maintain knowledge base consistency.
Yes, vault maintenance supports custom staleness thresholds for detecting inactive projects. You can configure the specific period for staleness detection, allowing the audit to identify projects that haven't been updated within your defined timeframe for reliable vault maintenance.
The consistency audit categorizes fixes into AUTO, PROPOSE, and NEVER zones to ensure user control over vault maintenance. AUTO applies safe automated fixes, PROPOSE offers solutions for complex issues requiring review, and NEVER designates actions that should not be automatically modified.
mindmorassWrite Markdown notes and Mermaid diagrams into Obsidian vault folders.
potetoPrune outdated and redundant brain notes using an auditor and reviewer.
ballredRead and write Obsidian vault notes while preserving YAML frontmatter and wiki-links.
arakitakashiDelegate error analysis and fix generation to a sub-agent.