skog-example

Use this agent when an existing markdown file (or directory of files) needs to be converted into a valid skogai-core typed document — i.e. it has prose/legacy structure (free-form headings like "## Status", "## Context", "## Decision") and fails (or would fail) skogai-core schema validation, and the user wants it reformatted into frontmatter + required `<xml>` sections without losing its content. Trigger this proactively whenever the user asks to "fix", "migrate", "normalize", "convert", or "make pass validation" for files against skogai-core's document grammar, or after `validate-schema.sh` reports FAIL on files the user wants repaired. <example> Context: User has old decision records in dash-skogai that predate skogai-core's schema. user: "Decisions 0001 through 0004 in /home/skogix/dash-skogai/knowledge/decisions/ still use the old prose template and fail schema validation. Can you bring them in line with 0005?" assistant: "I'll use the schema-converter agent to convert 0001-0004 to match the conforming format of 0005, mapping their old sections (## Status, ## Context, ## Decision, ## Consequences) onto the required decision schema's frontmatter and <context>/<decision>/<rationale> sections, then validate each one." <commentary> These are legacy prose files of a known type (decision) with a clear already-conforming exemplar (0005) in the same directory — exactly the reformat task this agent is designed for. </commentary> </example> <example> Context: A skill reference document was hand-written without frontmatter. user: "This file plugins/skogai-core/skills/skogai-core/references/caching.md needs to pass validate-schema.sh as a type: reference doc." assistant: "I'm going to use the schema-converter agent to add the required reference frontmatter and wrap the existing content in an <overview> section, then run the validator to confirm it passes." <commentary> The user wants a specific file reformatted to satisfy a named schema type (reference) and validated — this is the core workflow of schema-converter. </commentary> </example> <example> Context: User just ran the whole-tree validator and got failures. user: "validate-schema.sh on plugins/skogai-core just printed a bunch of FAIL lines for files in workflows/ — can you fix those up?" assistant: "Let me use the schema-converter agent to look at each failing workflow file, find a passing workflow as the format exemplar, and restructure each failing file's frontmatter and sections (objective/steps/validation) until the validator reports PASS for all of them." <commentary> Batch repair of files failing schema validation, with an in-tree exemplar to follow — directly matches the agent's iterate-until-PASS workflow. </commentary> </example> <example> Context: User mentions a markdown file doesn't fit any existing skogai-core type. user: "Can you make /skogai/notes/glossary.md pass validation as a skogai-core document?" assistant: "I'll use the schema-converter agent to inspect the file and figure out which of skogai-core's document types (router, workflow, reference, template, script, lesson, pattern, principle, decision, list) best fits a glossary — if none fit cleanly it will flag that rather than invent a new type." <commentary> Even when the target type is ambiguous, this agent is the right one to determine the best-fit type (or flag if none fits) and then perform the conversion. </commentary> </example>

Routes information through a progressive framework of routing files, workflows, references, templates, and scripts. Use as the starting point when deciding where guidance belongs, which endpoint should handle a request, or how to structure an agent-facing knowledge system.