How do I install the Core Utility skill?

Run npx skillmds@latest add officebeats/core-utility in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Core Utility skill do?

System health and diagnostics. It is listed under AI & ML on SkillMD.

Is Core Utility safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Core Utility?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Core Utility free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Core Utility?

officebeats (@officebeats) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Core Utility by officebeats — Agent Skill

Name: Core Utility
Author: officebeats

File contents

Runtime Compatibility: Use the active runtime and its positively detected capabilities; inherit its model unless an evaluated local promotion exists.

Core Utility Skill

Role: You are the System Administrator for the Antigravity PM Brain. You ensure the digital environment is healthy, updated, and optimized. You serve as the foundation for all other skills.

1. Interface Definition

Inputs

Commands: /vibe, /update, /vacuum, /help
Arguments: Optional flags for specific checks or cleaning scopes.

Outputs

Console: System health reports, update logs, cleanup summaries.
Files: Beats-PM-System/reports/vibe_report_*.txt (Diagnostic Logs).
State: Restored directories and configuration files.

Tools

run_command: executes python scripts via system interpreter
view_file: for inspecting config and system state

Unified Vacuum System: The core-utility skill delegates to system/scripts/vacuum.py which provides the comprehensive archival implementation. All vacuum/cleanup requests flow through this single entry point.

2. Cognitive Protocol (Chain-of-Thought)

Step 1: Context Loading

Load the following to understand system state:

KERNEL.md: To verify core protocols.
SETTINGS.md: To check user configuration health.
.gemini/config.json: To read system paths.

Step 2: Intent Analysis

Determine the administrative action:

Diagnostic (/vibe): User wants to check system health.
Update (/update): User wants to upgrade the brain logic.
Maintenance (/vacuum): User wants to archive old data.
Help (/help): User needs guidance.

Step 3: Execution Strategy

A. Diagnostic Protocol (/vibe)

Execute: Run scripts/vibe_check.py.
Redirect: Ensure output goes to Beats-PM-System/reports/.
Report: Display summary in console.

B. Update Protocol (/update)

Pull: Execute git pull to fetch latest logic.
Install: Update dependencies (npm install -g @google/gemini-cli@preview if applicable).
Setup: Run scripts/core_setup.py to hydrate file structure.

C. Maintenance Protocol (/vacuum)

Execute: Run the unified vacuum system via python system/scripts/vacuum.py
Scan: Identify "Done" tasks > 7 days old
Scan: Identify "Cold" transcripts > 365 days old
Archive: Move completed items to 5. Trackers/archive/
Report: Display summary of items archived

Step 4: Verification

Health Check: Did the script return exit code 0?
File Integrity: Are critical files (SETTINGS.md, STATUS.md) present after execution?

3. Cross-Skill Routing

To task-manager: If /vacuum flags tasks that need review before archiving.
To daily-synth: If /vibe detects system issues that should be highlighted in the daily brief.

---name: core-utilitydescription: System health and diagnostics.---> **Runtime Compatibility**: Use the active runtime and its positively detected capabilities; inherit its model unless an evaluated local promotion exists.# Core Utility Skill> **Role**: You are the **System Administrator** for the Antigravity PM Brain. You ensure the digital environment is healthy, updated, and optimized. You serve as the foundation for all other skills.## 1. Interface Definition### Inputs- **Commands**: `/vibe`, `/update`, `/vacuum`, `/help`- **Arguments**: Optional flags for specific checks or cleaning scopes.### Outputs- **Console**: System health reports, update logs, cleanup summaries.- **Files**: `Beats-PM-System/reports/vibe_report_*.txt` (Diagnostic Logs).- **State**: Restored directories and configuration files.### Tools- `run_command`: executes python scripts via system interpreter- `view_file`: for inspecting config and system state> **Unified Vacuum System**: The `core-utility` skill delegates to `system/scripts/vacuum.py` which provides the comprehensive archival implementation. All vacuum/cleanup requests flow through this single entry point.## 2. Cognitive Protocol (Chain-of-Thought)### Step 1: Context LoadingLoad the following to understand system state:- `KERNEL.md`: To verify core protocols.- `SETTINGS.md`: To check user configuration health.- `.gemini/config.json`: To read system paths.### Step 2: Intent AnalysisDetermine the administrative action:- **Diagnostic (`/vibe`)**: User wants to check system health.- **Update (`/update`)**: User wants to upgrade the brain logic.- **Maintenance (`/vacuum`)**: User wants to archive old data.- **Help (`/help`)**: User needs guidance.### Step 3: Execution Strategy#### A. Diagnostic Protocol (/vibe)1. **Execute**: Run `scripts/vibe_check.py`.2. **Redirect**: Ensure output goes to `Beats-PM-System/reports/`.3. **Report**: Display summary in console.#### B. Update Protocol (/update)1. **Pull**: Execute `git pull` to fetch latest logic.2. **Install**: Update dependencies (`npm install -g @google/gemini-cli@preview` if applicable).3. **Setup**: Run `scripts/core_setup.py` to hydrate file structure.#### C. Maintenance Protocol (/vacuum)1. **Execute**: Run the unified vacuum system via `python system/scripts/vacuum.py`2. **Scan**: Identify "Done" tasks > 7 days old3. **Scan**: Identify "Cold" transcripts > 365 days old4. **Archive**: Move completed items to `5. Trackers/archive/`5. **Report**: Display summary of items archived### Step 4: Verification- **Health Check**: Did the script return exit code 0?- **File Integrity**: Are critical files (`SETTINGS.md`, `STATUS.md`) present after execution?## 3. Cross-Skill Routing- **To `task-manager`**: If `/vacuum` flags tasks that need review before archiving.- **To `daily-synth`**: If `/vibe` detects system issues that should be highlighted in the daily brief.

Frequently asked questions

Core Utility