Universal AI skill compiler. Validate a portable skill spec and compile it into MCP, Claude, Gemini, DeepSeek, Meta and browser artifacts.
Three tools with clear verb-noun naming (bridge_targets, validate_skill, compile_skill) and explicit descriptions. All tools have input schemas with type definitions. However, parameter descriptions are minimal or absent, 'spec' parameter lacks guidance on structure/format; 'endpoint' has a description but no validation constraints. Output schemas are not documented. Tool annotations present (readOnlyHint, idempotentHint, openWorldHint) but error handling is absent, no guidance on what happens if validation fails or compilation errors occur. Descriptions are adequate (40-80 chars) but lack WHEN/WHY context for LLM selection.
List supported compilation targets and the current bridge version.
Compile a skill in memory; the endpoint string is embedded, not contacted.
Validate a portable D'AUBE skill specification without persisting it.
Parameter 'spec' lacks description and format guidance. LLMs cannot infer what fields a 'portable D'AUBE skill specification dictionary' requires without explicit documentation of structure, required keys, and example shape.
No output schema documentation. Tools return dict[str, Any] or dict[str, str] but LLMs cannot plan downstream calls without knowing what fields to expect (e.g., does compile_skill return 'artifacts', 'code', 'manifest'?).
No error handling guidance. If validate_skill detects invalid spec or compile_skill fails, tools return exceptions without recovery hints. LLMs need 'Try calling bridge_targets() first to see supported structure' or similar.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Parameter 'endpoint' has a default but no validation constraints. Description says 'endpoint string to embed' but does not specify format (must be valid URL?), length limits, or what happens if malformed.
Tool descriptions lack WHEN/WHY context. 'Validate a portable D'AUBE skill specification' does not explain when to call this vs compile_skill, or what the user should do with validation results.