Skip to content

cli: --kind rejects hyphen/case variants that algorithm names already accept (skill-library, SKILL_LIBRARY) #882

Closed

Description

@Birfy

Phenomenon

agentdescent algorithms list --kind skill-library, init --kind SKILL_LIBRARY, and algorithms run … --kind skill-dir fail, even though algorithm names (archive-selection, GEPA) and parameter names (batch-size, NOISE_BAND) already fold case and -/_. Hosts and users following CLI-style hyphens (or shouting a constant) hit a hard reject instead of the card list or a starter spec.

Evidence

On current main (b37fa40c):

skil_library (a near-miss typo) also lists every kind and does not say did you mean 'skill_library'?, unlike unknown algorithm / parameter names (#874, #876).

Expected

A --kind / spec kind that matches exactly one of text, skill_dir, skill_library, agent_dir, agent_code, plugin, policy_slot once case and -/_ are ignored resolves to that name (skill-library → skill_library, SKILL_DIR → skill_dir). Written specs and algorithms list/run/MCP list_algorithms use the canonical name. When the value is still unknown and is a close match (difflib, cutoff 0.75) to exactly one kind, append ; did you mean 'skill_library'?. No guess for unrelated names like nope.

Acceptance

  • algorithms list --kind skill-library and --kind SKILL_LIBRARY list the same cards as --kind skill_library
  • init --kind skill-library writes "kind": "skill_library" (same tree seeding as the canonical flag)
  • algorithms run / MCP algorithm_spec / list_algorithms accept the same aliases
  • A spec "kind": "skill-library" composes as skill_library
  • skil_library (or --kind skil_library) ends with did you mean 'skill_library'?; nope does not guess
  • changelog.d fragment

Non-goals

Risk hint

T1/T2 (CLI / spec kind validation only; no evolve-loop change).

Related

#874 (algorithm-name near-miss), #876/#877 (parameter-name fold + near-miss), #696 (algorithm-name aliases).

Activity

  1. added
    bugSomething isn't working
    area:cliThe agentdescent command line (cli.py, doctor, plan/evolve/status/apply)
    agent-readyTriaged spec: an agent may take it. Set by a maintainer or the maintenance routine only
    on Nov 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-readyTriaged spec: an agent may take it. Set by a maintainer or the maintenance routine onlyarea:cliThe agentdescent command line (cli.py, doctor, plan/evolve/status/apply)bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions