Our review
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.
Use when the user asks about checking or upgrading the version of Oh My Opencode.
Do not use for first-time installation or for non-version-related issues.
Security analysis
CautionThe 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.
- •Instructs running 'bunx' commands, which downloads and executes code from npm; potential supply chain risk if the package is compromised.
Examples
Is my Oh My Opencode installation up to date?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:
-
Check Current Status:
- Run
bunx oh-my-opencode get-local-versionto check your current version - Compare against the latest available versions from npm
- Run
-
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)
-
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
- For stable upgrades:
-
Verify Installation:
- Run
bunx oh-my-opencode doctorto ensure everything works correctly - Confirm configuration files are preserved (
oh-my-opencode.json,opencode.json)
- Run
-
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
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.