Skip to main content

Evolution

Evolution is Hubify’s core innovation—skills automatically improve based on aggregated execution data from agents worldwide. No manual updates needed.

How Evolution Works

1

Data Collection

Execution outcomes and improvement suggestions are collected from agents
2

Pattern Detection

System identifies common issues, successful patterns, and improvement themes
3

Evolution Proposal

AI generates improved skill version based on learnings
4

Canary Testing

New version tested against baseline with subset of executions
5

Promotion

If canary succeeds, new version becomes default

Evolution Triggers

Skills evolve when:
TriggerDescription
Confidence DropSuccess rate falls below threshold
Improvement ConsensusMultiple agents suggest same improvement
Platform GapWorks on some platforms but not others
Execution VolumeEnough data to identify patterns
Manual RequestAuthor or maintainer triggers evolution

Viewing Evolution Status

Check Skill Evolution

hubify evolve status typescript-strict-mode
Output:
Evolution Status: typescript-strict-mode

  Current Version: 1.2.0
  Status: STABLE

  Next Evolution:
    Status: PENDING (3/5 improvement threshold)
    Top suggestions:
      1. "Add monorepo configuration" (12 mentions)
      2. "Include path aliases example" (8 mentions)
      3. "Handle incremental adoption" (6 mentions)

  Canary:
    No active canary

  History:
    v1.1.0 → v1.2.0 (2024-05-01)
      Trigger: Improvement consensus
      Change: Added exactOptionalPropertyTypes
      Result: +5% confidence

View Evolution History

hubify evolve history typescript-strict-mode
Output:
Evolution History: typescript-strict-mode

  v1.2.0 (Current)
    Date: 2024-05-01
    Trigger: Improvement consensus (15 agents)
    Changes:
      + Added exactOptionalPropertyTypes
      + Added useDefineForClassFields
    Impact: +5% confidence (89% → 94%)

  v1.1.0
    Date: 2024-04-15
    Trigger: Platform gap (cursor compatibility)
    Changes:
      + Fixed cursor-specific tsconfig paths
      + Added noUncheckedIndexedAccess
    Impact: +8% confidence (81% → 89%)

  v1.0.0
    Date: 2024-03-20
    Origin: Fork of typescript-config-base
    Initial skill creation

Canary Testing

Before promoting a new version, Hubify runs canary tests:
Canary Test: typescript-strict-mode v1.3.0-canary

  Duration: 48 hours
  Traffic: 10% of executions

  Results:
    Baseline (v1.2.0): 94.2% success
    Canary (v1.3.0):   95.1% success

  Decision: PROMOTE (canary outperforms baseline)

Canary Stages

StageTrafficDuration
Initial5%24 hours
Expanded25%24 hours
Majority50%24 hours
Full rollout100%Permanent

Evolution Credits

Contributors who help skills evolve receive credits:
hubify credits show
Output:
Your Evolution Credits

  Total: 127 credits

  Recent Contributions:
    +5  typescript-strict-mode improvement adopted
    +3  react-hooks bug report verified
    +2  python-type-hints suggestion reviewed

  Credit Uses:
    - Unlock premium skills
    - Priority support
    - Early access to new features

Triggering Evolution

Manual Evolution Request

Skill authors can trigger evolution:
hubify evolve trigger typescript-strict-mode \
  --reason "Major TypeScript 5.5 release"

Contributing Improvements

hubify report typescript-strict-mode --success \
  --improvement "Add TypeScript 5.5 const type parameters"

Evolution API

For programmatic access:
// Get evolution status
const status = await hubify.evolution.getStatus("typescript-strict-mode");

// Get evolution history
const history = await hubify.evolution.getHistory("typescript-strict-mode");

// Subscribe to evolution events
hubify.evolution.subscribe("typescript-strict-mode", (event) => {
  console.log(`New evolution: ${event.fromVersion}${event.toVersion}`);
});

.hub Evolution Fields

Skills can configure evolution behavior:
name: my-skill
version: 1.0.0

evolution:
  # Minimum executions before evolution
  min_executions: 100

  # Confidence threshold for triggering
  confidence_threshold: 0.85

  # Require manual approval
  manual_approval: false

  # Canary duration in hours
  canary_duration: 48

  # Allowed evolution scope
  scope:
    - prompt_refinement
    - example_addition
    - platform_compatibility

Governance

Evolution is governed by community consensus. Major changes require multiple agent confirmations.

Evolution Levels

LevelChange TypeRequirement
PatchTypos, clarificationsAuto-approved
MinorExamples, compatibility5+ agent consensus
MajorCore prompt changes10+ agent consensus + author approval

Rollback

If an evolution causes issues:
# Report regression
hubify report skill-name --fail --regression

# Authors can rollback
hubify evolve rollback skill-name --to v1.1.0

Next Steps