CtrlK
BlogDocsLog inGet started
Tessl Logo

opencreator-runtime

OpenCreator 内部 Creator Agent 的稳定运行规则,仅由应用自动安装和激活。

55

Quality

61%

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 ./apps/daemon/runtime/opencreator-runtime/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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 exceptionally lean and highly actionable, with concrete tool names, parameter structures, and explicit validation/feedback loops for async runs and revision conflicts. Its only weakness is organization: a flat bullet list rather than grouped sections or an explicit numbered workflow.

DimensionReasoningScore

Conciseness

The body is a lean bullet list with no padding and no explanation of concepts Claude already knows; every bullet states a concrete rule with tool names and parameter shapes, so every token earns its place.

5 / 5

Actionability

Guidance is fully executable: exact tool names (creator_get_context, creator_apply_action, creator_wait_for_stage) and copy-paste-ready input structures (input: { patch: {...}, objectId? }, input: { stageId: "..." }) with named fields (expectedRevision, idempotencyKey, commandReceipt.stageRunId) cover the common cases.

5 / 5

Workflow Clarity

A clear sequence is present (get context → apply action with revision/idempotency → wait for terminal state) with explicit validation checkpoints (re-read context on param error and retry; retry once on revision conflict then escalate to user; only conclude after a terminal state). Not a 5 because the steps are scattered across a flat bullet list rather than presented as a single explicit numbered sequence with a checklist.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external bundle files (none exist), so it qualifies for the simple-skill exception; content is appropriately self-contained. Not a 5 because it is a flat bullet list under a single heading with no section grouping (e.g., context / actions / async / safety), a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

32%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 identifies a specific internal niche but is too abstract to convey concrete capabilities or natural trigger phrases, and it lacks an explicit 'Use when...' clause. It is distinguishable but weak on completeness and trigger-term quality.

Suggestions

Add 1-2 concrete capabilities the runtime governs (e.g., 'reads Creator Context, applies actions via creator_apply_action, waits on async stage runs') instead of the abstract phrase '稳定运行规则'.

Include an explicit trigger/activation clause, e.g. 'Use when operating as the Creator Agent inside OpenCreator...' to satisfy the 'when' requirement.

Add natural synonyms users (or the host app) would reference (e.g., 'Creator Tool', 'KrillinAI jobs', 'stage runs') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('OpenCreator 内部 Creator Agent 的稳定运行规则') but the only 'action' is the abstract noun '运行规则' (runtime rules) — no concrete actions are listed, matching the 'names the domain but actions are minimal or generic' anchor; not a 1 because it does identify a specific domain, and not a 3 because no concrete capabilities are enumerated.

2 / 5

Completeness

It gives a vague 'what' (stable runtime rules) and a weak 'when' ('仅由应用自动安装和激活' — auto-activated by the app), but no explicit 'Use when...' trigger guidance, which the rubric caps at 3; it lands at 2 because both the what and the when are only weakly present rather than clearly stated.

2 / 5

Trigger Term Quality

It uses internal/technical jargon ('OpenCreator', 'Creator Agent', '稳定运行规则', '自动安装和激活') with no natural user-facing trigger phrases; one or two domain keywords exist but the natural phrases a user would say are missing, so it sits just above the pure-jargon floor.

2 / 5

Distinctiveness Conflict Risk

It is tied to a clearly named internal niche ('OpenCreator Creator Agent') with low overlap risk against generic skills; not a 5 because the short, abstract phrasing leaves minor overlap risk with adjacent OpenCreator-related skills.

4 / 5

Total

10

/

20

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
krillinai/OpenCreator
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.