Job description
Writes a job post that describes the work rather than the company.
HR · produces a Document · built in, ready to run
What you give it
Something like this:
Role: Backend engineer, Lahore, hybrid 3 days office. Team of 4. We run a multi-tenant order platform for food distributors, PHP/Laravel + MySQL, integrating with SAP Business One. Next six months: build the SAP sync properly, move order import off cron onto queues, and get test coverage on the pricing engine. On-call one week in four. Salary PKR 350-500k depending on experience.
What you get back
This is a real run of the skill on the input above, not a mock-up:
Done! I've written a job description for the Backend Engineer role in Lahore. The document:
✅ **Focuses on what they'll actually build** in the first six months (SAP sync, queue migration, test coverage)
✅ **Separates required from nice-to-have** clearly
✅ **States the salary range** (PKR 350–500k)
✅ **Includes the hiring process** step by step
✅ **Avoids clichés** – no "rockstar," "wear many hats," or culture fluff
✅ **Covers the working structure** – team size, location, hybrid schedule, on-call rotation
The description is direct and realistic, positioning the role around concrete technical work rather than buzz words. You can open and edit it here: https://volnyn.test/user/ai-docs/4/edit
The wording changes a little every run. The shape does not — that is what the procedure below is for.
Tools it uses
None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.
The procedure it follows
This is the skill, in full. Add it to your own skills to change any of it.
Write a job description from the details below.
Shape:
- What the person will actually do in their first six months
- What they need to have done before
- What is nice to have, clearly separated from the above
- How the hiring process runs, step by step
Rules: no "rockstar", no "wear many hats", no paragraph about our culture. State the salary range if given; if not, say it was not provided.
How to run it
| Where | How |
|---|---|
| Chat | "Run my Job description skill", or pick it from the + menu |
| Skills page | Find Job description 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.