CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

future-self-lite

引导学习者完成给未来的自己留言的 Python 函数。

Quality

74%

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 ./examples/pbl/future-self-lite/skills/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 an exceptionally lean, well-sequenced instruction set that delegates all heavy content to the environment (read_next_skill, docs/brief.md, platform records) — appropriate progressive disclosure for a simple orchestration skill. Its main weakness is that tool usage guidance stops short of parameters, examples, and error-handling behavior.

DimensionReasoningScore

Conciseness

The body is four lean lines (~90 tokens) with zero padding and no explanation of concepts Claude already knows — every line is a distinct actionable instruction (e.g. "通过 read_next_skill 获取当前教学小节"). Matches 'Lean and efficient; assumes Claude's competence; every token earns its place'; there is nothing to trim, so it is not 4.

5 / 5

Actionability

For an instruction-only skill, the guidance is concrete: named tool invocations ("read_next_skill", "request_skill_review"), a named spec file ("docs/brief.md"), and a defined flow including waiting for the learner's answer. Matches 'Mostly executable guidance; concrete code or commands with minor gaps'; not 5 because no parameters, example prompts, or failure handling are specified, and not 3 because the tool calls and file reference are directly executable rather than pseudocode-level hints.

4 / 5

Workflow Clarity

A clear four-step sequence is present: fetch section → check inputs/return values against the brief → ask and wait for the learner's answer before confirming → report status from platform build/eval records, with explicit checkpoints ("核对输入和返回值", "等学习者回答后再确认理解"). Matches 'Clear sequence with most checkpoints present; minor validation gaps'; not 5 because there is no guidance on handling wrong answers or looping to the next section, and not 3 because validation checkpoints are explicit rather than missing.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files, and detail is appropriately delegated one level deep: section content comes from read_next_skill and specifications from the clearly signaled "docs/brief.md". Per the simple-skill guideline this earns the top anchor; the reference is well signaled and no content that belongs elsewhere is inlined, so it is not 4.

5 / 5

Total

18

/

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 clearly states a single, specific capability but is entirely missing activation guidance and natural trigger phrases, capping every dimension at the middle anchor. It reads as a bare 'what' statement rather than a complete skill description.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the learner is working on the 给未来的自己留言 (message-to-future-self) Python exercise or asks for guidance on this task' — this would raise completeness above 3.

Include natural synonyms users would actually say (Python 练习, 编程教学, tutorial, exercise) to broaden trigger term coverage beyond the current single phrasing.

Mention the distinctive flow (section-by-section guidance, Q&A review, build/eval status feedback) to differentiate it from other tutoring skills and reduce conflict risk.

DimensionReasoningScore

Specificity

The description names the domain and target concretely ("给未来的自己留言的 Python 函数" — a specific exercise) and one action ("引导学习者完成"), but lists no further capabilities. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; it is above score 2 because the exercise is specifically identified rather than generic, and below score 4 because only a single action is given.

3 / 5

Completeness

The 'what' is clear (guide a learner through completing a specific Python function), but there is no 'when' — no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Matches anchor 'Has a clear what but when is missing or only weakly implied'; not 4 because nothing indicates when this skill should activate.

3 / 5

Trigger Term Quality

It includes some relevant natural keywords ("Python", "函数", "学习者", "给未来的自己留言") but misses common variations and synonyms a user might say (练习/exercise, 教学/teaching, 编程任务, tutorial). Fits 'Some relevant keywords but missing common variations or synonyms'; below 4 due to thin synonym coverage, above 2 because the terms present are natural rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

The named exercise ("给未来的自己留言的 Python 函数") is distinctive, but the framing "引导学习者" (guide learners) is generic tutoring language that would overlap with any other teaching or guided-exercise skill. Fits 'Somewhat specific but could still overlap with similar skills'; below 4 because without trigger guidance similar instructional skills are hard to distinguish from it.

3 / 5

Total

12

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

THU-MAIC/OpenMAIC

Path

examples/pbl/future-self-lite/skills/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.