Skip to content

[computeSkillEffectiveness / retro analyst input bundle] The skillEffectiveness signal's attribution window (50 stories) #423

Description

@jackmcintyre

Problem
The skillEffectiveness signal's attribution window (50 stories) retains invocation records from skills that were retired and removed from disk during the command-surface simplification (flow:author, flow:judge, flow:status, flow:board, crew:board, flow:accept-proposal). These ghost entries appear with 0 effectiveness_ratio in the per_skill map and are structurally indistinguishable from active skills that fired but produced no useful work. A retro analyst following the skill-effectiveness discipline would incorrectly draft skill-retire proposals for skills that have already been deleted. The current cycle bundle contained 6 such ghost entries, each with 0 useful_fire_count.

Tool area
computeSkillEffectiveness / retro analyst input bundle

Suggested direction
Filter per_skill entries to only those whose skill_path resolves to an installed skill file on disk at the time the effectiveness helper runs, or tag each entry with an installed boolean flag so the retro analyst can skip uninstalled skills without having to probe the filesystem.

Trigger
retro-analyst / cycle-end retro


Filed from a Flow cycle-end retrospective maintainer-finding (auto-generated content; submitted with operator approval).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions