Volnyn – Website Builder, Domains, Property, Freelancers & Free Games
Open App

Weekly Report

One page from a week of scattered updates: what moved, what is stuck, who unblocks it.

Productivity · produces a Document · 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:

  • read_document
  • read_page
  • create_document

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.

Sort every item in the material into Shipped (only if it is live), In progress (with what it is waiting on), Blocked (with who can unblock it, by name or role), Numbers (each beside last week's value with one clause of reading) and Next week. Then write the three lines at the top: what actually moved, the biggest risk, what the reader is asked for. One line per item, every item traced to the material, no adjectives standing in for facts, under 400 words. Deliver inline, or with create_document when it is long or will be circulated.

How to run it

Where How
Chat "Run my Weekly Report skill", or pick it from the + menu
Skills page Find Weekly Report 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.