FAQ Support
v1.0.0Turn customer-support and pre-sales conversations into product-detail-page (PDP) copy—especially FAQs and objection-handling blocks—by mining recent tickets/...
⭐ 0· 71·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
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (turn support tickets into PDP FAQ/copy) match the SKILL.md, references, and evals. The skill asks for product scope, channels, and proof assets — all reasonable for its stated task. There are no unrelated credential or binary requests.
Instruction Scope
Runtime instructions confine the agent to: extracting themes from user-provided logs, producing a 4–5 row table, giving an ingestion sketch, and recommending placement and guardrails. It explicitly calls out PII de-identification and asks clarifying questions when data is missing. There are no instructions to read system files, environment variables, or to send data to external endpoints.
Install Mechanism
No install spec and no code files that will be written/executed. The skill is instruction-only, so nothing is downloaded or installed during enablement.
Credentials
The skill declares no required environment variables, credentials, or config paths. All data inputs are expected to be user-supplied ticket/chat exports or proof assets — proportional to the stated purpose.
Persistence & Privilege
always:false and user-invocable default behaviors are set. The skill does not request permanent system presence or modify other skills/configurations. Autonomous invocation is allowed (platform default) but not combined with other elevated privileges here.
Assessment
This skill is internally consistent and low-risk, but follow these practical precautions before using it: (1) only upload de-identified support logs — remove names, emails, order numbers and other PII first; (2) provide proofs (manuals, certifications, warranty docs) before the skill drafts any substantive claims and have legal/quality review for regulated categories; (3) limit scope to pre-purchase questions unless you explicitly want post-purchase policy copy; (4) test on small samples to validate the theme-extraction and avoid publishing inaccurate assertions. If you need the skill to operate on live ticket exports automatically, verify the ingestion pipeline enforces de-identification and access controls.Like a lobster shell, security has layers — review code before you run it.
latestvk97ae44ftry68mjfntzqqbrp4s83h861
License
MIT-0
Free to use, modify, and redistribute. No attribution required.