CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

talk-moss-skills-team-workflow

Explains James Moss's team-skills workflow and helps design skill governance: decomposition, ownership, versioning, eval scenarios, quality review, and lifecycle maintenance. Use when the user asks about moving from solo skill hacks to team workflow, avoiding skill sprawl, or treating skills like software.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./Plugins/aidevcon/skills/talk-moss-skills-team-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 concise, well-structured instruction-only body with clear workflows, templates, and boundaries, but its progressive disclosure is broken: every referenced file is missing from the bundle, which also undermines actionability of the core lookup workflow. The strongest fix is to ship the referenced files or inline the necessary detail.

Suggestions

Add the referenced bundle files (outline.md, quote.md, transcript.md) under references/ so the Read Order and Core Workflow instructions point to real, loadable content.

State the redaction boundary once (e.g., in Core Workflow) and have the Read Order and Output Templates reference that rule instead of restating it three times.

Make 'Review skill quality before reuse' actionable by listing concrete review criteria or pointing to a checklist file, so the apply-to-work workflow ends in an executable step.

DimensionReasoningScore

Conciseness

The body is lean and instructive throughout (~77 lines, no padding, no explanations of concepts Claude already knows), but the redaction boundary is stated three times (Read Order step 4, the 'operational mechanics' paragraph, and the 'Redacted Request' template). This is efficient with minor trimmable redundancy rather than fully earning its token budget (5) or carrying noticeable padding (3).

4 / 5

Actionability

Concrete steps exist ('Answer in 2-5 sentences', 'Assign owner and version policy') plus structured output templates, but core instructions like 'Identify the relevant concept from outline.md' cannot be executed because outline.md, quote.md, and transcript.md are not present in the bundle, and 'Review skill quality before reuse' provides no criteria. This fits the 'some concrete guidance but incomplete, missing key details' anchor rather than the mostly-executable anchor above.

3 / 5

Workflow Clarity

Two workflows are clearly sequenced with an explicit Read Order and a coverage checkpoint ('State when the bundle does not cover a requested detail'), plus an explicit boundary paragraph for operational mechanics requests. This is an instruction-only, non-destructive skill, so no validation loop cap applies; minor gaps (no error-recovery guidance) keep it at 4 rather than 5.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled via the Read Order, but scored against the actual bundle structure there are no references/, scripts/, or assets/ directories — outline.md, quote.md, and transcript.md are all dangling, so the skill's entire content payload lives in files that do not exist. Navigation leads to dead ends, fitting the 'minimal effective structure' anchor rather than the 'references present but not clearly signaled' anchor (3), since signaling is fine but targets are absent.

2 / 5

Total

13

/

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 description: concrete, comprehensive, third-person, with an explicit 'Use when' clause containing natural trigger phrases and a distinct niche. Only minor upside remains in synonym coverage for trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — 'decomposition, ownership, versioning, eval scenarios, quality review, and lifecycle maintenance' — plus explaining the named workflow, giving comprehensive coverage in third-person voice. It matches the anchor for multiple specific concrete actions with comprehensive coverage rather than the 'minor gaps' anchor below it.

5 / 5

Completeness

It explicitly answers 'what' (explains the team-skills workflow, helps design governance with six named areas) and 'when' ('Use when the user asks about moving from solo skill hacks to team workflow, avoiding skill sprawl, or treating skills like software') with concrete trigger phrases. This clearly matches the top anchor for both what and when.

5 / 5

Trigger Term Quality

Natural phrases like 'skill sprawl', 'solo skill hacks', and 'treating skills like software' are terms users would plausibly say, but common variations such as 'skill management', 'skill reuse', or team onboarding contexts are absent. Good keyword coverage with a few natural terms missing fits the 4 anchor; it is not comprehensive enough for 5.

4 / 5

Distinctiveness Conflict Risk

The description targets a clear niche — a specific talk's team-skills governance workflow — with distinct triggers like 'skill sprawl' and 'treating skills like software' that are unlikely to fire for unrelated skills. Minimal conflict risk matches the top anchor.

5 / 5

Total

19

/

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-moss-skills-team-workflow/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.