CtrlK
BlogDocsLog inGet started
Tessl Logo

use-dedalus-sdk

Use when building AI-powered applications with the Dedalus SDK (dedalus_labs)—covers orchestrating agents with DedalusRunner, defining local tools, using structured outputs with Pydantic/Zod schemas, streaming responses, routing via handoffs across models, connecting to MCP servers, and working across providers (OpenAI, Anthropic, Google, xAI, DeepSeek, Mistral).

72

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, executable reference for the Dedalus SDK with strong code coverage in both languages and clean progressive disclosure to real bundle files. The main improvements are removing the duplicated agent-as-tool example and linking references inline near their related sections.

Suggestions

Remove the duplicated 'Agent as Tool' example—it appears under both Tools and Handoffs; consolidate into one to save tokens.

Surface the references inline where their topics appear (e.g., link structured-outputs.md within the Structured Outputs section) instead of only at the end, to improve navigation.

Tighten the Streaming section, which shows three overlapping approaches (.run with stream=True, the for-await loop, and .stream()); clarify which to use when.

DimensionReasoningScore

Conciseness

Mostly efficient with minimal preamble and code-first examples that assume Claude's competence, but the 'Agent as Tool' pattern is demonstrated twice (in Tools and again in Handoffs) and could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript and Python examples for the common cases—runner.run, tools, structured outputs, streaming, and MCP—covering the SDK's main use cases.

5 / 5

Workflow Clarity

Sections are clearly sequenced by feature with parameter tables and a 'When to Use' guide for handoffs; no validation checkpoints are required for this feature-reference skill, but the multi-step handoff flow could be made more explicit.

4 / 5

Progressive Disclosure

A clear References section signals one-level-deep links to real files (tools.md, structured-outputs.md, authentication.md), keeping the body as an overview; references could additionally be surfaced inline where the topics are discussed.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that explicitly pairs a 'Use when' trigger with a comprehensive, concrete list of SDK capabilities and providers. Minor room to add a few more natural user-synonym phrases, but it is otherwise well-constructed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—'orchestrating agents with DedalusRunner', 'defining local tools', 'using structured outputs with Pydantic/Zod schemas', 'streaming responses', 'routing via handoffs', 'connecting to MCP servers'—giving comprehensive coverage of the SDK's capabilities.

5 / 5

Completeness

Explicitly answers both 'what' (the enumerated SDK capabilities) and 'when' via the 'Use when building AI-powered applications with the Dedalus SDK' trigger clause.

5 / 5

Trigger Term Quality

Includes natural terms like 'AI-powered applications', 'Dedalus SDK', 'streaming responses', 'structured outputs', 'MCP servers' and named providers, but a few common user-phrasing synonyms are absent, so it is just below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Tightly scoped to the Dedalus SDK (dedalus_labs) with named providers and specific features, giving a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
adamsardo/dedalus-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.