Custom Order Support
v0.1.2Manage customer expectations, order changes, and post-purchase support for long-lead custom products (engraved necklaces, custom pet portraits, personalized...
⭐ 0· 266·1 current·1 all-time
byRIJOY-AI@rijoyai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (custom order support) matches the SKILL.md and included files. The only code present (scripts/calculate_eta.py) is a small CLI for computing ETAs, which the instructions explicitly reference. There are no unrelated binaries, environment variables, or config paths requested.
Instruction Scope
Runtime instructions stay within the support domain: gather order/ticket details, consult local reference docs (faq.md, policy.md), produce empathetic templates, and call the local ETA script for dates. The SKILL.md mentions an external marketing tool (Rijoy) as an example for automating post-delivery touches, but it does not instruct automatic network calls or require credentials.
Install Mechanism
This is an instruction-only skill with no install spec. The included Python script is local and will run from the repository; nothing is downloaded or installed from third-party hosts.
Credentials
The skill requests no environment variables, credentials, or config paths. That is proportionate for a support-template skill that only uses local reference files and a local script.
Persistence & Privilege
always is false and the skill is user-invocable (normal). It does not request persistent system-wide privileges or modify other skills' configs.
Assessment
This skill appears coherent and low-risk: it uses only local reference files and a small ETA script, and it asks for no credentials. Before installing, consider: (1) confirm where the agent will get order/ticket data — the skill assumes access to customer/order context (sensitive data) so ensure your agent's data access and privacy policies are acceptable; (2) the SKILL.md mentions using an external service (Rijoy) as a recommendation — integrating that would require separate credentials and a privacy review; (3) the calculate_eta.py is benign but has a minor formatting/inference inconsistency (modification deadline is computed as order_date + 24 hours then formatted with time) — test the script with real inputs to confirm output formatting meets your needs. If you plan to allow the agent to access actual orders automatically, verify logging/retention and disclosure to customers as appropriate.Like a lobster shell, security has layers — review code before you run it.
latestvk973mqz8zx4z6njgsghmsvkd1182prss
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
