Skills Guide

Housekeeper

VerifiedCaution

It monitors development tool versions, checks for available updates for Oh My Opencode, and provides clear upgrade instructions. Useful for version check, update, or tool maintenance queries.

Download and use
Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#tool-maintenance#version-check#upgrade#oh-my-opencode

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Automated summary

This skill monitors and updates development tools, starting with Oh My Opencode, by checking versions and providing clear upgrade instructions.

Strengths

  • Automates checking local vs remote versions.
  • Provides clear upgrade commands with context.
  • Preserves configuration files during updates.
  • Distinguishes between stable and beta releases.

Limitations

  • Currently limited to Oh My Opencode only.
  • No auto-update feature; requires manual intervention.
  • Does not cover initial installation or feature troubleshooting.
When to use it

Use when the user asks about checking or upgrading the version of Oh My Opencode.

When not to use it

Do not use for first-time installation or for non-version-related issues.

Security analysis

Caution
Quality score85/100

The skill instructs the AI agent to execute 'bunx oh-my-opencode ...' commands for version checks and upgrades. While intended for a legitimate maintenance tool, this involves network downloads and execution of code, which could be exploited if the package is malicious. No destructive or exfiltration actions are present, but the risk warrants caution.

Findings
  • •Instructs running 'bunx' commands, which downloads and executes code from npm; potential supply chain risk if the package is compromised.
How this analysis is made

Examples

Check if Oh My Opencode is up to date
Is my Oh My Opencode installation up to date?
Upgrade to latest Oh My Opencode
How do I upgrade to the latest Oh My Opencode?

name: housekeeper description: Automatically triggers when users ask about upgrading, updating, or checking versions of Oh My Opencode or other development tools. Use for version checks, upgrade procedures, maintenance recommendations, and keeping development tools current. scope: global license: MIT

Housekeeper

What this skill does

The Housekeeper skill monitors and maintains your development tools, starting with Oh My Opencode. It checks current versions, identifies available updates, and provides clear upgrade instructions to keep your tools current.

When to use this skill

This skill automatically triggers when users ask about:

  • "upgrade", "update", or "check version" for Oh My Opencode
  • "is my tool up to date?", "how to update [tool name]"
  • "check for updates", "what's the latest version of [tool]"
  • General tool maintenance and version management queries

Never use this skill for:

  • Installing tools for the first time (use installation skills instead)
  • Questions about specific tool usage or features
  • Bug fixes or troubleshooting unrelated to versions

Instructions

For Oh My Opencode Maintenance:

  1. Check Current Status:

    • Run bunx oh-my-opencode get-local-version to check your current version
    • Compare against the latest available versions from npm

  2. Identify Update Type:

    • Determine if the latest version is stable or beta
    • Check release notes for breaking changes or new features
    • Consider your stability requirements (stable vs beta)

  3. Perform Upgrade:

    • For stable upgrades: bunx oh-my-opencode install
    • For specific versions: bunx oh-my-opencode@<version> install
    • For beta versions: bunx oh-my-opencode@3.0.0-beta.2 install

  4. Verify Installation:

    • Run bunx oh-my-opencode doctor to ensure everything works correctly
    • Confirm configuration files are preserved (oh-my-opencode.json, opencode.json)

  5. Provide Maintenance Recommendations:

    • Suggest regular update schedule (weekly/monthly)
    • Recommend testing major version upgrades in non-critical projects first
    • Advise on backing up configuration before major upgrades

Future Tool Support:

This skill will be extended to support additional development tools. The framework is designed to be extensible for:

  • Other OpenCode plugins
  • Development environment tools
  • Language-specific package managers
  • CLI utilities

Example Usage

User: "Is my Oh My Opencode installation up to date?"

Housekeeper Response:

  • Checks current version with bunx oh-my-opencode get-local-version
  • Compares against npm registry
  • Reports status and provides upgrade command if needed

User: "How do I upgrade to the latest Oh My Opencode?"

Housekeeper Response:

  • Identifies latest stable vs beta versions
  • Provides appropriate upgrade command
  • Explains any important considerations for the upgrade

Important Notes

  • Configuration Preservation: Your existing configuration files are preserved during upgrades
  • No Auto-Update: Manual intervention is required for all updates
  • Version Pinning: You can pin to specific versions if needed
  • Backup Recommended: Always backup configuration before major version upgrades
  • Stable vs Beta: Choose stable versions for production, beta for testing new features

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/housekeeper-mm78no1s/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/housekeeper-mm78no1s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/housekeeper-mm78no1s/download' --output '.skill-downloads/housekeeper-mm78no1s/SKILL.md.part' && mv '.skill-downloads/housekeeper-mm78no1s/SKILL.md.part' '.skill-downloads/housekeeper-mm78no1s/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/housekeeper-mm78no1s/SKILL.md' && test -s '.skill-downloads/housekeeper-mm78no1s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/housekeeper' && cp -R '.skill-downloads/housekeeper-mm78no1s' '.claude/skills/housekeeper'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/housekeeper-mm78no1s'

openskills read 'housekeeper-mm78no1s'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/housekeeper-mm78no1s/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot