rumo-linux-inspect
openbooklet.com/s/rumo-linux-inspectopenbooklet.com/s/[email protected]GET /api/v1/skills/rumo-linux-inspectUse when explicitly asked for a read-only Linux inspection, either a hardware inventory that saves raw evidence and a concise Chinese device-configuration TXT, or a memory and performance inspection for high memory, OOM, garbage-collection, slow-log, process, or port symptoms. Never change the target, install packages, or operate services.
Hand a bounded piece of work to another agent where the user can see it, end your turn, and accept the result on evidence.
Pick one workflow per diagram, then read its reference in full before producing files.
Use before implementing a request whose goal, scope, acceptance criteria, or a risky decision is still unclear, such as a vague feature ask, an open-ended change, or a task touching data, permissions, deletion, or external publication without a stated target. Group the questions that can be answered now, with recommendations; follow up only for newly exposed consequential decisions, or explore deeper when the user asks. Do not use when the request is already specific, for pure questions, or for reviews.
Generate a plain-language Chinese daily report from the current completed conversation and append it to the configured date-based TXT file when the user asks to æ´çæ¥æ¥ or generate a daily report.
Generate and save one raster image through a user-configured OpenAI-compatible image endpoint. Use only when the user explicitly selects this configured service; do not use for diagrams or screenshots.
Auto-indexed from rumoii/rumo-engineering-skills
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.