Resource

resource

Browse SmartCMP resources, inspect cloud host details, list current-user executable operations, and execute enabled no-parameter resource operations.

Purpose

Provide one skill for resource browsing, per-host property inspection, and day2 resource operations.

• Query /nodes/search for all-resource or virtual-machine lists
• Show each listed item's current status so users can decide whether to start or stop it
• Call PATCH /nodes/{id}/view for one cloud host detail snapshot until the CMP view API bug is fixed
• Present cloud-host detail in a compact CMP-style layout instead of dumping raw metadata
• Use GET /nodes/{category}/{id}/resource-actions to list enabled no-parameter operations executable by the current SmartCMP user
• Use POST /nodes/resource-operations for immediate no-parameter resource operations

Scope Rules

• Use smartcmp_list_all_resource when the user asks for 云资源 or 云主机 lists.
• Use smartcmp_resource_detail when the user asks for one cloud host detail or property analysis by exact visible resource name or resource ID.
• If the user provides an exact visible cloud-host name for detail, call smartcmp_resource_detail with resource_name directly. Do not call smartcmp_list_all_resource first just to resolve or display the name.
• Use smartcmp_list_resource_operations when the user asks what operations the current user can execute on a resource.
• Use smartcmp_operate_resource when the user wants to execute an enabled no-parameter operation on an existing cloud resource.
• Treat "我的" and "所有" the same for now because the provided UI URLs do not expose a separate owner-only filter; rely on SmartCMP access control and the current user's visible scope.

Operation Workflow

An operation intent means the user wants to change an existing resource state, for example stop 1 vm-a, restart vm-a, execute create_snapshot on this virtual machine, stop the second VM, or take a snapshot.

When operation intent is present, a resource lookup is only a target-resolution step. Do not stop at the smartcmp_list_all_resource visible list output, and do not answer only with Found N .... Use the returned metadata to continue to operation resolution, confirmation, or a clarification question.

1. Resolve the target resource.

• If the user references a recent table # item, such as 1, 第 1 台, or the first one, use the matching item from the latest smartcmp_list_all_resource metadata.
• If the user provides action + index + name, such as stop 1 vm-a, treat the index as the selection and the name as a safety check. If they match, use that resource UUID. If they conflict, ask the user to clarify.
• If the user provides only a display name, call smartcmp_list_all_resource with query_value, then map an exact unique match to its UUID. If multiple resources remain plausible, ask the user to choose by table #.
• Never pass a display name, list index, or natural-language phrase as resource_id to smartcmp_resource_detail or as resource_ids to smartcmp_operate_resource; use resource_name for name-based detail inspection and concrete UUIDs for operations.

1. Resolve the operation.

• Use start, stop, 开机, and 关机 aliases directly.
• Use exact operation IDs such as restart, refresh, or create_snapshot directly.
• If the user gives a natural-language operation name, such as take a snapshot, first call smartcmp_list_resource_operations for the resolved resource and match only against the current user's executable no-parameter operations. If there is no unambiguous match, show the executable operation IDs and ask which one to run.

1. Confirm before submission.

• Once both the resource UUID and operation ID are known, ask one concise confirmation using the resource name and operation ID/name, for example Confirm stop on vm-a?
• Stop after asking for confirmation. Do not submit until the user explicitly confirms.

1. Submit after confirmation.

• After explicit confirmation, call smartcmp_operate_resource with concrete resource UUIDs or detail URLs and the operation ID.
• The latest explicit operation command supersedes older unfinished operation intent. For example, if the previous turn was about snapshots but the latest user message says stop 1 vm-a, handle stop.

Critical Rules

• Do not switch to resource-compliance analysis unless the user explicitly asks for compliance, supportability, lifecycle, or security risk.
• Do not use smartcmp_list_all_resource when the user asks for detail of one exact cloud-host name; call smartcmp_resource_detail with resource_name and let the tool resolve the unique match internally.
• Do not use the list endpoint when the user already provided a concrete resource ID for host detail analysis.
• smartcmp_resource_detail uses PATCH /nodes/{id}/view to fetch the host evidence view until the CMP view API bug is fixed. Do not use older resource/detail APIs as fallback in this interactive detail skill.
• Keep list-mode output as a standard Markdown table. Include a # column for stable item references, a resource name column, and status; do not print object links in visible table cells.
• For host detail, present only grouped key facts. Do not dump raw properties, top-level keys, source endpoints, or every key/value returned by the API.
• smartcmp_list_resource_operations must only use GET /nodes/{category}/{id}/resource-actions with the current user context. Do not use /resource-types/.../support-actions, /resource-types/.../resource-actions, /nodes/build-in-actions, or other definition-level endpoints as executable-operation fallback.
• Only show enabled no-parameter operations as executable choices. Operations that are disabled, web-only, have inputsForm, or require non-empty parameters are outside this tool's execution scope.
• NEVER claim a resource operation was submitted or succeeded without actually calling smartcmp_operate_resource. You must call the tool and receive a real response before telling the user the operation is done.
• Before calling the operation tool, confirm with the user: show the target resource name + operation ID/name, ask Confirm this operation?, and STOP. Only call the tool after user confirms.
• After a resource operation succeeds, respond with only the action, resource ID(s), submitted status, message, and verification hint. Do not print raw request payloads or raw response details.
• Resolve every target to a concrete SmartCMP resource UUID before calling smartcmp_operate_resource.
• When the user only provides a resource name for a state-changing operation, use smartcmp_list_all_resource to find the resource and map the chosen item to its id; for detail inspection by name, use smartcmp_resource_detail.resource_name instead.
• Use the visible resource status from the list output to avoid redundant actions. If a resource is already started and the user asks to start it again, explain that no power change is needed.
• Do not guess between multiple resources that share the same display name. Ask the user to pick the correct one.
• Do not use this skill for provisioning new resources. For destructive or delete-like operations, show the exact operation and target and require explicit confirmation before execution.

Preferred Detail Layout

When showing one cloud-host detail, keep the response concise and close to the CMP detail page:

1. One short overview block:

• Name
• Status
• Compute
• IP address

1. Then only the sections that actually have values:

• Basic Information
• Attributes
• Service Information
• Organization Information
• Platform Information
• IP Addresses
• Disks
• Physical Host Information
• Resource Environment

Never show:

• Source endpoint paths
• Raw JSON blobs
• Flattened properties dumps
• “Top Level Keys”
• Repeated IDs or technical fields unless they are part of the compact detail view

Scripts

| Script | Description | |--------|-------------| | scripts/list_all_resource.py | Call the standalone resource list endpoint and emit a Markdown resource table with visible status | | scripts/resource_detail.py | Fetch one cloud host view and emit a compact grouped detail summary | | scripts/list_resource_operations.py | List enabled no-parameter operations executable by the current SmartCMP user for one resource | | scripts/operate_resource.py | Submit SmartCMP no-parameter resource operations for one or more resource IDs |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: CloudChef
• Source: CloudChef/atlasclaw-providers
• License: Apache-2.0
• Homepage: https://atlasclaw.ai/en/

Install and usage instructions live in the source repository linked above.