Install any skill in seconds. Free to start, no credit card required.
Get Started Free →catlog22/maestro-spec
Intent-driven spec precipitation — state a constraint in natural language (加一条规范:禁止用 any / 记录架构约束:服务间走 gRPC / 质量规则:覆盖率≥80%) and the workflow infers the category and records a <spec-entry>. Spec = 项目约束规则(编码规范、架构约束、质量标准);可复用知识文档走 /maestro-knowhow capture。
Passed 5 of 11 test cases with the skill, and 4 of 11 without it.
and 5 more in the full report
5 fixed4 passed either way10 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am recording an architectural rule requiring HMAC signature verification on all webhooks. Before loading the spec workflow file, should I spawn a new Maestro session or start a background execution run? I want to ensure the environment is initialized properly.
| Checked | Without skill | With skill |
|---|---|---|
| Reads and follows the execution workflow document directly. | Missed | Passed |
| Refrains from creating a new session or run context just to load the workflow. | Missed | Passed |
The instructions your model reads when the skill loads.
Categories: coding · arch · quality · debug · test · review · learning · ui
Scopes: project (default) · global · team · personal
Pass the full $ARGUMENTS to the workflow as its intent (the add keyword is implied). The workflow infers category, scope, and content, then appends the entry.
test cases passed, vs 4 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.