skills.rest
Qredence
QredenceOFFICIAL
Explore all skills by this author →
Website𝕏@agenticfleetGitHub

runtime-cleanup-worker

Consolidate runtime and API surfaces around fleet_rlm while preserving public contracts.

51|6|Updated Feb 7, 2026
Search Tags:#architecture#validation#quality#refactor#handoff#contracts#runtime-cleanup
One-click install
npx skills add https://github.com/Qredence/fleet-rlm --skill runtime-cleanup-worker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: runtime-cleanup-worker
Source: https://github.com/Qredence/fleet-rlm/tree/main/.factory/skills/runtime-cleanup-worker
Command: npx skills add https://github.com/Qredence/fleet-rlm --skill runtime-cleanup-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simplifies internal fleet_rlm internals while preserving validated public contracts, reducing maintenance burden and risk from sprawling, layered architectures.

Core Features & Use Cases

  • Eliminate dead or low-value compatibility layers to streamline runtime and API surfaces.
  • Tighten ownership boundaries across api, runtime, integrations, and cli to improve accountability.
  • Reduce runtime, CLI, and Daytona indirection introduced by refactors to improve stability.
  • Preserve contracts and provide explicit handoffs during cleanup to maintain trust and traceability.

Quick Start

Execute the smallest safe consolidation batch and document the handoff evidence.

Frequently Asked Questions about runtime-cleanup-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely consolidate runtime and API surfaces during a refactor?▼

Runtime cleanup consolidation streamlines internal architecture by eliminating dead compatibility layers while preserving validated public contracts. You execute the smallest safe batch and document handoff evidence to maintain traceability and reduce maintenance risk.

What is the best way to tighten ownership boundaries across API, runtime, and CLI components?▼

Tightening ownership boundaries improves accountability across api, runtime, integrations, and cli. You consolidate sprawling layers and reduce CLI indirection introduced by previous refactors to improve overall system stability and mission-wide maintenance.

How do I eliminate dead compatibility layers without breaking existing API contracts?▼

Eliminate dead compatibility layers by verifying base feature runs and performing focused validators before removal. Preserve validated public contracts by collecting handoff evidence during the cleanup process to maintain trust and traceability.

When should I perform a runtime cleanup on sprawling, layered architectures?▼

Perform runtime cleanup when maintenance burden and risk increase from sprawling, layered architectures. Apply it to mission-wide maintenance tasks and refactor cleanups where reducing CLI, runtime, and integrations indirection improves stability.

Does runtime cleanup work for mission-wide maintenance tasks across integrations and CLI?▼

Yes, runtime cleanup applies to mission-wide maintenance tasks across api, runtime, integrations, and cli. It specifies steps like verifying base feature runs and performing format checks to safely tighten ownership boundaries.

Related Skills

Explore More Software Engineering Skills→
ArvorCoArvorCo
96

plan

Convert feature specifications into implementation plans with TDD and governance requirements.

Community
Advanced
fyrsmithlabsfyrsmithlabs

consensus-review

Orchestrate parallel multi-agent code reviews with adaptive budgets and consolidated reports.

Official
Advanced
pkuppenspkuppens

v-model-design-verification

Verify APIs, data schemas, and module contracts against design specifications.

Community
Advanced
OutlineDrivenOutlineDriven
5

cleanup-codebase

Remove dead fields, redundant wrappers, and stale configurations from code.

Official
Intermediate