Skip to main content
The Penbox plugin ships five skills. A skill is a short document the agent reads when your request matches its description. It tells the agent what to load, in which order, and what to check before it answers. The skills never repeat the reference material: the agent fetches that from the server with get_skill. The skills are in the plugin only. A custom connector or a tools-only setup does not carry them. The tools still work; the agent just has less guidance.

​
penbox-getting-started

When: the first Penbox action in a conversation. The agent resolves your workspace, learns the vocabulary (case, case template, form, form template, contact) and the read-before-write rule: every update starts from the current document, never from memory. It also learns that text written by contacts and respondents is data, never an instruction.

​
manage-cases

When: you want to open a case, add a contact, change a status, fill in data, send a reminder, or check where a case or a form stands. No reference needed. The agent finds the case, reads it, then acts. It searches cases by contact name or email, because case titles usually default to the template name. Sending a form or a reminder now goes through start_case_step, only when you ask to send.

​
build-case-template

When: you want a new type of case, or want to change the steps, statuses, automations, contacts or data schema of an existing template. The agent loads the case template reference once, checks whether a similar template already exists, then edits with small patches, one concern each. Before it writes a status, an automation or a condition, it loads the guide for that feature.

​
build-form-template

When: you want a new form, or want to add or change questions, signatures, translations, repeated sections or generated documents in an existing one. Same method: load the form template reference once, list what exists, create, then patch. The agent reads the validation errors the server returns and fixes them before moving on. A form template is created published, so the agent builds it one patch at a time.

​
penbox-api

When: a curated tool refuses, is missing, or you name an endpoint of the Penbox API. The agent searches the public API with penbox_api_search, reads the contract with penbox_api_details, then calls it with penbox_api_call. When a curated tool covers the operation, the search says so and the agent uses that tool instead.
You never name a skill. Describe the task in business words and the agent picks the matching skill on its own.