Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Alibabacloud Hologres Instance Manage

v0.0.2

Alibaba Cloud Hologres Instance Management Skill. Use for listing and querying Hologres instances. Triggers: "hologres", "list instances", "get instance deta...

0· 115·0 current·0 all-time
byalibabacloud-skills-team@sdk-team

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for sdk-team/alibabacloud-hologres-instance-manage.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Alibabacloud Hologres Instance Manage" (sdk-team/alibabacloud-hologres-instance-manage) from ClawHub.
Skill page: https://clawhub.ai/sdk-team/alibabacloud-hologres-instance-manage
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install sdk-team/alibabacloud-hologres-instance-manage

ClawHub CLI

Package manager switcher

npx clawhub@latest install alibabacloud-hologres-instance-manage
Security Scan
Capability signals
CryptoRequires walletCan make purchasesRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
The skill's declared requirements list no required binaries or credentials, but the runtime SKILL.md explicitly requires the Aliyun CLI (aliyun >= 3.3.3) and a valid Alibaba Cloud credential profile. The metadata omission (not declaring 'aliyun' as a required binary) is an inconsistency that can mislead users about what the skill needs.
Instruction Scope
The SKILL.md instructions are narrowly scoped to listing and fetching Hologres instances using the aliyun CLI and the hologram API. They include appropriate parameter confirmation, permission-check steps, and explicit user-agent/timeout requirements. However, the bundled reference docs contain example commands that demonstrate setting AK/SK directly (aliyun configure set --access-key-id / --access-key-secret), which contradicts the SKILL.md's 'NEVER ask/print AK/SK' rule and could confuse less-experienced users.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the SKILL.md recommends installing/updating the Aliyun CLI via curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash and enabling plugin auto-install. The install URL is Alibaba's CDN (aliyuncli.alicdn.com) which is the vendor's distribution point — less risky than a personal server, but 'curl | bash' remains a higher-risk pattern and modifies the system (installs CLI and updates plugins).
Credentials
The skill declares no required environment variables or primary credential, and the SKILL.md states it uses the Alibaba Cloud default credential chain and will not handle AK/SK values directly. That is proportionate for a read-only listing skill. However, the included CLI installation/reference docs show environment-variable and non-interactive credential examples (ALIBABA_CLOUD_ACCESS_KEY_ID, ALIBABA_CLOUD_ACCESS_KEY_SECRET and direct aliyun configure set with keys). This discrepancy could lead to accidental exposure if users follow the reference examples without care.
Persistence & Privilege
The skill is not forced-always, and does not request elevated platform privileges. It does require the CLI to be present and asks to enable auto-plugin-install and run 'aliyun plugin update' (which modifies local CLI state), but it does not request persistent platform-level privileges in the registry metadata.
What to consider before installing
This skill appears to do only Hologres listing and instance-detail queries, but review these before installing: - Metadata omission: the registry did not declare 'aliyun' as a required binary even though SKILL.md requires the Aliyun CLI (>=3.3.3). Expect to install the CLI before use. - Installation caution: the author recommends running curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash and enabling automatic plugin installation; while the URL points to Alibaba's CDN, 'curl | bash' executes remote code on your machine — only run it if you trust the source and understand the change. - Credential handling: the skill says it will not read or ask for AK/SK and relies on the default credential chain, which is good. But several reference docs include direct examples showing 'aliyun configure set --access-key-id/secret' and environment-variable usage. Do not paste secrets into chat, and avoid embedding permanent keys in shared files. Prefer temporary STS tokens or IAM/RAM roles and least-privilege policies as recommended in references/ram-policies.md. - Permissions: the skill requires hologram:ListInstances and hologram:GetInstance permissions — verify and grant least-privilege scoped policies rather than broad wildcards when possible. - Ask the publisher to correct the registry metadata to list the Aliyun CLI as a required binary and to clarify/remove contradictory examples that instruct storing or printing long-term keys. If you decide to proceed: install the Aliyun CLI from the official vendor site, verify the installer checksum from an official source if available, verify your credentials via 'aliyun configure list' locally, and grant only the RAM permissions this skill needs.

