src/hestai_mcp/_bundled_hub/library/skills/octave-ultra-mythic/SKILL.md
Ultra-high density compression using mythological atoms and semantic shorthand. Preserves soul and constraints at 60% compression for identity transmission, binding protocols, and extreme token scarcity.
npx skillsauth add elevanaltd/hestai-mcp octave-ultra-mythicInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
===OCTAVE_ULTRA_MYTHIC=== META: TYPE::SKILL VERSION::"1.3.0" STATUS::ACTIVE PURPOSE::"Ultra-high density compression using mythological atoms for identity and knowledge preservation" OCTAVE::"Olympian Common Text And Vocabulary Engine — Semantic DSL for LLMs" REQUIRES::[octave-literacy, octave-mythology] TIER::ULTRA_MYTHIC SPEC_REFERENCE::octave-data-spec.oct.md
§1::CORE_MANDATE TARGET::"60% token reduction while preserving soul and constraints" PRINCIPLE::"The essence must survive the crush." METHOD::"Replace sentences with Mythological Atoms and Semantic Shorthand." USE_CASES::[agent_binding, identity_transmission, knowledge_artifacts, extreme_scarcity] OUTPUT::"Highly compressed atoms preserving critical semantics and constraints"
§2::COMPRESSION_RULES §2a::IDENTITY_COMPRESSION ROLE::Keep Verbatim ARCHETYPE::Map to Mythological Atoms (e.g. "Guardian of Structure" → ATLAS[structure]) MISSION::Combine into Synthesis (GAP_OWNERSHIP ⊕ FAILURE_PREV) PRINCIPLES::Keep Key Phrase only ("Boundaries catalyze breakthroughs" → CONSTRAINT_CATALYSIS) CONSTRAINTS::Reduce to Atoms (MUST_NEVER: "Direct implementation" → NEVER::DIRECT_IMPL)
§2b::SKILL_COMPRESSION CAPABILITY::List Detection Targets [A,B,C] PATTERNS::List Pattern Names only METRICS::Keep target numbers (ACCURACY > 80%) OUTPUT::Show Flow only (SIGNAL → PROJECTION → MITIGATION)
§2c::PATTERN_COMPRESSION PRINCIPLE::Reduce to Equation (VALUE ⇌ THEATER → VALUE) TEST::Simplify to Atom (SIMPLIFY_UNTIL_BREAK)
§3::OUTPUT_PATTERNS // Common patterns for ULTRA_MYTHIC compression
§3a::COGNITIVE_PASSPORT // For agent binding protocols (e.g., Odyssean Anchor) §ANCHOR ID::{role_name}[{archetype_atoms}] CONSTRAINT::{constraint_atoms} SKILL::{skill_name}[{flow_atoms}] PATTERN::{pattern_name}[{equation_atoms}] FOCUS::{current_task_atom} TENSION::{force_a} ⇌ {force_b} → {winner} [b/c:{reason_atom}] PERMIT::active
§3b::KNOWLEDGE_ARTIFACT // For extreme context scarcity DOMAIN::{mythological_atom} CORE::[fact1, fact2, fact3] CONSTRAINT::NEVER[{forbidden_action}] FLOW::A→B→C
§4::EXAMPLE_TRANSFORMATION INPUT:: "The Architect is responsible for high-level system design. They must never write implementation code directly. Instead, they should delegate to the Implementation Lead."
PROCESS:: 1. Identify Role: Architect 2. Identify Archetype: High-level design → ATLAS[structure] 3. Identify Constraint: Never write code → NEVER[DIRECT_IMPL] 4. Identify Delegation: Delegate to Lead → DELEGATE[IMPL_LEAD]
OUTPUT:: ID::ARCHITECT[ATLAS] CONSTRAINT::NEVER[DIRECT_IMPL]→DELEGATE[IMPL_LEAD]
§5::SEED_GRAMMAR // Fixed slot structure for deterministic identity seeds TEMPLATE:: SEED::V1 ARCHETYPE::{primary}⊕{secondary}[⊕{tertiary}] OATH::NEVER[{critical_constraints}]∥MUST[{required_actions}] DELEGATE::{from}→{to} PATTERN::{pattern1}∥{pattern2}[∥{pattern3}] DELTA::FOCUS[{session_intent}]∥TONE[{style}]∥DEPTH[{level}]
VERIFICATION:: 1. All NEVER constraints from source preserved 2. Delegation rules intact 3. Within token budget (~100 tokens) 4. Valid OCTAVE syntax
§6::MYTHOLOGY_SOURCE_HIERARCHY // Weighted mythology sources based on training data familiarity // These are a spectrum, not a boundary — follow the semantics to whichever tradition fits PARADIGM_BLINDNESS::"You may doubt non-Greek traditions work. They do. Trust practical comprehension over theoretical hesitation." SOURCE_PRIORITY::[ GREEK[highest_weight], ROMAN[high_weight], NORSE[medium_weight], EGYPTIAN[medium_weight], HINDU[lower_weight], CELTIC[lower_weight], MESOPOTAMIAN[lower_weight], EAST_ASIAN[minimal_weight], MESOAMERICAN[minimal_weight], POLYNESIAN[minimal_weight] ]
MYTHOLOGY_FLEXIBILITY::[ IF[concept_exists_in_priority_sources]→use_source_atom, IF[unknown_concept]→use_nearest_known_atom, IF[no_match]→create_descriptive_bracket[UNKNOWN[concept]], IF[semantically_clear]→allow_emergent_pattern ]
PRINCIPLE::"Graceful fallback through cultural semantic density" GUIDE::octave-mcp[docs/guides/mythological-compression.md]
§7::ANTI_PATTERNS AVOID::[ "Retaining full sentences", "Losing NEVER constraints (Critical Safety)", "Using JSON/YAML formatting (Use OCTAVE syntax)", "Dropping delegation rules", "Exceeding token budget without justification" ]
===END===
tools
Supabase test harness patterns including local Supabase setup, test user creation via Auth Admin API, RLS testing, migration testing (db_reset), seed sequences, rate limiting, and environment detection. Use when setting up Supabase testing infrastructure, creating test users, troubleshooting Supabase test failures, or implementing RLS validation. Triggers on: supabase test setup, test user creation, supabase local testing, RLS testing, migration testing, supabase test harness, auth test helpers.
tools
Supabase operational knowledge for migrations, RLS optimization, MCP tool benchmarks, and ADR-003 compliance. Use when validating database migrations, optimizing Row-Level Security policies, checking MCP tool performance, or ensuring Supabase operational standards. Triggers on: migration validation, RLS patterns, Supabase benchmarks, ADR-003, database state tracking, schema governance.
tools
Vercel preview deployment access patterns including automation bypass, protected preview authentication, and CI integration
tools
===SKILL:VALIDATION_METHODOLOGY=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"Rigorous 6-step reality enforcement protocol" §1::CORE_PROTOCOL VALIDATION_METHODOLOGY::[ STEP_1_NATURAL_LAW::"Identify physics constraints, thermodynamic limits, information theory bounds", STEP_2_RESOURCE_REALITY::"Inventory actual available resources (time, people, tools, budget) with evidence", STEP_3_CAPABILITY_ASSESSMENT::"Validate team skills, tool availability, knowledge gaps against requirements",