feat(skill): add skill context and registry #296

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

Metadata

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

Subtasks

  • Implement SkillContext (plan/resource access, sandbox path, change tracker) and SkillRegistry in src/cleveragents/skills/context.py.
  • Wire SkillRegistry to Tool Registry for tool resolution and validation node inclusion.
  • Add context helpers for resolving bound resources and exposing plan metadata.
  • Include change tracking hooks so every skill execution registers a ToolInvocation in ChangeSet.
  • Ensure SkillContext enforces read-only plan restrictions (block write tools when plan is read-only).
  • Add docs/reference/skills_context.md with context fields and helper methods.
  • Tests (Behave): Add features/skill_context.feature for sandboxed access and registry resolution.
  • Tests (Robot): Add robot/skill_context.robot for registry smoke tests.
  • Tests (ASV): Add benchmarks/skill_context_bench.py for registry resolution overhead.
  • 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 context and registry` - **Branch**: `feature/m3-skill-protocol` ## Subtasks - [x] Implement SkillContext (plan/resource access, sandbox path, change tracker) and SkillRegistry in `src/cleveragents/skills/context.py`. - [x] Wire SkillRegistry to Tool Registry for tool resolution and validation node inclusion. - [x] Add context helpers for resolving bound resources and exposing plan metadata. - [x] Include change tracking hooks so every skill execution registers a ToolInvocation in ChangeSet. - [x] Ensure SkillContext enforces read-only plan restrictions (block write tools when plan is read-only). - [x] Add `docs/reference/skills_context.md` with context fields and helper methods. - [x] Tests (Behave): Add `features/skill_context.feature` for sandboxed access and registry resolution. - [x] Tests (Robot): Add `robot/skill_context.robot` for registry smoke tests. - [x] Tests (ASV): Add `benchmarks/skill_context_bench.py` for registry resolution overhead. - [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:02 +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#296
No description provided.