codex-owner-move-debug-1778257045Validates owner migration by creating a skill under a personal owner and moving it to OpenClaw while documenting cleanup steps.
Install via ClawdBot CLI:
clawdbot install steipete/codex-owner-move-debug-1778257045Grade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 13, 2026
A developer creates a skill under a personal owner, then moves it to OpenClaw to validate the owner migration flow during a pull request. The process includes explicit migration intent and cleanup steps to ensure the transition is smooth and auditable.
When a team member leaves or changes roles, their skills need to be transferred to another owner. This scenario validates that the migration workflow handles ownership changes correctly, preserving skill metadata and access controls.
A temporary skill is created for a specific project, then migrated to a permanent owner after the project ends. This scenario tests that temporary skills can be properly retired or transferred without data loss.
During a compliance audit, an administrator needs to verify the ownership history of a skill. This scenario ensures that the migration workflow logs all ownership changes with timestamps and reasons.
A platform charges a commission on each sale of a skill. Transparent owner migration ensures that royalties are correctly attributed to the original creator even after ownership changes.
Enterprises pay for premium features including skill ownership management and migration tools. This model generates recurring revenue from subscription fees.
Consultants or system integrators offer migration services to clients, helping them transfer skill ownership during organizational changes. Revenue comes from service fees.
💬 Integration Tip
Integrate the migration workflow with your CI/CD pipeline to automate ownership transfer during PR merges, ensuring consistent validation and audit logging.
Scored May 13, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.