Like a lobster shell, security has layers — review code before you run it.

latestvk974j0eq3wp6q72qawg35tnmqs85eqgx
115downloads
0stars
2versions
Updated 3h ago
v0.0.2
MIT-0

Hologres Instance Management

Skill for managing Alibaba Cloud Hologres instances - list all instances and get instance details.

Architecture

User → Aliyun CLI → Hologres API (hologram) → Instance List / Instance Details

Installation

Pre-check: Aliyun CLI >= 3.3.3 required

Run aliyun version to verify >= 3.3.3. If not installed or version too low, run curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash to update, or see references/cli-installation-guide.md for installation instructions.

Pre-check: Aliyun CLI plugin update required

[MUST] run aliyun configure set --auto-plugin-install true to enable automatic plugin installation. [MUST] run aliyun plugin update to ensure that any existing plugins are always up-to-date.

curl -fsSL --connect-timeout 4 --max-time 120 https://aliyuncli.alicdn.com/setup.sh | bash
aliyun version

[MUST] CLI User-Agent — Every aliyun CLI command invocation must include: --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage

Authentication

This skill relies on the Alibaba Cloud default credential chain. It never reads, prints, or explicitly handles AK/SK values.

Security Rules:

  • NEVER read, echo, or print AK/SK values
  • NEVER ask the user to input AK/SK directly
  • NEVER use aliyun configure set with literal credential values
  • ONLY use aliyun configure list to verify credential status
aliyun configure list

Check the output for a valid profile (AK, STS, EcsRamRole, or RamRoleArn).

If no valid profile exists, STOP here. The user must configure credentials outside of this session and return after aliyun configure list shows a valid profile.

RAM Policy

The following RAM permissions are required for this skill:

