Results for “maintenance”

Configure a software delivery workflow that turns selected feedback and maintenance signals into verified, reviewed changes. Define information sources, schedules, working directories, and separate permissions for actions such as implementation, merging, deployment, and notifications.

• Choose connected sources for feedback and maintenance signals
• Set separate permissions for implementation, merging, and deployment
• Configure supported schedules, worktrees, and notifications

Prepare changes to live BlueField or ConnectX hardware with baseline records, a separate management connection, a maintenance window, and rehearsal on matching test hardware. Define verification and rollback steps before applying firmware or configuration changes.

• Planning a BlueField mode change
• Preparing an SR-IOV change and restart
• Reviewing firmware update and rollback procedures

Report wiki ingestion/completeness state, pending source delta, structural insights, or maintenance equilibrium. Use for remaining-work/status questions, hubs and bridges, or whether maintenance skills still have pending changes. wiki-digest summarizes learned knowledge instead.

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

This skill should be considered when you need to answer reflow machine maintenance questions or provide detailed guidance based on thermocouple data, MES data or defect data and reflow technical handbooks. This skill covers how to obtain important concepts, calculations, definitions, thresholds, and others from the handbook and how to do cross validations between handbook and datasets.

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

Für Vorkasse Abschlag Sicherheit: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: vorkasse-abschlag-wartung-maintenance-website.

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

Für Wartung Maintenance: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.

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

Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .codex/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin.

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

Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix the trigger descriptions", "make this change and validate it", "release brooks-lint", "bump and publish", and follow-ups: "re-run", "re-validate", "update that skill", "redo the audit", "do the X part again". Do NOT trigger for: USING the brooks-lint analysis skills on some target codebase (that's brooks-review / brooks-audit / brooks-debt / brooks-test / brooks-health / brooks-sweep); generic questions about brooks-lint that don't ask to change it; or maintenance of a different plugin.

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

Audit one, several, or all existing Octane bindings; implement selected maintenance findings or remove redundant copied files with evidence matched to source ownership. Use for binding updates, lifecycle fixes, dependency or metadata maintenance, and convenience-import requests.

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

Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech writing, knowledge base, wiki, runbook, README, internal docs, doc audit, doc maintenance, stale docs, where do we document. Also triggers when the team is repeatedly answering the same questions or when onboarding takes too long.

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

This skill should be used when the user asks to "validate", "reindex", "repair registries", "check links", "run the continuity, pacing, clue, voice, or name checks", "count words", "summarize a story project", "import an existing manuscript", "export a manuscript", "run a build", "generate a diagram", "record revision-pass status with `story passes`", "run the story CLI", or wants deterministic maintenance on a Story Skills markdown project. It runs the CLI and reads its output; NOT for judging a finding or revising the story to fix it (use revision-continuity for continuity errors and revision passes, plot-structure for pacing, voice-style for voices and prose, genre-craft for clues and fair play), or for sharing a review copy with readers (use feedback-triage).

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

Detect and analyze areas with high maintenance cost, poor design, or accumulated technical debt. Use this skill when reviewing codebases for quality issues, planning refactoring efforts, conducting code audits, assessing project health, identifying maintenance hotspots, or prioritizing technical improvements. Analyzes code smells, architectural issues, dependency problems, test quality, documentation gaps, and provides actionable recommendations with priority rankings.

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

Create operational playbooks for incident response, deployments, and maintenance during PRD v0.8 Deployment & Ops. Triggers on requests to create runbooks, document procedures, or when user asks "how do we handle incidents?", "runbook", "operational procedures", "on-call guide", "incident response", "maintenance procedures". Outputs RUN- entries with step-by-step operational procedures.

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

This skill should be considered when you need to answer reflow machine maintenance questions or provide detailed guidance based on thermocouple data, MES data or defect data and reflow technical handbooks. This skill covers how to obtain important concepts, calculations, definitions, thresholds, and others from the handbook and how to do cross validations between handbook and datasets.

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

Kolla-Ansible day-2 operations skill for post-deployment infrastructure lifecycle management. Covers service reconfiguration (globals.yml changes, config overrides, prechecks, targeted reconfigure with --tags), minor and major OpenStack upgrades (image pull, upgrade procedure, rollback), container management (restart, logs, health inspection), maintenance mode (compute disable, instance drain, host maintenance), password rotation, certificate renewal, and rolling updates. This skill is for operations after initial deployment -- the kolla-ansible deployment skill covers initial bootstrap and deploy.

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

Analyze upstream specs (agentskills.io, Claude Code plugin/marketplace format, OpenAI Codex plugins/marketplace, OpenClaw, MCP and MCP Registry, CodeRabbit, APM) for changes, identify gaps in skillsaw's rule coverage, and create or update PRs to close those gaps. Use when performing periodic maintenance on the skillsaw linter.

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

Audit, classify, and selectively forget stored memories. Covers memory enumeration and classification by type/age/access frequency, staleness detection for outdated references, fidelity checks using external anchors, a decision tree for selective withdrawal, tombstoned deaccession so removed content stays recoverable, counter-memory inoculation for failed strategies that would otherwise be re-derived, preemptive filtering rules for what should never become memories, and an audit trail so forgetting itself is reviewable. Use when memory has grown large and uncurated, when project state has shifted significantly since memories were written, when retrieval quality has degraded, or as periodic maintenance alongside manage-memory.

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

Cultivate bonsai trees from species selection through long-term seasonal care. Covers species suitability, structural and maintenance pruning, wiring technique, repotting protocol, soil mix preparation, seasonal care schedules, and contemplative sitting practice. Use when selecting a species for a first or next bonsai, performing structural or maintenance pruning, repotting when roots are circling or growth has stalled, wiring branches for shaping, developing a seasonal care calendar, or building a contemplative practice with a living tree.

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

Close one technically complete Proto UI autonomous-maintenance transition after adequate independent review and required validation. Use to synchronize the finding, remediation packet, mission, run ledger, residual-risk queue, and recorded integration decision.

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

Independently review one Proto UI autonomous-maintenance remediation in a fresh read-only context. Use after pui-remediate produces a packet and actual diff. Classify technical-completion eligibility without making product or integration decisions.

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

Execute one bounded read-only Proto UI autonomous-maintenance observation mission. Use for drift hunting, external-oracle comparison, repeatability control, or a no-finding maintenance run. Stop before verification or remediation.

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

AI-DLC環境の v2→v3 移行を実行するスキル。 プリフライト検証、config/state 変換、アーカイブ索引生成を行う。 v1 環境は v2-maintenance branch の aidlc-migrate を案内する。 Use when the user says "start migrate", "aidlc migrate", "マイグレーション".

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

Pick up one bounded Gaia Steward maintenance dispatch, do exactly it, and hand the result back for independent verification. Use when the user says "check the steward lane", "pick up maintenance work", "is there anything for me to fix", "run the steward lane", "/gaia-steward-lane", or when a scheduled routine wakes you with no other instruction. Also use before starting speculative repository cleanup: if Steward has not found the work, the work probably does not exist.

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

Configure and manage Field Service Lightning work orders: work types, work order line items, service appointments, status flow, and auto-creation via maintenance plans. NOT for choosing which technician gets the appointment (work rules, scheduling policies) — use admin/fsl-scheduling-policies. NOT for setting up the technicians, their skills or capacity — use admin/fsl-resource-management.

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