CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

guardian-retrospective

Guardian 复盘分析,检测偏差信号和行为模式

Quality

77%

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 ./skills/guardian-retrospective/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a model of token-efficient, actionable instruction: concrete inputs, a named analysis checklist, a complete JSON output contract, and explicit quality thresholds. Its only real weakness is a few under-specified output attributes (severity criteria, derivation of preferred_time and success_rate).

DimensionReasoningScore

Conciseness

The body contains no explanations of concepts Claude already knows and no padding; every section (task, input template, four analysis requirements, output schema, thresholds) carries task-specific information. This matches the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It provides a concrete input template, four named analyses, a complete copy-paste JSON output schema with example values, and explicit filtering thresholds (confidence < 0.5, samples >= 3). It falls short of 5 because severity assignment criteria and how preferred_time/success_rate should be derived are left implicit — minor gaps rather than missing key steps.

4 / 5

Workflow Clarity

This is a single-purpose, non-destructive analysis skill with an unambiguous flow: consume the three inputs, perform the four listed analyses, emit the constrained JSON. The 注意 section acts as explicit output-quality checkpoints (confidence and sample-size gates), matching the simple-skill exception for a clear, well-organized single action.

5 / 5

Progressive Disclosure

There are no bundle files and none are needed; the body is compact and cleanly sectioned (任务, 输入, 分析要求, 输出格式, 注意) with no content that belongs in separate files. Per the guidelines, a short self-contained skill with well-organized sections scores 5.

5 / 5

Total

19

/

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 communicates a clear what but is too terse to be a strong trigger: it lacks any 'when to use' guidance and provides only two of the skill's several capabilities, with no keyword variations. It is distinct thanks to the Guardian/复盘 niche yet under-specified for reliable skill selection.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks for a Guardian retrospective, review of deviation signals, or behavioral pattern analysis from event logs.'

Enumerate the main capabilities to raise specificity, e.g., add task success-rate statistics, best execution window analysis, and daily/weekly time pattern detection.

Include natural keyword variations such as 复盘/回顾/总结 and 偏差检测/偏差分析 so common user phrasings match.

DimensionReasoningScore

Specificity

The description names its domain ("Guardian 复盘分析") and two concrete actions ("检测偏差信号" and "行为模式"), matching the anchor for domain plus 1-2 concrete actions. It is not 4 because it omits several capabilities the body actually defines (task success rates, best execution windows, daily/weekly time patterns).

3 / 5

Completeness

The 'what' is clearly stated (retrospective analysis detecting deviation signals and behavior patterns), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"复盘", "偏差信号", and "行为模式" are natural, relevant terms a user might say, but there are no synonyms or variations (e.g., 回顾, 总结, 偏差分析, 行为分析), fitting the 'some relevant keywords but missing common variations' anchor. It is above 2 because the keywords are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

The "Guardian 复盘" niche is clearly bounded and unlikely to trigger for unrelated skills, matching the 'mostly distinct; minor overlap risk' anchor. It is not 5 because "行为模式" (behavior patterns) is broad enough to overlap with other behavioral-analysis skills absent any explicit trigger scoping.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

ooooooooooooooooooop/ai_life_os

Path

skills/guardian-retrospective/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.