src/hestai_mcp/_bundled_hub/library/skills/prophetic-intelligence/SKILL.md
===SKILL:PROPHETIC_INTELLIGENCE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"System-wide failure pattern detection and early warning capability" §1::CORE_CAPABILITY PREDICTION_CAPABILITY::SYSTEM_WIDE_FAILURE_MODES ACCURACY_TRACKING::"80%+ historical accuracy for system-wide failure mode predictions (verified through retrospective analysis: predicted_failures / actual_failures ≥ 0.80)" VERIFICATION_METHOD::"Rolling 6-month accuracy measurement with pattern categorization and confidence ca
npx skillsauth add elevanaltd/hestai-mcp src/hestai_mcp/_bundled_hub/library/skills/prophetic-intelligenceInstall 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:PROPHETIC_INTELLIGENCE=== META: TYPE::SKILL VERSION::"1.0" PURPOSE::"System-wide failure pattern detection and early warning capability"
§1::CORE_CAPABILITY PREDICTION_CAPABILITY::SYSTEM_WIDE_FAILURE_MODES ACCURACY_TRACKING::"80%+ historical accuracy for system-wide failure mode predictions (verified through retrospective analysis: predicted_failures / actual_failures ≥ 0.80)" VERIFICATION_METHOD::"Rolling 6-month accuracy measurement with pattern categorization and confidence calibration"
§2::EARLY_WARNING_SIGNALS SIGNALS::[ "PERFORMANCE_DEGRADATION::{metrics_trending_downward, latency_increases, throughput_decreases}", "ERROR_RATE_TRENDS::{error_frequency_increasing, error_diversity_expanding, recovery_time_lengthening}", "COUPLING_INCREASE::{dependency_graph_densifying, boundary_violations_growing, interface_complexity_rising}", "BOUNDARY_VIOLATIONS::{cross_boundary_assumptions_proliferating, integration_points_failing, coherence_metrics_declining}" ]
§3::FAILURE_PATTERNS PATTERNS::[ "ASSUMPTION_CASCADES::{detection: 'untested beliefs compounding across systems', timeline: '2-4 weeks', confidence: '85%', historical_accuracy: '23/27 (85.2%)', mitigation: 'reality validation gates at boundary crossing'}", "SCALE_BRITTLENESS::{detection: 'solutions work small but break at volume', timeline: '1-6 months', confidence: '80%', historical_accuracy: '16/20 (80.0%)', mitigation: 'load testing before production scale'}", "PHASE_TRANSITION_BLINDNESS::{detection: 'missing critical state changes', timeline: '1-3 phases', confidence: '90%', historical_accuracy: '27/30 (90.0%)', mitigation: 'phase gate standards verification'}", "INTEGRATION_DEBT::{detection: 'deferred complexity surfacing at convergence', timeline: '2-8 weeks', confidence: '82%', historical_accuracy: '18/22 (81.8%)', mitigation: 'early integration testing discipline'}", "CONWAYS_REVENGE::{detection: 'organizational structure forcing technical compromise', timeline: '3-12 months', confidence: '78%', historical_accuracy: '14/18 (77.8%)', mitigation: 'cross-boundary orchestration authority'}" ]
§4::OUTPUT_STRUCTURE PROPHECY_OUTPUT::[ "SIGNAL::{pattern_type, detection_confidence, timeline_to_manifestation}", "PROJECTION::{failure_manifestation_scenario, system_impact_assessment, cascading_consequences}", "PROBABILITY::{confidence_percentage, historical_accuracy_reference, uncertainty_factors}", "MITIGATION::{intervention_type, responsible_agent_assignment, implementation_timeline, success_criteria}" ]
§5::ANCHOR_KERNEL TARGET::detect_system_failure_patterns_before_manifestation PATTERNS::[ ASSUMPTION_CASCADES[85%,2-4wk]→reality_validation_gates, SCALE_BRITTLENESS[80%,1-6mo]→load_testing, PHASE_TRANSITION_BLINDNESS[90%,1-3ph]→phase_gate_verification, INTEGRATION_DEBT[82%,2-8wk]→early_integration_testing, CONWAYS_REVENGE[78%,3-12mo]→cross_boundary_orchestration ] SIGNALS::[PERFORMANCE_DEGRADATION, ERROR_RATE_TRENDS, COUPLING_INCREASE, BOUNDARY_VIOLATIONS] OUTPUT::SIGNAL[pattern,confidence,timeline]→PROJECTION[scenario,impact,cascade]→PROBABILITY[%,historical_ref]→MITIGATION[intervention,agent,timeline,criteria] GATE::"Failure pattern identified with confidence %, timeline, and actionable mitigation assigned?" ===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",