feat(skill): add skill protocol and metadata #295

Closed
opened 2026-02-22 23:41:01 +00:00 by freemo · 0 comments
Owner

Metadata

  • Commit: feat(skill): add skill protocol and metadata
  • Branch: feature/m3-skill-protocol

Subtasks

  • Define Skill protocol interface, SkillMetadata, SkillResult, and SkillError types in src/cleveragents/skills/protocol.py.
  • Add SkillDefinition model that references Tool Registry names and optional inline tool definitions.
  • Add error mapping helpers to normalize tool failures into SkillError payloads.
  • Require explicit writes/read_only metadata on skills and propagate to ToolRuntime gating.
  • Add schema validation for inputs/outputs in SkillDefinition to match Tool Registry schemas.
  • Add docs/reference/skills_protocol.md describing metadata, tool composition, and JSON schema rules.
  • Tests (Behave): Add features/skill_protocol.feature for metadata validation and error capture.
  • Tests (Robot): Add robot/skill_protocol.robot smoke tests.
  • Tests (ASV): Add benchmarks/skill_protocol_bench.py for validation throughput.
  • Verify coverage >=97% via nox -s coverage_report. If coverage is <97% then review the current unit test coverage report at build/coverage.xml and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun nox -s coverage_report to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
  • Run nox (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Section: ### Section 5: Actors, Skills & Tool Execution [WORKSTREAM C - Aditya Lead]
Status: Completed

## Metadata - **Commit**: `feat(skill): add skill protocol and metadata` - **Branch**: `feature/m3-skill-protocol` ## Subtasks - [x] Define Skill protocol interface, SkillMetadata, SkillResult, and SkillError types in `src/cleveragents/skills/protocol.py`. - [x] Add `SkillDefinition` model that references Tool Registry names and optional inline tool definitions. - [x] Add error mapping helpers to normalize tool failures into SkillError payloads. - [x] Require explicit `writes`/`read_only` metadata on skills and propagate to ToolRuntime gating. - [x] Add schema validation for `inputs`/`outputs` in SkillDefinition to match Tool Registry schemas. - [x] Add `docs/reference/skills_protocol.md` describing metadata, tool composition, and JSON schema rules. - [x] Tests (Behave): Add `features/skill_protocol.feature` for metadata validation and error capture. - [x] Tests (Robot): Add `robot/skill_protocol.robot` smoke tests. - [x] Tests (ASV): Add `benchmarks/skill_protocol_bench.py` for validation throughput. - [x] Verify coverage >=97% via `nox -s coverage_report`. If coverage is <97% then review the current unit test coverage report at `build/coverage.xml` and use it to write new Behave based unit tests to improve code coverage. Specifically, write Behave style unit tests that are descriptively named and specifically improves coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `nox -s coverage_report` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [x] Run `nox` (all default sessions, including benchmark), fix any errors if needed ensuring nox passes across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. **Section**: ### Section 5: Actors, Skills & Tool Execution [WORKSTREAM C - Aditya Lead] **Status**: Completed
freemo added this to the v3.1.0 milestone 2026-02-22 23:41:01 +00:00
freemo self-assigned this 2026-02-22 23:41:01 +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#295
No description provided.