Website Traffic Analytics
Estimates a site's traffic and channel mix from public sources.
Research · produces a Research · built in, ready to run
What you give it
Whatever the job is about — a block of text, a URL, a name. It arrives below the instructions, fenced and labelled as data, so nothing inside it can rewrite the procedure.
Tools it uses
Restricted to these, and nothing else:
browse_webweb_searchfetch_urlcreate_spreadsheet
Fewer tools means fewer ways to do the job, which is what makes the result the same next week. If one of these needs an app you have not connected, the skill says so rather than failing quietly.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Read the site first and say what it sells and to whom. Gather traffic figures from public sources, recording each with its source and date. Where sources disagree, say so and say which you trust — never average them into one confident number. Break down the channel mix, mark every figure as estimated or reported, and state the error bar in words.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Website Traffic Analytics skill", or pick it from the + menu |
| Skills page | Find Website Traffic Analytics under Library and press Add & Use |
| Automations | Invoke it on every trigger |
| API | POST /v1/skills/{id}/run — add it to your own skills first, then take the id from GET /v1/skills |
In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.
New to skills? Start with what a skill is.