Shop from Samsung - With your creditcard
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is a high-impact payment skill with guardrails, but its Samsung-facing registry name does not match its broad CreditClaw wallet/card shopping capabilities.
Review this carefully before installing: only proceed if you want a broad CreditClaw payment/shopping skill, not a Samsung-only shopper. Verify the publisher and API base, use strict spend limits and approval mode, restrict merchants/domains, and keep the CREDITCLAW_API_KEY private.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A user could think they are installing a Samsung-specific shopping helper while actually granting a broad online payment/shopping integration.
The public label points to Samsung, while the provided files identify the skill as CreditClaw and document broad wallet/card spending across Amazon, Shopify, SaaS, any online merchant, and x402 payments. For a payment-capable skill, that scope mismatch can mislead users.
Name: Shop from Samsung - With your creditcard; Slug: samsung
Install only if you intend to use CreditClaw broadly, and the publisher should rename or republish the skill with clear CreditClaw branding and full payment scope.
Anyone or any agent with the key can initiate purchase/payment requests within the configured CreditClaw guardrails.
The skill requires a CreditClaw API key used as the delegated identity for wallet/card operations. This is expected for the stated service, but it can authorize financially meaningful actions.
"credentials": ["CREDITCLAW_API_KEY"], "api_base": "https://creditclaw.com/api/v1"
Use a dedicated key, keep spend limits low, prefer ask-for-everything approval, restrict merchants/domains, and never send the key outside creditclaw.com.
Purchases or subscriptions can result in real financial charges if the agent submits checkout requests within configured limits.
The documented checkout flow can create real charges at broad merchant categories, with auto-approval possible inside owner-set allowance. The docs also include confirmation and guardrail steps, so this is purpose-aligned but high impact.
Use this rail for: Any online store ... If the amount is within your auto-approved allowance, it processes immediately
Require explicit user confirmation before checkout, set very small auto-approval thresholds, and use merchant/category allowlists where possible.
If a user manually fetches the remote files later, the instructions could differ from the reviewed package.
The optional local setup fetches skill documentation and metadata from remote URLs. It does not execute code, but users rely on the remote source matching the reviewed artifacts.
curl -s https://creditclaw.com/creditcard/skill.md > ~/.creditclaw/skills/creditcard/SKILL.md
Prefer the reviewed registry artifacts or verify fetched files before use; do not run any additional unreviewed commands from changed remote content.
The agent may contact CreditClaw regularly and may prompt for top-ups when balances are low.
The docs recommend recurring status and balance checks. No background code is provided, but an autonomous agent could treat this as a periodic task.
CreditClaw Heartbeat (suggested: every 30 minutes) Run this routine periodically
Enable heartbeat behavior only if desired, cap its frequency, and require user approval before any top-up request.
Owner dashboard notes can influence the agent's purchasing behavior.
The skill tells the agent to treat a field returned by the authenticated payment API as actionable instructions. That is appropriate for owner spending rules, but it should remain scoped to shopping/payment policy.
`notes` — read and follow these; they are direct instructions from your owner
Keep CreditClaw notes limited to payment and shopping constraints, and do not let returned notes override unrelated user or system instructions.