Method tools
The two tools that serve methods to the agent: the ones Stratta ships and the ones your organization wrote.
A method (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 organization writes its own on the Methods page (Méthodes), and an office method 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 method | 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 methods the agent can follow: the office's first, then Stratta's that no office method replaces. Each row carries the name, the description (what the method does and when to follow it) and the source.
No parameters.
get_skill
Reads one method 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 method has that name.
namestringrequiredThe name as list_skills gives it: project-basis.
Writing a method
On the Methods page, an owner or an admin writes a method with Écrire une méthode (write a
method): a title, the sentence that says when to use it (it is what the agent picks it on), and
the instructions. The technical name the agent asks for (project-basis) is derived from the
title: there is nothing to type. Instructions are imperative, short, in order, with the expected
plan, what not to write, and one example. On a Stratta method, Écrire votre version (write
your version) starts from its text and replaces it for the office; Revenir à la version
Stratta (back to the Stratta version) removes yours.
Methods are also served as the resource stratta://skills/{name} for clients that pin a
document to a conversation.
Learning the plan of an office report
An office does not write its report plan: it has one, in the last report it delivered. On the Methods page, Apprendre d’un rapport (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 (Valider ce plan); nothing is served before.
For the project basis, the use agreement or the verification note, the learned plan takes the
name of the Stratta method (project-basis, use-agreement, verification-note) and replaces
it. Another kind of document is added to the methods. Either way, list_skills lists it and
get_skill reads it. The Word file stays in the organisation for the rendering to come.