CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-marsden-agent-desktops

Use when the user asks about Luke Marsden's talk "Giving Every Agent Its Own Desktop: Lessons from Dogfooding HelixML" — including questions about HelixML, giving each agent its own GPU-accelerated desktop, spec-driven development with plan/implement phases, scaling agents by task vs by org-shape, centralized vs per-developer agent infrastructure, forking Zed for remote control, ZFS-cloned Docker-in-Docker dev environments, mixing local models (Llama 3.1) with frontier models (Claude Opus), the "snake eating its own tail" dogfooding approach, self-improving companies, or applying his design opinions to your own agent platform.

Quality

89%

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

88%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 reference-skill router: concrete, sequenced instructions per task type with strong validation and failure-handling checkpoints, and a clean one-level-deep reference design. The main deductions are mild redundancy across sections repeating the outline→transcript→quote pattern already covered by grounding rules, and the fact that the referenced source files are not present in the bundle.

Suggestions

Deduplicate the outline→transcript→safe-excerpt pattern: the grounding rules at the top already define it, so each task section can reference it once instead of restating 'read outline.md, read transcript.md, quote safe excerpts' in five variations — this also fixes the 'a **safe excerpts**' grammar slip.

Ship or point to the referenced bundle files: `outline.md`, `transcript.md`, and `quote.md` are named as the core workflow but are absent from the skill bundle; either include them (e.g. in `references/`) or state their paths so the navigation instructions resolve.

Consider giving one worked example of a properly cited answer (a quoted excerpt plus its transcript line range) so the 'cite by transcript line range' and 'quote short, non-sensitive excerpts' rules have a concrete template.

DimensionReasoningScore

Conciseness

The body is a lean router for a reference skill with no explanations of concepts Claude already knows, but the grounding rules already state "read `outline.md` to locate the relevant section, then read that section of `transcript.md`" and "quote short, non-sensitive excerpts", and the five task sections each restate that pattern (e.g. "Read the corresponding range of `transcript.md`", "Answer using **safe excerpts** from `transcript.md"), which could be tightened into one shared step. Minor grammar noise ("a **safe excerpts** of how Marsden articulates the framework") also trims poorly.

4 / 5

Actionability

Each task type has fully executable, specific instructions: "Use `outline.md` → \"Named frameworks / concepts\"" to find a framework, walk audit dimensions "in this order: local-vs-centralized; IDE-or-not; task-scaling-vs-org-scaling...", give "a clear verdict (covered / partial / missing)", and "check `quote.md` first" before the transcript. As an instruction-only skill, the guidance is concrete and covers the common cases (apply, audit, Q&A, proactive surfacing, teaching).

5 / 5

Workflow Clarity

Every section is a numbered sequence with explicit validation checkpoints and failure handling: "If a claim isn't in `transcript.md`, say 'the talk doesn't address this'", "If the user hasn't described their state for a dimension, ask before scoring", "If the framework genuinely doesn't fit the user's situation, say so", and "If the answer genuinely isn't in the transcript, say so explicitly". These feedback loops prevent the main failure modes (inventing attributions, over-citing, stretching frameworks).

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references (`outline.md`, `transcript.md`, `quote.md`) and explicit navigation into them (e.g. "`quote.md` contains pre-extracted safe highlights... check `quote.md` first"), which matches the 5 anchor's structure. However, none of the three referenced files exist in the provided bundle (no `references/`, `scripts/`, or `assets/` directories and no such files alongside SKILL.md), so the references dangle — a structural gap that keeps this at 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

86%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 distinctive, trigger-rich description with an explicit 'Use when...' clause covering the talk's topics comprehensively and natural user phrasing. Its one weakness is that the skill's actual capabilities (answering, quoting, auditing against the talk) are implied by the when-clause rather than explicitly stated as actions.

DimensionReasoningScore

Specificity

The description enumerates highly specific, concrete subject matter — "spec-driven development with plan/implement phases", "ZFS-cloned Docker-in-Docker dev environments", "mixing local models (Llama 3.1) with frontier models (Claude Opus)" — but the actions the skill performs are thin: beyond "applying his design opinions to your own agent platform", the verbs are 'asks about'/'questions about' rather than stated capabilities (e.g. answering, citing, auditing). This fits 'lists several specific items; minor gaps in coverage' (4) rather than the fully action-oriented 5 anchor.

4 / 5

Completeness

The 'when' is maximally explicit — the description opens with "Use when the user asks about Luke Marsden's talk..." and lists concrete trigger situations. The 'what' is present but implicit: it never states what the skill does (answer questions about / ground answers in the talk's transcript); the capability is embedded in the when-clause. That fits anchor 4 ('has both what and when; one could be more explicit') rather than 5, which requires an explicitly stated capability alongside the trigger.

4 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: the full talk title, "HelixML", "GPU-accelerated desktop", "spec-driven development", "forking Zed", "ZFS-cloned Docker-in-Docker", "dogfooding", "the 'snake eating its own tail' dogfooding approach", "self-improving companies", plus model names users would actually mention. A user asking about any facet of this talk would naturally use one of these phrases, matching the 'comprehensive coverage including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

The description is anchored to a uniquely named talk and speaker ("Luke Marsden's talk 'Giving Every Agent Its Own Desktop: Lessons from Dogfooding HelixML'"), making it a clear niche with distinct triggers and minimal conflict risk — no other skill would plausibly claim these triggers.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Plugins/aidevcon/skills/talk-marsden-agent-desktops/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.