ProductRAM ActionResource ScopeDescription
Hologramhologram:ListInstancesacs:hologram:{#regionId}:{#accountId}:instance/*List all Hologres instances
Hologramhologram:GetInstanceacs:hologram:{#regionId}:{#accountId}:instance/{#InstanceId}Get instance details

See references/ram-policies.md for the complete RAM policy document.

[MUST] Permission Failure Handling: When any command or API call fails due to permission errors at any point during execution, follow this process:

  1. Read references/ram-policies.md to get the full list of permissions required by this SKILL
  2. Use ram-permission-diagnose skill to guide the user through requesting the necessary permissions
  3. Pause and wait until the user confirms that the required permissions have been granted

Parameter Confirmation

IMPORTANT: Parameter Confirmation — Before executing any command or API call, ALL user-customizable parameters (e.g., RegionId, instance names, resource group IDs, tags, etc.) MUST be confirmed with the user. Do NOT assume or use default values without explicit user approval.

Parameter NameRequired/OptionalDescriptionDefault Value
RegionIdOptionalRegion where instances are locatedUser's default region
InstanceIdRequired (for GetInstance)The ID of the Hologres instanceNone
resourceGroupIdOptionalFilter by resource group IDNone
tagOptionalFilter by tags (key-value pairs)None
cmsInstanceTypeOptionalCloud Monitor instance type (standard/follower/mc-acceleration/warehouse/high-memory/serverless)None

Core Workflow

Task 1: List All Hologres Instances

Query all Hologres instances in the specified region.

# List all instances
aliyun hologram POST /api/v1/instances \
  --header "Content-Type=application/json" --body "{}" \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage

# List instances with resource group filter
aliyun hologram POST /api/v1/instances \
  --header "Content-Type=application/json" \
  --body '{"resourceGroupId":"rg-acfmvscak73zmby"}' \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage

# List instances with tag filter
aliyun hologram POST /api/v1/instances \
  --header "Content-Type=application/json" \
  --body '{"tag":[{"key":"env","value":"production"}]}' \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage

# List instances by CMS instance type
aliyun hologram POST /api/v1/instances \
  --header "Content-Type=application/json" \
  --body '{"cmsInstanceType":"standard"}' \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage

Response Fields:

  • InstanceId: Instance ID
  • InstanceName: Instance name
  • InstanceStatus: Status (Creating/Running/Suspended/Allocating)
  • InstanceType: Type (Warehouse/Follower/Standard/Serverless/Shared)
  • InstanceChargeType: Payment type (PostPaid/PrePaid)
  • RegionId: Region ID
  • Endpoints: Network endpoints list

Task 2: Get Instance Details

Get detailed information about a specific Hologres instance.

# Get instance details by ID
aliyun hologram GET /api/v1/instances/{instanceId} \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage

# Example with actual instance ID
aliyun hologram GET /api/v1/instances/hgprecn-cn-i7m2v08uu00a \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage

Response Fields:

  • InstanceId: Instance ID
  • InstanceName: Instance name (2-64 characters)
  • InstanceStatus: Status (Creating/Running/Suspended/Allocating)
  • InstanceType: Type (Warehouse/Follower/Standard/Serverless/Shared)
  • InstanceChargeType: Payment type (PostPaid/PrePaid)
  • Cpu: CPU cores
  • Memory: Memory in GB
  • Disk: Standard storage size in GB
  • ColdStorage: Cold storage capacity in GB
  • Version: Instance version
  • Endpoints: Network endpoints with VPC/Internet/Intranet details
  • AutoRenewal: Whether auto-renewal is enabled
  • EnableHiveAccess: Whether data lake acceleration is enabled
  • EnableServerless: Whether serverless computing is enabled
  • EnableSSL: Whether SSL is enabled
  • StorageType: Storage type (redundant/local)

Success Verification Method

See references/verification-method.md for detailed verification steps.

Quick Verification

# Verify ListInstances
aliyun hologram POST /api/v1/instances \
  --header "Content-Type=application/json" --body "{}" \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage | jq '.InstanceList'

# Verify GetInstance
aliyun hologram GET /api/v1/instances/{your-instance-id} \
  --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manage | jq '.Instance.InstanceStatus'

Success Indicators:

  • HTTP status code 200
  • Success field is true
  • InstanceList or Instance field contains valid data

Cleanup

This skill performs read-only operations. No cleanup is required.

Command Tables

See references/related-commands.md for the complete CLI commands reference.

ActionCLI CommandDescription
List Instancesaliyun hologram POST /api/v1/instances --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manageGet list of all Hologres instances
Get Instancealiyun hologram GET /api/v1/instances/{instanceId} --read-timeout 4 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-hologres-instance-manageGet details of a specific instance

Best Practices

  1. Always verify credentials before executing commands using aliyun configure list
  2. Use filters (resourceGroupId, tags) to narrow down results when listing many instances
  3. Check instance status before performing operations - ensure instance is in Running state
  4. Use appropriate network endpoints - choose VPCSingleTunnel for internal access, Internet for external access
  5. Monitor instance expiration - check ExpirationTime for PrePaid instances to avoid service interruption
  6. Enable SSL for production environments to ensure secure connections

Reference Links

ReferenceDescription
references/cli-installation-guide.mdAliyun CLI installation guide
references/ram-policies.mdRequired RAM permissions
references/related-commands.mdComplete CLI commands reference
references/verification-method.mdSuccess verification steps
Hologres API DocumentationOfficial API documentation

Error Handling

HTTP StatusError CodeError MessageResolution
403NoPermissionRAM user permission is insufficientGrant AliyunHologresReadOnlyAccess permission
400InvalidParameterInvalid parameter valueCheck parameter format and constraints
404InstanceNotFoundInstance does not existVerify instance ID is correct

For more error codes, see Hologres Error Center.

Comments

Loading comments...