# Octave Literacy

> Fundamental reading and writing capability for the OCTAVE format. Inject this to give an agent basic structural competence without the overhead of full architectural specifications. Triggers on: octav

- Skill: `majiayu000/octave-literacy-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add majiayu000/octave-literacy-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/octave-literacy-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/majiayu000/octave-literacy-2

---


---
name: octave-literacy
description: Fundamental reading and writing capability for the OCTAVE format. Inject this to give an agent basic structural competence without the overhead of full architectural specifications. Triggers on: octave format, write octave, octave syntax, structured output.
allowed-tools: Read
implements: specs/octave-5-llm-core
---

# OCTAVE Literacy Skill

===OCTAVE_LITERACY===
META:
  TYPE::SKILL
  VERSION::"1.1"
  PURPOSE::"Essential syntax and operators for basic OCTAVE competence"
  TIER::LOSSLESS
  SPEC_REFERENCE::octave-5-llm-core.oct.md

§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::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
  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)

  §3b::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

§4::EXAMPLE_BLOCK
  ===EXAMPLE===
  STATUS::ACTIVE
  PHASES:
    PLAN::[Research → Design]
    BUILD::[Code ⊕ Test]
  METRICS:
    SPEED::"High"
    QUALITY::"Verified"
  ===END===

===END===