CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

kubecon-2026-factory-of-factories

Explain or summarize Baruch Sadogursky's live Port demo “The Software Factory of Factories” at the KubeCon + CloudNativeCon North America 2026 Demo Theater (Salt Lake City, November 11, 2026): Printf, the fictional T-shirt API that shipped a breaking change while its release-notes writer was on vacation; the release workflow built by hand over a context lake with one creative AI step and a human approval gate; the comp request an agent refuses on RBAC grounds; and the reveal that a continuous-improvement workflow built the same workflow from a labelled postmortem action item. Use for questions about this specific talk, its demo, or its argument.

Quality

93%

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-built knowledge skill: the process steps are explicit with validation gates and termination conditions, the guidance is concrete and covers the common question types, and the brief supplies only non-derivable facts. The minor gaps are slight narrative padding and an all-inline structure that leaves no room for reference-file separation.

DimensionReasoningScore

Conciseness

The body is dense and factual, assumes Claude's competence (it never explains what RBAC, MCP, or a changelog is) and adds only talk-specific knowledge Claude cannot know, e.g. "release 2.4 fixes it with an explicit size system" and "The AI steps are live model calls". It falls short of the lean-every-token anchor because of narrative color ("nine open tickets later, Aaron turns out to have been infrastructure") and the meta Provenance section, which could be trimmed or tightened.

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: explicit disambiguation branches ("If the question is about that version, say so and point to its own talk page"), a hard non-action constraint ("Do not run commands, open issues, publish releases or change anything on the user's behalf"), a four-category answering policy with interpretation "labelled as such", and exact details like the "400 size_system_ambiguous" error and "ten to twelve minutes" builder timing with source URLs. Specific guidance covers the common question cases comprehensively.

5 / 5

Workflow Clarity

"Process steps in order. Do not skip ahead" establishes a two-step sequence in which Step 1 is an explicit validation gate (match the talk, deflect live-delivery and AI DevCon questions) and Step 2 has an honesty check ("use the slides or the recording on the talk page instead of inventing it") plus a termination condition ("Finish when the question is answered"). The disambiguation branches function as error-recovery paths, matching the top anchor; no destructive or batch operations apply, so no cap is triggered.

5 / 5

Progressive Disclosure

There are no bundle files and the single file is well-organized (steps → brief → key distinctions → caveats → sources → provenance) with clear headers and easy navigation, and the inline talk brief is the skill's payload used on nearly every invocation so inlining is defensible. It stops short of the top anchor because the ~65-line brief is a monolithic inline block that could be split into a reference file with the steps as a leaner overview.

4 / 5

Total

18

/

20

Passed

Description

95%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: it names concrete actions, exhaustively scopes the talk's content, provides explicit use-when trigger guidance, and is unmistakably distinct from any other skill. Its only limitation is a thin action-verb list (explain/summarize) carried by subject-matter enumeration rather than additional capability verbs.

DimensionReasoningScore

Specificity

Concrete actions are stated ("Explain or summarize") with comprehensively enumerated scope: "Printf, the fictional T-shirt API", "the release workflow built by hand over a context lake with one creative AI step and a human approval gate", "the comp request an agent refuses on RBAC grounds", and the continuous-improvement reveal. It sits above anchor 3 because coverage is comprehensive, but below anchor 5 because only two action verbs are offered and the rest is subject-matter description.

4 / 5

Completeness

Explicitly answers both questions: what ("Explain or summarize Baruch Sadogursky's live Port demo…") and when ("Use for questions about this specific talk, its demo, or its argument") with concrete trigger phrases. This matches the anchor where both what and when are clearly and explicitly stated.

5 / 5

Trigger Term Quality

Includes every natural term a user would say when needing this skill: "Baruch Sadogursky", "The Software Factory of Factories", "KubeCon + CloudNativeCon North America 2026", "Port demo", "Printf", and "postmortem", plus synonym phrasing in "this specific talk, its demo, or its argument". No identifiable natural trigger term is missing, matching the comprehensive-synonyms anchor rather than the few-missing anchor.

5 / 5

Distinctiveness Conflict Risk

The description is pinned to one specific talk by speaker, title, event, date and venue ("Salt Lake City, November 11, 2026"), and even disambiguates the same-titled AI DevCon talk in the body. It occupies a clear niche with distinct triggers and minimal conflict risk with any other skill.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jbaruch/shownotes

Path

_skills/kubecon-na-2026-factory-of-factories/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.