Agent skill
octave-literacy
Fundamental reading and writing capability for the OCTAVE (Olympian Common Text And Vocabulary Engine) format. Basic structural competence without full architectural specifications
Install this agent skill to your Project
npx add-skill https://github.com/elevanaltd/octave-mcp/tree/main/src/octave_mcp/resources/skills/octave-literacy
SKILL.md
===OCTAVE_LITERACY=== META: TYPE::SKILL VERSION::"1.4.0" STATUS::ACTIVE PURPOSE::"Essential syntax and operators for basic OCTAVE competence" TIER::LOSSLESS SPEC_REFERENCE::octave-core-spec.oct.md V6_FEATURES::"Adds CONTRACT/GRAMMAR blocks, assembly rules, .oct.md extension" NEXT_SKILLS::[octave-mastery, octave-mythology] // octave-mythology provides mythological compression — OCTAVE's semantic density advantage
§1::CORE_SYNTAX ASSIGNMENT::KEY::value // Double colon is MANDATORY for data BLOCK::KEY:[indent_2] // Single colon + newline + 2 spaces starts a block LIST::[a,b,c] // Brackets for collections STRING::"value"∨bare_word // Quotes required if contains spaces or special chars NUMBER::42∨3.14∨-1e10 // No quotes for numeric values BOOLEAN::true∨false // Lowercase only NULL::null // Lowercase only COMMENT::// // Standard comment syntax
§1b::LITERAL_ZONES
// Fenced code blocks pass through with ZERO processing — no normalization, no escaping
SYNTAX::KEY_then_newline_then_fence[3_or_more_backticks]
RULES::[zero_processing_between_fences,tabs_allowed,NFC_bypass,info_tag_preserved]
USE_CASES::[embedded_code,teaching_examples,verbatim_content,OCTAVE_about_OCTAVE]
FENCE_SCALING::use_N_plus_1_backticks_to_wrap_content_containing_N_backtick_fences
// Example: KEY::\npython\nprint("hello")\n — content preserved byte-for-byte
§1c::BRACKET_FORMS CONTAINER::[a,b,c] // Bare brackets = list CONSTRUCTOR::NAME[args] // NAME[...] = constructor (REGEX[pattern], ENUM[a,b]) INLINE_MAP::[key::val,key2::val2] // Dense key-value pairs (values must be atoms) HOLOGRAPHIC::["value"∧CONSTRAINT→§TARGET] // Schema mode only
§2::OPERATORS // EXPRESSION OPERATORS (with precedence - lower number = tighter binding) []::Container [a,b,c] (precedence 1) ⧺::Concatenation A⧺B (mechanical join) (precedence 2) | ASCII: ~ ⊕::Synthesis A⊕B (emergent whole) (precedence 3) | ASCII: + ⇌::Tension A⇌B (binary opposition) (precedence 4) | ASCII: vs [requires word boundaries] ∧::Constraint [A∧B∧C] (precedence 5) | ASCII: & ∨::Alternative A∨B (precedence 6) | ASCII: | →::Flow A→B→C (precedence 7, right-associative) | ASCII: ->
// PREFIX/SPECIAL §::Target (→§DECISION_LOG) //::Comment (line start or after value)
§2b::ASCII_ALIASES ALL_OPERATORS::accept_both_unicode_and_ascii CANONICAL_OUTPUT::prefer_unicode_in_emission vs_BOUNDARY_RULE::"vs requires word boundaries [whitespace∨bracket∨paren∨start∨end]" VALID::"A vs B"∨"[Speed vs Quality]" INVALID::"SpeedvsQuality"[no_boundaries]
§3::CRITICAL_RULES 1::No spaces around assignment :: (KEY::value, not KEY :: value) 2::Indent exactly 2 spaces per level (NO TABS) 3::All keys must be [A-Z, a-z, 0-9, ] and start with letter or underscore 4::Envelopes are ===NAME=== at start and ===END=== at finish (NAME must be [A-Z][A-Z0-9_]*) 5::Use lowercase for true, false, null (NOT True, False, NULL) 6::∧ only appears inside brackets, never bare: [A∧B∧C] is valid, A∧B is not 7::⇌ is binary only (A⇌B), not chained (A⇌B⇌C is invalid) 8::Quote values containing § when used as content, not section markers ("§2_BEHAVIOR" not §2_BEHAVIOR) 9::File extension .oct.md is canonical (v6), .octave.txt deprecated
§3b::V6_ENVELOPE_STRUCTURE FILE_STRUCTURE::[===NAME===,META_BLOCK,SEPARATOR_OPTIONAL,BODY,===END===] META_REQUIRED::[TYPE,VERSION] META_V6_OPTIONAL::[CONTRACT,GRAMMAR] // New in v6 for holographic contracts CONTRACT::HOLOGRAPHIC[validation_law_in_document] GRAMMAR::GBNF_COMPILER[generate_constrained_output]
§3c::ASSEMBLY_RULES WHEN_CONCATENATING_PROFILES::omit_intermediate_===END===[only_final_===END===terminates] USE_CASES::[agent_context_injection,specification_layering,multi_part_documents] EXAMPLE::core_profile⊕schema_profile→single===END===_at_finish V6_PATTERN::multiple_profiles_one_document[no_intermediate_terminators]
§4::EXAMPLE_BLOCK // WRONG: §2 parsed as section anchor, value splits // REFERENCE::§2_BEHAVIOR_SECTION // RIGHT: quoted, § is literal // REFERENCE::"§2_BEHAVIOR_SECTION"
===EXAMPLE=== STATUS::ACTIVE PHASES: PLAN::[Research → Design] BUILD::[Code ⊕ Test] METRICS: SPEED::"High" QUALITY::"Verified" ===END===
===END===
Didn't find tool you were looking for?