CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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).

Quality

83%

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

75%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-organized, code-first reference that is executable and easy to navigate, with genuinely useful bundle files correctly linked one level deep. The main improvements are removing the duplicated agent-as-tool section, fixing the small code gaps (missing Request import, stub helpers), and moving the common-patterns detail into references to slim the main file.

Suggestions

Merge the duplicate agent-as-tool examples from 'Tools' and 'Handoffs' into a single section and cross-reference it.

Fix the FastAPI example (import Request from fastapi) and either define or flag load_session/save_session as user-provided helpers.

Move the Common Patterns (session management, FastAPI endpoint) and the model-provider table into a reference file, keeping SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is dominated by lean, runnable code with almost no concept-explaining prose — it does not explain what an SDK or MCP is, and tables carry parameter/provider data compactly. It is not anchor 5 because of avoidable duplication: the agent-as-tool pattern appears twice (under 'Tools > Agent as Tool' and 'Handoffs > Agent-as-Tool Pattern') with near-identical examples, and both streaming APIs are each shown in full in both languages.

4 / 5

Actionability

Nearly all guidance is executable copy-paste code: install commands, the API-key export, DedalusRunner usage in both languages, tool definitions, structured-output parsing, streaming, MCP slugs, and a FastAPI SSE endpoint. It falls short of anchor 5 on small gaps: the FastAPI example uses 'Request' without importing it, and 'load_session'/'save_session' (session management) and 'db.query' (async tool example) are undefined stubs the user must fill in.

4 / 5

Workflow Clarity

The getting-started path is clear and correctly ordered (install → set DEDALUS_API_KEY → construct runner → run), and each feature section is an unambiguous, self-contained recipe; no destructive or batch operations exist that would require validation checkpoints. It does not reach anchor 5 because there is no error-handling/recovery guidance at all (e.g., what happens when tool execution fails, maxSteps is exceeded, or a provider rejects the request), leaving minor gaps in checkpoints.

4 / 5

Progressive Disclosure

Structure is good: clear section headers, and a References section pointing to three real bundle files (references/tools.md, references/structured-outputs.md, references/authentication.md) that are one level deep with no nested references. It is not anchor 5 because the main file still carries substantial detail that could be split out — the full Common Patterns code (session management, FastAPI endpoint) and the model-provider table are inline rather than in references, making SKILL.md heavier than an overview.

4 / 5

Total

16

/

20

Passed

Description

83%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 description that names the domain, enumerates concrete capabilities with specific class/library names, and includes an explicit 'Use when' clause. Its main weaknesses are a single-variant trigger clause and missing common spellings/synonyms (the hyphenated package name 'dedalus-labs', 'tool calling') that would improve recall.

Suggestions

Add trigger variations to the when clause, e.g. 'or when the user mentions Dedalus, dedalus-labs, DedalusRunner, or agent orchestration/tool calling with the SDK'.

Include the published package spelling 'dedalus-labs' (npm/pip) alongside 'dedalus_labs' so the description matches how users refer to the package.

DimensionReasoningScore

Specificity

The description lists multiple concrete, named actions: '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', comprehensively covering the SDK's feature surface. This matches the anchor-5 example (multiple specific concrete actions, comprehensive coverage) rather than anchor 4, which requires minor coverage gaps.

5 / 5

Completeness

Both parts are explicit: 'Use when building AI-powered applications with the Dedalus SDK (dedalus_labs)' answers when, and the enumerated capability list answers what. Not anchor 5 because the when clause offers a single trigger phrasing, whereas anchor-5 examples enumerate multiple concrete trigger variants ('or when the user mentions...'); not anchor 3 since the when is explicit, not merely implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'building AI-powered applications', 'Dedalus SDK', 'agents', 'streaming', 'MCP servers', plus concrete provider names (OpenAI, Anthropic, Google, xAI, DeepSeek, Mistral). It falls short of anchor 5 because common variations are missing — the npm/pip package spelling 'dedalus-labs' (vs. 'dedalus_labs'), and synonyms like 'tool calling' or 'function calling'.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — a named third-party SDK with class-level triggers (DedalusRunner, dedalus_labs) — so it is unlikely to fire for unrelated skills. The generic opener 'AI-powered applications' creates only negligible overlap with other LLM-SDK skills, fitting anchor 5 (clear niche, distinct triggers, minimal conflict) rather than anchor 4 (minor overlap risk).

5 / 5

Total

18

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

adamsardo/dedalus-skills

Path

skills/use-dedalus-sdk/SKILL.md

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.