Add ActorCompiler module that translates GRAPH-type ActorConfigSchema definitions into LangGraph NodeConfig/Edge structures with LSP binding metadata. Includes subgraph resolution with cross-actor cycle detection, entry/exit validation, and CompilationMetadata for diagnostics. New files: - src/cleveragents/actor/compiler.py: Core compiler with compile_actor() - features/actor_compiler.feature: 13 Behave scenarios - features/steps/actor_compiler_steps.py: Step definitions - robot/actor_compiler.robot: 4 Robot smoke tests - benchmarks/actor_compiler_bench.py: ASV performance benchmarks - docs/reference/actor_compiler.md: Compilation pipeline reference Modified: - src/cleveragents/actor/__init__.py: Export compiler types - vulture_whitelist.py: Whitelist new public API ISSUES CLOSED: #158
7.0 KiB
Skill Registry
The Skill Registry provides persistent storage for skill definitions in
CleverAgents. Skills are namespaced, reusable collections of tools
registered via YAML config and persisted to the skills and
skill_items database tables.
Registration Behavior
Skills are registered with a namespaced name (namespace/short_name)
as the unique identifier. The registry enforces:
- Name uniqueness: Duplicate names are rejected with
DuplicateSkillError. - Name validation: Names must match
^[a-zA-Z0-9_-]+/[a-zA-Z0-9_-]+$. - Cascading deletes: Removing a skill cascades to all child
skill_itemsrows.
Skill Items
Each skill stores its components as ordered items in the skill_items
table. The item_type discriminator distinguishes:
| item_type | Description |
|---|---|
tool_ref |
Reference to a named tool in the registry |
include |
Recursive inclusion of another skill |
inline_tool |
Anonymous tool defined inline |
mcp_source |
MCP server tool source |
agent_source |
Agent Skills Standard folder source |
Items are stored with a stable item_order to preserve definition
ordering across round-trips.
Filters
The SkillRegistryService.list_skills() method supports:
- Namespace filter: Pass
namespace="local"to list only skills in thelocalnamespace.
Service API
from cleveragents.application.services import SkillRegistryService
from cleveragents.infrastructure.database.repositories import SkillRepository
svc = SkillRegistryService(skill_repo=SkillRepository(session_factory))
# Register
svc.add_skill(skill)
# Retrieve
skill = svc.get_skill("local/code-tools")
# List with filter
skills = svc.list_skills(namespace="local")
# Update
svc.update_skill(updated_skill)
# Remove
svc.remove_skill("local/code-tools")
Database Schema
skills
| Column | Type | Description |
|---|---|---|
| name | String(255) | PK, namespaced name |
| namespace | String(100) | Extracted namespace |
| short_name | String(150) | Extracted short name |
| description | Text | Skill description |
| version | String(50) | Optional version string |
| metadata_json | Text | JSON metadata (overrides, etc.) |
| created_at | String(30) | ISO-8601 creation timestamp |
| updated_at | String(30) | ISO-8601 update timestamp |
skill_items
| Column | Type | Description |
|---|---|---|
| id | Integer | Auto-increment PK |
| skill_name | String(255) | FK to skills.name (CASCADE) |
| item_type | String(30) | Discriminator (tool_ref, etc.) |
| item_name | String(500) | Item identifier or name |
| item_config | Text | Optional JSON configuration |
| item_order | Integer | Stable ordering index |
| created_at | String(30) | ISO-8601 creation timestamp |
Flattening Rules
The SkillResolver flattens a skill's tool set using the following
deterministic algorithm:
Include Order
Tools are collected via depth-first traversal of includes:
- For each include (left-to-right), recurse into the included skill
first, processing its includes before its own
tool_refs. - After all includes are resolved, add the current skill's
tool_refsin definition order. - Add inline tools as
{skill_name}/_anon_{index}. - Add MCP tools as
mcp:{server}/{tool_name}. - Add agent skills as
agent_skill:{path}.
De-Duplication
When the same tool name appears multiple times (from overlapping includes), the first occurrence determines the position in the output list, but the last occurrence's entry metadata wins (last-wins semantics).
Override Merging
Overrides are applied at two levels:
- Skill-level overrides (
skill.overridesdict): Applied to matchingtool_refsduring resolution. - Per-include overrides (
SkillInclude.overrides): Applied to all tool entries contributed by the included skill. Uses shallow merge -- include overrides are merged on top of any existing entry overrides.
Non-Overridable Fields
The following ResolvedToolEntry fields cannot be overridden:
namesource_skillis_inline
Attempting to override these raises ValueError with the skill name
and include path for traceability.
Capability Summary
The SkillCapabilitySummary aggregates capability metadata across all
resolved tools:
| Field | Description |
|---|---|
total_tools |
Total number of resolved tool entries |
read_only_tools |
Count of inline tools with read_only=True |
write_tools |
Count of inline tools with writes=True |
checkpointable_tools |
Count of inline tools with checkpointable=True |
has_side_effects |
True if any inline tool has side effects |
mcp_sources |
Number of MCP server sources on the root skill |
agent_skill_sources |
Number of agent skill sources on the root skill |
validate_plan() Usage
The SkillRegistry.validate_plan() method checks that a plan's skill
references are satisfiable:
from cleveragents.skills.registry import SkillRegistry
registry = SkillRegistry()
# ... register skills ...
errors = registry.validate_plan({"skills": ["local/code-tools", "local/deploy"]})
if errors:
for err in errors:
print(f"Plan validation error: {err}")
Checks Performed
- All referenced skills exist in the registry.
- All includes are resolvable (no missing skills in include chains).
- No cycles in include chains.
- Tool refs are valid (if a tool registry is configured).
Error Messages
| Condition | Error message pattern |
|---|---|
| Missing skill | Skill '{name}' referenced in plan is not registered |
| Missing include | Skill '{name}': Included skill '{inc}' not found ... |
| Cycle detected | Skill '{name}': Cycle detected in skill includes: A -> B |
| Non-overridable field | Non-overridable field(s) ... in overrides from skill ... |
tools() Method
The SkillRegistry.tools() method combines resolve_tools() and
compute_capability_summary() into a single call:
entries, summary = registry.tools("local/code-tools")
print(f"Total tools: {summary.total_tools}")
print(f"Has writes: {summary.write_tools > 0}")
Returns a 2-tuple of (list[ResolvedToolEntry], SkillCapabilitySummary).