[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M788EGY8RTRAZVXB2WCB8PQA":3,"skill-same:01M788EGY8RTRAZVXB2WCB8PQA":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M788EGY8RTRAZVXB2WCB8PQA","structured-exchange-project",null,"Set up the model and the review rules a project holds its structured-exchange documents to — the registry (.pi-outpost\u002Fstructured-exchange.json), its profiles (kinds, attributes, enumerations, which kinds a relationship joins) and its rules files. Read it before writing or changing any of those files, and when the project's structured-exchange registry cannot be used. Use when asked to build a profile from a requirements tool's export or a data model, to turn review rules from a standard or a plan into rules files, or to show a project's rules for review with present_project_model.","laurentftech\u002Fpi-outpost","laurentftech","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44120190?v=4","01M788DKJAGDDS1CAJHA6B819B","Laurent","01M788DKK4ZXN1066CCDVCM39A",29,"MIT","https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fskills\u002Fstructured-exchange-project\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: structured-exchange-project\ndescription: Set up the model and the review rules a project holds its structured-exchange documents to — the registry (.pi-outpost\u002Fstructured-exchange.json), its profiles (kinds, attributes, enumerations, which kinds a relationship joins) and its rules files. Read it before writing or changing any of those files, and when the project's structured-exchange registry cannot be used. Use when asked to build a profile from a requirements tool's export or a data model, to turn review rules from a standard or a plan into rules files, or to show a project's rules for review with present_project_model.\nlicense: MIT\nmetadata:\n  version: \"1.0\"\n---\n\n# Setting up a project's model and rules\n\nA project writes three kinds of files, and people review them:\n\n- a **profile** — the words that exist: element kinds, relationship kinds and the kinds each\n  relationship joins, the attributes of each kind, the values of each enumeration;\n- a **rules file** — how those words must fit together: \"a derived requirement does not\n  satisfy an upstream requirement\";\n- the **registry**, `.pi-outpost\u002Fstructured-exchange.json` at the project root, listing both.\n\nYou draft them. A person confirms them. Every document the agent presents in this project is\nthen held to them — so a wrong file does not look wrong: it refuses good documents, or\nchecks less than anyone meant.\n\n## The loop\n\n1. **Start from the source.** A requirements tool's export, a data model, a standard, a\n   safety plan the user gave you. Every kind, attribute, value and rule comes from it. Never\n   invent one to fill a gap: ask the user.\n2. **Write the profile, then the registry listing it.** Call `present_project_model` with\n   `view: \"rules-register\"`. Its result lists the whole profile as text: compare it with the\n   source, value by value. The tool is offered only once the conversation touches the model:\n   if you do not see it, read `.pi-outpost\u002Fstructured-exchange.json` (or write it) first.\n3. **Write the rules**, one rule per sentence of the source, starting from the example below.\n   Add the rules file to the registry's `rules` and call `present_project_model` again.\n4. **Fix what it returns.** An error result means the files are unusable — and while they\n   are, every structured-exchange document in the project is refused. Each issue names the\n   file, the rule and a pointer (see [What the check says](#what-the-check-says)). Fix and\n   call again until it presents.\n5. **Read the listing it returns.** For each rule: do its conditions say what its statement\n   says? Check against [What passes silently](#what-passes-silently).\n6. **Show the user.** Call it with `view: \"rule-patterns\"` — one small drawing per rule, what\n   it selects and what it requires — and ask them to confirm each rule. Rules are written, or\n   at least validated, by people; say so rather than presenting your draft as settled.\n\nNever write or draw the register or the patterns yourself: only the tool's are generated from\nthe files.\n\nOutside this application, the reference validator does the same checks:\n`--check-profile profile.json`, `--registry .pi-outpost\u002Fstructured-exchange.json` (checks it\nall), `--registry … --describe-profile` (the listing), and `--registry … --rules-register\nregister.json --rule-patterns patterns.json` (the two views).\n\n## The files\n\nThe registry. Paths are relative to the project and must stay inside it; `rules` and\n`default` are optional. With a `default`, every document is held to that profile.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-profile-registry:1\",\n  \"profiles\": [\"profiles\u002Frequirements.json\"],\n  \"rules\": [\"rules\u002Freview.json\"],\n  \"default\": \"acme\u002Frequirements\"\n}\n```\n\nA profile. Enumerations list their values in the order a reviewer reads them, and say whether\nthey are `closed` (anything else is refused) or open (anything else is accepted and reported).\nA relationship kind may say which element kinds it joins: `from` at its source, `to` at its\ntarget. Declare them whenever the source model says so — a side left out allows any kind.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-profile:1\",\n  \"id\": \"acme\u002Frequirements\",\n  \"label\": \"ACME requirements model\",\n  \"elementKinds\": [\n    {\n      \"kind\": \"requirement\",\n      \"attributes\": [\n        { \"name\": \"status\", \"type\": \"enumeration\", \"values\": [\"draft\", \"approved\", \"withdrawn\"], \"closed\": true, \"required\": true },\n        { \"name\": \"category\", \"type\": \"enumeration\", \"values\": [\"derived\", \"refined\", \"direct\"], \"closed\": true },\n        { \"name\": \"safety\", \"type\": \"enumeration\", \"values\": [\"yes\", \"no\"], \"closed\": true }\n      ]\n    },\n    {\n      \"kind\": \"test\",\n      \"attributes\": [{ \"name\": \"bench\", \"type\": \"enumeration\", \"values\": [\"hil\", \"vehicle\", \"simulation\"], \"closed\": true }]\n    }\n  ],\n  \"relationshipKinds\": [\n    { \"kind\": \"satisfies\", \"from\": [\"requirement\"], \"to\": [\"requirement\"] },\n    { \"kind\": \"verifies\", \"from\": [\"test\"], \"to\": [\"requirement\"] }\n  ]\n}\n```\n\nA rules file, for one registered profile. `statement` is the rule in the source's own words\nand language: it is what every refusal and report quotes. `id` and `source` say where it\ncomes from.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-rules:1\",\n  \"profile\": \"acme\u002Frequirements\",\n  \"rules\": [\n    {\n      \"id\": \"ARP4754A-derived-no-satisfy\",\n      \"source\": \"ARP4754A\",\n      \"statement\": \"Une exigence dérivée ne satisfait pas une exigence amont.\",\n      \"level\": \"refuse\",\n      \"relationship\": \"satisfies\",\n      \"when\": { \"from\": { \"category\": [\"derived\"] } },\n      \"then\": \"forbidden\"\n    },\n    {\n      \"id\": \"SAF-satisfied-by-safety\",\n      \"source\": \"Safety plan\",\n      \"statement\": \"Une exigence safety n'est satisfaite que par des exigences safety.\",\n      \"level\": \"refuse\",\n      \"relationship\": \"satisfies\",\n      \"when\": { \"to\": { \"safety\": [\"yes\"] } },\n      \"then\": { \"from\": { \"safety\": [\"yes\"] } }\n    },\n    {\n      \"id\": \"VER-safety-on-hil\",\n      \"source\": \"Verification plan\",\n      \"statement\": \"Une exigence safety est vérifiée sur banc HIL.\",\n      \"level\": \"report\",\n      \"relationship\": \"verifies\",\n      \"when\": { \"to\": { \"safety\": [\"yes\"] } },\n      \"then\": { \"from\": { \"bench\": [\"hil\"] } }\n    },\n    {\n      \"id\": \"SAF-approved\",\n      \"source\": \"Safety plan\",\n      \"statement\": \"A safety requirement is approved.\",\n      \"level\": \"report\",\n      \"element\": \"requirement\",\n      \"when\": { \"safety\": [\"yes\"] },\n      \"then\": { \"status\": [\"approved\"] }\n    }\n  ]\n}\n```\n\n## Writing a rule\n\n- **Item or link.** A rule about one thing names `element` (a kind of element or table row).\n  A rule about a link names `relationship`, and conditions its source under `from` and its\n  target under `to`.\n- **`when` selects, `then` requires.** `when` says which items or links the rule is about;\n  without it, all of that kind. `then` says what those must have — or is `\"forbidden\"`:\n  nothing selected may exist.\n- **Translate the sentence, do not improve it.** \"A safety requirement is satisfied only by\n  safety requirements\" selects links whose *target* is safety, and requires their *source* to\n  be. Writing it the other way round is a different rule that also validates.\n\n## What passes silently\n\nEach of these validates, and checks something other than what the statement says.\n\n- **Values in one condition are alternatives; conditions in one set must all hold.**\n  `{ \"category\": [\"derived\", \"refined\"] }` selects derived *or* refined.\n  `{ \"category\": [\"derived\"], \"safety\": [\"yes\"] }` selects what is derived *and* safety. There\n  is no way to require two values of one attribute at once, because an attribute holds one.\n- **An item lacking an attribute named in `when` is not selected, and escapes the rule.** A\n  requirement exported without `safety` is never checked by a rule whose `when` reads\n  `safety`. If the rule must reach every requirement, make the attribute `required` in the\n  profile, or ask the user whether a missing value should be written as a value.\n- **A link rule reads its conditions on the kinds the relationship allows at that end.**\n  Without declared ends, `from: { \"safety\": [\"yes\"] }` is read on *any* kind that declares\n  `safety` — a `test` too, if it has one. Declare `from` and `to` on the relationship kind.\n- **`from` and `to` belong to link rules only.** An item rule's `when` and `then` are flat\n  attribute conditions.\n- **An attribute holding a list or a reference cannot be conditioned**, and is refused.\n- **What a rule cannot read is not a pass.** When a link's other end is not in the document,\n  or is carried without the attribute the rule reads, the rule is *not verifiable here*: a\n  finding to check, never a silent pass and never a refusal.\n\n## Refuse or report\n\n- **`refuse`** stops the agent's tools from presenting a document that breaks the rule. Use it\n  for what is never acceptable in the source's own terms — a prohibition in a standard.\n- **`report`** accepts the document and lists the violation as a finding for a person to\n  check. Use it for what is usually wrong but may be justified, or while a new rule is being\n  tried on real data.\n\nWhen the source does not say, ask the user; do not choose `refuse` to look strict.\n\n## What the check says\n\n| Rule in the issue | What it means | What to do |\n|---|---|---|\n| `rules-format\u002Fundeclared-value` | a condition names a value the enumeration does not list | use the profile's value exactly, or ask whether the profile is missing it |\n| `rules-format\u002Fundeclared-attribute` | the kind — or no kind allowed at that end — declares the attribute | check the kind and the ends; never add the attribute to the profile to make a rule pass |\n| `rules-format\u002Fundeclared-kind` | the rule names a kind the profile does not have | use the profile's kind; mind element versus relationship |\n| `rules-format\u002Funsupported-attribute` | the attribute holds a list or a reference | a rule cannot condition it; tell the user |\n| `rules-format\u002Fvalue-type` | a value's type differs from the attribute's | write a number as a number, a boolean as a boolean |\n| `profile-format\u002Funresolved-end-kind` | `from` or `to` names an element kind the profile does not declare | fix the name; ends name element kinds, not relationships |\n| `registry\u002Fduplicate-rule-identifier` | two rules of one profile share an `id` | give each rule its own identifier |\n| `registry\u002Frules-for-unregistered-profile` | a rules file names a profile the registry does not list | fix the rules file's `profile`, or register the profile |\n| `registry\u002Fmissing-…`, `…\u002Foutside-project` | a listed file is missing or outside the project | fix the path in the registry |\n| `registry\u002Fappearance\u002Fcolor` | a colour is not `#rrggbb` | write six hexadecimal digits after `#` |\n\n## Project colours\n\nIf the user wants the project's kinds drawn in set colours, add an `appearance` section to the\nregistry and declare it version 2. Colours apply to every drawing in the project; never put a\ncolour in a structured-exchange document.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-profile-registry:2\",\n  \"profiles\": [\"profiles\u002Frequirements.json\"],\n  \"appearance\": {\n    \"kinds\": { \"requirement\": { \"color\": \"#2563eb\" } },\n    \"relationshipKinds\": { \"verifies\": { \"color\": \"#16a34a\" } }\n  }\n}\n```\n\n`kinds` is for elements, participants and timeline items; `relationshipKinds` for relationships.\nEach colour is exactly `#` and six hexadecimal digits. Ask the user for the colours: do not pick\nthem yourself. A registry may declare `appearance` and no profile at all.\n\n## Changing a model that is in use\n\nEvery document is checked against the files as they are on disk when it is shown. Narrowing a\nprofile — a value removed from a closed enumeration, an end restricted — makes documents\npresented earlier say they no longer conform. Tell the user before you narrow anything.\n\nDeclaring `from` or `to` on a relationship kind is newer than the profile format's first\nrelease: a pi-outpost or a validator older than that refuses a profile using them. If the\nproject's files are also read by another tool or an older installation, say so to the user.\n\nFor authoring the documents themselves — and acting on a refusal while presenting one — read\nthe `structured-exchange` skill.\n","# Setting up a project's model and rules\n\nA project writes three kinds of files, and people review them:\n\n- a **profile** — the words that exist: element kinds, relationship kinds and the kinds each\n  relationship joins, the attributes of each kind, the values of each enumeration;\n- a **rules file** — how those words must fit together: \"a derived requirement does not\n  satisfy an upstream requirement\";\n- the **registry**, `.pi-outpost\u002Fstructured-exchange.json` at the project root, listing both.\n\nYou draft them. A person confirms them. Every document the agent presents in this project is\nthen held to them — so a wrong file does not look wrong: it refuses good documents, or\nchecks less than anyone meant.\n\n## The loop\n\n1. **Start from the source.** A requirements tool's export, a data model, a standard, a\n   safety plan the user gave you. Every kind, attribute, value and rule comes from it. Never\n   invent one to fill a gap: ask the user.\n2. **Write the profile, then the registry listing it.** Call `present_project_model` with\n   `view: \"rules-register\"`. Its result lists the whole profile as text: compare it with the\n   source, value by value. The tool is offered only once the conversation touches the model:\n   if you do not see it, read `.pi-outpost\u002Fstructured-exchange.json` (or write it) first.\n3. **Write the rules**, one rule per sentence of the source, starting from the example below.\n   Add the rules file to the registry's `rules` and call `present_project_model` again.\n4. **Fix what it returns.** An error result means the files are unusable — and while they\n   are, every structured-exchange document in the project is refused. Each issue names the\n   file, the rule and a pointer (see [What the check says](#what-the-check-says)). Fix and\n   call again until it presents.\n5. **Read the listing it returns.** For each rule: do its conditions say what its statement\n   says? Check against [What passes silently](#what-passes-silently).\n6. **Show the user.** Call it with `view: \"rule-patterns\"` — one small drawing per rule, what\n   it selects and what it requires — and ask them to confirm each rule. Rules are written, or\n   at least validated, by people; say so rather than presenting your draft as settled.\n\nNever write or draw the register or the patterns yourself: only the tool's are generated from\nthe files.\n\nOutside this application, the reference validator does the same checks:\n`--check-profile profile.json`, `--registry .pi-outpost\u002Fstructured-exchange.json` (checks it\nall), `--registry … --describe-profile` (the listing), and `--registry … --rules-register\nregister.json --rule-patterns patterns.json` (the two views).\n\n## The files\n\nThe registry. Paths are relative to the project and must stay inside it; `rules` and\n`default` are optional. With a `default`, every document is held to that profile.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-profile-registry:1\",\n  \"profiles\": [\"profiles\u002Frequirements.json\"],\n  \"rules\": [\"rules\u002Freview.json\"],\n  \"default\": \"acme\u002Frequirements\"\n}\n```\n\nA profile. Enumerations list their values in the order a reviewer reads them, and say whether\nthey are `closed` (anything else is refused) or open (anything else is accepted and reported).\nA relationship kind may say which element kinds it joins: `from` at its source, `to` at its\ntarget. Declare them whenever the source model says so — a side left out allows any kind.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-profile:1\",\n  \"id\": \"acme\u002Frequirements\",\n  \"label\": \"ACME requirements model\",\n  \"elementKinds\": [\n    {\n      \"kind\": \"requirement\",\n      \"attributes\": [\n        { \"name\": \"status\", \"type\": \"enumeration\", \"values\": [\"draft\", \"approved\", \"withdrawn\"], \"closed\": true, \"required\": true },\n        { \"name\": \"category\", \"type\": \"enumeration\", \"values\": [\"derived\", \"refined\", \"direct\"], \"closed\": true },\n        { \"name\": \"safety\", \"type\": \"enumeration\", \"values\": [\"yes\", \"no\"], \"closed\": true }\n      ]\n    },\n    {\n      \"kind\": \"test\",\n      \"attributes\": [{ \"name\": \"bench\", \"type\": \"enumeration\", \"values\": [\"hil\", \"vehicle\", \"simulation\"], \"closed\": true }]\n    }\n  ],\n  \"relationshipKinds\": [\n    { \"kind\": \"satisfies\", \"from\": [\"requirement\"], \"to\": [\"requirement\"] },\n    { \"kind\": \"verifies\", \"from\": [\"test\"], \"to\": [\"requirement\"] }\n  ]\n}\n```\n\nA rules file, for one registered profile. `statement` is the rule in the source's own words\nand language: it is what every refusal and report quotes. `id` and `source` say where it\ncomes from.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-rules:1\",\n  \"profile\": \"acme\u002Frequirements\",\n  \"rules\": [\n    {\n      \"id\": \"ARP4754A-derived-no-satisfy\",\n      \"source\": \"ARP4754A\",\n      \"statement\": \"Une exigence dérivée ne satisfait pas une exigence amont.\",\n      \"level\": \"refuse\",\n      \"relationship\": \"satisfies\",\n      \"when\": { \"from\": { \"category\": [\"derived\"] } },\n      \"then\": \"forbidden\"\n    },\n    {\n      \"id\": \"SAF-satisfied-by-safety\",\n      \"source\": \"Safety plan\",\n      \"statement\": \"Une exigence safety n'est satisfaite que par des exigences safety.\",\n      \"level\": \"refuse\",\n      \"relationship\": \"satisfies\",\n      \"when\": { \"to\": { \"safety\": [\"yes\"] } },\n      \"then\": { \"from\": { \"safety\": [\"yes\"] } }\n    },\n    {\n      \"id\": \"VER-safety-on-hil\",\n      \"source\": \"Verification plan\",\n      \"statement\": \"Une exigence safety est vérifiée sur banc HIL.\",\n      \"level\": \"report\",\n      \"relationship\": \"verifies\",\n      \"when\": { \"to\": { \"safety\": [\"yes\"] } },\n      \"then\": { \"from\": { \"bench\": [\"hil\"] } }\n    },\n    {\n      \"id\": \"SAF-approved\",\n      \"source\": \"Safety plan\",\n      \"statement\": \"A safety requirement is approved.\",\n      \"level\": \"report\",\n      \"element\": \"requirement\",\n      \"when\": { \"safety\": [\"yes\"] },\n      \"then\": { \"status\": [\"approved\"] }\n    }\n  ]\n}\n```\n\n## Writing a rule\n\n- **Item or link.** A rule about one thing names `element` (a kind of element or table row).\n  A rule about a link names `relationship`, and conditions its source under `from` and its\n  target under `to`.\n- **`when` selects, `then` requires.** `when` says which items or links the rule is about;\n  without it, all of that kind. `then` says what those must have — or is `\"forbidden\"`:\n  nothing selected may exist.\n- **Translate the sentence, do not improve it.** \"A safety requirement is satisfied only by\n  safety requirements\" selects links whose *target* is safety, and requires their *source* to\n  be. Writing it the other way round is a different rule that also validates.\n\n## What passes silently\n\nEach of these validates, and checks something other than what the statement says.\n\n- **Values in one condition are alternatives; conditions in one set must all hold.**\n  `{ \"category\": [\"derived\", \"refined\"] }` selects derived *or* refined.\n  `{ \"category\": [\"derived\"], \"safety\": [\"yes\"] }` selects what is derived *and* safety. There\n  is no way to require two values of one attribute at once, because an attribute holds one.\n- **An item lacking an attribute named in `when` is not selected, and escapes the rule.** A\n  requirement exported without `safety` is never checked by a rule whose `when` reads\n  `safety`. If the rule must reach every requirement, make the attribute `required` in the\n  profile, or ask the user whether a missing value should be written as a value.\n- **A link rule reads its conditions on the kinds the relationship allows at that end.**\n  Without declared ends, `from: { \"safety\": [\"yes\"] }` is read on *any* kind that declares\n  `safety` — a `test` too, if it has one. Declare `from` and `to` on the relationship kind.\n- **`from` and `to` belong to link rules only.** An item rule's `when` and `then` are flat\n  attribute conditions.\n- **An attribute holding a list or a reference cannot be conditioned**, and is refused.\n- **What a rule cannot read is not a pass.** When a link's other end is not in the document,\n  or is carried without the attribute the rule reads, the rule is *not verifiable here*: a\n  finding to check, never a silent pass and never a refusal.\n\n## Refuse or report\n\n- **`refuse`** stops the agent's tools from presenting a document that breaks the rule. Use it\n  for what is never acceptable in the source's own terms — a prohibition in a standard.\n- **`report`** accepts the document and lists the violation as a finding for a person to\n  check. Use it for what is usually wrong but may be justified, or while a new rule is being\n  tried on real data.\n\nWhen the source does not say, ask the user; do not choose `refuse` to look strict.\n\n## What the check says\n\n| Rule in the issue | What it means | What to do |\n|---|---|---|\n| `rules-format\u002Fundeclared-value` | a condition names a value the enumeration does not list | use the profile's value exactly, or ask whether the profile is missing it |\n| `rules-format\u002Fundeclared-attribute` | the kind — or no kind allowed at that end — declares the attribute | check the kind and the ends; never add the attribute to the profile to make a rule pass |\n| `rules-format\u002Fundeclared-kind` | the rule names a kind the profile does not have | use the profile's kind; mind element versus relationship |\n| `rules-format\u002Funsupported-attribute` | the attribute holds a list or a reference | a rule cannot condition it; tell the user |\n| `rules-format\u002Fvalue-type` | a value's type differs from the attribute's | write a number as a number, a boolean as a boolean |\n| `profile-format\u002Funresolved-end-kind` | `from` or `to` names an element kind the profile does not declare | fix the name; ends name element kinds, not relationships |\n| `registry\u002Fduplicate-rule-identifier` | two rules of one profile share an `id` | give each rule its own identifier |\n| `registry\u002Frules-for-unregistered-profile` | a rules file names a profile the registry does not list | fix the rules file's `profile`, or register the profile |\n| `registry\u002Fmissing-…`, `…\u002Foutside-project` | a listed file is missing or outside the project | fix the path in the registry |\n| `registry\u002Fappearance\u002Fcolor` | a colour is not `#rrggbb` | write six hexadecimal digits after `#` |\n\n## Project colours\n\nIf the user wants the project's kinds drawn in set colours, add an `appearance` section to the\nregistry and declare it version 2. Colours apply to every drawing in the project; never put a\ncolour in a structured-exchange document.\n\n```json\n{\n  \"schema\": \"urn:structured-exchange-profile-registry:2\",\n  \"profiles\": [\"profiles\u002Frequirements.json\"],\n  \"appearance\": {\n    \"kinds\": { \"requirement\": { \"color\": \"#2563eb\" } },\n    \"relationshipKinds\": { \"verifies\": { \"color\": \"#16a34a\" } }\n  }\n}\n```\n\n`kinds` is for elements, participants and timeline items; `relationshipKinds` for relationships.\nEach colour is exactly `#` and six hexadecimal digits. Ask the user for the colours: do not pick\nthem yourself. A registry may declare `appearance` and no profile at all.\n\n## Changing a model that is in use\n\nEvery document is checked against the files as they are on disk when it is shown. Narrowing a\nprofile — a value removed from a closed enumeration, an end restricted — makes documents\npresented earlier say they no longer conform. Tell the user before you narrow anything.\n\nDeclaring `from` or `to` on a relationship kind is newer than the profile format's first\nrelease: a pi-outpost or a validator older than that refuses a profile using them. If the\nproject's files are also read by another tool or an older installation, say so to the user.\n\nFor authoring the documents themselves — and acting on a refusal while presenting one — read\nthe `structured-exchange` skill.\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25},"1.0","main","c8d342c3f95fb1721cfee185876230cdb792bfa9","skills\u002Fstructured-exchange-project",3,"https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost","https:\u002F\u002Flaurentftech.github.io\u002Fpi-outpost\u002F","https:\u002F\u002Fgithub.com\u002Flaurentftech","👋 Hi, I’m Laurent — system engineer and software enthusiast passionate about building practical tech solutions to simplify everyday tasks. ","2026-11-15 01:56:41",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add laurentftech\u002Fpi-outpost --skill structured-exchange-project",{"tool":41,"command":42},"bunx","bunx skills add laurentftech\u002Fpi-outpost --skill structured-exchange-project",{"tool":44,"command":45},"pnpm","pnpm dlx skills add laurentftech\u002Fpi-outpost --skill structured-exchange-project","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fskills\u002Fstructured-exchange-project\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M788EQ5TN6CCQQR4ARHNK6RW","structured-exchange","Author a structured-exchange document — a graph, sequence, table or planning timeline the interface renders natively, such as a table of requirements with their attributes, a programme schedule with milestones and dependencies, or a proposal to change one an external authority holds — and write figures of one into a document you are authoring. Read it before calling present_structure or write_structure_figure. Use when asked to draw or diagram a structure, to present requirements or other typed items, to plan or show a schedule, roadmap or Gantt chart, to propose an evolution of an existing model, to illustrate a report you are writing, when a project's profile refuses a kind, attribute or value, or when a result would otherwise be a hand-written diagram.","https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fskills\u002Fstructured-exchange\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M788E8ZY03V1YX0QC0QC8XBP","pptx-from-template","Build a PowerPoint presentation (.pptx) from a template (.potx or .pptx) — or from no template at all, on the built-in Office theme — titles, bullets, pictures, native tables and editable charts, or update an existing deck slide by slide, with pptx_layouts, pptx_create, pptx_update and pptx_render, then check it is readable by rendering it with PowerPoint (Windows), LibreOffice or ONLYOFFICE and fixing what the render shows. Use whenever the user asks for a deck, slides or a presentation — from their template, a corporate\u002Fbrand deck, on the default or standard PowerPoint theme, or with no theme named at all — and to turn a document, notes or an outline into slides, and whenever a .potx file is involved.","https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fskills\u002Fpptx-from-template\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M788E49P7S5MF73NHYVS0J3C","posters","Make a poster, a worksheet, a slide or any one-page visual (a class poster, a vocabulary sheet, a timetable, an announcement) as a .poster.html file the user opens in the file viewer, retouches there — corrects a text, moves a pictogram, changes a colour — and exports to Word to print or PowerPoint to show. Use whenever the user asks for a poster, an affiche, a printable sheet, a visual, or a slide made to look designed, or to change an existing .poster.html file.","https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fskills\u002Fposters\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M788DYE39M1ES4BBT7SPEFQF","drawio","Write a draw.io diagram (.drawio) — flowchart, architecture, sequence of steps, org chart, network or data-flow map — as XML the user can open and edit in draw.io, then check it with drawio_check and show it in the reply. Use whenever the user asks for a draw.io or diagrams.net diagram, an editable diagram file, or to change an existing .drawio file. The conversation and the file viewer draw it; the user touches it up there, or edits it in draw.io desktop.","https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fskills\u002Fdrawio\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M788DR6SFH7F6BTJDGSVH8H8","docx-from-template","Write a Word document (.docx) in a template's house style — or update an existing one section by section, as tracked changes, or bring an old one onto a template (restyle) — with docx_styles, docx_create, docx_update, docx_restyle and docx_render, then check it by rendering it with Word (Windows), LibreOffice or ONLYOFFICE and fixing what the render shows. Use whenever the user asks for a report, memo, specification or letter in their Word template, to turn notes or Markdown into a Word document, or to revise sections of an existing .docx, to fix a document's inconsistent fonts or move it onto a new template — and whenever a .dotx file is involved.","https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fskills\u002Fdocx-from-template\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M788DPVPF1BJW81KVHM7GNM3","test-skill","A skill for testing isolation.","https:\u002F\u002Fgithub.com\u002Flaurentftech\u002Fpi-outpost\u002Fblob\u002Fmain\u002Fserver\u002Ftest\u002Ffixtures\u002Ftest-skill\u002FSKILL.md",[],[]]