Training Quiz

v1.0.0

Interactive product knowledge training and quiz system for retail staff. Tests employees on product specs, store policies, sales techniques, and FAQs through...

0· 108·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the implementation: SKILL.md + question templates + a question-generation script that reads a provided knowledge_base.json and emits quizzes. There are no unrelated required binaries, credentials, or config paths.
Instruction Scope
Instructions operate on the agent's knowledge base (products[], policy_entries[], faqs[]) and agent memory for per-employee progress. This is coherent for a training quiz but assumes the agent supplies the KB and staff config; it also records staff_id and progress in memory (personal data) — consider privacy/ACLs for that memory and any manager-reporting flows.
Install Mechanism
No install spec; this is an instruction-only skill with a small helper script included. The Python script is self-contained, reads local JSON, and does not download or execute remote code.
Credentials
The skill requests no environment variables or credentials. It expects access to the agent's knowledge base and memory (reasonable). Ensure the KB does not contain secrets and that the agent is authorized to access the staff records it will read/write.
Persistence & Privilege
always is false and disable-model-invocation is default; the skill stores progress under its own agent-memory namespace (training_progress.<staff_id>) and does not modify other skills or system-wide settings.
Assessment
This skill appears to do exactly what it claims: generate quizzes from your product/policy/FAQ knowledge base and track progress in agent memory. Before installing, confirm (1) the agent will supply the intended KB and staff config (knowledge_base.json) and that no sensitive secrets are stored there, (2) you are comfortable with per-employee progress being stored in agent memory and how manager reports are emitted, and (3) any automated reporting to managers uses approved channels. If you need logs or exported results, verify output destinations and access controls. If you want stricter privacy, require explicit consent before storing staff IDs or reporting performance.

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

latestvk974f9wzxkn9eestdmhehmc2yd83f6t9

License

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

Runtime requirements

🎓 Clawdis

Comments