Loading...
Loading...
Found 168 Skills
Switches NixOS/Home Manager configurations, cleans old generations, and performs system maintenance. Use when running os/home switch, pruning the Nix store, or managing system generations.
Automated skill maintenance. Detects and fixes common skill issues: missing frontmatter, name mismatches, unlinked references, empty directories, dead references. Triggers: "heal-skill", "heal skill", "fix skills", "skill maintenance", "repair skills".
Build 3D scenes and visualizations using SceneKit. Use when creating 3D views with SCNView and SCNScene, building node hierarchies with SCNNode, applying materials and lighting, animating with SCNAction, simulating physics with SCNPhysicsBody, loading 3D models (.usdz, .scn), adding particle effects, or embedding SceneKit in SwiftUI with SceneView. Note: SceneKit was deprecated at WWDC 2025 and is in maintenance mode; RealityKit is recommended for new projects.
VRChat skill renovator for knowledge fill, refresh, and quality improvement. Use this skill when updating VRChat skills to new SDK versions, filling missing knowledge, fixing outdated information, or improving skill quality. Targets unity-vrc-udon-sharp and unity-vrc-world-sdk-3 skills. Triggers on: update skills, SDK latest, knowledge fill, skill maintenance, information audit, catch-up, renovate, refresh, improve skills, SDK update.
Inspect or run the manual maintenance workflow. Uses explicitly configured repository checks, applies safe auto-fixes, and archives successful maintenance changes.
Audit a codebase for maintenance and modernization. Challenges scope, reviews architecture/quality/tests/performance/dependencies, files deferred work via bd. Language-specific addendums for iOS/Swift, Go, and Web/JS/CSS activate automatically based on what's in the repo. Supports monorepos with mixed stacks.
For answering, using, and debugging @wot-ui/cli. Keywords: wot, @wot-ui/cli, CLI, MCP, doctor, usage, lint, list, info, doc, demo, token, changelog, extract, wot mcp. Applicable for command queries, parameter explanations, MCP integration, local debugging, data extraction, and open-wot repository maintenance.
Work with the DatoCMS CLI tool (datocms) for command-line migrations, schema type generation, direct one-off CMA calls, typed one-off TypeScript CMA scripts, environment operations, deployment workflows, and multi-project profile syncing. Use when users ask for datocms CLI commands or scripts such as migrations:new, migrations:run, schema:generate, cma:call, cma:docs, cma:script (for ad-hoc typed TypeScript scripts with ambient client/Schema globals), migration scaffolding for models/fields/blocks, CLI setup with datocms.config.json and profiles, OAuth authentication (login, logout, whoami), discovering accessible projects (projects:list), project linking (link, unlink), environment commands (list/fork/promote/rename/destroy), maintenance-mode toggling, CI/CD migration pipelines, blueprint/client project sync, imports from WordPress or Contentful (including assets/content), and CLI plugin management (plugins:install, plugins:add, plugins:available, plugins:link for local plugin development, plugins:remove, plugins:update, plugins:reset, plugins:inspect).
Audit a skill repository or installed skill collection for global consistency, lifecycle coverage, routing quality, documentation drift, memory writeback coverage, stale future-skill references, broken helper paths, and validation readiness. Use this skill whenever the user asks for a global consistency audit, skill taxonomy review, lifecycle audit, cross-skill routing audit, README or AGENTS inventory consistency check, or maintenance pass over a collection of agent skills.
Run the daily wiki maintenance cycle: check all source freshness, update the index, and regenerate hot.md. Use this skill when the user says "/daily-update", "run the daily update", "update everything", "morning sync", "refresh the wiki index", or when triggered by the launchd cron at 9 AM. Also use to set up or verify the cron + terminal notification infrastructure for the first time ("set up the daily cron", "install the terminal notification", "how do I get the morning reminder?").
How to design a content hub that earns topical authority. Pillar topic selection, cluster planning, internal linking architecture, URL structure, pillar and cluster page anatomy, topical authority signals for SEO and AEO/GEO, and the maintenance discipline that distinguishes intentional hubs from accidental orphans. Triggers on pillar content, content hub, topic cluster, topical authority, content architecture, hub and spoke, pillar page, cluster page, content silo, internal linking strategy. Also triggers when a content set is not ranking despite individual piece quality, when a pillar was launched without a cluster, or when content has accumulated without an architecture.
Decide when DuckLake is the right MotherDuck storage pattern. Use when evaluating fully managed DuckLake, BYOB, own-compute DuckLake access, data inlining, object-storage layout, or file-aware maintenance instead of native MotherDuck storage.