SKILLEMALL.ai

BD amemo-skill

amemo-skill 统一调度中心,专为 AI 工具链接麦小记 APP 而开发的技能包,专注于笔记、清单和健康数据的管理。 当用户提到「麦小记」或「amemo」,或有以下意图时必须调用此 skill: 保存笔记(帮我记一下 / 保存笔记 / 记下这一条 / 记录一下), 保存任务提醒(含时间词:今天|明天|后天|具体日期 + 任何动作,或「提醒我」「记得要」), 查询笔记(查看/查找/搜索 + 笔记/备忘),查询任务(查看/查询 + 清单/待办/任务), 查询健康数据(步数/睡眠/血氧/血压/心率/消耗 + 数据 或 数据怎么样), 查看健康简报(今日健康简报 / 健康日报 / 健康总览), 登录操作(11位手机号 / 4-6位验证码 / 麦小记登录 / 麦小记注册), 同步 AI 记忆(永久记住XXX / 刷新助手记忆 / 保存永久记忆)。

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 2 files body ≈ 2 045 tokens Open the sourcegithub.com analyzed 2 d ago

amemo-skill 统一调度中心,专为 AI 工具链接麦小记 APP 而开发的技能包,专注于笔记、清单和健康数据的管理。 当用户提到「麦小记」或「amemo」,或有以下意图时必须调用此 skill: 保存笔记(帮我记一下 / 保存笔记 / 记下这一条 / 记录一下),…

As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 43/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 11 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 44 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2045 tokens
  • low 10 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 377: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 44 items
  • +4Has examples (9 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.