Interpret and explain YON documents, tags, and records in plain English.
npx skills add https://github.com/allemaar/open-skills --skill yon-read-allemaar
Please help me install this Agent Skill. Skill: yon-read Source: https://github.com/allemaar/open-skills/tree/main/skills/yon-read Command: npx skills add https://github.com/allemaar/open-skills --skill yon-read-allemaar
High-intent search queries and answers about installing and using this skill.
Start with the @DOC header to learn the document's kind, profile, and format, then walk each @SEC section and interpret records by tag. This Skill translates tags like @RULE, @STEP, and @MAP into plain-English explanations grouped by section.
YON rules carry a lvl field with values MUST, MUST_NOT, SHOULD, SHOULD_NOT, or MAY, indicating how binding the constraint is. When explaining a document, mandatory rules are stated prominently while SHOULD rules are presented as recommendations.
Reading and interpreting Layer 4 records like @AGENT, @STREAM, and @SIGNAL is always supported, but executing @AGENT-routed dispatch depends on the host runtime. Claude Code supports it via the Agent tool; other runtimes vary.
Use yon-read when you want to interpret, summarize, or explain existing YON content. Use yon-write when you want to create, edit, convert, or extend YON documents. Generic questions about the format with no content present trigger neither.
Trust measures the reliability of the source that produced a record, while confidence measures the certainty of the content itself. Both range from 0.0 to 1.0 and must not be conflated when interpreting cognition or memory records.
VMAFxDraft Markdown model cards for ONNX tiny-AI models with provenance validation.
AizenvoltPrimeAutomate Word .docx tracked changes, comments, edits, and text extraction with OOXML preservation.
happier-devAudit reports by re-deriving load-bearing claims from primary sources.
nielsmadanExplain unfamiliar code grouped by logical concepts with optional syntax details.
