CtrlK
BlogDocsLog inGet started
Tessl Logo

team-live-ops

Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.

63

Quality

76%

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

85%

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

The body is a well-structured, actionable orchestration pipeline with clear validation checkpoints and error feedback loops; the only meaningful weakness is mild verbosity in the ethics and error-recovery sections.

Suggestions

Tighten the Phase 7 ethics-review and Error Recovery Protocol blocks by collapsing the long inline flag strings into concise rules, moving the full flag wording to a reference if the skill grows.

Consider extracting the per-phase delegation details (subagent_type + output) into a short reference table to reduce repeated role listings across Team Composition and How to Delegate.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but the lengthy ethics-review and error-recovery sections could be tightened; some phrasing is more detailed than strictly necessary.

2 / 3

Actionability

Provides concrete, executable guidance: explicit subagent_type mappings, specific file paths (e.g., design/live-ops/economy-rules.md, ethics-policy.md), named output documents, and exact AskUserQuestion options — copy-ready despite being instruction-only.

3 / 3

Workflow Clarity

A clearly sequenced 7-phase pipeline with explicit validation checkpoints (ethics review gate, BLOCKED verdict handling) and a feedback-loop error-recovery protocol that surfaces, assesses, and offers retry/skip options.

3 / 3

Progressive Disclosure

No bundle files are present, so the single SKILL.md carries well-organized, clearly headed sections (Team Composition, Pipeline, Output Documents, Error Recovery) — appropriate for a skill that needs no external references.

3 / 3

Total

11

/

12

Passed

Description

67%

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 specific and clearly distinguishes the skill's niche, but it omits an explicit 'Use when...' trigger and could include more natural user phrasings to improve discoverability.

Suggestions

Add an explicit 'Use when...' clause naming the natural situations that trigger this skill (e.g., planning a season, scheduling a live event, or designing a battle pass).

Surface common user-facing terms such as 'live ops', 'battle pass', and 'season pass' to broaden trigger coverage.

Keep the role list but consider leading with the user-facing outcome ('plan a season, event, or live content update') before the internal team composition.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('coordinates' six named roles 'to design and plan a season, event, or live content update'), naming the domain and several specific activities rather than vague language.

3 / 3

Completeness

Clearly answers 'what' the skill does, but lacks an explicit 'Use when...' trigger clause; per the judging guideline, a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant natural terms ('season', 'event', 'live content update', 'post-launch content planning') but misses common user phrasings like 'live ops' or 'battle pass', so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (live-ops team orchestration with named sub-roles) with distinct triggers unlikely to be confused with other skills.

3 / 3

Total

10

/

12

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.

Validation14 / 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
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.