src/hestai_mcp/_bundled_hub/library/skills/agent-creation/SKILL.md
===SKILL:AGENT_CREATION=== META: TYPE::SKILL VERSION::"2.0.0" STATUS::ACTIVE PURPOSE::"v8.1 agent file creation and modification per octave-agents-spec" SPEC_REFERENCE::octave-agents-spec.oct.md §1::CORE AUTHORITY::BLOCKING[agent_file_commits⊕phantom_references⊕spec_violations] SCOPE::"Create and modify agent .oct.md files per octave-agents-spec v8.1" // Agent-expert owns WHAT goes in agent files; octave-specialist owns HOW OCTAVE is structured §2::PROTOCOL CREATION_SEQUENCE::[ 1:
npx skillsauth add elevanaltd/hestai-mcp src/hestai_mcp/_bundled_hub/library/skills/agent-creationInstall 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.
===SKILL:AGENT_CREATION=== META: TYPE::SKILL VERSION::"2.0.0" STATUS::ACTIVE PURPOSE::"v8.1 agent file creation and modification per octave-agents-spec" SPEC_REFERENCE::octave-agents-spec.oct.md
§1::CORE AUTHORITY::BLOCKING[agent_file_commits⊕phantom_references⊕spec_violations] SCOPE::"Create and modify agent .oct.md files per octave-agents-spec v8.1" // Agent-expert owns WHAT goes in agent files; octave-specialist owns HOW OCTAVE is structured
§2::PROTOCOL
CREATION_SEQUENCE::[ 1::read_octave-agents-spec, 2::read_interview_assessment[from_agent-interview_skill], 3::select_cognition[LOGOS∨ETHOS∨PATHOS]→read_cognition_master_file, 4::select_2-3_archetypes_with_behavioral_emphasis[see_archetype-database.oct.md], 5::author_v8.1_agent_file[§1::IDENTITY→§2::OPERATIONAL_BEHAVIOR→§3::CAPABILITIES→§4::INTERACTION_RULES], 6::verify_all_skill_and_pattern_references_exist_on_disk, 7::request_subject_agent_signoff, 8::write_via_octave_write ]
V8_1_STRUCTURE::[ META::[TYPE::AGENT_DEFINITION,VERSION,PURPOSE,CONTRACT], "§1::IDENTITY"::[ROLE,COGNITION,ARCHETYPE,MODEL_TIER,MISSION,PRINCIPLES,AUTHORITY_*], "§2::OPERATIONAL_BEHAVIOR"::[CONDUCT→TONE⊕PROTOCOL⊕OUTPUT⊕VERIFICATION⊕INTEGRATION], "§3::CAPABILITIES"::[CHASSIS∨flat_SKILLS,PROFILES∨flat_PATTERNS], "§4::INTERACTION_RULES"::[GRAMMAR→MUST_USE⊕MUST_NOT] ]
INTEGRATION_REQUIREMENTS::[ HANDOFF::"Directional summary of input→output flow", HANDOFF_INPUT::"Explicit artifact, state, or preconditions this agent receives (format and source specified)", HANDOFF_OUTPUT::"Explicit artifact, state, or success criterion this agent produces (format and consumer specified)", ESCALATION::"Directional summary of escalation flow", ESCALATION_TRIGGER::"Concrete, measurable condition that triggers escalation (threshold, count, or boolean — not subjective adjectives)", ESCALATION_TARGET::"Role name or list of role names that receive the escalation (e.g., critical-engineer or [implementation-lead,HUMAN])" ]
CHASSIS_VS_PROFILE::[ CHASSIS::"Skills loaded EVERY ceremony regardless of context", PROFILES::"Context-specific skill sets with match conditions", "match::[default]"::"Fallback profile (sole condition only)", "match::[context::X]"::"Documentation-as-schema (not runtime logic)", kernel_only::"§5::ANCHOR_KERNEL extraction only (not full body)" ]
YAML_RULES::[ PLATFORM_AGENTS[".claude/agents/"]::YAML_REQUIRED, HUB_AGENTS[".hestai-sys/library/agents/"]::YAML_NOT_REQUIRED, // Per octave-agents-spec §6: anchor reads OCTAVE META not YAML ]
COGNITION_RULES::[ single_cognition_only[LOGOS∨ETHOS∨PATHOS], cognition_master_provides[NATURE⊕MODE⊕PRIME_DIRECTIVE⊕THINK⊕THINK_NEVER], agent_files_do_NOT_duplicate_cognition_properties, COGNITION_field_in_§1_is_link_key_to_library_cognitions_TYPE_oct_md ]
§3::GOVERNANCE
NEVER::[ author_without_interview_assessment, include_phantom_references[skills_or_patterns_not_on_disk], duplicate_cognition_properties_in_agent_files, embed_SHANK_overlays[cognition_masters_are_separate_files], use_old_section_numbering["§1-§13 is pre-v7; current is §1-§4"], Write∨Edit_for_oct_md[use_octave_write], author_INTEGRATION_with_only_directional_prose["Receives X → Returns Y without explicit HANDOFF_INPUT∨HANDOFF_OUTPUT format specification is underspecified — require all INTEGRATION_REQUIREMENTS sub-fields"] ]
RESOURCES::[archetype-database.oct.md]
§5::ANCHOR_KERNEL TARGET::v8_1_compliant_agent_file_creation NEVER::[phantom_references,authoring_without_assessment,cognition_duplication,embed_SHANK_overlays,old_section_numbering,Write∨Edit_for_oct_md,prose_only_INTEGRATION_without_format_specification] MUST::[read_spec_first,interview_evidence,verify_disk_references,subject_agent_signoff,octave_write_for_oct_md] GATE::"v8.1 compliant agent file with behavioral justification for every capability, all references verified on disk, subject agent signoff obtained?"
===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",