CtrlK
BlogDocsLog inGet started
Tessl Logo

talk-foxwell-reinvention-dev-team

Assists with questions about Hannah Foxwell's talk 'The Reinvention of the Dev Team'. Use when a user asks about Foxwell's arguments on agentic software development, engineering team composition, AI-driven velocity, dev-to-PM ratios, the three anchors (build something worth building, speed requires safety, people matter), the Keep/Trash/Try inventory, on-call sustainability, broken-comb skills, or wants to audit their own team against Foxwell's framework.

72

Quality

88%

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

The canonical home for this skill is ainativedev/aidevcon-2026-ldn

SKILL.md
Quality
Evals
Security

Quality

Content

77%Scale 1-3

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

This is a well-structured reference/lookup skill with strong actionability and workflow clarity. The grounding rules and lookup workflow provide clear, enforceable constraints that prevent hallucination and ensure faithful representation of source material. The main weaknesses are minor: slight verbosity in example responses and a somewhat disconnected introduction of quotes.md that could be better integrated into the primary workflow.

Suggestions

Integrate the quotes.md reference into the main lookup workflow (e.g., add a step between Locate and Read: 'Check quotes.md for pre-extracted highlights before reading full transcript sections').

Tighten the example responses section — consider showing a brief concrete output snippet rather than describing the expected approach in prose.

DimensionReasoningScore

Conciseness

The skill is reasonably efficient but includes some unnecessary elaboration. The example responses section, while helpful, could be more concise — the expected approach descriptions are somewhat verbose. The grounding rules and lookup workflow are well-structured but slightly repetitive (e.g., rules 4-5 overlap with edge-case handling).

2 / 3

Actionability

The skill provides a clear, concrete lookup workflow (Locate → Read → Quote → Cite), explicit grounding rules with specific do/don't instructions (e.g., never put quotation marks around paraphrased content), and two worked example responses showing expected format. The guidance is specific and directly executable.

3 / 3

Workflow Clarity

The 4-step lookup workflow is clearly sequenced and serves as a validation checkpoint process — locate before reading, read before quoting, cite for verification. Edge-case handling covers multi-section spans and ambiguous questions with explicit instructions. The grounding rules enforce verification (check transcript before answering, say so if claim isn't found).

3 / 3

Progressive Disclosure

The skill references three companion files (outline.md, transcript.md, quotes.md) with clear roles, which is good structure. However, no bundle files were provided to verify these references exist, and quotes.md is introduced only at the very end in a somewhat disconnected section rather than being integrated into the lookup workflow where it logically belongs. The relationship between quotes.md and the main workflow could be clearer.

2 / 3

Total

10

/

12

Passed

Description

100%Scale 1-3

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

This is an excellent skill description that clearly defines its narrow scope (a specific talk by a specific person), lists numerous concrete concepts and frameworks as trigger terms, and includes an explicit 'Use when' clause with diverse trigger scenarios. The description is well-structured, uses third person voice, and would be highly distinguishable from any other skill in a large collection.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions and concepts: answering questions about agentic software development, engineering team composition, AI-driven velocity, dev-to-PM ratios, three anchors framework, Keep/Trash/Try inventory, on-call sustainability, broken-comb skills, and auditing teams against the framework.

3 / 3

Completeness

Clearly answers both 'what' (assists with questions about Foxwell's talk and its specific concepts) and 'when' (explicit 'Use when' clause listing numerous trigger scenarios including asking about specific arguments, frameworks, or wanting to audit their team).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms a user would say: 'Hannah Foxwell', 'Reinvention of the Dev Team', 'agentic software development', 'dev-to-PM ratios', 'broken-comb skills', 'Keep/Trash/Try inventory', 'three anchors', 'on-call sustainability'. These are highly specific and natural keywords someone familiar with this talk would use.

3 / 3

Distinctiveness Conflict Risk

Extremely distinctive — it's scoped to a specific person's specific talk with highly unique trigger terms like 'Hannah Foxwell', 'Reinvention of the Dev Team', 'Keep/Trash/Try inventory', and 'broken-comb skills'. Virtually no risk of conflicting with other skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
AINativeDev/aidevcon-2026-ldn
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.