CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-live-ops

Orchestrate the live-ops team — live-ops-designer, economy-designer, analytics-engineer, community-manager, writer — for a season or live event.

Quality

71%

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 ./.claude/skills/team-live-ops/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

The body is an exceptionally concrete and well-sequenced orchestrator skill: literal prompt contracts, per-agent write targets, explicit parallelism and gate rules, artifact verification, and full error/ethics feedback loops. Its weaknesses are token efficiency — the bounded write-exception is argued three times and Phase 0/active-set sections over-justify — and a monolithic inline structure where policy rationale belongs in a referenced document. Workflow and actionability are near best-in-class.

Suggestions

State the bounded write-exception once (e.g. keep the blockquote under the write-paths table) and reduce the "Output Documents" and "File Write Protocol" restatements to one-line references to it, naming only the phase-specific differences.

Move the team.size collapse rationale and the "enforced but never surfaced" meta-commentary into a reference doc (e.g. alongside .claude/docs/automation-modes.md) and keep a one-line rule plus pointer in SKILL.md — this also improves progressive disclosure.

Tighten the Phase 0 "phase gate" definitional paragraph: define the term once and reference that definition from the Decision Points and team.size sections instead of re-deriving it in each place.

DimensionReasoningScore

Conciseness

Most of the body is load-bearing orchestration guidance, but it is noticeably tightened-past-due in places: the bounded write-exception policy is fully restated three times (the blockquote under the write-paths table, "Output Documents", and "File Write Protocol"), and Phase 0 plus the "Announce the active set" section carry long meta-justification paragraphs ("The collapse is correct...", "a constraint that is enforced but never surfaced is indistinguishable...") that could be trimmed or offloaded. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the 'noticeably verbose; several padded sections' anchor, since the redundancy mostly adds reader- or phase-specific context rather than pure padding.

3 / 5

Actionability

Guidance is copy-paste ready: the literal return-contract text to append to every agent prompt, a per-agent write-path table, the [season-slug] naming rule (lowercase, spaces → hyphens), the exact usage-error blockquote, exact ETHICS FLAG/BLOCKED verdict strings, and the exact Phase 0 bash command. Not below 5 because the common cases (valid run, missing argument, blocked ethics, missing artifact) are all covered with specific executable wording.

5 / 5

Workflow Clarity

Seven phases are explicitly sequenced with parallelism gates ("Phases 3 and 4 can run simultaneously", Phase 5 "Start only after both Phase 3 and Phase 4 results are collected"), decision checkpoints via AskUserQuestion at each transition, and an artifact-verification step ("a named artifact that is not on disk is a failed phase, however fluent the response reads"). The error-recovery and ethics-review sections provide full feedback loops (resume naming the unmet contract; revise / override with rationale / cancel with re-spawn), matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the external doc references (.claude/docs/automation-modes.md, error-recovery-protocol.md, design/live-ops/economy-rules.md, ethics-policy.md) are clearly signaled and one level deep — but the SKILL.md is a ~230-line monolith that inlines substantial policy argumentation (the threefold write-exception rationale, the team.size collapse philosophy) that would live better in a referenced doc. Fits 'some structure but could be better organized; content that should be separate is inline' more than the 'good structure; most content appropriately placed' anchor, given how much policy prose occupies the main file.

3 / 5

Total

16

/

20

Passed

Description

53%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.

The description is third-person, concise, and clearly identifies the domain and team composition, with a distinct live-ops niche. Its main weakness is the absence of any explicit 'Use when...' trigger guidance and the lack of concrete action or deliverable language beyond the single verb "orchestrate". Adding a trigger clause and naming 2-3 concrete outputs would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to plan a season, live event, or in-game event cadence, or mentions live ops / battle pass planning."

Replace or supplement the agent roster with concrete deliverables, e.g. "produces the season brief, battle-pass economy design, success metrics plan, and communication calendar" — this covers both specificity and the 'what'.

Include natural synonyms users would actually say — "live operations", "in-game event", "seasonal content" — to improve trigger term coverage.

DimensionReasoningScore

Specificity

"Orchestrate the live-ops team ... for a season or live event" names the domain and one concrete action, and the em-dash roster of five roles adds concrete detail, but no further specific actions (planning cadence, economy tables, analytics, comms) are stated. Not 4 because the description does not list several specific actions; not 2 because the domain and team composition are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (orchestrate the named team to produce a season/live-event plan), but there is no 'Use when...' clause or equivalent explicit trigger guidance; "for a season or live event" only weakly implies when. Per the judging guidelines a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

"live-ops", "season", "live event" are natural keywords a user might say, but common variations and synonyms ("live operations", "in-game event", "battle pass", "seasonal content") are missing. Fits the 'some relevant keywords but missing common variations' anchor rather than the 'good keyword coverage' anchor.

3 / 5

Distinctiveness Conflict Risk

"live-ops team ... for a season or live event" carves a distinct niche (game live-ops seasonal planning) with clear differentiators from generic planning skills. Not 5 because within a game-development skill suite it could overlap with closely related team orchestrators (e.g. team-release, team-narrative) whose names also respond to 'season' requests.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/team-live-ops/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.