Library tools
The two tools that serve procedures to the agent: the ones Stratta ships and the ones your office wrote.
A procedure (a skill, in the sense of the Agent Skills standard) is a Markdown text the agent reads before a repeatable task: drafting the project basis, writing the terrain chapter of a report, instructing a type of structure, preparing the review of a dossier. Stratta ships nine with the connector; your office writes its own on the Library page, and an office procedure with the same name as a Stratta one replaces it for your agent.
The method served by get_methodology asks the agent to call list_skills before drafting a
document or starting such a task, then get_skill on the one that fits.
| Shipped procedure | What it makes the agent do |
|---|---|
consult-stratta | The consultation method: navigation, citation, dossier |
ingest-norm | Ingesting a norm from a PDF |
verification-note | The verification note of a dossier, every paragraph resting on evidence |
project-basis | The project basis (SIA 260 clause 2.5) from the dossier and the site sheet |
use-agreement | The use agreement (SIA 260 clause 2.2), to be read with the owner |
site-chapter | The terrain chapter of a report, one sentence per fact, with its source |
instruct-structure | Opening the questions of a type of structure and filing the clauses, no decision |
review-open-questions | The review brief: what is retained, what is still open |
handoff-to-word | Formatting a document for the office's Word template |
list_skills
Lists the procedures the agent can follow: the office's first, then Stratta's that no office procedure replaces. Each row carries the name, the description (what the procedure does and when to follow it) and the source.
No parameters.
get_skill
Reads one procedure in full, as Markdown with its front matter (name, description) and its
text. The office version wins over the Stratta version of the same name. Returns null when
no procedure has that name.
namestringrequiredThe name as list_skills gives it: project-basis.
Writing a procedure
On the Library page, an owner or an admin writes a procedure in three fields: the name (lowercase and hyphens, it is what the agent asks for), the sentence that says when to follow it (it is what the agent picks it on), and the text. The text follows what makes an agent apply it well: imperative, short, the steps in order, the expected plan, what not to write, and one example. Opening a Stratta procedure and clicking "Adapt" makes a copy under the office's name, ready to edit.
Procedures are also served as the resource stratta://skills/{name} for clients that pin a
document to a conversation.
Learning a template from an office report
An office does not write its report plan: it has one, in the last report it delivered. On the Library page, "Learn from a report" takes a Word file whose chapters use Heading styles; Stratta derives the plan, the standing mentions (notice, validity, signature), the wording that carries a retained value, the language and the kind of document. The office reviews every field and validates; nothing is served before.
A validated template is an office procedure like any other: list_skills lists it, get_skill
reads it, and when it takes the name of a Stratta procedure (project-basis) it replaces it.
The Word file stays in the organisation for the rendering to come.