CtrlK
BlogDocsLog inGet started
Tessl Logo

goal-flourishing

目标繁荣规划,为用户规划深度心流和高质量连接时段

56

Quality

64%

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/goal-flourishing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is lean, well-structured, and gives a concrete JSON output format with specific parameters and examples for both session types. Its main gap is the absence of a verification step tying generated plans back to the stated principles.

DimensionReasoningScore

Conciseness

The body is compact and does not explain concepts Claude already knows; ritual examples like "关闭通知、播放白噪音、深呼吸3次" are concrete rather than padded. It is efficient with only minor trimmable phrasing, fitting the 4 anchor rather than 5 (a few role/framing lines could be tighter).

4 / 5

Actionability

It provides a concrete, copy-paste-ready JSON output schema with fields (description, estimated_time, difficulty, type) plus specific time ranges (90-120 / 60-90 min) and ritual examples. It is mostly executable guidance with minor gaps (the [Deep Work Theme]/[Ritual] placeholders are templates), matching 4 rather than 5.

4 / 5

Workflow Clarity

This is a simple single-purpose skill (produce a session-plan JSON) whose single action is unambiguous, with constraints listed in 注意事项. It earns 4 rather than 5 because there is no verification that the generated sessions actually satisfy the stated principles (保护注意力, 仪式感).

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no need for external references, and is well-organized into clear sections (核心原则, 输出格式, 设计原则 with Deep Flow/Connection subsections, 注意事项). Per the simple-skill exception this qualifies for 5 with well-organized sections and no bundle files.

5 / 5

Total

17

/

20

Passed

Description

50%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 states a clear purpose with two concrete session types but lacks any explicit trigger/usage guidance, capping completeness. It is concise and uses third-person voice, yet keyword coverage and distinctiveness are only moderate.

Suggestions

Add an explicit 'Use when...' clause in the description, e.g. 'Use when the user wants to plan deep-work or meaningful-connection time blocks.'

Include natural trigger synonyms users might say (e.g. '深度工作', '心流时间', '专注时段', '陪伴/连接时间') to improve trigger-term coverage.

Sharpen the niche framing to reduce overlap with generic planning/scheduling skills.

DimensionReasoningScore

Specificity

The description names the domain ("目标繁荣规划") and 1-2 concrete actions ("规划深度心流和高质量连接时段"), but coverage is not comprehensive — only two session types are named. It fits the 'names domain and 1-2 concrete actions' anchor, not 4 which requires several specific actions.

3 / 5

Completeness

There is a clear 'what' ("规划深度心流和高质量连接时段") but no 'when' — no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the guidelines. It is above 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

Relevant keywords like "深度心流" and "高质量连接" are present, but there are no common variations, synonyms, or natural phrasings a user would casually say. It matches 'some relevant keywords but missing common variations or synonyms', not 4 which needs fuller coverage.

3 / 5

Distinctiveness Conflict Risk

"目标繁荣规划" with deep-flow/connection framing is a somewhat specific niche, but as a generic planning/scheduling skill it could overlap with other time-management skills. It fits 'somewhat specific but could still overlap with similar skills', not 4 which requires mostly distinct triggers.

3 / 5

Total

12

/

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.

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