Ask how before acting
The assistant can search Wallboard’s own docs. Ask how content scheduling works before you ask it to schedule.
Skills guide
A skill, in this guide, is a prompt your team saves and runs again. The first time you ask an assistant to find every lobby screen that went offline this week, you check its work line by line. A good skill means the fifth run gives the same kind of answer as the first, touches only the screens it should and stops when it hits a limit your admin set, so the people who reuse it never have to guess what it will do.
How it works
Take a prompt you have already checked by hand, such as list content in the Lobby folder.
Say which folder, device group or tag it covers. Scope written into the prompt is scope the assistant can query.
Ask for a list first. Change nothing until the list looks right and someone says go ahead.
Store the prompt where your team can find it, and note which Wallboard user it should run as.
The assistant can search Wallboard’s own docs. Ask how content scheduling works before you ask it to schedule.
A reporting skill run by a user with read-only MCP access can look at everything and change nothing.
Delete is off by default. Leave it off for shared skills, and turn it on only for the person who owns a cleanup job.
The API has no batch create, so the assistant makes one call per item. Big jobs take longer and use more AI tokens.
A blocked action returns a reason, such as delete not allowed. Fix the permission or the prompt, not the wording.
Permission changes can take up to five minutes to reach an assistant. Wait before you rerun a refused skill.
Pick one job, like the Monday offline check. We’ll write it as a skill with you in the demo, and our support team can help you choose which user it should run as.