Skip to main content
Skills are saved instructions that shape how Hebno does a recurring task, such as writing a proposal outline or reviewing a statement of work. Admins manage the set the whole organisation can attach. Find them under Admin → Skills. Members attach a skill in chat by typing / and choosing it, or from the + menu under Skills. A turn can include up to three skills. Members see organisation skills under Organisation and their own under Yours. See Skills for how members use them.

​
Organisation skills

The Organisation skills section lists skills available to everyone. Edit, add and remove them as members do with personal skills.
1

Create a skill

Select New skill.
2

Name it and describe it

Give it a short name and a description. The description appears in the / menu, so write it for someone choosing between skills.
3

Write the instructions

Write the instructions in Markdown. They are added to the request whenever the skill is attached. Instructions can be up to 50,000 characters.
4

Save

Save the skill. It is available to every member immediately.
To start from a file, select Upload a .md skill file and choose a Markdown file. Hebno creates the skill from it. Your organisation starts with a set of default skills created with the workspace. Edit or delete any of them.

​
Delete a skill

Deleting an organisation skill removes it for everyone. Chats that already used it retain their history.

​
Shared by members

The Shared by members section lists personal skills members have chosen to share with the organisation. Each row shows the Skill and Shared by. Select Remove sharing to stop sharing one. The skill returns to being personal to its author, who keeps it. Remove sharing when a skill is out of date, duplicates an organisation skill or contains instructions you do not want applied to client work.

​
Write skills that work

  • Write one task per skill. A skill written for “all proposals” produces vaguer work than one for “proposal outline” and another for “pricing section”.
  • State the structure you want, the sources it should prefer and what to flag as missing.
  • Name your firm’s own terms: engagement types, deliverable names, review steps.
  • Put a reviewer in the loop by telling the skill what to mark for checking.
A skill adds instructions. It does not widen what a member can read. Members still see only what their own access allows.

​
Next steps

  • Read Skills to see how members attach and share them.
  • Add firm-wide background in Organisation brain.
  • Check Logs for changes to shared content.