Results for “maintenance”

Manage the NV oOS Pro Toolkit Security Operations system — audit events, security training, maintenance windows, and incident records. Covers the full security ops lifecycle: audit logging, incident detection/response, maintenance scheduling, and compliance training tracking. Use when working with security audit trails, investigating incidents, scheduling maintenance windows, managing security training programs, or troubleshooting security operations data.

The English summary is being prepared. Showing the original description.

Unified workspace maintenance skill. Covers: (1) backing up the workspace to GitHub git repo, and (2) updating OpenClaw and skills. Use when: asked to backup, push to git, update openclaw, update skills, or run maintenance.

The English summary is being prepared. Showing the original description.

Use this skill when the user asks how to design or improve a Preventive Maintenance (PM) program for a fleet — mileage vs time intervals, A/B/C/D inspection levels, ATA standards, common PM tasks, scheduling software, cost tracking, and how PM affects roadside inspections + CSA scores. Reference ATA Equipment Maintenance Council standards.

The English summary is being prepared. Showing the original description.

Search locally archived GitHub issues and pull requests, find related discussions and possible duplicates, and check archive freshness. Verify the current GitHub state before making maintenance decisions or changing public content.

• Find issues and pull requests related to a reported problem
• Review groups of possible duplicate issues
• Check archive freshness before making a maintenance decision

Review Archify issues, pull requests, and code by weighing user value, implementation and maintenance costs, and wider impact. Use evidence to decide whether work is worthwhile, compare alternatives, and identify questions that still affect the decision.

• Prioritizing reported issues
• Reviewing the cost and impact of a pull request
• Assessing code maintainability

Review JavaScript written directly in HTML and move suitable code into external files. Replace inline event handlers with addEventListener, clarify browser verification steps, and explain how separating code supports maintenance, caching, and security.

• Moving JavaScript out of HTML markup
• Replacing onclick handlers with addEventListener
• Reviewing script separation for caching and maintenance

Audit a codebase across nine areas, including architecture, tests, security, and documentation. Produces TECH_DEBT_AUDIT.md with source locations, severity ratings, estimated repair effort, and prioritized recommendations to help plan maintenance work.

• Assessing a codebase before maintenance
• Prioritizing technical debt fixes
• Checking architecture and code consistency

Guide AAS maintainers through pull request review, batch merging, generated-file synchronization, and scripted releases. Follow protected-branch procedures and check evidence tied to the exact revision before accepting changes.

• Reviewing and merging a batch of pull requests
• Synchronizing generated files after source changes
• Preparing and publishing a protected release

Review PostgreSQL queries and data designs using execution plans, which show how queries run, and targeted index recommendations. Get guidance on JSONB, arrays, full-text search, analytical queries, extensions, and routine database maintenance.

• Investigating slow queries and choosing indexes
• Reviewing JSONB searches and full-text search
• Writing running totals and ranking queries

Turn an existing GitHub Actions workflow into a structured specification for maintenance and AI reference. Document its purpose, triggers, job dependencies, inputs, outputs, permissions, and failure handling, focusing on expected behavior rather than implementation details.

• Documenting an existing GitHub Actions workflow
• Reviewing job order and dependencies
• Organizing permissions and failure handling

Improve PostgreSQL performance through a staged workflow covering slow query analysis, indexes that speed up data access, query rewrites, configuration tuning, routine maintenance, and monitoring for production databases.

• Investigating slow PostgreSQL queries
• Reviewing database indexes
• Tuning database configuration

Check your gbrain setup and receive prioritized suggestions for overdue updates, pending migrations, stalled jobs, and other maintenance issues. Findings include repair commands, while any fixes require your approval.

• Reviewing your gbrain setup
• Getting a weekly maintenance check
• Prioritizing updates and stalled jobs

Audit a gbrain knowledge base for outdated pages, broken or missing links, inconsistent tags, and missing citations. Get issue counts and specific repair actions, with additional checks for search quality and maintenance status.

• Audit knowledge base quality
• Find isolated pages and broken links
• Review citations and inconsistent tags

Build a persistent connection that receives Zoom events, such as meeting starts and participant arrivals. This reference covers choosing WebSockets, a connection kept open for events, plus authentication, connection maintenance, and reconnection.

• Receive meeting start and end events
• Track participant arrivals and departures
• Receive events without a public endpoint

Scan a codebase for technical debt—issues that make future maintenance harder—and prioritize fixes using business impact and effort. Generate a ranked backlog, sprint allocations, and trend reports to assess cleanup work over time.

• Assess technical debt across a codebase
• Prioritize refactoring for the next sprint
• Compare debt levels before and after cleanup

Generate an operational runbook template from a service name. Provide sections for starting, stopping, health checks, incident handling, maintenance, and rollback, so teams can add service-specific commands and build consistent operating procedures.

• Creating an initial runbook for a new service
• Standardizing incident procedures across teams
• Preparing documentation for on-call onboarding

Prepare a daily NemoClaw maintenance plan by ranking pending pull requests and issues, checking work carried over from earlier versions, and selecting release targets. Produce a queue with owners, next actions, and merge readiness.

• Plan the day's maintenance work
• Find work carried over from earlier releases
• Rank pull requests for review

Monitor TPU workloads on GKE using system metrics and PromQL, a metrics query language. Check utilization, memory, node availability, and interruptions to investigate infrastructure issues and calculate average recovery times and intervals between interruptions.

• Checking TPU utilization and memory usage
• Investigating node and node pool availability
• Tracing maintenance and preemption interruptions

Install LifeOS into an existing AI agent environment, then use a guided interview to capture current circumstances and goals for the Pulse dashboard. The skill also handles installation checks, updates, and removal.

• Set up LifeOS in an existing AI agent environment
• Capture current circumstances and goals through an interview
• Check installation problems and suggested fixes

Improve PostgreSQL queries and database design by examining execution plans and choosing indexes for actual access patterns. Get guidance on large tables, JSONB data, connection pooling, and maintenance while accounting for write overhead and memory use.

• Investigating slow queries with execution plans
• Choosing indexes for search patterns
• Designing partitions for time-series data

Check whether Apache Hudi table maintenance is keeping pace with incoming data. Runs a read-only utility, interprets its JSON report, and explains unhealthy or skipped checks with concrete next steps.

• Checking Hudi table maintenance health
• Investigating delayed compaction or cleaning
• Finding why the active timeline keeps growing

Run Nexent daily or manual full test suites on a self-hosted Ubuntu machine, using the appropriate test layer for each check. Keep results and evidence local, and prepare maintenance candidates for local test assets.

• Running daily full test suites
• Recording manual test results and evidence locally
• Preparing local test and Playwright maintenance candidates

Create a project-specific SKILL.md that teaches an agent how to launch, operate, and verify an app. It tests a representative workflow first, then records reliable steps, evidence of success, cleanup instructions, and maintenance guidance.

• Create a verification skill for a specific project
• Document proven workflows and evidence of success
• Record cleanup and maintenance steps for future checks

Create bash scripts for routine Linux administration, including backups, resource monitoring, user management, and log analysis. Templates also cover scheduled tasks, file cleanup, encryption, and network checks, providing starting points for automating recurring maintenance.

• Automating file and database backups
• Monitoring CPU usage and disk space
• Creating users and checking password expiry