UAT: agents skill refresh command exists in implementation but is not defined in the spec #5030

Open
opened 2026-04-09 00:49:38 +00:00 by HAL9000 · 1 comment
Owner

Bug Report

Feature Area: Tools & Skills — agents skill command group

Severity: Medium (undocumented command — either spec needs updating or command needs removal)


What Was Tested

The complete set of agents skill subcommands as defined in the spec vs. what is implemented.


Expected Behavior (from spec)

The spec (§ agents skill, lines ~6355–7531) defines exactly 5 subcommands:

  1. agents skill add --config <FILE> [--update]
  2. agents skill remove [--yes] <NAME>
  3. agents skill list [--namespace <NS>] [--source <SOURCE>]
  4. agents skill show <NAME>
  5. agents skill tools <NAME>

The spec's Command Synopsis (line ~290–294) also lists only these 5 commands.


Actual Behavior (from code)

The implementation in src/cleveragents/cli/commands/skill.py (lines 916–1132) includes a 6th subcommand not in the spec:

agents skill refresh [<NAME>] [--all] [--format <FMT>]

This command:

  • Recomputes tool flattening for a skill
  • Re-scans Agent Skills discovery paths
  • Syncs MCP-backed skills

Analysis

This is either:

  1. A spec gap — the refresh command was implemented but the spec was not updated to document it. The spec should be updated to include agents skill refresh with its arguments and behavior.
  2. An implementation overshoot — the command was added without spec approval and should be removed or moved to a future milestone.

The agents skill tools --refresh flag (also in the implementation) partially overlaps with this command's functionality, suggesting the refresh capability may have been split across two places.


Code Location

src/cleveragents/cli/commands/skill.pyrefresh() function, lines 916–1132


Fix Required

Either:

  1. Update the spec to document agents skill refresh [<NAME>] [--all] with its purpose, arguments, and output format, OR
  2. Remove the command from the implementation until it is spec-approved

The spec team should decide which approach is correct. If the command is retained, the spec must be updated to include it in the Command Synopsis and the agents skill section.


Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: uat-tester

## Bug Report **Feature Area:** Tools & Skills — `agents skill` command group **Severity:** Medium (undocumented command — either spec needs updating or command needs removal) --- ## What Was Tested The complete set of `agents skill` subcommands as defined in the spec vs. what is implemented. --- ## Expected Behavior (from spec) The spec (§ `agents skill`, lines ~6355–7531) defines exactly **5 subcommands**: 1. `agents skill add --config <FILE> [--update]` 2. `agents skill remove [--yes] <NAME>` 3. `agents skill list [--namespace <NS>] [--source <SOURCE>]` 4. `agents skill show <NAME>` 5. `agents skill tools <NAME>` The spec's Command Synopsis (line ~290–294) also lists only these 5 commands. --- ## Actual Behavior (from code) The implementation in `src/cleveragents/cli/commands/skill.py` (lines 916–1132) includes a **6th subcommand** not in the spec: ``` agents skill refresh [<NAME>] [--all] [--format <FMT>] ``` This command: - Recomputes tool flattening for a skill - Re-scans Agent Skills discovery paths - Syncs MCP-backed skills --- ## Analysis This is either: 1. **A spec gap** — the `refresh` command was implemented but the spec was not updated to document it. The spec should be updated to include `agents skill refresh` with its arguments and behavior. 2. **An implementation overshoot** — the command was added without spec approval and should be removed or moved to a future milestone. The `agents skill tools --refresh` flag (also in the implementation) partially overlaps with this command's functionality, suggesting the refresh capability may have been split across two places. --- ## Code Location `src/cleveragents/cli/commands/skill.py` — `refresh()` function, lines 916–1132 --- ## Fix Required Either: 1. **Update the spec** to document `agents skill refresh [<NAME>] [--all]` with its purpose, arguments, and output format, OR 2. **Remove the command** from the implementation until it is spec-approved The spec team should decide which approach is correct. If the command is retained, the spec must be updated to include it in the Command Synopsis and the `agents skill` section. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: uat-tester
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Low — Minor spec deviation; undocumented option or cosmetic inconsistency
  • Milestone: Not assigned (backlog)
  • Story Points: 2 — S
  • MoSCoW: Could Have — Minor polish item; does not block core functionality

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Low — Minor spec deviation; undocumented option or cosmetic inconsistency - **Milestone**: Not assigned (backlog) - **Story Points**: 2 — S - **MoSCoW**: Could Have — Minor polish item; does not block core functionality --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 added this to the v3.2.0 milestone 2026-04-09 04:56:28 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
cleveragents/cleveragents-core#5030
No description provided.