团建横幅标语生成

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

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.

What this means

A payment could be created with a recipient or amount different from what the user thought they configured.

Why it was flagged

SKILL.md tells users to edit configs/config.json to configure the payee and amount, but the implementation loads configs/config.yaml instead. A user following the documented setup could believe they changed the payment recipient while the code still uses the bundled YAML values.

Skill content
return os.path.join(script_dir, "..", "configs", "config.yaml")
Recommendation

Use one documented configuration file and schema, fail closed if the configured payee is missing, and show the exact recipient and amount for explicit user confirmation before payment.

What this means

The user may be asked to pay for an order that appears to belong to a different service, and the later banner-generation step may not find the order it created.

Why it was flagged

The order code hardcodes an unrelated spring-couplet skill slug and description, contradicting the advertised team-banner service.

Skill content
SLUG = "ai-chunlian" ... "description": "春联生成服务费用"
Recommendation

Align the slug, skill-id, description, and indicator calculation with 'team-banner' before enabling payment.

What this means

The agent or user could be told payment succeeded when no real payment verification occurred, making the paid workflow unreliable.

Why it was flagged

The script prints payment success after loading a local order file, but it does not check for payCredential, paid status, or a provider verification result.

Skill content
order_data = load_order(indicator, order_no) ... print(f"PAY_STATUS: 成功")
Recommendation

Validate the payment credential or provider status before printing success or delivering the service.

What this means

An agent could install or use an unreviewed payment processor to handle a purchase and payment credential.

Why it was flagged

The skill depends on another payment-handling skill and instructs installation if missing, but does not pin a source, version, or permission boundary for that payment component.

Skill content
使用技能 `clawtip` 处理支付并获取支付凭证。若该技能不存在,需先安装。
Recommendation

Declare the payment dependency with a trusted source and version, and require explicit user approval before installing or invoking it.

What this means

The skill can participate in a payment flow and handle a payment credential/proof.

Why it was flagged

Payment processing and credential access are disclosed and are expected for a paid service, but they are sensitive capabilities.

Skill content
capabilities:\n    - "payment.process"\n  permissions:\n    - "network.outbound"\n    - "credential.read"
Recommendation

Only proceed after confirming the payment recipient, amount, and the exact payment helper being used.

What this means

Activity descriptions and payment metadata may remain on the local machine after use.

Why it was flagged

The skill persists order data locally; create_order.py includes the user question, encrypted payment data, pay_to, and amount in that order data.

Skill content
orders_dir = os.path.join(get_orders_dir(), indicator) ... json.dump(order_data, f, ensure_ascii=False, indent=2)
Recommendation

Avoid entering sensitive team details, and provide or document a cleanup path for stored order files.