CtrlK
BlogDocsLog inGet started
Tessl Logo

roleplay-mode-implementation

规划、实现或重构角色扮演模式(默认上帝视角下的单角色接管)时使用。适用于一期文本决策、二期统一有限选择框架、三期依附 Conversation 动作的自由对话,以及对应的 runtime/API/frontend/test 收口。

71

Quality

86%

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

87%

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

A well-structured, highly actionable skill body with concrete file paths, commands, and per-phase checklists. The main gap is workflow_clarity: validation is suggested rather than enforced as a gated feedback loop.

Suggestions

Promote the test commands from "建议至少运行" to an explicit gated step: run, and if any fail, fix and re-run before considering the change done.

Tie each phase checklist to a hard checkpoint (e.g. "通过以下三项后再进入下一阶段") so the validation loop is explicit rather than implied.

Add a short rollback/revert note for runtime semantic changes (load/reinit/reset) given the "扮演态不进存档" constraint.

DimensionReasoningScore

Conciseness

Lean bullet structure with no explanation of concepts Claude already knows; every section (心智/工作流/检查清单/约束) earns its place, and checklist questions reinforce rather than restate principles.

3 / 3

Actionability

Provides exact entry-point file paths (e.g. src/server/runtime/session.py, web/src/stores/roleplay.ts) and concrete verification commands (pytest ..., npm run type-check, npm run test) — copy-paste ready.

3 / 3

Workflow Clarity

The sequence (先看锚点文档 → 看落点 → 判断层级) and per-phase checklists are clear, but verification is framed softly ("建议至少运行") with no explicit validate→fix→retry feedback loop or hard gate before proceeding.

2 / 3

Progressive Disclosure

Overview body points to clearly signaled one-level-deep detail docs (docs/specs/avatar-roleplay-mode.md, single-choice-unified-framework.md, .cursor/rules/roleplay-mode.mdc) under "优先查看", keeping the SKILL.md a navigable index rather than a monolith.

3 / 3

Total

11

/

12

Passed

Description

85%

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 specific, well-scoped description that clearly states both capability and an explicit use-when trigger. Its only weak spot is trigger-term quality: the natural phrasing is concentrated in the first clause while the rest leans on internal phase jargon.

Suggestions

Lead with natural user phrasing such as "角色扮演 / roleplay 模式" and add common variations (e.g. "玩家接管角色", "对话扮演") before the phase jargon.

Soften or parenthesize the 一期/二期/三期 framing so a user who does not know the phase numbering still matches on plain "角色扮演模式" triggers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "规划、实现或重构" roleplay mode — plus three concrete phase scopes (text decisions, unified limited-choice framework, Conversation-attached free dialogue) and runtime/API/frontend/test收口.

3 / 3

Completeness

Explicitly answers both: what (the three phases plus收口 scope) and when ("...时使用" = "use when planning/implementing/refactoring roleplay mode").

3 / 3

Trigger Term Quality

The opening "角色扮演模式" with 规划/实现/重构 is a natural trigger, but the bulk is technical phase jargon (一期/二期/三期, 统一有限选择框架, Conversation动作) a user would rarely say verbatim, and common variations are missing.

2 / 3

Distinctiveness Conflict Risk

Narrow niche — god-view single-role takeover roleplay mode scoped to this codebase's three-phase architecture — unlikely to trigger for unrelated skills.

3 / 3

Total

11

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
4thfever/cultivation-world-simulator
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.