Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

goal-flourishing

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/goal-flourishing/SKILL.md

Quality

Content

72%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 lean, well-organized instruction-only skill with a concrete JSON output template and specific durations/rituals, so actionability and conciseness are solid. Its main weakness is workflow clarity: it never sequences how to produce the output (input gathering, mode selection, verification), leaving the operator to improvise.

Suggestions

Add a short step sequence for producing the plan (gather the user's available time and goals, choose Deep Flow vs. Connection, emit the JSON, then check it against the template) to improve workflow clarity.

Include one fully worked example of the output JSON with realistic values instead of only '[Deep Work Theme] - [Ritual]' placeholders, and clarify when to pick each mode.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding and no explanation of concepts Claude already knows; the only slack is the unexplained '[L2: Flourishing]' hierarchy framing in the role line. Not 5 because that framing token does not earn its place; not 3 because there is no real over-explanation to tighten.	4 / 5
Actionability	The JSON output template is concrete ('Session 1: [Deep Work Theme] - [Ritual]', '90min', 'session') along with explicit durations and ritual examples ('关闭通知、播放白噪音、深呼吸3次'). Not 5 because the placeholders are pseudocode-like with no full worked example and no guidance on session count or mode selection; not 3 because the guidance is far more concrete than high-level hints.	4 / 5
Workflow Clarity	Design considerations and the output format are presented, but there is no operational sequence for producing the output — no steps for gathering the user's time/goals, choosing Deep Flow vs. Connection, or verifying the JSON matches the format. Not 4 because sequence and checkpoints are absent rather than minor gaps; not 2 because the structure is coherent, not a rough broken sequence.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files and no content that belongs in separate files; sections (设计原则, 注意事项) are well-organized. Per the simple-skills scoring note, this earns a 5.	5 / 5
	Total	16 / 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 'what' in a fairly distinctive niche, but reads more like a title than a capability description: the action is generic, trigger terms include invented jargon, and the 'when' is entirely missing. It sits at the midpoint of the scale with clear, actionable gaps.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., when the user wants to plan focus sessions, deep-work blocks, or meaningful connection time), which would raise completeness.

Replace the invented term '目标繁荣' with natural user phrasing and include synonyms users would actually say (deep work, focus time, flow, quality time) to improve trigger-term quality.

Enumerate 2-3 concrete actions instead of the single generic verb '规划' (e.g., structures large time blocks, defines entry rituals, outputs a session plan in JSON) to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain ('目标繁荣规划') and 1-2 concrete objects of the action ('规划深度心流和高质量连接时段'), but the only action verb is the generic '规划' (plan) and coverage is thin. It exceeds a bare domain label (score 2) but does not list several specific actions (score 4).	3 / 5
Completeness	The 'what' is stated (plan deep-flow and connection time blocks), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Score 4 would require a present-but-imperfect 'when'; score 2 would require a vague 'what'.	3 / 5
Trigger Term Quality	'深度心流' (deep flow) and '高质量连接' (connection) are somewhat natural phrases, but '目标繁荣' (goal flourishing) is invented jargon users would not say, and no synonyms or variations appear. Keyword coverage exists but has clear gaps, fitting anchor 3.	3 / 5
Distinctiveness Conflict Risk	The flow/connection-session niche is fairly specific, but '规划时段' (planning time slots) overlaps broadly with general scheduling and time-management skills, so it could trigger for the wrong skill. Overlap risk is more than minor (not 4) but the skill is not a catch-all (not 2).	3 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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/goal-flourishing/SKILL.md
Revision: 61ead80

Reviewed: 23 hours ago

Discovery Implementation Validation

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.

goal-flourishing

Table of Contents

Is this your skill?