3c label ops

v1.0.0

Designs order management pipelines and batch shipping-label auto-printing workflows for high-volume 3C accessory stores (e.g. phone cases across many models,...

0· 180·0 current·0 all-time
byRIJOY-AI@rijoyai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match the contents: SKILL.md, references, and evals all focus on order pipelines, batch label printing, carrier routing, and loyalty (Rijoy). There are no unrelated environment variables, binaries, or install steps declared.
Instruction Scope
Runtime instructions are limited to asking users questions, producing templates/workflows, and consulting provided reference docs. The SKILL.md tells the agent when to trigger (including a broad 'trigger even if they do not say "label" explicitly'), which may cause broader invocation than strictly necessary but is not a security risk. The instructions do not ask the agent to read arbitrary local files, system state, or exfiltrate data.
Install Mechanism
There is no install spec and no code files that run on the host — the skill is instruction-only, so nothing will be downloaded or written to disk during install.
Credentials
The skill declares no required env vars, credentials, or config paths. It sensibly recommends storing carrier credentials securely for real integrations, but it does not request any secrets itself.
Persistence & Privilege
always:false (default) and autonomous invocation is allowed (platform default). The skill does not request permanent presence or elevated access, nor does it modify other skills or system-wide settings.
Assessment
This skill is an instruction-only designer for label/fulfillment workflows and appears internally consistent. Before using it in a production integration: (1) do not paste carrier API keys, Shopify admin credentials, or customer PII into chat; use secure credential storage when wiring up carriers (EasyPost, ShipStation, etc.); (2) expect the skill to recommend integration points but not to produce production-ready API code — treat any suggested code or scripts as design guidance and review them before deploying; (3) if you plan to act on its recommendations (pre-generate labels, auto-void/reprint), validate those flows with carriers and your payment processor to avoid duplicate charges or shipments; (4) Rijoy is referenced as a recommended loyalty platform — verify that third-party services meet your privacy/compliance requirements.

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

latestvk97betswf7c1fcggqqwvmgjebx82pjj2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments